Open WP Visibility → Review queue, choose the Applied filter, and click Revert this change on the proposal. After you confirm, the plugin puts back the values it recorded just before that proposal was applied. It does not check whether anything was edited since, so later edits to those values are overwritten. The confirmation prompt says so: it discards “any later edits to the same fields.”
Right after approval
The notice that follows Approve offers Undo for a moment. It is the same operation as Revert this change, one click sooner and without the confirmation prompt.
What a revert restores
When a proposal is applied, the plugin first saves a snapshot of the state it is about to change. Revert writes that snapshot back:
- For a post, the snapshot is the post’s whole WP Visibility SEO record (title, description, canonical, robots, social, schema and redirect fields), not only the fields the proposal changed. Revert restores all of them, so a description you rewrote on that post after the proposal was applied goes back to its earlier value too. A bulk proposal does the same for each post it changed.
- For settings, only the setting keys the proposal changed.
- For llms.txt, the on/off switch and the custom content. For the AI crawler policy, the policy as it stood.
- For a redirect the proposal created, revert deletes that row. For a redirect it deleted, revert creates it again with the same source, target, status and regex setting.
If you have edited the post’s SEO fields since the proposal was applied, note your values before you revert and set them again afterwards.
When it refuses
| Message | Meaning | What to do |
|---|---|---|
| “Only applied proposals can be reverted.” | The proposal is pending, rejected, already reverted, or in another state. | Nothing to undo. Check its status in the queue. |
| “No before-state snapshot exists for this proposal, so it cannot be reverted automatically.” | The plugin has no snapshot to put back. | Restore the value by hand. |
| “The created redirect row could not be identified; remove it from the Redirects screen instead.” | The plugin cannot tell which redirect row the proposal created. | Delete the redirect in WP Visibility → Redirects. |
| “A redirect for this source already exists.” | The proposal deleted a redirect, and a redirect for the same source was added since. | Keep the newer redirect, or delete it in WP Visibility → Redirects and revert again. |
| “The Redirects module is disabled.” | A redirect proposal needs the Redirects module to revert. | Turn the module back on, then revert. |
If a revert fails, the proposal stays Applied, so you can try again.
What it is not
A revert is not a rollback of the site or of the post. It restores what one proposal’s snapshot holds, nothing else. Post content, redirects created outside the queue, and changes made through other plugins are out of its reach. Viewing the queue, or running wp visibility proposals list, also deletes resolved proposals, applied ones included, that were proposed more than 90 days ago, and keeps at most 500 resolved proposals; a deleted proposal can no longer be reverted. For anything wider, restore from a backup.
From the command line
wp visibility proposals list --status=applied
wp visibility proposals revert 123The same rules apply and the same messages are printed. The command does not ask for confirmation. On success it prints Success: Proposal 123 is now reverted.