Visiting a WooCommerce product page could open the slide cart, add the product to the cart or redirect to checkout when FunnelKit Cart, Funnel Builder or CartHopper Skip Cart was active.
A database update that kept failing could be retried on every page load.
Robots.txt rules containing colons, line breaks, special characters or a “0” value could look different in the editor preview than in the served file.
Malformed imported robots.txt rules could break the robots.txt editor or the settings import.
Improved access protections in the AI Image Generator: it now only deletes AI-generated images and respects the AI off-switch.
The AI Image Generator now explains why a selected image can’t be edited.
The Edit Snippet button in the SEO Preview could be missing on a homepage that uses the theme’s layout when a Posts page was still set in Settings > Reading.
Post and term titles containing square brackets could break their links in llms.txt and llms-full.txt.
Some dropdowns in the Local SEO and AIOSEO metaboxes, such as Payment Info, Country, Article Tags, Priority Score, Keywords and Redirects, were cut off by the metabox container.
An empty coloured block could appear over the highlighted option in AIOSEO dropdowns.
Focus keywords set on taxonomy terms were missing from the Keyword Rank Tracker’s Import Keywords list.
The Keyword Rank Tracker’s Import Keywords list was capped at 50 keywords and could miss some posts’ focus keywords.
Recipient email addresses in the SEO Alerts settings weren’t saved.
Several settings weren’t imported correctly from Yoast SEO Premium, including breadcrumbs, website name, number of employees, term meta and crawl optimization settings (with their robots.txt rules and the taxonomy feed setting).
Redirects created from a 404 log entry with a space (%20) in the URL could lose the space, so the redirect didn’t match.
AI agents using AIOSEO’s abilities couldn’t read or update SEO data on posts that hadn’t been opened in AIOSEO yet.
Version 5.0.4
New
TruSEO now fully supports Elementor, Divi and WPBakery Page Builder: see issues highlighted right in your layout, jump straight to them, fix spelling mistakes in one click and get AI suggestions without leaving the builder.
Updated
The AI Suite MCP setup now tells you which security plugin or setting is blocking Application Passwords, and how to turn them back on.
Fixed
Page updates could fail and redirect to a 404 page on some sites when TruSEO analysis data grew too large.
Regex redirects could carry the request’s query string into the target URL regardless of the Query Param setting, and encoded characters in the request weren’t always handled correctly.
An asterisk in a regex redirect couldn’t be used as a quantifier, so patterns such as \d* matched more than intended.
Regex redirects now correctly replace capture group placeholders $10 and above.
Redirects now warns about redirect loops when the target URL includes your site’s full domain.
The Lite post editor could request a Pro-only Redirects endpoint when a post’s slug or status changed, causing occasional errors.
The AI Suite (MCP) robots.txt abilities could fail on sites using Crawl-delay or Clean-param rules, and couldn’t create those rules.
Installing the MCP Adapter could fail on multisite subsites.
MCP Adapter install and activation errors in AI Suite showed raw HTML tags.
The Spell Checker flagged all-caps acronyms such as SEO as misspellings, including in words like SEO-friendly.
The TruSEO score was missing from the AIOSEO Details column for users who can’t manage AIOSEO settings.
Optimize with AI could time out on longer posts before the optimization finished.
A PHP warning could appear in the editor on sites where the 5.0.0 database update hadn’t fully completed.
AIOSEO could interfere with themes and plugins that detect the Block Editor when the Classic Editor was in use.
Re-opening the AIOSEO sidebar in the block editor could land on the tab last opened from the pre-publish panel’s Fix link.
The post editor sent duplicate SEO Revisions requests when saving a post.
Site Audit could fail to load on WordPress 5.7 and on sites with debugging enabled.
Typing a page number past the last page in an AIOSEO table loaded one page at a time instead of going straight to the last page.
The Open Graph image database update could fail to finish on some sites.
Empty category archives are now set to noindex when the “No Index Empty Categories” option is enabled.
The sitemap breadcrumb now links to the sitemap index instead of the homepage.
Layout issues with the upgrade prompt in the category and tag editor.
The dismiss button on the meta keywords notice looked broken in the Bricks editor.
The table pagination arrows and the score badge on the SEO Analysis page weren’t vertically centered.
Version 5.0.3
Updated
SEO Revisions comparisons now show the current value of a smart tag when you hover over it, including Custom Field and Taxonomy Name tags.
Removed unused breadcrumb schema code that ran on every page load.
Fixed
AI features now check your available credits before sending a request, and AI schema generation always uses the schema credit cost.
The AI Bulk Generator and the Media Library’s Generate Alt Text with AI action now tell you when generation fails, for example when you’re out of AI credits.
Improved security and access protections in the AI Image Generator and Markdown (.md) versions of posts.
Regenerating an image from an earlier result in the AI Image Generator now works for everyone who can edit the post, and AI permission errors in the REST API return the correct status code.
The AI Suite MCP setup could show as complete on sites where another plugin bundles the MCP Adapter library.
The Back to Posts link in the AI Bulk Generator now returns you to the same list view, and some links in the plugin interface now open in a new tab.
Homepage SEO data could be incomplete or incorrect when a theme uses a custom homepage layout.
The AIOSEO editor now works when editing a WooCommerce product in Elementor, and the AIOSEO button no longer stays on screen when editing a theme template or Site Settings.
WPBakery and Avada elements could run twice on the front end and break layouts, tabs and forms.
Auto-generated descriptions could miss or mix up text from WPBakery and Avada elements.
Markdown (.md) versions of posts and llms-full.txt could show content from the wrong post, or breadcrumbs and other content from the 404 page.
Markdown (.md) versions of posts and llms-full.txt now keep tables and code samples, and no longer include XML declarations, embedded icon data or HTML tags.
Markdown (.md) URLs could return a 404 or the wrong post for posts with non-Latin slugs, on subdirectory installs, on sites with more than 50 posts, or when a post shares its slug with a custom post type item.
The Markdown (.md) version of a post could fail to generate when a link contained many inline SVG icons, and Divi 5 posts were processed twice.
llms.txt now shows the site description as a blockquote with HTML entities decoded, and descriptions from legacy Divi builder content no longer include shortcode tags or encoded characters.
The llms.txt and llms-full.txt files could be left behind after uninstalling AIOSEO, turning off LLMs.txt or resetting settings, and llms-full.txt could be generated again after being turned off.
Breadcrumb fields in the REST API now respect per-term breadcrumb settings, and a breadcrumb template with a page-number or search tag no longer causes an error.
The AIOSEO Breadcrumbs and Table of Contents blocks could fail to load in the Widgets and Customizer editors.
The Link Format options in the block editor now work on WordPress 6.5 and earlier, and typing a link title before the URL no longer stops the editor from working.
The Network Admin Robots.txt Editor now previews each site’s own rules and sitemaps, and no longer removes a site’s custom rules when you save while they’re loading.
Managing settings backups for another site in Network Tools could affect the wrong site’s settings.
robots.txt could return an error when a saved rule had an invalid value; that rule is now skipped.
The REST API now returns an error instead of silently ignoring SEO changes from users without SEO permissions, or saving “Array” when the legacy _aioseop_title and _aioseop_description fields get a value that isn’t text.
Redirects created automatically for trashed or deleted posts could point to the homepage or replace a redirect you had already set up, and restoring a post from the trash could remove its redirect.
SEO Analysis could get stuck on, or report false issues for, pages with an empty response or no visible content.
Scheduled SEO Analysis scans could keep failing in the background, and scans now run on network-licensed multisites.
Uninstalling AIOSEO now also removes capabilities added by older versions, and deleting Lite and Pro together no longer leaves empty tables and options behind.
SEO Alerts no longer flags an empty sitemap, such as a News Sitemap with no recent posts, as an error, and sitemaps that don’t exist, are disabled or are past their last page now return a 404.
Background “Unescape data” tasks could be cancelled on AIOSEO Lite.
Link Assistant domain icons now show a fallback icon instead of a broken image when a site’s icon can’t be loaded.
Display issues in the Search Statistics Index Status chart.
Version 5.0.2.1
Fixed
Improved security protections for shortcodes on search pages.
The Elementor editor could get stuck on “Loading” on some hosts when Redirects was active.
Version 5.0.2
Updated
The minimum required PHP version is now 7.4.
Reduced duplicate database queries on admin page loads.
The mobile tabs dropdown now has a visible border, so it no longer blends into white backgrounds.
The Taxonomy Name smart tag now shows a taxonomy-specific input placeholder.
Fixed
Rating values could appear as text instead of numbers when comparing SEO Revisions.
An unchanged rating could lose precision when comparing SEO Revisions.
The SEO Revisions comparison could appear blank for a post’s first revision.
A conflict with a third-party plugin that could cause the editor to reload repeatedly on pages using certain blocks.
The Default 404 Redirect no longer redirects plugin, theme and core asset requests when set to an external URL, which could cause errors during plugin updates.
The 404 log was missing requests for assets such as images, scripts and stylesheets.
The canonical URL and og:url could point to an incorrect address on paginated static front pages.
The next-page link on a paginated static front page could point to an invalid address.
The llms.txt file now follows the llms.txt specification more closely.
Special characters could appear as HTML codes in the llms.txt site title and description.
Sitemap settings for content excluded from search results are now disabled.
Taxonomies and the HTML sitemap now honour the site-wide No Index setting.
The llms.txt file now leaves out taxonomies set to No Index.
An excluded parent term with no posts of its own wasn’t actually excluded from the sitemap.
Terms excluded under Sitemap Advanced Settings could still appear in the sitemap, along with the posts assigned to them.
The HTML Sitemap could show no publish date for a term, and sitemap index dates could be wrong.
RSS sitemap entries could be ordered incorrectly because dates were mis-compared.
Posts using the default priority could be ordered below lower-priority posts in the sitemap.
Pages could be reported as not indexed in Search Statistics on sites using TranslatePress with a subdirectory on the default language.
Search Statistics could keep an old page path after the address changed, such as following a parent page slug change or the removal of a static front page.
Posts and terms could be missing from the Index Status report when they shared the same numeric ID.
A PHP warning that could appear when AIOSEO Lite’s files were removed while still marked active.
TruSEO analysis in the Divi builder could include Theme Builder template content and the builder’s own interface in the analysis.
An error and broken term links that could occur when a category or tag had a deleted parent.
Divi 5 front-end styling could be affected on some pages when AIOSEO generated meta descriptions automatically.
An error that could occur when loading robots.txt on Multisite with AIOSEO Pro network-activated.
Robots.txt rules set at the network level are now included in each site’s robots.txt file.
The robots.txt file and the Robots.txt Editor could stop working when a rule had been saved in an invalid format.
The robots.txt Editor could show blank rows for stored entries that aren’t rules.
A robots.txt rule added through the AI tools with an unusable user agent is now rejected instead of stored.
The Regenerate TruSEO Score bulk action could clear focus and additional keyphrases.
The Regenerate TruSEO Score bulk action was offered in list views where the score couldn’t be recalculated, leaving it at 0.
A subsite’s Search Appearance settings could be reset when saving robots.txt settings from the Network Admin.
Saving network robots.txt settings could change a site’s robots.txt toggle or clear its stored rules.
Network Tools requests could apply settings to the wrong site on Multisite.
Exporting another site’s content could save the current site’s settings into that site’s database on Multisite.
Viewing another site in the Network Admin Robots.txt Editor could overwrite the current site’s Search Appearance settings.
Archived, spam and deleted subsites no longer appear in the Domain Activations list or network site selectors.
PHP deprecation notices when searching the Domain Activations list on Multisite.
The AI credit balance could show as zero after generating content.
The Pay-As-You-Go credit breakdown could disappear from the AI credit counter after generating content.
The Home breadcrumb link now includes a trailing slash in both the breadcrumb trail and its schema.
The site SEO audit could report the sitemap as disabled while it was enabled.
The AI Suite MCP setup page didn’t show the new Application Password in the client snippet.
The Block Settings panel of the AIOSEO blocks could appear empty after reopening it or switching sidebar tabs.
The AIOSEO button in the Thrive Architect sidebar now shows its label when the sidebar is expanded.
The Post Excerpt smart tag now shows the real excerpt in the Avada and WPBakery editors.
Archives didn’t output their configured meta keywords when dynamic keyword generation returned nothing.
PHP warnings and a missing keywords meta tag when a keywords setting held a list of plain text values.
A custom title separator using < or > could appear as an HTML code.
Email reports showed a green up-arrow on Top Losing rows that had a positive change in clicks.
Errors that could occur when inserting the Local SEO and HTML Sitemap blocks in the block editor.
In the AIOSEO Details column quick editor, Save and Discard affected both the Title and Description instead of only the field being edited.
Posts and pages couldn’t be removed from the Exclude Posts / Pages field when the list was taller than the browser window.
A link’s title attribute could be applied to other links in the same paragraph in the block editor.
SeedProd page detection no longer treats a post as page-builder content after SeedProd is deactivated.
The Facebook image could appear in the Twitter preview, and vice versa, in the Social snippet preview.
Improved security and access protections in SEO Revisions, SEO Analysis and the SEO Preview.
Version 5.0.1.1
Fixed
The link toolbar’s nofollow, sponsored and UGC options were missing from the editor, and the Classic Editor’s Insert/Edit Link dialog did not open.
The link toolbar could crash the block editor on WordPress 6.5 and older.
Links were saved with an empty title attribute, and the title field could be cut off in the link popover.
Version 5.0.1
New
TruSEO content analysis for taxonomy terms, starting with WooCommerce product categories.
Fixed
SEO Analysis now shows a clear “Preview unavailable” message when a firewall blocks the homepage or competitor screenshot.
Sitemap image URLs being duplicated on WordPress subdirectory installations.
Redirects no longer create cache entries on sites that don’t use the Redirects feature.
Overlapping redirects now apply in the correct order.
A textdomain loading notice that could appear when checking for addon updates on WordPress 6.7 and later.
Table of Contents block sometimes reset custom heading text and pointed to incorrect links.
Added a warning when a redirect’s destination URL contains invalid characters in the domain.
Redirects from child pages to parent pages not working for smart 404 redirects.
Version 5.0.0.1
Updated
Made Search Appearance and Social Appearance cards in metabox collapsible.
Fixed
Focus keyword and additional keywords sometimes not appearing in TruSEO after 5.0.0 update.
Resurfaced missing product ID, SKU and image alt text checks in TruSEO.
Version 5.0.0
New
TruSEO just got a major revamp — it’s smarter, faster, supports 10+ new languages and has a new modern UI.
TruSEO Highlighter revamp — an improved editor highlighter that flags issues TruSEO found, working seamlessly across the Block Editor and Classic Editor (page builder support coming soon!).
Spell checker – automatically detect spelling mistakes directly in the editor as you write and fix them instantly.
Optimize posts with AI – let our smart AI assistant automatically optimize your post for SEO by improving your SEO title, meta description, headline, keyword checks and spelling mistakes in just one click!
Actionable AI-powered fixes for TruSEO — let AI help you rewrite sentences or paragraphs to fix readability and SEO issues in your content.
Updated
AIOSEO blocks to add support for WordPress 6.3+ iFrame editor.
Fixed
MCP setup snippets for Claude Desktop, Cursor, and Gemini CLI so the connection no longer fails.
Version 4.9.10
New
Added a new ability to list terms that are missing SEO data.
Fixed
PHP 8.5 deprecation notice when decoding HTML entities from empty content.
High CPU usage caused by the translations check on sites with large user tables.
Fatal error in breadcrumbs on PHP 8 when a third-party plugin added an invalid entry to the breadcrumb trail.
PHP error in redirects when a request URL contained array-style (bracketed) query parameters.
Keyword density displaying “Infinity%” in the TruSEO analysis when the content had no readable text (e.g. some Divi pages in the block editor).
Various security hardening improvements across the plugin.
Cookie Consent
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
These cookies are used for managing login functionality on this website.
Name
Description
Duration
wordpress_logged_in
Used to store logged-in users.
Persistent
wordpress_sec
Used to track the user across multiple sessions.
15 days
wordpress_test_cookie
Used to determine if cookies are enabled.
Session
WPForms is a user-friendly WordPress plugin for creating custom forms with drag-and-drop functionality.
Name
Description
Duration
wpfuuid
Used to track user interactions with forms.
11 years
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
TruSEO issues now show up right on your Elementor, Divi, or WPBakery layout. It’s the same set of tools you’ve been using in the block editor, now in your favorite page builders.
What’s included:
Issue highlighting: TruSEO marks problems right on your layout, and the “found” links jump you straight to each one
Spell Checker: fix typos in 1 click, or add a term to your dictionary
Suggest a fix: apply AI rewrites directly to your content (requires AI Credits)
Supported editors: Elementor V3 and V4, Divi 4 and Divi 5, and WPBakery’s frontend and backend editors
Broken Link Checker 1.3.1 expands what it scans beyond posts and pages, catching broken links in corners of your site you’d never think to look. Here’s what’s new:
Navigation menus: every link in your header, footer, and custom menus gets scanned
Custom fields and author bios: 2 places broken links used to hide completely
Page builder support: Elementor, Divi, SiteOrigin, Avada, and WPBakery content is now checked automaticall
Oh, and synced patterns and templates? Those are covered, too.
Broken Link Checker’s new dashboard organizes your broken links by priority, worst domains, and distribution across your site, so you know where to start.
Fix-first priority view: see which broken links to tackle first instead of working through an unsorted list
Worst domains: spot the external sites with the most broken links pointing at your content
Broken link distribution: see how broken links are spread across your site
The new dashboard is available on every BLC plan, including Lite.
Broken Link Checker now emails you within a week if a link on your site breaks, plus sends a full monthly summary of all links analyzed, so you don’t have to log in and check manually.
What’s included:
Weekly alert: hear about a new broken link within about a week of it breaking, no checking required
Monthly summary: a full report of every link checked that month, sent either way, broken or not
Independent from scan frequency: your scan schedule and your email reports run on separate tracks
Multiple recipients: send reports to your own address, teammates, or clients right from settings