Start with the Activity log tab. If the call is there with a successful outcome and a proposal ID, the proposal exists and the queue’s filter is hiding it. If the call is there with an error, the outcome tells you why nothing was queued. If the call is not there at all, the assistant did not go through the plugin, and what it changed, if anything, went through a WordPress route the queue does not see.
1. Check the filter
On the Proposals tab set Show to Needs review. Approved and rejected proposals are under their own filters. The menu count can lag by up to a minute after a proposal is created.
2. Check the three settings
Proposals are created only when all three hold:
- The Assistant connection module is on (Settings → Modules).
- The Autopilot module is on.
- Assistant changes is set to Hold for my review. With Apply immediately selected, supported writes are applied at once and never appear as proposals; look for them in the activity log instead.
3. Check what the assistant actually called
Seven abilities create proposals: updating a post’s SEO fields, bulk SEO updates, settings changes, creating a redirect, deleting a redirect, editing llms.txt and changing the AI crawler policy. Anything else does not, by design:
- A bulk dry run is a preview. It executes as a preview and creates nothing.
- Creating or editing a draft is content work and is separate from the SEO queue.
- Imports run directly.
- A change made through the core WordPress editor or the core REST API, which an administrator credential can reach, is not a plugin ability and is never queued. The activity log will not show it either.
Ask the assistant which tool it used. If it used one of the seven, the activity log has the row.
4. Read the outcome in the log
| Outcome | Meaning |
|---|---|
agent_paused |
The assistant is paused. Nothing was queued or written. |
module_disabled |
The module that owns the ability is off. |
wpvis_forbidden |
The connecting user lacks the capability for that ability. Post SEO needs edit rights on the post; settings, bulk updates and redirects need an administrator. |
| A rate limit (HTTP 429) | The hourly write limit was reached. Nothing was written. |
| A proposal ID | The proposal exists. Go back to step 1. |
If the queue itself will not load
“The review queue could not be loaded.” means the page’s own request to /wp-json/wpvis/v1/ failed. Confirm you are still logged in as an administrator, then look for a security plugin or firewall blocking that path, and click Try again.
Still stuck? Write to support@wpvisibility.com with the activity log row and your plugin version.