Changelog

The release history for the WP Visibility WordPress SEO plugin, newest first. Every release requires WordPress 7.0 or newer and PHP 8.1 or newer.

2.10.2 (August 9, 2026)

A fix to the optional Assist module, which stays off unless you turn it on. Asking it for a suggestion returned an error instead of an answer, because it was reading the AI provider’s reply the wrong way. It now asks for text properly, and if a provider sends back something unexpected you get a clear message rather than a failure with no explanation.

2.10.1 (August 9, 2026)

Code samples stay code samples. A post explaining a shortcode such as [gallery] ran the shortcode on the front end and published a gallery instead of showing the text, and a bare URL on its own line inside a code block turned itself into an embed. Code an assistant writes is now escaped the way the block editor escapes it, so what you wrote is what your readers see.

2.10.0 (August 3, 2026)

The Review queue can fill itself. A new button on the queue runs the audit on demand: it reads your published posts and queues a proposal for the ones with no meta description, each one drafted from that post’s own content. Nothing is applied until you approve it, and the run is limited to once a minute. This matters most on a fresh install. The weekly audit is off by default, so a new queue was empty with no way to fill it from the admin screen, and the only route to a first proposal was connecting an AI assistant. That left the queue and its before-and-after diff, the part of the plugin most worth seeing, out of sight until after the most technical step of setup. The button sits in the queue toolbar and in the empty queue itself.

2.9.1 (August 1, 2026)

A correctness pass over 2.9.0, from a full adversarial review of the release. Fourteen fixes, three of which corrected behavior that did not match what the previous release said it did: creating a draft of certain post types could produce something publicly visible, the protection against overwriting a post someone had open in the editor never ran when an assistant made the request, and backslashes were being stripped out of saved drafts, which corrupted code samples and Windows file paths. The check that refuses to rewrite content it cannot safely reproduce now looks at structure rather than block type alone, so nested lists, lists inside quotes, inline images, shortcodes and custom list numbering are refused with a reason instead of being quietly flattened. Content with Windows line endings no longer skips those refusals, posts with eleven or more code blocks are no longer corrupted when rewritten, and mentioning an HTML tag name in inline code no longer makes the whole post un-editable by an assistant.

2.9.0 (July 27, 2026)

Your assistant can write drafts. Ask it for a post and it arrives in your editor as a real, properly formatted draft, not as a wall of literal markdown characters or one unparsable block that gets worse every time you open it. That difference is the whole feature: the WordPress block editor stores content in its own annotated format, and anything pasted in another way lands broken. It writes drafts only. A published post is refused, nothing here can change a post’s status, and the publish button stays yours. It also refuses rather than guesses: images, tables, nested lists and raw HTML are declined with an explanation instead of being approximated, and a draft containing anything that would not survive a rewrite is left alone. Reading a post for an assistant also stopped throwing away links and formatting, so it can finally see the internal links you are asking it about.

2.8.1 (July 27, 2026)

A correctness pass over the last four releases, from a full adversarial review of our own recent work. Twelve fixes, none of which change how anything is meant to behave: applied proposals no longer carry a “content changed since proposed” warning they earned by being applied at all; the Review queue keeps your keyboard position when you move through it while an approval is still saving; bulk proposals keep their loaded diff when the list refreshes; clearing a redirect search that matched nothing no longer removes the search box you are typing in; and reduced-motion preferences now switch off the press animation, which the previous release claimed and did not do. On the account side: a refunded license no longer reports itself as active with a renewal date, the plugin download link no longer dead-ends when your session has lapsed, and the setup instructions now name the correct menu path.

2.8.0 (July 26, 2026)

The Review queue stops blanking. Approving or rejecting a proposal used to replace the entire list with a spinner: every row unmounted, your keyboard position was lost, and all twenty rows re-fetched their details. The list now updates in place and keeps your place in it, so working down a queue with j, k and a is a continuous rhythm rather than a series of page flashes. Proposals also arrive ready to act on, because the diff a reviewer needs now travels with the list instead of loading one request per row afterwards, and approving something tells you what it was (“Description updated.”) so the Undo beside it is usable when you are moving fast.

2.7.2 (July 26, 2026)

Three fixes from a study of how the admin screens feel to use. Activating a license used to clear the key field even when activation failed, so a typo or a brief network problem wiped the key you had pasted a moment earlier and sent you back to your email for it; it now stays put unless it worked. The count of proposals waiting for review moved to the top-level WP Visibility menu item, so you can see work waiting from anywhere in wp-admin, and it appears only when something is waiting. And buttons and toggles now respond the instant you press them instead of waiting for the server, which matters most on slow hosts and on touch screens, where there is no hover state at all.

2.7.1 (July 20, 2026)

A pre-launch sweep, plus a Redirects fix. The Redirects page now shows the add form up front, with source, target, status and the regular-expression toggle visible, instead of hiding it behind an “Add redirect” button that sat beside the search box and read like a search submit; search moved down with the list of rules, where it belongs. Two links that pointed at pages which do not exist were also corrected.

2.7.0 (July 19, 2026)

Redirects get their own page. When the Redirects module is on, the manager now lives directly in the WP Visibility menu instead of inside the settings screen. A redirect list is content you manage, not a setting you configure: it grows with your site and you read it like a table, so it earned the same promotion the Review queue got in 2.3.0. Nothing about the rules changed: same manager, same CSV import, same REST routes and assistant abilities. The WordPress command palette gains a matching jump straight to the page, and opening this page or the Review queue with its module off now shows a pointer to the module toggle instead of an access error.

2.6.3 (July 16, 2026)

Two editor fixes from the fourth audit pass. The Heading structure check had it backward: it warned on a correctly structured post, where the theme renders your title as the page’s only H1, and passed once you added a second H1 in the body, which is worse for your SEO. It now passes on the correct state. And a canonical or redirect URL typed without https:// or a leading slash now warns inline that it will not be saved as written, instead of vanishing silently on save. The same pass swept every change since 2.5.0 for regressions and found none.

2.6.2 (July 15, 2026)

Your site’s own choices win. WordPress’s Discourage search engines setting is no longer overridden by the plugin, so staging and pre-launch sites stay out of the index. The AI Traffic Lens, Link Graph, and activity log tables now retry when a host refuses to create them, instead of permanently marking themselves done. Uninstalling no longer leaves the agent kill switch behind to pause a fresh reinstall, and Revert on an applied proposal now says plainly that it discards later edits to the same fields.

2.6.1 (July 15, 2026)

An honesty release. The submit-indexnow ability had never worked; it now does, and reports real errors. A redirect or canonical typed without a scheme, like new-page, was being rewritten to http://new-page and accepted as a real off-site URL; schemeless values are now rejected on every surface: the admin screen, the REST API, your assistant, and per-post fields. Creating a redirect through your assistant now works on sites set up entirely over the command line, and the 451 status code the documentation promised is accepted.

2.6.0 (July 15, 2026)

The redirect manager arrives in the admin. When the Redirects module is on, you get a searchable, paged list of your rules with hit counts, add and inline edit, delete, and a CSV import that reads Redirection and Rank Math exports, with a dry-run preview that writes nothing. The redirect engine itself had already shipped; until now it was reachable only over REST or your AI assistant. A new rule whose target is another rule’s source warns about the chain when you create it, not after visitors find it.

2.5.0 (July 14, 2026)

The Import screen arrives. Pick a detected source (Yoast, Rank Math, SEOPress, The SEO Framework, or All in One SEO), preview exactly what would change with word-level diffs on a sample, then run the import with live progress and a Stop button. Previously the importer ran only over WP-CLI, REST, or your assistant.

2.4.4 (July 11, 2026)

The Modules toggle list now follows the sidebar section order, so each switch sits in the same order as the section it controls.

2.4.3 (July 11, 2026)

The admin content column widens further, to 1800px on large displays.

2.4.2 (July 11, 2026)

The settings and Review queue screens use your screen: the content column widens from 1100px to 1440px on large displays, bounded so forms never sprawl on ultrawides.

2.4.1 (July 11, 2026)

The admin learns to show its work. The plugin now holds every agent change for your review by default, on new and updated installs alike, and the Review queue gains a status header with the pause switch, the guard mode, the hourly write budget, and the assistant’s last activity, plus an Activity log tab where the tamper-evident record is verified in plain sight. Diffs highlight the exact words that changed, approving carries a 10-second Undo, and the whole queue works from the keyboard: j and k to move, a to approve, r to reject. Assistants can now attach a reason to each proposal, so you see why a change was suggested before you decide. A review pass before release corrected a series of races, screen-reader gaps, and contrast misses found by the same approve-then-verify process the queue itself uses.

2.3.1 (July 10, 2026)

Bulk approve and bulk reject arrive in the Review queue. Select proposals with per-row checkboxes or select all, confirm the count, and clear a busy queue in one pass. Every item in a batch still passes the same per-proposal safety checks, so a proposal whose target changed since it was written is skipped and reported, never forced through.

2.3.0 (July 10, 2026)

The Review queue is now its own admin page under WP Visibility, with a pending count bubble in the menu like the one WordPress shows for comments. Waiting proposals are visible from anywhere in wp-admin, and you review them on a dedicated screen instead of next to unsaved settings. The queue opens on the proposals that need your attention, so the page always matches the number in the menu.

2.2.1 (July 9, 2026)

Long values in the Review queue, such as an llms.txt body or a block of custom schema, now collapse behind a Show more toggle, so a document-sized proposal no longer crowds out one-line changes. Proposals that target a post also link to that post’s editor for context.

2.2.0 (July 9, 2026)

The Review queue gets a face in wp-admin. When Autopilot holds agent changes for your review, each proposal now appears with a field-level before-and-after diff and Approve, Reject, Refresh, and Revert actions. Before this release the queue was reachable only from the command line or the REST API, which asked far too much of a normal admin.

2.1.0 (July 9, 2026)

The plugin gains a built-in MCP endpoint at /wp-json/wp-visibility/mcp. Your own AI assistant, whether Claude, ChatGPT, or any other client that speaks MCP, now connects to the plugin directly with a WordPress Application Password and no extra plugins. Every safeguard applies unchanged: permissions, the hourly write budget, the kill switch, and the tamper-evident log.

2.0.2 (July 9, 2026)

This update fixes a bug that stopped the plugin’s agent abilities from registering on WordPress 7.0, a fault that left the entire agent surface unavailable without an error. It also corrects release metadata so the update channel serves the right package.

2.0.1 (July 9, 2026)

The Autopilot module description on the settings screen now names both halves of the module: the review queue for agent changes and the optional weekly audit. It also states plainly that holding changes for review is a choice, not the default.

2.0.0 (July 5, 2026)

The first public release; earlier development builds are rolled up into this version. A final hardening pass tightened security and correctness across the plugin: stricter escaping of everything printed to the page, tighter permission rules for redirects, reliable SEO fields on custom post types, a sturdier redirect manager, a hardened approval flow for agent proposals, network-safe cleanup on uninstall, and dependable update delivery. The settings screen also gained the controls the engine already honored, including title and description templates, site verification fields, per-post-type indexing choices, an llms.txt editor, an agent kill switch, and one-click links to your live sitemap, robots.txt, and schema output.

Docs and support

Every feature named above is covered in the WP Visibility docs. If an update behaves badly on your site, write to support@wpvisibility.com.