AI Agents Can Now Edit Your WordPress Metadata Without Touching wp-admin. Yoast 28.7 Made That Official.
On October 13, Yoast released version 28.7. Brief release notes. Significant scope change.
Starting with this build, your AI tool can update post titles, meta descriptions, and social preview fields directly inside WordPress via the Yoast SEO Abilities system. No tab switching. No manual Bulk Editor queue. The agent reads the SEO data, updates the fields, and returns per-post confirmation, all inside a single conversation through the WordPress MCP Adapter.
For marketing teams running AI-assisted content pipelines, this closes a specific friction point that has been sitting in the workflow for months. AI could identify which posts had stale or mismatched metadata, but someone still had to open each record and fix it by hand.
What Changed in 28.7
The update extends the yoast-seo/update-post-seo-data ability with six new writable fields:
- Post title (what Google displays in search results)
- Meta description
- Open Graph title (what LinkedIn and Facebook pull when a post is shared)
- Open Graph description
- Twitter/X card title
- Twitter/X card description
The Yoast team's practical example from the release notes: a product gets renamed, but its title and social previews still show the old name. You can now use your AI tool to read the post's SEO data, review what is out of date, and update it in the same conversation.
That example is deliberately narrow. The actual scope is broader. Any task that involves reading SEO data, comparing it against a standard, and pushing updates across multiple posts can now be handled by an agent working through an MCP-aware client like Claude Desktop, Claude Code, or Cursor. No custom integration needed. Typed input and output schemas define exactly what to send and what to expect back.
How the Abilities System Got Here
Yoast introduced the Abilities API in April 2026. The initial release let AI tools check SEO scores, readability scores, and inclusive language scores across recently modified posts. Read access only. The September 29 release added read-write access to technical settings: canonical URL, robots flags, schema type, and cornerstone designation. Real write access, not just suggestions. Still no changes to what users actually see in search results or social platforms.
Version 28.7 completes the visible layer. Now an agent can update the metadata that appears in SERPs and on social, not just the settings behind them.
For agencies, this also means one standard setup across every WordPress build they manage, with no manual per-site reconfiguration once the WordPress MCP Adapter is connected.
Where the Line Still Falls on You
The focus keyphrase is read-only. Always has been, and 28.7 does not change that.
This is deliberate. An automated change to the keyphrase invalidates the content brief, the readability scoring, and any internal linking decisions tied to that term. One wrong automated write cascades across assessments. The Yoast team locked it down, and that is the right call.
Access follows WordPress native capability checks, not a separate permission system. An agent operating with editor-level credentials cannot update posts that require admin access. You audit AI access the same way you audit any other admin-level access in your install.
There is also a session constraint that matters in practice. Once the context window closes, the previous values go with it. The recommended workflow from Yoast: read the SEO data before updating, stay in that session while reviewing results, and confirm before closing. This is not a background job running independently.
What This Means for Content Automation Workflows
Content teams spend real hours every year correcting metadata that drifted from its original spec. Product renames, campaign pivots, page consolidations, seasonal refresh cycles. Each correction was a context switch. Open the post, update the field, save, next post.
Batch operations through the Abilities API return per-post results. Your agent can apply a get-filter-update cycle across dozens of posts in one call, show you exactly what changed, and flag anything that does not match the expected pattern.
This is not the same as generating content at scale. It is routine metadata maintenance, which sounds unglamorous but accounts for a meaningful share of the manual work in any site with a content archive of 50 posts or more.
The human role does not disappear here. Your AI tool still needs a clear instruction. The focus keyphrase stays yours. And the review pass before bulk updates go live, especially for metadata visible in SERPs, remains essential. Google flagged unreviewed AI output as low effort earlier this month, and that signal compounds when it appears in the title and description users and crawlers see first.
Human-assisted AI content is the operating model. The 28.7 release makes the AI's operating range wider inside WordPress. It does not make the content team's judgment smaller.
Getting Connected
The integration runs through the WordPress MCP Adapter. Connect your own LLM subscription to Yoast first. After that, read access, core SEO field updates, and bulk operations are all included without additional cost or separate credit purchase.
If you already set up the Abilities API in 28.6, the new metadata fields are ready immediately after updating. No new setup. The developer documentation at Yoast covers the full ability list and schemas for teams building on top of it.
