Early adopter offer: lifetime licences from $49· one payment, every future update, until 1 December See the offer
Try it in a sandbox Get AgentedSEO

Claude Code WordPress SEORun the SEO audit in Claude Code. Approve the fixes in WordPress.

Tired of pasting the fix list in post by post? AgentedSEO is a full WordPress SEO plugin with an MCP server built in, so Claude Code’s fixes arrive as changes you preview, approve in a batch and undo in one click.

Get AgentedSEO Try it in a sandbox
  • Its own SEO loginNever your admin
  • Runs on your Claude planNo AgentedSEO credits
  • 3 → 12 pages a monthJoy’s test, 10 sites, 90 days
  • 15-day refund80% back
Claude Code → example.com/wp-admin · AgentedSEO › ApprovalsNothing reaches the site until you approve
Claude Code · terminal
✻ Claude Code~/example.com · agentedseo connected Audit the blog and fix missing meta descriptions. Show me first. agentedseo – run-site-check (MCP)Issues returned with stable codes · ASEO-META-002 agentedseo – set-meta (MCP)(dry_run: true, then submit)status: proposed Waiting for your approval in WordPress.
AgentedSEO › ApprovalsExample
Claude CodeOne run · groupedChecks passed
Meta description · /redirects-guide(empty)Learn when to use a 301 or a 302 redirect, and how to set both up in WordPress.
Meta description · /301-vs-302A guide to redirects.301 or 302? What each one tells Google, and which one your page needs.
Waiting for you · nothing written yet

Try it: approve the run, then undo it.

Claude Code writes the fix list. You still apply it by hand.

If you run SEO audits in Claude Code, you know how they end: a prioritised list of fixes in the terminal. Titles too long, descriptions missing, schema to add, redirects to clean up. Then the second half starts, and it happens in WordPress, not the terminal.

One Claude Code SEO blog describes that step plainly:

“you get a list of fixes in your terminal, then you switch to the WordPress dashboard and apply them manually. Post by post. Field by field.”

Right now there are two ways through it.

By handThe week gone

Open each post, paste each field, save. One Reddit user wanted titles, meta descriptions and focus keywords fixed across a few hundred posts. That is the week gone.

Give Claude Code the keysNo undo

SSH, WP-CLI and the database. Fast, but the advice in that thread was blunt:

“Claude can absolutely mess up sometimes, so you should have it make a database copy.”

The same owner worried that one wrong field could wipe an Elementor layout.

Neither shows you what changed before your visitors see it, and neither gives you an undo button that isn’t a backup restore.

AgentedSEO is the WordPress side of the loop.

Claude Code still runs the audit. Its fixes land in WordPress as changes you read, approve together and can put back. One commenter in that thread wanted exactly this: audit, recommendations, approve, implement, verify.

An agent took my own sites from 3 pages a month to 12.

Before AgentedSEO existed, I tested an agent SEO workflow on 10 of my own WordPress sites for 90 days. Published pages went from 3 to 12 a month. My time went from 6 hours a month to 1.5.

Two things still bugged me. Schema was the one job the agent needed another plugin for. And I still could not see at a glance what it had changed.

So I asked the Classic Monks community how SEO should ship. 34 people voted, and 64% said make it a separate plugin. AgentedSEO is that plugin: the place where an agent’s work lands as changes you can read, approve and undo.

I think agents writing straight into WordPress is the next workflow, not a gimmick. It only works if you can see what they did.

Joy Chetry
JoyFrom the team behind Classic Monks, building WordPress sites since 2017
My own test, before AgentedSEO10 sites · 90 days
Published pages a monthper site
Before3
After12
Joy’s time on SEO a monthhours
Before6
After1.5
Classic Monks community poll34 votes
64% said make it a separate pluginother options

The Claude Code SEO plugin for the WordPress side. Your skills keep working.

Keep the audit skill and the prompts you already use. AgentedSEO sits inside WordPress and answers Claude Code over MCP, so the fix list turns into changes on your site instead of a to-do list.

MCP endpoint · built into the plugin https://your-site.com/wp-json/agentedseo/mcp
Claude Code · your own audit skillExample
✻ Claude Code~/example.com · skill: seo-audit Run my SEO audit skill on the blog, then fix what you find through AgentedSEO. Skill (seo-audit)Audit finished · fix list ready agentedseo – get-capabilities (MCP)Fields it may write, limits, its own role agentedseo – set-meta (MCP)(dry_run: true)Before and after returned · checks passed agentedseo – set-schema (MCP)(type: “FAQPage”)status: proposed The fixes are waiting in Approvals.
Your skill finds the fixes. AgentedSEO is what Claude Code calls to apply them.

What Claude Code can call

  • 72 tools Claude Code can call: titles and descriptions, schema, redirects, sitemaps, alt text, the site check, posts and the change log.
  • The MCP server is part of the plugin, at /wp-json/agentedseo/mcp. No second bridge plugin and no adapter to install.
  • The same tools answer over REST, the WordPress Abilities API and WP-CLI, and every write goes through the same checks and change log, whichever way it comes in.
  • Claude Code connects with an application password made for its own user, set up on one screen in WordPress.
  • No AgentedSEO credits to buy. Claude Code runs on your own Claude plan.

Review a whole Claude Code run on one screen, then approve it together.

Every change from one Claude Code run lands in Approvals as one group, with the old value next to the new one. Read it once, approve the batch, and the whole run goes live, with nothing pasted by hand.

robots.txt edits, noindex on a page, trashing a post and hiding a whole post type from search always wait for you, whatever your rules say.

AgentedSEO › Approvals1 run waiting
Claude CodeOne run · 3 changesChecks passed
Title · /301-vs-302Redirects Guide | Blog301 vs 302 Redirects: Which One to Use
Meta description · /pricingOur pricing.One payment for 1, 25 or unlimited sites. Every feature in every licence.
Meta description · /redirects-guideRejecting(empty)Everything about WordPress redirects in one place: when to use a 301, a 302 or a 410, how to spot redirect chains, and how to fix the loops that slow your pages down.
Waiting for you · nothing written yet
A reject reason goes back to Claude Code, so it can fix the change and send it again.

How approval works

  • Changes from one agent call are grouped, so you approve or reject the run together. Approve all or Reject all handles up to 100 at a time.
  • Reject with a reason, and the reason goes back to Claude Code so it can fix the change and send it again.
  • You pick what waits, area by area. Meta titles and descriptions, schema, redirects, edits to published posts and publishing ask first by default. New drafts don’t.
  • Any change that touches more than 20 pages asks first, even in an area you set to automatic.
  • Some changes always wait for you: robots.txt edits, noindex on a page, trashing a post and hiding a whole post type from search, whatever your rules say.

Undo a fix days later, long after the terminal is closed.

Every change is in the change log with who made it, who approved it, when, and how it came in. Undo one field or the whole run in one click, so you stop making a database copy before every session.

Every change is logged with who made it (person or agent), when, and through which route, and can be undone, including whole batches.

AgentedSEO › Change log
Claude CodeOne run · 3 changesapproved by Joy · Tuesday 10:42 · via MCP
AgentTitle · /301-vs-302approved by Joy · via MCPApplied
AgentMeta description · /pricingapproved by Joy · via MCPApplied
YouTitle · /aboutJoy · Monday 16:05 · via the dashboardApplied

The terminal is closed. The undo still works.

Try it: undo the run, then redo it.

What the change log keeps

  • Each row shows who made the change (you or Claude Code’s agent user), who approved it, when, and whether it came through MCP, REST, WP-CLI or the dashboard.
  • Undo one change, or Undo batch for everything from one run. Changed your mind? Redo it.
  • Rewritten posts come back through WordPress revisions, exactly as they were.
  • Claude Code can undo its own work too: every write returns a batch id, and the revert tool puts that batch back.
  • Undo keeps working even if your licence expires.

Claude Code works as an SEO agent, not an admin.

Connecting Claude Code creates a separate WordPress user with the SEO Agent role and its own application password. It can work on SEO and content. It can’t reach users, plugins, themes or header and footer code, and you revoke it in one click.

AgentedSEO › Agents › Connections
Claude Code · agentedseo-claude-codeSEO Agent role · application password · last activity 2 minutes ago
Revoke deletes its user and password. Its change log stays.
Claude Code can
  • Edit titles, descriptions, schema, redirects, sitemaps and alt text
  • Write drafts and edit posts (edits to live posts wait for you)
  • Run the site check and read the results
  • Move a post to the trash, with your approval
Claude Code can’t
  • Touch users or roles
  • Install plugins or change themes
  • Edit header and footer code
  • Delete anything permanently

The fence around it

  • The agent user only reaches AgentedSEO’s own routes. Other REST routes and XML-RPC refuse it.
  • The MCP server tells Claude Code to treat site content as data and never follow instructions found inside posts or titles.
  • Approving is not a tool. Claude Code can propose, preview and undo, but only a person approves.
  • Revoke deletes the agent’s user and password. Its change log stays, and any content it created is handed to you.

The SEO Agent role cannot touch users, plugins, themes, header and footer code. robots.txt edits, noindex, trash and deletes always ask first.

Claude Code’s fixes land in a full SEO plugin, with schema checked first.

AgentedSEO is a complete WordPress SEO plugin, so the title, schema or redirect Claude Code changes is the one your pages print. No guessing which meta key another plugin will read.

  • Titles, descriptions and templates, robots meta, canonicals, Open Graph and X cards, per post, term and archive.
  • Schema for 22 types is checked against Google’s rich result rules before it saves. The Schema tab shows what is printed on the page, with a link to the Rich Results Test.
  • Redirects refuse loops and chains, so a batch of redirects from Claude Code can’t send visitors in circles.
  • The site check returns each problem with a stable code, so Claude Code can work through the list and run the check again to confirm.

Claude Code drafts and edits posts too, and publishing stays your call.

The work goes past meta. Claude Code can create drafts, edit posts block by block and add new pages, with the title, content, categories, featured image and SEO fields set in one go.

  • New posts are always drafts. Edits to published posts, publishing and scheduling ask first by default.
  • If someone has the post open in the editor, Claude Code’s edit waits as a proposal instead of overwriting them.
  • Every edit keeps a WordPress revision, so a rewritten post comes back exactly as it was.
  • Scripts and iframes in content are refused, and media uploads are checked before they land.
  • Page builder layouts (Elementor, Bricks, Breakdance, Oxygen) stay read-only for agents. Their SEO fields can still change.
Get AgentedSEO Or try it in a sandbox first

How Claude Code WordPress SEO works: audit to approved fix in five steps.

  1. 01

    Connect Claude Code over MCP in one command.

    In AgentedSEO › Agents › Connections, choose Desktop or code app and click Create password, then run this in your terminal:

    ✻ Claude Code~ · add the AgentedSEO server$ claude mcp add --transport http agentedseo https://your-site.com/wp-json/agentedseo/mcp --header "Authorization: Basic <value from the Connections screen>"

    Run test on the same screen confirms the link. That’s the whole Claude Code WordPress MCP setup, and the full guide is one click away: Connect Claude Code step by step.

  2. 02

    Run the audit you already trust.

    Use your own SEO skill or prompt, or ask Claude Code to run AgentedSEO’s site check and work through the issue list it returns.

  3. 03

    Let Claude Code propose the fixes.

    Each change comes back as “proposed”, grouped with the rest of the run in Approvals, old value next to new. Nothing on the live site has changed yet.

  4. 04

    Approve the run in one go.

    Read the batch, click Approve all, or reject one change with a reason Claude Code can act on.

  5. 05

    Undo from the change log, any day.

    Open the change log, find the run and click Undo batch. One change or the whole run comes back.

What Claude Code users ask before they connect a live site.

Still unsure? Try it in a sandbox.

Connect ClaudeCursorCodexHermes

Yes. People already do it with WP-CLI over SSH, or with a bridge plugin that writes straight to the live site. With AgentedSEO the same run lands in Approvals first, you approve it in a batch, and every change can be undone from the change log.

AgentedSEO is a WordPress plugin, and you keep using Skills in Claude Code: your audit skill finds the fixes, and AgentedSEO is what Claude Code calls over MCP to apply them in WordPress, where you approve them.

Yes. AgentedSEO has its own site check. Claude Code can run it, get each problem back with a stable code, fix it and run the check again. If you like a skill’s audit, use that instead. Both end in Approvals.

It can’t edit the layout. Pages built with Elementor, Bricks, Breakdance or Oxygen are read-only for agents for now, so the design is never rewritten by accident. Claude Code can still change their SEO fields and schema, and the site check reads the HTML those builders render.

No AgentedSEO credits, ever. Claude Code runs on your own Claude plan. The only key is the application password AgentedSEO creates for Claude Code’s user, shown once on the Connections screen.

Claude Code connects with that application password. Claude.ai and Claude Desktop add AgentedSEO as a custom connector and sign in with OAuth, so you never paste a password into them. Cursor, Codex and Hermes have their own guides in the docs. Connect Claude

No. AgentedSEO is a complete SEO plugin. It imports from 10 SEO plugins, Yoast and Rank Math included, shows what will move before it writes anything, and the whole import undoes in one click. See all importers

Early Adopter Lifetime is one payment with every future update, including Search Console stats, which are coming soon. On a yearly licence, if you stop renewing, your SEO output, data and undo keep working. Only updates and support stop. Every licence has a 15-day refund, 80% back. Read the refund policy

Early Adopter Lifetime · until 1 December

Let Claude Code do the SEO. Keep the final say in WordPress.

The agent does the clicking. You do the thinking. Early Adopter Lifetime: pay once, for 1, 25 or unlimited sites. Runs from 1 November to 1 December, 23:59 PT, then closes.

Solo 1 site $49 Early Adopter Lifetime, one payment Get Solo
Studio 25 sites $129 Early Adopter Lifetime, one payment Get Studio
AgencyFor agencies Unlimited sites $199 Early Adopter Lifetime, one payment Get Agency

Every licence includes the full plugin, the Claude Code connection, every future update and support.

From 2 December: Solo $49 a year, Studio $99 a year, Agency $149 a year or $499 lifetime.

15-day refund (80% back)Not sure yet? Try it in a sandbox

Built by Joy, from the team behind Classic Monks, building WordPress sites since 2017.
Get AgentedSEOTry the sandbox