AISA 2.0.9: every SEO change now has a history, and you can undo it
When One-Click, a colleague or an AI client changes a title, you can now see who did it, when, and what was there before. One click takes you back. Redirects also learn wildcards and regex, the sitemap lists images, and DeepSeek Search arrives. Here is what each feature does, how to use it, and what it does not do.
Six new features, five with no AI cost at all
SEO history with Restore
Title, description, focus keyphrase and slug: who, when, before and after. Its own item in the AISA menu and a box in the editor.
Wildcard and regex redirects
One rule for a whole folder. It is saved only after it works on an address you try, so a wrong rule never goes live.
Grouped 404s, CSV, editing
Missing pages are grouped by folder, with "Create redirect" and "Ignore". Redirects can be edited, imported and exported.
Images in the sitemap
When AISA serves the sitemap, each page lists its images: featured, in the text, galleries, page builders and WooCommerce products.
You choose the address
sitemap.xml, sitemap_index.xml or wp-sitemap.xml. And "Manage the sitemap with AISA" now also works with AIOSEO and SEOPress.
DeepSeek Search and Fetch
A search engine for GEO Radar and SEO Consultant with just a DeepSeek key, and a reading of your page as an AI engine sees it.
Who changed this title, and what was there before?
If you use AI for SEO, you make a lot of changes quickly, and sooner or later one of them does not convince you. SEO history records every change to an SEO title, meta description, focus keyphrase and slug, and shows it in its own item in the AISA menu, right before the usage report. It is also in the editor, in a box that appears as soon as a content has changes.

Before, after, who and from where
For each change you see the date, content, field, old and new value, and the user. Below the name is the source: Editor, One-Click / Bulk, SEO Doctor, Find and replace, REST API, AI client (MCP), WP-CLI, scheduled task.
One click, and the value is back
Restore puts the previous value back in the active SEO plugin, or in AISA if it works on its own. The restore goes into the history too, so you can undo that as well.
Its own table, no extra weight
The history lives in a dedicated table, never in the options loaded on every page, and it stays if you uninstall the plugin. It records only what was actually written: a failed write leaves no false rows.
One rule for a whole folder, but only if it works
Settings → Redirects & 404 now has three rule types: exact, wildcard and regex. A wildcard like /old-blog/* to /blog/$1 moves a whole folder. A regex like ^/news/(\d+)$ to /articles/$1 handles the more particular cases.
Write the rule
Choose the type, then from and to. With a wildcard or a regex you must also give an address to try it on: it is required.
AISA tries it
It checks that the rule is valid and matches the address you tried, then tells you where it goes. If there is a problem it does not save, and it says why.
It applies to 404s only
Rules fire only on pages that would be a 404, so a page that exists is never touched. If there is an exact rule, that one wins.

- Rules that are too broad:
/*or.*would catch almost the whole site. - Invalid regex and rules over 200 characters.
- Loops: a destination equal to the start, or one that falls back into the same rule.
- External destinations built from the address:
https://$1no,https://example.com/$1yes.
- Edit: change an entry without deleting it, and its visit count stays.
- Import CSV: from, to and code columns, up to 1 MB and 5,000 rows. Existing redirects do not change, and at the end you see how many were added, already there or not valid.
- Export CSV: the whole list, types and visits included.
- Saved rules come first: before, with plugins such as NextGEN Gallery, the WordPress URL guess could run ahead of a saved rule.
Thirty 404s in one folder are a single problem
After a migration, the 404 log becomes a very long list of similar addresses. Now two or more pages in the same folder become a group, such as /catalog-2023/*, with the total requests. "Create redirect" already proposes the wildcard rule. "Ignore" removes an address or a folder you do not care about from the log, and you can always bring it back.

The AISA sitemap now lists images too
The WordPress sitemap does not list images. When AISA serves the sitemap, each page now shows its own, and the option is already on: you find it in Settings → Sitemap & Robots. The list is prepared in the background and updated when you save a content, so the sitemap stays fast.
- The featured image first, then those in the text and in galleries.
- Page builders: Elementor, WPBakery, Divi, Beaver Builder, Bricks and Flatsome.
- WooCommerce products and Revolution Slider slides.
- Images outside the media library, for example on a CDN, including lazy-loaded ones.
- Background images, except Revolution Slider slide backgrounds.
- Logo, small icons and graphics from themes and plugins.
- Avatars and tracking pixels.
You choose the address, and AISA works with two more SEO plugins
You can keep the current address, which is the recommended choice, or move to sitemap.xml, sitemap_index.xml or wp-sitemap.xml. robots.txt and llms.txt show only the one you chose, and the old addresses keep answering as long as you leave on the option that keeps them.

| What | What changes | What you need to do |
|---|---|---|
| AIOSEO and SEOPress | "Manage the sitemap with AISA" joins Yoast SEO and Rank Math. The address stays the same, noindex content stays out, and your plugin still does the rest of the SEO | Nothing: it stays off until you turn it on |
| Password-protected pages | They were listed in the AISA sitemap, but show Google only the form. They now stay out | Nothing |
| Section dates | The index shows the last modified date of each section, so search engines can see which one changed | Nothing |
| Non-public sites | A site set to discourage search engines still served a sitemap when no SEO plugin was active. It now follows the WordPress setting | Nothing |
One DeepSeek key is enough to search and to read the web
DeepSeek Search
A new engine for GEO Radar and SEO Consultant: if you only have a DeepSeek key, you no longer need Perplexity, OpenAI or Gemini. It costs $0.75 per 1,000 calls and you see the estimate before it starts. It returns search results, not an AI answer, and AISA says so clearly.
How an AI engine reads this page
In the Clarity panel, a button reads the published page with DeepSeek Fetch and shows how many characters it found and the text. It runs only when you click, costs about $0.00075 per read and is not part of the score.
The other changes
Titles that stopped halfway
A title that ended on part of the focus keyphrase, or on an unfinished phrase, went through unchecked. AISA now tries once more and, if nothing better comes back, warns you.
Descriptions reduced to the keyphrase
When the AI wrote a description that was too long and had no punctuation, only the focus keyphrase could be left. That no longer happens.
Icons and preview
The side panel, Rotation and the SEO fields use the AISA icon set. The LIVE SEO preview stays anchored to the top right corner.
One update, nothing to redo
Update AISA
From Dashboard → Updates or the Plugins page. With automatic updates on, 2.0.9 arrives by itself. If you use AISA Premium, the Premium component updates on the same screen.
The history starts by itself
There is nothing to turn on. It records changes made after the update: it cannot know about the ones made before.
Sitemap: only if you want
The address does not change until you choose. If you change it, submit the new address in Search Console and Bing.
What this version does not do
- The history does not see changes made inside the AIOSEO panel, which saves them in its own table. It does see those made by AISA with AIOSEO active. For categories and tags it records only changes made through AISA, and the slug only on published content.
- We have tried Restore on real sites with no SEO plugin, with Yoast SEO and with AIOSEO Lite. With Rank Math and SEOPress it takes the same path, but we have not tried it on a real site yet.
- CSV import creates exact redirects only: a wildcard or regex rule must be saved with its test, one at a time. You can have at most 50 wildcard or regex rules.
- Listing images helps Google find them, but does not guarantee indexing or ranking. NextGEN galleries are not seen, because they exist only when the page is displayed, and Revolution Slider 7 is not handled yet. Divi, Beaver Builder, Bricks and Flatsome are covered by automated tests, not real sites.
- "Manage the sitemap with AISA" is not available with SEOPress PRO, AIOSEO Pro and the AIOSEO News, Video and Local Business add-ons: we have not tried them yet, and the switch stays off and says why.
- If you later deactivate AISA without an SEO plugin, only
wp-sitemap.xmlandsitemap.xmlkeep working. If you expect that, submit one of those in Search Console. - DeepSeek Search gives search results; it does not tell you whether an AI engine cites you in its answers. Fetch reads only pages reachable from the internet, so it does not work on a local site.
AISA 2.0.9 is on WordPress.org
SEO history, redirects, 404s and the sitemap are in the free plugin. If you already have AISA, update it. If you do not, download it from WordPress.org.
Download AISA freeWhat's new in 2.0.7 · SEO at Claude's command · The complete AISA tutorial
Release notes for AISA 2.0.9, taken from the changelog published on WordPress.org. This version also includes the work planned for 2.0.8, which did not ship on its own. The screenshots come from a test site with demo data. DeepSeek costs are from its price list on 1 November 2026 and are set by the provider. Settings and features of third-party plugins may change.
