How it works
Install, audit, review. The assistant comes last.
The whole loop: install, audit, review the diffs.Connect an assistant last, if you connect one at all.
The loop
Four steps, in order
The first three involve no AI at all. By the time an assistant is connected, you have already used the review queue on your own work and know exactly what it shows you.
- 1
Install
Add WP Visibility to any site running WordPress 7.0 or newer on PHP 8.1. Importers for Yoast, Rank Math, SEOPress, The SEO Framework and All in One SEO show a dry run before a single value changes, and they never delete the source data, so going back is always possible.
- 2
Run the audit
One button reads your own published posts and fills the review queue with fixes in priority order. Nothing is connected yet: this is the plugin checking your site against its own rules, so you watch the review flow work before any assistant is involved.
- 3
Review the diffs
Every proposal is a field-level before and after, with the reason attached. Approve it, reject it, or clear a batch in one pass. A proposal that has gone stale refuses to apply rather than clobbering an edit you made in the meantime.
- 4
Connect your assistant
Optional, and last on purpose. Turn on the built-in connection and Claude, ChatGPT or whatever your team already pays for can operate the same controls you just used by hand. Everything it proposes lands in the queue you have already been clearing.
The connection
Where the assistant fits
The connection is built in
The plugin ships with an MCP connection at /wp-json/wp-visibility/mcp. There is nothing extra to install and no vendor AI to adopt. Any assistant that speaks MCP can use it, so the tool your team already pays for is the tool that does the work.
What the assistant gets is the same set of controls you use in the admin, with one difference: the seven write abilities do not write. They create a proposal.
The queue is the whole mechanism
A proposal shows the field, the value that is live now, the value the assistant wants to put there, and the reason it gave. You approve one, reject one, or clear a batch in a single pass.
Approving is the only thing that writes to your site, and only a signed-in human can approve. A kill switch pauses everything at once, an hourly write budget caps how much can change while you are not watching, and a hash-chained log records every call.
The limits
What the agent can never do
Four limits enforced below the layer the assistant talks to. They are not settings, so there is no instruction, clever or otherwise, that reaches them.
- 01
It cannot publish
Drafts stay drafts. Post status is untouchable, and no path through the plugin publishes anything.
- 02
It cannot approve its own work
The approve ability ships disabled. That is the point of the queue, not an oversight.
- 03
It cannot enable its own modules
Module toggles, the license key and the uninstall flag are all rejected. It never sees credentials.
- 04
It cannot resume after the kill switch
It can stop itself and everything else. Only a human starts it again.
Underneath all four: a hash-chained audit log of every call, and an hourly write cap applied per user and per connected client.
Ways of working
Run it your way
The connection is a door, not a requirement. Three ways of working, one plugin.
By hand
Never connect an assistant and WP Visibility holds up as a classic SEO plugin: title and description templates, redirects, XML sitemaps, schema, social cards, breadcrumbs, llms.txt and AI-crawler controls, all managed from the admin you already know.
By assistant
Hand the routine work to your assistant and clear the review queue once a week. You delegate the work without giving up the final word on any of it.
Both
The two are not exclusive. Keep the settings you care about under your own hand and let the long tail arrive as proposals.
Every way of working comes with the same license: $99 a year, unlimited sites, client sites included, with a 30-day refund.
Start with the scan
The scan is the fastest way to see what this does. It takes about 30 seconds, and nothing on your site changes until you install the plugin and approve a diff yourself.