SEO suites · 7 modules
WordPress SEO Plugin MCP that reads the page before writing metadata.
A WordPress SEO plugin MCP works through the SEO plugin that already renders the site's titles, descriptions, canonicals and schema. The agent reads the visible page and the stored metadata, proposes a change a person can check, and the plugin keeps rendering the output.
What goes wrong without a plugin-aware module
- Metadata generated without reading the visible page
- Structured data that does not match visible facts
- Redirects created without checking chains, loops, canonicals, or internal links
Why it matters
What plugin-aware changes for seo suites
SEO plugins store metadata and use WordPress hooks to render titles, descriptions, canonicals, robots directives and schema. Write descriptions and structured data from visible, verified facts. A saved field is not proof of the rendered tag, indexing or a ranking improvement.
A first safe workflow
Use supplied Search Console evidence and business importance to choose one page with a specific problem. Read its visible content and rendered tags, propose a bounded title/description diff and review it before writing. If search data is absent, report that gap. Measure changes over time without assuming the metadata caused them.
How to tell it worked
Read the rendered page source, not the plugin's own field. Confirm the canonical points where you expect, that any structured data describes something a visitor can actually see, and that new redirects do not extend a chain that already existed.
Worked example
Write meta descriptions for the guides that have none, without touching the pages that already rank.
Whichever SEO plugin the site runs: the bulk calls read and write Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, Slim SEO and SmartCrawl in one shape.
wppilot/seo-bulk-get-metaProLists the guides with missing_description set, from the active plugin. A filtered read inspects at most 1,000 posts and says so with truncated=true when there were more.
wppilot/get-page-snapshotFreeReads each page's digest, its block outline and SEO candidates included, so every description is written from what the page actually says.
wppilot/seo-bulk-update-metaProRuns first with dry_run=true and returns each post's before and after without writing. A field the plugin does not store fails that post rather than being skipped silently.
wppilot/seo-bulk-update-metaProRuns again with confirm=true once a person has read the plan. Results come back per post, and one failure never stops the rest.
wppilot/list-changesFreeShows one ledger row per written post. Rows for most plugins restore with wppilot/rollback-change; All in One SEO rows are marked irreversible because it keeps post SEO in its own table.
What to check yourself. View the rendered source of two or three of the pages and read the description tag there, not in the plugin's box. Then leave the batch alone long enough for Search Console to show whether anything changed before writing the next one.
Modules
7 modules compared
Each module loads only when its plugin is active. The Edition column shows how much of each one GoBuildWP Free covers; the rest needs Pro. Open a module for its full ability list, requirements and safety notes.
| Module | Edition | Abilities | Inspect / change / destructive | Covers |
|---|---|---|---|---|
 AIOSEO | Free 2 + Pro 10 | 12 | 6 / 5 / 1 | post SEO, term SEO, post schema, redirects |
 Rank Math | Free 2 + Pro 11 | 13 | 7 / 4 / 2 | post SEO, term SEO, post schema, redirects |
 SEOPress | Free 2 + Pro 14 | 16 | 9 / 6 / 1 | post SEO, term SEO, post schema, schema fields and templates |
 Yoast SEO | Free 2 + Pro 8 | 10 | 5 / 4 / 1 | post SEO, term SEO, redirects (Yoast SEO Premium), plugin settings (read-only) |
| The SEO Framework | Free 2 + Pro 1 | 3 | 2 / 1 / 0 | separator, title placement and default robots, what a post stores, what TSF prints in the head, per-post writes through TSF's API |
| Slim SEO | Free 2 + Pro 1 | 3 | 2 / 1 / 0 | title templates and enabled features, what a post stores, rendered title and description, writes to the slim_seo row |
| SmartCrawl | Free 2 + Pro 1 | 3 | 2 / 1 / 0 | enabled modules and post-type templates, what a post stores, rendered title, description and robots, up to three focus keywords |
Matching the SEO plugin to the job
Full SEO modules and lighter ones
The seven SEO plugins share the bulk metadata abilities, so a prompt that fills in missing descriptions works on any of them. Past that point they split into two groups. Yoast SEO, Rank Math, All in One SEO and SEOPress have full modules with post and term SEO, and depending on the plugin, schema and redirects. The SEO Framework, Slim SEO and SmartCrawl have lighter ones: a setup read, a read of what a post stores and what the plugin actually prints, and per-post writes.
Through these modules, site-wide settings are read, not written. Title separators, templates and global robots rules are reported so an agent can explain why a page renders as it does, and changed by a person in the plugin's screen. Some fields simply do not exist in a given plugin: The SEO Framework and Slim SEO have no focus keyword, Slim SEO has no nofollow or Open Graph text, and a bulk write naming one of those fails for that post instead of being dropped quietly.
What an SEO change costs to undo, plugin by plugin
Where the plugin stores its data decides whether the change ledger can put it back. If you write in bulk, this is worth knowing before the first confirm:
- Rank Math: post SEO and post schema restore from the ledger. Term SEO and the Rank Math redirect abilities' creates, updates and deletes do not, because Rank Math keeps redirects in its own table; trashed redirects stay restorable in Rank Math's own screen for a limited time.
- SEOPress: post SEO, schema rows and redirect creation or edits restore. Term edits and redirect deletions do not, and a redirect delete is a hard delete.
- Yoast SEO: per-post writes through the bulk abilities leave a ledger row per post. Redirects, a Premium feature, are irreversible.
- All in One SEO: it keeps post SEO, term SEO, schema and redirects in its own tables, so Pro writes there, bulk ones included, are recorded as irreversible. Note the old values before a large batch.
- The SEO Framework, Slim SEO and SmartCrawl: undo restores only that plugin's own keys for the post, so later content edits survive it.
Choosing where redirects live
Redirects can be kept by Rank Math, All in One SEO Pro, SEOPress Pro, Yoast SEO Premium or the separate Redirection plugin, and an agent can work with each of them. When GoBuildWP Pro adds a 301 because a published slug changed, it uses the first store available, with Redirection preferred when it is installed. On a free Yoast site with neither Redirection nor Rank Math, that falls back to WordPress's own old-slug handling, which misses pages and parent changes.
Run redirects-status before relying on automatic redirects; it reports which store is in use and whether the SEO plugin also watches slug changes itself, which is how a site ends up with two rules for one move. If your SEO plugin's redirects need a paid edition you do not have, Redirection is the simpler fix than switching suites. The redirects reference has the fields.
Schema: how much each plugin lets an agent change
If structured data is the main reason you are choosing a plugin, this is where the difference shows:
- All in One SEO can only switch a post's default graph on or off; its type follows the post type. Adding a recipe or FAQ graph is not an ability.
- Rank Math replaces a post's own schema with one primary entry of the chosen type, and needs its rich-snippet module on.
- SEOPress Pro stores manual schema and schema templates, which render only while its site-wide rich-snippets feature is on; the read reports whether it is.
- Yoast SEO, The SEO Framework, Slim SEO and SmartCrawl have no schema write here.
One SEO plugin per site
Running two SEO suites at once is a common inheritance on agency sites, and it leaves two plugins each holding their own idea of a page's title and description. When more than one is active, the bulk SEO abilities refuse to guess and need a provider named, which is a useful signal in itself. Ask the agent for seo-bulk-get-meta from each active plugin, compare what each stores with what the page prints, and plan to deactivate one in wp-admin. Retire the second plugin only after its titles, descriptions and redirects have a home in the one you keep.
FAQ
SEO suites and AI, answered
Will an agent write metadata that matches the page?
Only if it reads the page first, which is why these modules pair metadata writes with content reads. A description generated from a title alone is how sites end up claiming things the page never says.
Can an agent manage redirects safely?
It can create and read them through the SEO plugin's own redirect store, or the Redirection plugin's, and Pro adds a 301 in the installed redirect plugin when a published slug changes, touching only redirects it created itself. The judgement that stays with a person is whether a new rule extends an existing chain or contradicts a canonical that is already set.
Does GoBuildWP change how my SEO plugin outputs tags?
No. It writes to the same storage the plugin already uses, so the plugin remains the thing that renders the output and its own filters continue to apply.
Start in Read Only, then add what the site runs
Connect your AI client to the free MCP foundation and check what it can see. The free plugin already covers the basics for AIOSEO, Rank Math, SEOPress, Yoast SEO, The SEO Framework, Slim SEO and SmartCrawl; add Pro when a job needs more.