WordPress editing after handoff
Let Clients and AI Update Content While Preserving the Page Structure
After launch, clients need to update text and images. Agencies need the agreed sections and their order to remain intact in both Gutenberg and AI-assisted editing.
How it works Agent Composer lets the agency define editable fields, protected sections, and areas for additional blocks. WordPress checks changes against these rules. Separately, user permissions control which operations an AI agent may request through MCP. Shared templates can later change through reviewed migrations that preserve compatible page-specific content.
After handoff
Content updates can accidentally change the layout
The agency needs to allow routine editing, prevent unintended structural changes, and retain a way to update shared layouts later.
Client editing
A text update can also move or delete a section
Without suitable restrictions, an editor can move, remove, or replace structural blocks while updating content. The agency then has to restore the layout.
AI-assisted editing
Model instructions do not check the saved page
A system prompt can describe the required structure. The model still interprets those instructions, so WordPress needs a separate check before accepting the change.
Later redesigns
A protected layout still needs a way to change
Agencies may need to reorder shared sections or revise a page type. Those changes should preserve compatible text, images, and other values entered on individual pages.
What the agency needs Content editing within defined limits, with a reviewed process for changing the shared structure.
Editing and approval
Check access and page structure separately
The AI agent acts on behalf of the signed-in user. Their permissions determine which operations are available; structural rules determine whether the resulting page is accepted.
PAGE SETUP Page blueprint + synced patterns → shared structure Structure rules → protected sections, named fields, allowed insertion areas Page-specific values → individual text and images CONTENT EDITING Gutenberg editor or AI agent acting for a signed-in user MCP access: user group or role + OAuth permissions + Composer permissions Allowed change → whole-page validation → draft or update proposal Human review → publication SHARED TEMPLATE UPDATE New blueprint or pattern version → migration plan Preserve compatible page values → flag conflicts Separate migration proposal → human review
WordPress-side checks For managed pages, Composer code locates the declared field or insertion area, applies the requested change, and validates the complete result. This structural rule set is called a Structure Contract.
Agency configuration
Define editing rules before handing over the site
Plan both routine client updates and later changes to the shared templates.
- Identify the shared sections and editable fields — Give sections and content fields stable names. Define required blocks, their order, image fields, and where extra blocks may be inserted.
- Set the limits for client editing — Allow changes to selected text and images and to clients’ own blocks in permitted areas. Keep protected sections and their order subject to the structural rules.
- Tie AI access to the signed-in user — For authenticated MCP access, the user’s group or role, OAuth permissions, and Composer permissions must all allow the requested operation. Connecting an AI tool does not itself grant administrator access.
- Review changes to shared templates — Plan a migration from the exact existing version. Preserve compatible page-specific values, flag conflicts, and prepare separate proposals for review before published pages change.
When are structural rules useful?
Useful for client sites
When clients edit content within an agreed layout
- Clients need to update content without accidentally moving or deleting required sections.
- AI tools must work within the signed-in user’s permissions and the managed page’s structural rules.
- The agency expects to change shared templates later while preserving compatible page-specific content.
A simpler setup may suffice
When structural restrictions are unnecessary
- The site has few pages and the original developer reviews every change.
- Clients intentionally have full control over the layout, with no requirement to preserve a shared page structure.
- AI only creates prototypes or drafts outside the site’s managed editing process.
Practical questions
Editing permissions and later template changes
How does this relate to Gutenberg block locking?
Block locking restricts operations such as moving or removing blocks. A Structure Contract also defines named editable fields, protected sections, and allowed insertion areas, then checks the whole managed page. Versioned page blueprints support a separate migration process.
What does the WordPress check add to model instructions?
Instructions describe what the AI should do. Composer code checks the requested change against the declared fields and structure, and rejects a result that breaks those rules.
Can an MCP-connected agent do everything the WordPress user can do?
No. The user’s group or role, OAuth permissions, and Composer permissions must all allow the operation. An MCP connection does not automatically make unrelated WordPress administration available.
Can the agency change templates after clients have edited pages?
Yes, for managed page types set up for migration. The plan uses the exact published version, preserves compatible page-specific values, and flags conflicts or changes that no longer match the shared structure. Separate proposals can then be reviewed before publication.
WP Suite Agent Composer
See how controlled content editing works
Explore the editing rules, access permissions, and review process available for client sites.