From AISA 2.0.2 to 2.0.5: what changed in ten days, explained properly
Between 29 September and 9 October 2026 we shipped four versions of AISA. Here are the five changes that matter, with what they do, who they are for and where to find them. At the end you will find the fixes, version by version, and a section on what these versions do not do.
Five changes, plus the fixes
Clarity: readability as you write
Readability measured while you write, with the right formula for your language. From 2.0.5 also on pages built with WPBakery and Divi.
It doesn't just flag
AISA splits the sentences that are too long. Numbers, names and links stay untouched, and nothing changes until you approve.
Your AI assistant runs the audit
It finds site-wide issues in a single request, shows you what is wrong and writes only the values you decide.
Pages & indexing
For every public page: can search engines index it or not, and why. With your sitemap side by side.
Multilingual SEO Consultant
It asks AI engines in each market's language and counts a mention only when it is your brand, not your type of business.
And what you don't see
A safer "Undo import", the right language in One-Click, retiring AI models already replaced.
Clarity: readability in your language, as you write
"Clarity" is the readability panel that arrived with 2.0.2. It gives you a score with a traffic light and shows the sentences to look at. It updates as you write and runs in your browser: nothing is sent to an AI provider and it costs nothing. The full story is in Readability analysis in AISA.
Flesch for English, Gulpease for Italian
A readability formula is built on one language. AISA uses Flesch for English text and Gulpease, the index designed for Italian, for Italian text. It reads the language from the text, not from the site settings.
Nine checks, with the sentences to review
Long sentences, long paragraphs, long text without subheadings, passive voice, transition words, repeated sentence openings, length and sentence variety. For each one you see the sentences that trigger it.
Five audience profiles
The pass mark depends on who reads you. Choose one profile for the whole site in Settings and, if needed, a different one for a single post in the panel. The page audit uses the same pass mark.
Now with WPBakery and Divi too
On pages built with WPBakery or Divi the panel showed no values. It now reads the text inside the builder's rows and columns. And the analysis looks only at the text visitors read, also when it is called through MCP, the REST API or a background job.
The panel is in the block editor, the Classic editor and Elementor. In the content lists you also get a sortable "Readability" column next to the SEO score: it is filled in when a post is saved.
It doesn't just flag: it splits long sentences
Knowing that a sentence is too long is useful. Shortening it is the work. With AISA Premium, the Clarity panel has "Split long sentences": it takes the longest sentences and proposes how to divide them.
AISA proposes
For each long sentence you see the proposal divided into shorter ones. Numbers, names and links stay as they are: it splits, it does not rewrite your text.
You choose
You tick the proposals you like. Until you do, nothing changes in your content.
AISA applies
It applies only the proposals you ticked. Every other sentence stays exactly as you wrote it.
The same principle applies to the other fixes. Since 2.0.2, Auto SEO Fix tells you what it really fixed, what is left to you and what it could not fix: a fix counts as done only when the audit confirms it. 2.0.5 adds three cases that used to slip through.
Pages with a link in every paragraph
Fix Content did nothing where every paragraph contains a link. Paragraphs with links, images or shortcodes are still never rewritten, but it now adds the new paragraphs and the subheading with your keyphrase, and tells you which checks it could not fix and why.
Image ALT with WPBakery
Fix SEO now writes the image ALT also for images added with WPBakery image, gallery and carousel modules. It writes it in the Media Library.
The H1 printed by the theme
The "H1 heading present on the page" check was red where the theme prints the title. When the content has no H1, AISA now checks the published page once and counts the H1 it finds there.
Your AI assistant runs the audit, and writes only what you decide
With MCP you connect an AI assistant, for example Claude, to your WordPress: the assistant uses AISA as a tool and you talk to it in plain language. The connection is explained in Your site's SEO, at Claude's command. These versions close the loop: look at the site, understand what is wrong, fix it.
- SEO Doctor summary (2.0.5): the site-wide issues in a single request
- Site overview (2.0.4): how the site is built and what it contains
- List the pages and find pages by topic (2.0.4), from 2.0.5 also with a short summary of each page's AI Search Context
- The single-page audit, which shows what is wrong check by check
- Set SEO values (2.0.5): the assistant writes exactly the title, description and keyphrase you decided together
- It gives you back the previous values, so you always know what changed
- A repeated request is not written twice
- It can refuse to overwrite a value that someone else changed in the meantime
In practice: you ask the assistant for the site's issues, have it show you the worst pages, discuss the new titles and only then tell it to write them. Every ability has to be switched on by hand and the connection needs your consent: no assistant touches your site unless you decided it should.
Which pages search engines can index, and which they can't
Since 2.0.4 the SEO Doctor has a new card, "Pages & indexing". It is a read-only inventory built from the data of WordPress and your SEO plugin: nothing is downloaded and nothing is changed.
Every page, with the reason
For every public page you see whether search engines can index it. When they can't, you see why: noindex on the page, noindex set for the whole content type, site hidden from search engines, shop service pages, a canonical pointing elsewhere.
Your sitemap checked against your settings
AISA shows what your SEO plugin's sitemap lists and where it does not add up, for example a content type that is in the sitemap but set to noindex. It never changes your SEO plugin's settings.
Which pages have context for AI
The same card shows which pages have an AI Search Context and which are in your llms.txt. You see at a glance what is ready for search engines and what is ready for AI assistants.
With your SEO plugin, or none
It works with Yoast SEO, Rank Math, All in One SEO and SEOPress, and also without an SEO plugin. In that case you choose which content types and taxonomies the WordPress sitemap lists.
Multilingual SEO Consultant: one answer for each market
The SEO Consultant asks AI engines what one of your customers would ask and checks whether they cite you. We told that story in You're a great SEO and GEO consultant. With AISA, there are two of you. Up to 2.0.4 it worked in one language only. With 2.0.5, on multilingual sites running Polylang or WPML you choose the languages to scan in.
The right question in each market
Each target search is rewritten the way people in that market would search, and the question is asked in that language. For each language you get a score, the sites cited instead of you, suggestions and drafts.
The other names of your brand
You can add up to 10 other names or spellings of your brand. The brand name is also taken from the first part of a site title written as "Brand | tagline".
Only your brand counts
The scan used to count an answer as a mention when it named your type of business, for example "law firm". A mention now needs your brand name, one of its aliases, or your domain among the sources.
One consequence you should know: after the update your visibility score may go down. You did not lose mentions, the counting rules changed. The new criterion applies from this version, and past results stay in the history with a note.
The fixes, and what you need to do
| Version | What changes | What you need to do |
|---|---|---|
| 2.0.5 9 October | "Undo import" for SEO Dinamico removed every AISA field from all your content. It now removes only the values the import wrote and you have not changed since, puts back what the import had overwritten and keeps what it removes in a trash | Nothing. If needed, restore from the trash within 30 days |
| 2.0.5 | On multilingual sites One-Click could propose a keyphrase in the wrong language, for example Italian on English pages. Summary and keyphrase now follow the real language of each page | Nothing. If you had noticed the problem, regenerate those pages |
| 2.0.5 | The notice about the WordPress AI connector made a request to the AI provider on every admin page. It now appears only on AISA screens and uses a cache | Nothing |
| 2.0.5 | New German (formal) translation. Deprecation notices with PHP 8.5 fixed. In internal link suggestions, two icons to copy the address or a ready-to-paste link | Nothing |
| 2.0.4 4 October | OpenAI turns off gpt-image-1 on 23 October 2026 and Google is retiring Gemini 3.6 Flash and 3.7 Flash. AISA moves to the replacements by itself | Update before 23 October if you use the SEO Consultant with OpenAI for images |
| 2.0.4 | AI Context Index: a list of your indexable pages with their AI Search Context, linked from your llms.txt. It is an AISA format, not a Google feature | Nothing: it is off until you turn it on |
| 2.0.3 30 September | In the Classic editor, saving the readability result was rejected by some firewalls, and on some servers two saves were enough to get your IP address blocked for hours | Update if your host uses ModSecurity or another OWASP firewall |
| 2.0.2 29 September | Clarity panel, internal link suggestions that read the text of the page, an Auto SEO Fix that says what it really fixed | Optional: choose the audience profile of the site in Settings |
One update, no settings to redo
Update AISA
From Dashboard → Updates, or from the Plugins page. If you turned on automatic updates for AISA, 2.0.5 arrives by itself.
AISA Premium follows
If you use AISA Premium, the Premium component gets its update on the same screen, like any other plugin.
What you find afterwards
The Clarity panel on builder pages too, the "Pages & indexing" card in the SEO Doctor and, on multilingual sites, the choice of languages in the SEO Consultant.
What these versions do not do
- A more readable text is easier to understand. It does not guarantee a better ranking.
- "Split long sentences" divides sentences. It does not rewrite your text or improve its content. The Clarity panel works in English and Italian today.
- "Indexable" means your site does not prevent it. Whether Google then indexes the page is Google's decision: for that, Search Console remains the place to look.
- The SEO Consultant tells you whether AI engines cite you today, on the questions you chose. It cannot make them cite you, and AI answers change over time.
- Over MCP the assistant writes only with AISA Premium and only what you ask. What gets published remains your responsibility.
AISA 2.0.5 is on WordPress.org
The Clarity panel, "Pages & indexing" and the MCP tools that read are in the free plugin. "Split long sentences", writing over MCP and the SEO Consultant are Premium features. If you already have AISA, update it; if you don't, try it.
Try it freeReadability analysis in AISA · SEO at Claude's command · SEO Consultant · What's new in 2.0
Release notes of AISA from 2.0.2 (29 September 2026) to 2.0.5 (9 October 2026), taken from the changelog published on WordPress.org. Model retirement dates are those on the official pages of OpenAI and Google checked on 4 October 2026: they may change. Third-party plugin settings and formats may change.