AI-assisted WordPress editing with clear rules
Create and update content with AI while preserving your site’s design.
Agent Composer lets compatible AI tools create Gutenberg drafts and propose changes to published pages. You define the content types, named content sections, and blocks they may edit. The same structural rules protect content in the WordPress editor, while people retain the final publication and approval decisions.
Design and content
Keep the page structure consistent as content changes
Define the order and editing rules for clearly named sections such as the introduction, benefits, or customer story. Editors and AI tools can update the permitted content while the site’s structure stays protected.
Review and approval
New content is saved as a draft. Changes to published content become a separate update proposal that an editor can approve, return for revision, or reject.
Try it before installing it
Launch a complete WordPress sandbox in your browser.
Connect your AI tool to a temporary WordPress site, let it read the site’s content rules, and review the Gutenberg draft it creates.
Built for the work after launch
Keep client websites consistent after handoff
Give clients room to create and maintain useful content without repeatedly rebuilding layouts or granting unrestricted administration access.
01
Preserve the agency’s design system
Map recurring content types to approved templates, patterns, blocks, fields, media rules, and layout constraints. Clearly named content sections keep each page’s text identifiable when the shared structure changes. See the guide to AI page creation within a design system.
02
Give clients a safer CMS handoff
Clients can request case studies, solution pages, landing pages, and posts within the site’s rules. Structural protection also applies to human editors, including which sections they may change and where they may add blocks. The client handoff guide covers this operating model after launch.
03
Keep private WordPress private
Connect through authenticated MCP, directly or through an optional outbound tunnel for a local or firewall-protected WordPress site. With Cognito authentication, group membership, OAuth permissions, and Composer rules jointly limit available actions. The least-privilege MCP guide explains these permissions; the MCP comparison helps decide when broader site authority is actually justified.
04
Keep published changes reviewable
For published content, an agent can prepare a separate update proposal instead of overwriting the live item. Editors can review it, request changes, reject it, or merge an approved proposal back into the original content.
Core capabilities
Use existing content, preserve structure, and review every proposed change
Reuse approved Media Library assets
Find existing images, preserve useful captions and alt text, place them in approved layouts, and assign an existing featured image without giving the agent general upload or deletion access.
Work with structured content and relations
Fill approved structured fields, search permitted relation targets, and connect related records through the site’s registered providers instead of flattening everything into page copy.
Validate the complete page
Check the content type, required sections, permitted blocks, headings, excerpt, SEO description, and saved markup. When a shared structure changes, preserve compatible page content and review migration proposals for changes that need approval.
Connected language versions
Create drafts in multiple languages, connect new drafts to existing translation groups, and prepare separate update proposals for published translations. Composer keeps the language relationships with the WordPress content; people review each version before publication.
End-to-end workflow
Create a draft or propose a change, then review it in WordPress
The site builder defines the design and content rules. AI tools create new drafts or separate proposals for published content. Human editors work within the protected structure and decide what to publish or merge.
Site setup: theme, patterns, content types, and editing rules. New content: AI request → Composer checks → WordPress draft → human review → publication. Published content: AI request → Composer checks → update proposal → review → approve, return, or reject. Shared structure changes: compare affected pages → preserve compatible content → review migration proposals. Optional static publishing follows the approved WordPress content.
WordPress stores the configuration, drafts, proposals, metadata, media assignments, relations, and validation results. Revision and checksum checks stop stale agent work from silently overwriting newer edits. Clearly named content sections help preserve each page’s content when a shared structure changes. Agent Canvas, Static Publisher, and Static Site Guardian are optional parts of the wider workflow.
Common questions
Design, permissions, and publication
Does Composer require Agent Canvas or a particular theme?
No. Composer can work with an existing compatible WordPress site when its content types, templates, patterns, blocks, and rules are represented by the active configuration. Agent Canvas is an optional first-party theme.
Can Composer use the Media Library and structured relationships?
Yes, within the active Blueprint. It can search and place approved existing images, assign an existing featured image, fill supported structured fields, and search permitted relation targets. Optional remote image ingestion must be enabled for exact HTTPS hosts by an administrator.
How is remote access controlled?
With Cognito authentication, the caller’s group membership, OAuth permissions, and Composer permissions must all allow an action. A compatible client can connect directly through authenticated MCP or use an optional outbound tunnel for a local or firewall-protected site.
Can the agent publish to WordPress or production?
No. Composer does not give the agent direct WordPress publication authority. New content remains a governed draft. For existing published content, the agent can prepare an update proposal that a human reviewer may merge, return with comments for revision, or reject. Rejected proposals can later be reopened by an authorized user; publication and final production release remain human-controlled.
Content maintenance after launch
Set the rules once and keep improving the content.
Define what clients and AI tools may edit, preserve the approved page structure, and review drafts and update proposals in WordPress. When the design needs a larger change, retain compatible page content and approve the required migration.
Need hands-on help mapping an existing design system and content model? Explore Agent Composer professional services on AWS Marketplace.