For years SEO work has had one shape: open wp-admin, open the page, read the checks, fix, save, move to the next one. It works. It is also why some things never get done, because doing them means opening fifty tabs.

With 2.0, AISA changes the starting point. The plugin registers its functions in the WordPress abilities registry — the one that landed in core with 6.9 — and exposes them over MCP, the protocol AI assistants use to connect to an external service. From that moment Claude does not explain what you should do on your site: it does it, with your permissions, inside your site.

We call it AISA SEO Commander.

What it looks like in practice

Open Claude and write an ordinary sentence. Not a command, not a syntax: a sentence you would say to a colleague.

"Audit the Contact page, apply the fixes, then audit it again and tell me what changed."

Claude reads the SEO status of the content, calls the AISA on-page audit, gets the list of checks with each outcome, asks for the fix, then reads again and reports the difference. You read two lines and decide whether you like it.

Or: "Optimize in the background the twenty published pages with no meta description and tell me when it is done." Nothing is left hanging here: AISA accepts the work, answers with a job id and runs it on its own while you close the laptop. When you come back, you ask how far it got.

Thirteen tools, two kinds

Five tools read, and they are in the free plugin: the SEO status of a content item, the on-page audit, the llms.txt document, the Brand Context, the site diagnostics. They are the most honest way to show what the plugin does: a connected assistant can tell anyone what is wrong with their site without touching a comma.

Eight tools write, and they come with AISA Premium, the separate companion plugin: optimizing a page, fixing the failing audit checks, background batches with job status, the Brand Context, image alt text and title with AI Vision, checking and repairing internal links, scanning visibility in AI answers.

What each one does exactly, and with which parameters, is covered in a guide of its own. Here it is enough to say that the names Claude sees are the names of the functions you already know from the interface. This is not a second product; it is the same product with a second door.

The boring part, which is the important one

An automated channel that writes to a production site is a serious thing, and we treated it as one.

The connection uses a WordPress application password: a secondary password for your user, created in two clicks and revoked in one. Claude introduces itself to the site as you, with your permissions and not one more. A page your user cannot edit stays uneditable from the chat as well.

API keys, licences and tokens cannot be reached by any tool: ask "where is my OpenAI key?" and the answer only says whether a provider is configured. Actions that change what visitors read — slug, H1, content — are off by default and have to be requested explicitly. Before touching a content item AISA saves a revision, and with Elementor a backup of the builder data. An AI visibility scan, which costs real money at an answer engine, only estimates the first time: the scan runs after you confirm. There is also a per-user limit on calls per minute, because an assistant that gets stuck in a loop should not be able to hammer your site.

And if one day you would rather not have it: abilities are switched off with a checkbox in Settings, or with one line in wp-config.php.

Does it need anything else installed?

Not necessarily. AISA has a built-in MCP endpoint: one address, the application password, and Claude Code or Claude Desktop are connected. No extra plugins.

If you want the assistant to manage the rest of the site as well — drafts, images, menus — a general connector such as the official MCP Adapter, or Easy MCP AI, lists the AISA abilities alongside everything else. That is also the route for ChatGPT, which requires OAuth.

On a local or staging site it all works the same way, as long as the assistant runs on your own computer.

There is more in 2.0

MCP is the headline, not the whole release: 2.0 also brings questions and answers with review and approval — no half-written answer goes online — business details as real fields that reach the structured data and llms.txt, FAQs inside your SEO plugin's graph, new checks in the audit and in SEO Doctor, an AI model catalogue that updates without waiting for a release, and an error log that finally says what went wrong. The full list is in the release notes.