Your AI is about to drive AISA
By the end of September, AISA connects to AI assistants through MCP, the standard WordPress has brought into its own core. You won’t have to install anything new: your site becomes the connection point, you describe the job in plain language, and the assistant carries it out inside AISA.
Published: September 6, 2026 · Last updated: September 6, 2026 · Preview of a feature in development
What is it, in plain words?
It’s a remote control. AISA already knows how to do dozens of things: generate titles and meta descriptions, fix alt texts, rewrite schema, check broken links, rebuild the llms.txt file. Until now you pressed those buttons yourself, one at a time. The MCP connection hands them to the AI assistant you already work with.
Put more precisely: AISA doesn’t get smarter. It becomes drivable. You stop guiding it click by click and start telling it what you want to achieve.
How does it change a morning’s work?
Today Twenty pages, one morning
You open Search Console, look at which pages are underperforming, write them down. You open WordPress, find the first page, open AISA, read what’s wrong, decide the new title, type it, save. Then move to the second one. Twenty times over.
With the connection Twenty pages, one sentence
“Look at the pages on this site sitting on Google’s second page, check which ones have a weak title, rewrite it and save.” The assistant reads the real numbers from its own Search Console connection, asks AISA for each page’s SEO status, proposes the changes and has them applied. You read the summary and say yes or no.
The real leap shows up when there are many sites. Anyone running twenty or forty of them skips certain maintenance today — not for lack of know-how, but because multiplied by forty it simply doesn’t fit in a week. With the remote control, the same check costs the same effort on one site or on twenty: one sentence.
What will you be able to ask for?
The functions AISA will expose to the assistant are the ones you already use from the panel, published one by one along with their permissions.
From one page to the whole site
Generating titles, meta descriptions, focus keyphrases and AI Context on a single item or in bulk, with the heavy jobs running in the background.
Audits and repairs
A page’s SEO health, the problems found and the fixes proposed: the part that answers “what needs fixing here, and why this and not something else”.
llms.txt, schema and AI Context
Rebuilding the llms.txt file, proposing the right schema for a piece of content, refreshing the context generative engines read.
Alt texts, broken links, variants
Describing images that have no alt text, finding and fixing links that end in a 404, creating the variants used for title rotation.
Will it be part of the free version?
Partly, and the line is clear: understanding is for everyone, doing is in the paid plans.
Free The diagnosis
The assistant will be able to ask AISA for a page’s SEO status, read the problems it found and the llms.txt file, and explain what’s wrong. On any site, no licence needed.
Premium The execution
Applying changes, optimizing in bulk, describing images, running GEO scans: everything that writes or works at volume sits in the paid plans.
Why that line: what you pay for isn’t the single command, it’s repeated work at volume — the twenty pages in the example above. A remote control that did everything for free would hollow out the paid plan, and a product that doesn’t sustain itself stops being developed. We’d rather say it now than at the moment you click.
Why won’t you need to install anything?
Because WordPress built the bridge. Version 6.9 brought the Abilities API into core: a standard way for a plugin to declare “here is what I know how to do”. In February 2026 the official adapter arrived, publishing those abilities over MCP, and with WordPress 7.0 the mechanism goes deeper into core still.
AISA introduces itself
Each function is declared to the core with its name, description, the data it accepts and who is allowed to use it.
WordPress runs the switchboard
Authentication, permissions and the directory of available functions are handled by core. On our side there’s no program to install and no server in the middle: AISA declares what it can do, WordPress supplies the rest.
The assistant finds them by itself
Any MCP-compatible assistant sees AISA’s functions appear and can use them. Not just ours: the standard is open.
On sites running earlier WordPress versions the connection isn’t there, but the same functions stay reachable through AISA’s REST API: nobody is left behind, only the route changes.
Who decides what the AI can touch?
You do, under the same rules WordPress already applies to users. Every function carries its own permission: if an account can’t edit a piece of content, it won’t be able to do so through the assistant either.
Keys stay untouched
API keys, credentials and external connections stay outside the bridge: no assistant will be able to read or change them.
Before, after and back again
Changes go through the same machinery as the panel: a preview of what changes, and the ability to roll it back.
Big jobs go in a queue
Bulk operations run in the background and can be followed step by step, instead of all firing at once without you noticing.
Won’t everyone do this sooner or later?
Yes — and it’s only fair to say so. Driving WordPress by voice is becoming a baseline feature: it landed inside WordPress itself, for free, and within months plenty of plugins will have it. Anyone selling “your site, piloted by AI” as an exclusive will be selling hot water six months from now.
What a generic remote control doesn’t give you is judgement: knowing which title needs changing and why that one, cross-referencing real Google positions with the page’s intent. Without that piece, the deciding is still your job.
So the value here isn’t “AISA can be driven by voice”. It’s that AISA understands what needs doing — and from late September it can also do it.
When does it land?
The target is by the end of September 2026. Functions will appear progressively, starting with diagnosis and single-page optimization; bulk operations follow alongside the background engine. Meanwhile the plugin is already available and working: this connection adds to what it does, it doesn’t replace it.
For the wider picture behind all this, start from the guide What is GEO; to see AISA at work today, there’s the full video tutorial.
You can already try it today
AISA is free on the official WordPress.org directory: install it now — AI diagnosis will reach the free version with an update.
AI SEO & GEO Assistant · This is a preview of a feature in development: timing and scope may shift along the way, and we’ll update this page accordingly. The MCP connection requires a WordPress version that includes the Abilities API and its official adapter; on earlier installs the plugin’s REST API remains available.