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

The AIOSEO alternative built for agent workBring your AIOSEO work with you. Then approve what your agent changes.

Worried you’ll lose your keyword settings? The importer brings your AIOSEO titles, descriptions, keyphrases and redirects across as one batch you can undo. After that, your agent signs in as its own SEO user, and the areas you pick wait for your approval.

Get AgentedSEO
  • AIOSEO data untouchedWe only read it
  • No admin loginYour agent gets its own
  • Import is undoableEvery change logged
  • 15-day refund80% back
example.com/wp-admin · AgentedSEO › Import, then Approvals
1 · Bring your All in One SEO work across Dry run
Found: All in One SEOcounts come from your site
TitlesReady
DescriptionsReady
Focus keyphrasesReady
CanonicalsReady
RedirectsReady
Pages that already have a value
Nothing written · All in One SEO data untouched
2 · Approve what your agent changesExample
ClaudeFirst job · 1 changeChecks passed
Meta description · /redirects-guideThe description AIOSEO hadLearn when to use a 301 or a 302 redirect, and how to set both up in WordPress.
Waiting for you

Try it: run the import, then undo the whole batch.

Leaving AIOSEO shouldn’t mean typing years of SEO titles again.

You’ve spent years filling in AIOSEO: a title and a description on every post, focus keyphrases, redirects, schema. Is that work the reason you haven’t moved?

Doing it again costs the same evenings it took the first time, post by post, with the worry that rankings slip while the fields sit empty.

It’s a fair worry. After one plugin switch, a site owner on Reddit wrote:

“some pages/blogs lost the keywords settings.”

Another warned someone weighing a move:

“Changing Yoast can remove keywords and other things and you have to do it again.”

Neither was about AIOSEO. Losing work in a switch is the risk with any SEO plugin.

The fear of retyping shouldn’t keep you on a plugin.

I don’t think the fear of retyping should be what keeps anyone on an SEO plugin. I’d rather you pick one for what it does. So our AIOSEO importer reads what AIOSEO saved, shows how many values each field would get before it writes anything, and leaves AIOSEO’s own data where it was. If the preview looks wrong, don’t import. If the import looks wrong, one click puts it back.

Agent SEO on 10 of my own sites: 3 pages a month became 12.

I tested an agent workflow on 10 WordPress sites over 90 days. Published pages went from 3 to 12 a month, and the time I spent went from 6 hours a month to 1.5. That was my own test, not a customer result.

What I still couldn’t do was see, at a glance, what the agent had changed, or put it back. So when the Classic Monks community voted on how SEO should ship, and 64% of 34 votes said make it a separate plugin, I built it around that gap: a preview before the change, approval where you want it, a login for the agent that isn’t yours, and undo on every write.

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

An All in One SEO alternative that brings your titles and keyphrases along.

The AIOSEO importer reads what AIOSEO saved on the site and shows a preview before it writes anything. Everything lands as one batch, AIOSEO’s own data stays untouched, and one click undoes the lot.

Per pageComes across

  • Titles and descriptions
  • Focus keywords
  • Canonicals
  • Robots settings
  • Social settings
  • The primary category
  • Redirects

Site-wideComes across

  • Title templates and separator
  • Sitemap on or off
  • Social defaults and site identity
  • Indexing rules
  • The attachment-page redirect
  • Verification codes
  • Breadcrumb settings

Not importedStays behind

  • SEO and readability scores
  • Cornerstone or pillar flags
  • noimageindex and a few other rare robots tags
  • Schema set on single posts (your post type defaults cover it)
  • Settings with no match are listed as notes
The preview is a dry run: how many values each field would get, the conflicts and the skips. Where a page already has an AgentedSEO value, you choose to keep it or overwrite it.
One batch in the change log, undone in one click. Values edited after the import stay as written. When it’s done, the importer offers to deactivate AIOSEO for you. Nothing is deleted from it.

Every change is logged and undoable, with batch undo for imports.

AIOSEO MCP and AgentedSEO: what happens after your agent connects.

I’ll say this first: AIOSEO’s MCP is free on every plan, including Lite. If you’re happy for an agent’s changes to land straight away and to check them afterwards, that free MCP is enough, and I’d stay put. We differ on what happens after the agent is in, and that’s what this table covers.

AIOSEO MCP compared with AgentedSEO, checked 30 October 2026
Checked 30 Oct 2026AIOSEO MCPAgentedSEO
Price of agent accessFree on every plan, including LitePart of the paid licence
How the agent connectsWordPress 6.9 or higher; AIOSEO installs the separate MCP Adapter plugin; an Application Password “tied to your user account”Endpoint built into the plugin; each agent gets its own SEO Agent user, or OAuth 2.1 for the Claude.ai connector
Clients namedClaude Desktop, Claude Code CLI, Cursor, VS Code, Gemini CLI; ChatGPT users are pointed to one of thoseTested with Claude, Codex, Cursor and Hermes, each with a setup guide
When a change landsIts walkthrough: meta descriptions “updated in real time”; the AI “will work through the list and confirm each update”Areas set to Ask me first show a before and after with checks and wait for your approval; edits to published posts ask first by default
What the agent can’t touch“passwords, payment data, user accounts, or anything outside AIOSEO’s scope”Users, plugins, themes, header and footer code; robots.txt edits, noindex, trash and deletes always ask first
UndoSEO Revisions on Plus (15), Pro (30) and Elite (unlimited), with 1-click restore of SEO settings and meta. Whether MCP writes are recorded there: not statedA change log on every write, on every licence: undo one change, undo a batch (agent run or import), redo
Where AIOSEO is ahead: its MCP costs nothing, it names VS Code and Gemini CLI setups out of the box, and its agent can already summarise Search Console data. Our Search Console stats are coming soon.

I checked every AIOSEO line on aioseo.com on 30 Oct 2026 (sources linked on the build: the AIOSEO MCP announcement, the SEO Revisions page, the pricing page). If something has changed, write to [email protected] and I’ll fix the table.

Get AgentedSEO

Once you’ve switched, your agent works inside these rules.

The parts AgentedSEO adds on top of the SEO you brought across: a preview, approval where you want it, undo on every write, and a login for the agent that isn’t yours.

Read the before and after of an agent change before your visitors do.

When an agent asks to change something in an area set to Ask me first, AgentedSEO turns the request into a proposal: the old value, the new one, and the checks it passed. The live site stays as it is until you approve.

  • Every write, from a person, an agent or an import, goes through one path that can run as a dry run first, so an agent can show the whole job before doing it.
  • Each proposal carries its check results. If the page changed after the proposal was made, it is flagged as stale, so you never approve against an old version.
  • Edits to published posts ask first by default.
  • An email tells you something is waiting, and the same preview shows in Approvals and in the editor’s Agent view.

Every change logged and undoable.

Approve the risky changes. Let the routine ones run on their own.

Each area is set to Ask me first or Automatic. One setup I’d suggest: meta on old posts runs on its own, while live edits and publishing wait for you. Flip it if you prefer. Either way, approval doesn’t turn into a second job.

  • Areas you set: meta, schema, redirects, new drafts, edits to live posts and publishing.
  • Fixed rules always ask first, whatever you set: robots.txt edits, noindex, trash and deletes, and hiding a whole post type, taxonomy or the author archive from search.
  • Approve all or Reject all, up to 100 at once, or a whole batch. Changes from one agent request are grouped, so you review them together.
  • Reject with a reason and the agent gets the reason back. The change log shows who approved each change.

Robots.txt edits, noindex, trash and deletes always ask first.

Put back one change, an agent’s whole run or the import, in one click.

Every write is logged with who made it, you or the agent, when, and how it came in. Undo works from the change log, so it still works after the agent session has ended and the chat is gone.

  • Undo a single field, or a whole batch from one agent run or one import.
  • Redo puts an undone change back, and a settings reset can be undone too.
  • Rewritten posts keep a WordPress revision, so they come back exactly as they were.
  • Writes other plugins make to AgentedSEO’s own fields go through the same log, so those can be undone too.
  • Export the log as CSV when a client asks what changed.

Every change logged with who, when and how, and undoable; batch undo for imports and bulk jobs.

Your agent signs in as its own SEO user, not as you.

Connecting an agent creates a separate WordPress user with the SEO Agent role and its own credentials. It does SEO work inside that role, and you cut it off in one click without touching your own login.

  • One user per agent, with an application password, or OAuth 2.1 for the Claude.ai connector.
  • The role can’t touch users, plugins, themes, or header and footer code.
  • The Role & permissions screen lists what it can and can’t do, and the agent activity log records what each agent did and tried to do, with CSV export.
  • Agent users can’t sign in over XML-RPC, and an address is locked out after ten failed sign-ins.
  • Revoke an agent and the content it created passes to you.

The SEO Agent role cannot touch users, plugins, themes, header and footer code.

The everyday SEO tools are all here, with or without an agent.

An agent is optional. I use one, but the plugin works without it: titles, descriptions and schema are edited in the editor, and sitemaps, redirects and site checks run from the WordPress dashboard.

Edit post · SEO drawer › Schema
Printed on the page
Article · post type defaultValid
BreadcrumbList · site settingValid
Organization · site identityValid
View printed JSON-LDRich Results Test

What works from the dashboard

  • An SEO drawer in the block editor, the classic editor and the posts list, and in Bricks, Elementor, Breakdance and Oxygen.
  • Schema for 22 types, validated before it saves. The Schema tab shows what is printed on the page, with a link to Google’s Rich Results Test.
  • XML sitemaps, redirects with a 404 monitor and an automatic redirect when a slug changes, breadcrumbs, a robots.txt editor with a URL tester, llms.txt and IndexNow.
  • A site check that lists issues in plain language, with one-click fixes for site-level problems.
  • AI helpers are off by default and run on your own key, so there are no AI credits to buy.

Move to an AIOSEO alternative in five steps, without retyping your meta.

Get AgentedSEO Try it in a sandbox first
  1. 01

    Install AgentedSEO next to AIOSEO.

    While both are active, AgentedSEO prints nothing in the page head and shows a notice instead, so search engines never see two sets of tags.

  2. 02

    Run the AIOSEO importer and read the preview.

    The dry run shows how many values each field would get, the conflicts and the skips, and you choose keep or overwrite.

  3. 03

    Import, then spot-check a few posts.

    I’d open the SEO drawer on two or three of your busiest posts and check the Schema tab’s “Printed on the page” list.

  4. 04

    Switch AIOSEO off.

    The importer offers to deactivate it. Nothing is deleted, so you can switch it back on.

  5. 05

    Connect your agent and approve its first job.

    Paste one URL into Claude, Codex, Cursor or Hermes, give it a job, and read the before and after.

Questions AIOSEO users ask before they switch.

Still unsure? Try it in a sandbox.

How agent access works[email protected]

They are on the import list. I built the importer to read AIOSEO’s data and never change it. It copies titles, descriptions and keyphrases across, and the dry run shows how many values each field would get, the conflicts and the skips before anything is written. If something looks wrong afterwards, undo the whole import in one click; edits made after the import stay.

Per page: titles, descriptions, focus keywords, canonicals, robots, social, the primary category and redirects. Site-wide: templates and separator, sitemap on or off, social defaults, site identity, indexing rules, the attachment-page redirect, verification codes and breadcrumb settings. Not imported: SEO and readability scores, cornerstone or pillar flags, noimageindex and a few other rare robots tags, and schema set on single posts, because AgentedSEO’s schema defaults for each post type cover those pages. AIOSEO’s robots.txt rules and per-post breadcrumb titles are not on the AIOSEO importer’s list either, so copy those by hand into the robots.txt editor and the post. Any setting with no match in AgentedSEO is listed as a note.

Yes. While AIOSEO is active, AgentedSEO prints nothing in the page head, so nothing doubles up. I’d keep both on until the import looks right, then switch over.

If changes landing straight away suits you, AIOSEO’s free MCP covers it, and I’d tell a friend to stay. I built AgentedSEO for the people who want a preview and an approval step first, an agent that signs in as its own limited user, and undo on every write, imports and agent runs included.

I’ve tested Claude, Codex, Cursor and Hermes, and each has a setup guide. The Claude.ai connector signs in with OAuth. Connection details on the For agents page

Yes, if your daily tools are titles, descriptions, schema, sitemaps, redirects and site checks. They all work from the dashboard, and there are no AI credits to buy: the optional AI helpers are off by default and use your own key. I haven’t built internal link suggestions or keyword rank history yet, so if those are part of your week in AIOSEO, weigh that first.

The SEO drawer works inside Bricks, Elementor, Breakdance and Oxygen, and the site check reads the HTML those builders render. Divi and WPBakery are not on that list today. If your site runs on one of them, write to me at [email protected] before buying and I’ll give you a straight answer.

Early Adopter Lifetime is one payment and includes every future update. Our Search Console stats are coming soon, and lifetime buyers get them too. If a licence ever lapses, your SEO output, data and undo keep working; only updates and support stop. There’s a 15-day refund, with 80% of the purchase returned. Read the refund policy

Early Adopter Lifetime · until 1 December

Keep your AIOSEO work, and keep the final say on your agent.

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 AIOSEO importer, the agent 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)Compare every plan on the pricing page

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