AISA SEO Commander: the plugin talks to AI assistants

This is the headline of the release. AISA registers thirteen tools in the WordPress abilities registry and exposes them over MCP, the protocol AI assistants use to connect to an external service. From Claude you can ask for a page audit, for the fixes to be applied, for image alt text or for a broken-link report, and the work happens on your site. Five tools read and are in the free plugin; eight write and come with AISA Premium, the separate companion plugin.

It connects with nothing else installed

AISA has its own MCP endpoint at /wp-json/aisa/v1/mcp: that address and a WordPress application password are enough to connect Claude Code or Claude Desktop, with no extra plugin. If the official MCP Adapter is installed on the site, the same tools also show up there under their own names, next to those of WordPress and the other plugins; the dedicated address in that case is /wp-json/aisa/mcp.

The switch is where you can find it

Abilities are on by default, because otherwise nobody upgrading would ever discover that the plugin speaks MCP, and they go off with a checkbox in Settings → API Keys. The same section shows the real status of the site: the MCP address, whether the MCP Adapter is installed, how many abilities are registered right now and whether the WordPress version is recent enough. If you would rather decide from the configuration file, define( 'AISA_ABILITIES', false ); takes precedence over the panel.

Background batches, with no waiting

Asking an assistant to optimize two hundred contents used to mean keeping it hanging for twenty minutes. Now AISA accepts the work, answers immediately with a job id and runs it on its own using the background engine that already powered One-Click SEO. You can ask for progress whenever you like, see the outcome content by content, and stop whatever is still queued: what has already been written stays written.

No half-written answers online

AI-generated questions and answers now carry a status, one by one. Approved ones go live; the ones waiting for approval and the ones waiting to be completed stay in the dashboard and appear neither on the site, nor in the FAQPage schema, nor in llms.txt. The rule behind the change is the same everywhere in the plugin: if AISA does not have a fact, it writes nothing. An answer that used to read "we are located in [TO BE VERIFIED]" is now born empty, with a line saying which piece of information is missing and a link to the field where you add it.

In the editor of a set you get an "Approved" checkbox on every row, the All / Approved / To approve / Suggested filters with their counters, an "Approve all complete" button — which becomes "Approve all shown" while a filter is active — and an Undo until you save. The list of sets carries the bulk action "Approve complete questions". A deterministic check compares the opening hours, phone numbers and country names found in the answers against the business details you configured: what it cannot confirm is not blocked, but it stays flagged and out of automatic approval. The "Regenerate answer" button rewrites a single answer once the missing fact has been entered.

If you are upgrading, answers that contained a placeholder leave the site immediately, with the old text preserved and recoverable from the editor. Everything else stays approved and visible.

The Q&A page is no longer born an orphan

After "Create dedicated page" AISA offers three routes: add the page to an existing menu, append the Q&A to the end of a page you already have — with a revision saved first and a confirmation — or nothing at all, in which case the audit reminds you. The page slug follows the language of the set, and the page is created with the right language and linked to its sibling translations when you use Polylang or WPML. With a page builder the page is created without builder mode, so the content renders: if you later open it in Elementor, the panel hands you the shortcode to paste into a Shortcode widget.

Your FAQs go into your SEO plugin's schema

With Yoast, Rank Math or All in One SEO active, the AISA nodes now join the SEO plugin's JSON-LD graph instead of adding a second structured-data block. On an FAQ page the questions become that page's main content; otherwise AISA adds the FAQ node and the page references it. If the host graph already contains an FAQPage, AISA adds nothing. With SEOPress the grafting is not implemented yet and AISA prints its own node: a second block is better than FAQs that come out nowhere, which was the earlier defect.

Business details become real fields

The Local SEO (Google) page, in the "Business details" card, has four new fields: legal name, VAT number, area served as a typed list (Country, AdministrativeArea, City) and a list of services, one per line. They are not decoration: they end up in the structured data as legalName, vatID, areaServed and hasOfferCatalog, in the Location line of llms.txt, in the title and description variants, and in the Q&A answers. A field left empty produces no key in the schema at all: better to say nothing than to state something untrue.

The "Autofill with AI" button (formerly "Detect from site") reads your Contact page and your footer, straight from the database, and proposes the address, phone numbers, email, opening hours, area served, legal name and VAT number. Before writing anything it shows you a field-by-field comparison with tick boxes: applying only fills the form, and the database is touched when you press Save.

In the graphs of Yoast and the other SEO plugins, these details now enrich the Organization instead of sitting only in llms.txt: address, phone, area served, social profiles, what you know how to do. AISA fills only the missing keys and never overwrites a value you wrote yourself.

The area served reaches your titles and your llms.txt

On the home page and on service pages, with an area served configured, AISA asks the model that at least two variants out of five name the place — and afterwards it actually counts them: if fewer than the minimum do, it regenerates only the missing variants once, and if that does not improve things the originals are kept. The Location line of llms.txt is now built from the structured area-served fields instead of free text, and a saved document regenerates itself when those fields change. A version you wrote by hand is never touched.

New checks in the audit and in SEO Doctor

Nine more checks, all deterministic, with no AI call and no extra HTTP request: duplicate H1, brand name truncated in the title, a local page whose text never names the place, subheadings with nothing underneath, generic alt text. SEO Doctor adds three site-level checks — the site address in http while the front end is https, a home page with comments open, leftover postmeta from other SEO plugins — and three that came out of the Q&A work: the tagline published as the site identity, a Q&A page nothing links to, a Q&A page with no language assigned. False positives are excluded by construction rather than by caution: each check fires only under the conditions that make the statement certain.

"Verify on the live page"

It can happen that a content item looks optimized in the dashboard while the front end prints nothing, for example after switching SEO plugin. AISA now downloads the page as visitors receive it and compares the title, the meta description and the social image with what was saved, also flagging duplicate Open Graph tags. The check never runs on its own: you start it from the Auto SEO Fix box with the "Verify on the live page" button, and the result is cached for twelve hours. A connected assistant can ask for it too, and it is the right question whenever a result does not convince you.

The SEO now says where it was written

Next to the generation date there is now the destination: standalone, Yoast, Rank Math, SEOPress or All in One SEO. If the destination differs from the active SEO plugin, the work has been left behind and you can see it at a glance. On top of that, the "N pages have SEO your plugin cannot see" notice no longer disappears forever when you dismiss it: it comes back if the mismatch genuinely gets worse, and the status card updates immediately even when the fields change outside AISA.

One-Click and Bulk errors: a full log and an honest report

A report saying "23 out of 78, 55 errors" next to an empty error log: that no longer happens. Every error the report counts has its own line in the log with the real cause — provider, model, HTTP status, message, duration — including the failures only the browser sees, such as timeouts and 429s. The log keeps three hundred lines, says where each error came from, and can be copied as text for a support request. When a provider slows down, AISA halves the number of parallel requests, waits and retries up to twice, and the report tells apart what was recovered on the second attempt from what genuinely failed. Contents optimized only in part are reported as a warning with the list of fields: they no longer pass for a full success. And the cheer only appears when the error count is zero.

Models and prices updated without waiting for a release

AI providers retire models whenever they like, and until now every adjustment needed a new version of the plugin. AISA now asks the provider for its model list using your key and merges it with its own catalogue, and downloads an updated price list once a day. If a model you saved is no longer offered, the API page tells you and gives you a link to reload the list: your saved value is never changed without you. Offline, nothing changes.

The schema engine is more careful and clearer

Business type detection is no longer convinced by the same fact repeated four times: signals are grouped into families, each with a cap on the points it can contribute. Proposing a LocalBusiness now requires real proof of a place, meaning a postal address and not just a phone number; without it, AISA falls back to the most honest type and spells out the reason. Confidence is no longer a percentage but a level with a score, and the advertised software product carries its price in an Offer node, only when a price is set.

Elementor content, the H1 and social images

"Fix Content" now also works inside the Elementor HTML widget, the one used by many themes and by anyone laying out markup by hand: it used to answer that there was no editable text. Widgets holding scripts, iframes or heavy style blocks are skipped and counted, and the markup that is not touched stays byte for byte identical. The keyphrase can also go into the H1, if you ask for it: AISA writes into the Elementor heading widget, into the H1 in the content or, if the page has no H1 of its own, into the post title — always reporting where it wrote, with before and after, and with a backup. On the social side, the image set in the SEO block of a content item now always wins over the others, and social profiles are saved per network instead of in a list the Settings tab could not read back.

In AISA Cloud the first Q&A set costs 1 credit

The Brand Context ("Generate all") already cost 1 credit, because it is configuration rather than content to publish. Now the first Q&A set of a site costs 1 credit too: the initial setup is 1 + 1. From the second set onwards a Q&A set goes back to 5 credits. The cost is always shown before the click, next to the button, and the end-of-generation report says what was actually charged. With your own API keys, or in the free plugin, nothing changes: credits only concern AISA Cloud.

The invitation to install AISA Premium appears where it should

With a valid licence and the Premium component not yet installed, users saw "licence ok" and nothing else. Now the invitation — activate, install or download — appears on every AISA screen, in the plugins list and in the setup wizard, including in the package downloaded from WordPress.org, with a direct link to the latest component zip.