Everything WP Visibility stores stays on your own site, nearly all of it in the database. Deactivating the plugin changes nothing stored. Deleting it from the Plugins screen also keeps everything, unless you turn on Delete all plugin data on uninstall first, in which case every row listed below is removed.
What is stored
Options
| Name | Holds |
|---|---|
wpvis_settings |
Your settings, stored as the differences from the defaults, including the license key |
wpvis_state |
Internal state: license status cache, sitemap cache version, any custom llms.txt text, the IndexNow key, which abilities are switched off, table versions, activity log bookkeeping |
wpvis_agent_paused |
The assistant kill switch, when it has been used |
Post and term meta
| Key | Holds |
|---|---|
_wpvis on posts |
One serialized row per post with its SEO fields: title, description, canonical, indexing, social, schema and redirect. A post that was never customized has no row. |
_wpvis_noindex on posts |
A flag present only on posts individually set to noindex, so sitemaps and llms.txt can skip them quickly |
_wpvis on terms |
One row per customized category, tag or other public taxonomy term with its title, description, canonical, indexing and social image |
Tables, each created only if its module was ever turned on:
| Table | Module |
|---|---|
wpvis_redirects |
Redirects |
wpvis_links |
Link Graph |
wpvis_lens |
AI Traffic Lens |
wpvis_agent_log |
Assistant connection (the activity log) |
Everything else
- Review queue proposals are private posts of the type
wpvis_proposal, with their own meta. They are never public, and the WordPress export tool leaves them out. - Short-lived caches are transients whose names start with
wpvis_: sitemap files for up to a week, the schema map for 12 hours, and a few counters and locks that last between one minute and one hour. - The Autopilot Weekly audit, when switched on, is the one scheduled event,
wpvis_autopilot_audit. - No user meta is written. The “Get started” panel remembers that you dismissed it in your browser, not in the database.
What it sends
Two outbound requests, both to wpvisibility.com: the update check and license activation. The IndexNow module, when on, adds submissions to the IndexNow endpoint. The experimental Assist module, when on, sends a post’s title and excerpt to the AI provider configured in your WordPress AI Client when a user who can edit that post requests a draft. The full list, generated from the installed code, is public on every site at /wp-json/wpvis/v1/privacy-manifest and prints with:
wp visibility privacy
wp visibility privacy --format=jsonDeactivate, delete, remove data
| You do | What happens to the data |
|---|---|
| Deactivate on the Plugins screen | Nothing. The output stops; everything stays. |
| Delete, with the default settings | Nothing is removed. A reinstall picks up where it left off. |
| Turn on Delete all plugin data on uninstall, then delete | Everything listed above is removed |
The toggle is in the Advanced section of WP Visibility → Settings. Turning it on shows a warning that there is no undo. The assistant abilities and the review queue cannot turn it on; the setting is protected there. The plugin’s own settings REST route accepts it from any administrator, so an assistant connected with an administrator’s Application Password can still change it that way.
When it is on, deleting the plugin removes the two options and the kill switch, every wpvis_ transient stored in the options table, the _wpvis and _wpvis_noindex post meta, the _wpvis term meta, the four tables, every review queue proposal, and the scheduled audit. Take a database backup first.
Multisite: each site decides for itself with its own toggle. A network administrator can force removal on every site by adding this to wp-config.php before deleting the plugin:
define( 'WPVIS_DELETE_DATA_ON_UNINSTALL', true );Two things are not reached: caches held only in a persistent object cache such as Redis, which expire on their own, and the dismissed flag in each browser. With such a cache, WordPress may keep transients there instead of in the database (Transients API, checked September 27, 2026).
Leaving for another plugin? Copy what it cannot read first: Move to Another SEO Plugin.
Behavior checked against WP Visibility 2.10.3.