SupportFind the fix, then ask us.
Most problems have a fix inside the plugin. Check the docs, then the list of common problems below. If neither solves it, open a ticket and a person on the team will answer.
Read the docs for your agent.
The docs cover setup, every screen and connecting an agent. Most connection questions are answered in the guide for your agent.
I put the fixes first because most of them take two minutes and a ticket takes longer. If your problem isn’t on the list, say so in the ticket and I’ll add it here once it’s solved, so the next person doesn’t wait.
Common problems and their fixes.
Each answer names the exact screen and setting. Start with the connection test: it catches most agent problems in a few seconds.
Open AgentedSEO › Agents › Connections and click “Run test” under “Test the connection”. It checks what an agent outside the site sees: sign-in discovery, the MCP endpoint and whether your host passes the Authorization header. If the header check fails, the server is dropping it: on Apache, add SetEnvIf Authorization “(.*)” HTTP_AUTHORIZATION=$1 to .htaccess, or ask the host.
Ten failed sign-ins from one address in 15 minutes lock that address out of REST and MCP for 15 minutes. Usually it’s an old application password still saved in the agent. Wait 15 minutes, then paste the current one, or create a new connection.
It uses OAuth, so the site has to answer /.well-known/oauth-authorization-server at its root. Most hosts send unknown paths to WordPress and this just works. If it doesn’t, a security plugin or a server rule is blocking that path.
The tool list only shows what that connection is allowed to call. Check what the agent role may do under AgentedSEO › Agents › Role & permissions. If you connected through the official MCP Adapter plugin, agent users can’t use it: connect them to the built-in endpoint at /wp-json/agentedseo/mcp.
It’s probably waiting for you. Open AgentedSEO › Dashboard › Approvals. Some changes always wait, whatever your rules say: robots.txt edits, noindex on a page with traffic, deleting redirects or schema, and trashing or unpublishing.
Open AgentedSEO › Dashboard › Change log, find the change or the whole batch, and click Undo. Content edits come back from their WordPress revision.
That’s conflict mode: AgentedSEO found another SEO plugin and prints nothing so pages don’t get two sets of tags. Deactivate the other plugin, or turn on “Remove other plugins’ SEO output” under AgentedSEO › Tools › Advanced. Verification tags and code snippets still print either way.
Both stay off while Settings › Reading has “Discourage search engines” ticked. llms.txt is also not served in conflict mode, and a real llms.txt file on your server wins over ours. Check that the module is on under AgentedSEO › Tools › Features.
Each part of the plugin can be switched off. Check AgentedSEO › Tools › Features.
They work together. While both are active, AgentedSEO runs sitemaps, 404s, redirects and noindex, and keeps Classic Monks’ redirects in sync. Turn AgentedSEO off and Classic Monks takes those jobs back.
Search Console is built and switched off until its connection service is live. It’s first on the roadmap. Roadmap
No. SEO output, data, approvals and undo keep working. Only updates and support stop.
Still stuck? Open a ticket.
Send the details below and the first reply can be the fix.
Open a ticket
I ask for these details up front so the first reply can be the fix, not a list of questions.