Fixes
Everything our scanner can report, and how to fix each one yourself. No account needed, nothing held back.
- Your robots.txt asks every crawler to stay away from the whole site
critical A single line is telling all crawlers — search engines included — to ignore your entire site. - Your server turns AI crawlers away
critical Your site serves browsers normally but refuses crawlers like GPTBot and ClaudeBot. Here is how to find what is doing it and undo it. - A robots.txt file is overriding your SEO plugin
high Your site has a real robots.txt file on disk, so every robots setting in your SEO plugin is being silently ignored. - Your robots.txt asks the crawlers that answer questions to stay away
high You are blocking the crawlers that fetch pages so AI assistants can cite them — which is how a site disappears from AI answers. - Your security plugin is blocking AI crawlers
high A security plugin on your site has rules naming AI crawlers. Here is where those rules live and how to decide what to keep. - Your server treats all crawlers differently from browsers
high It is not AI-specific — Googlebot is affected too, which points at a different cause and a different fix. - Some of your content never reaches an AI crawler
medium Part of your page is built by JavaScript in the visitor's browser. AI crawlers don't run JavaScript, so they never see that part. - What your site serves is not what WordPress generates
medium Something between WordPress and the internet is changing or replacing your robots.txt. - Your .htaccess blocks AI crawlers, but your server ignores that file
medium You have rules in .htaccess that block AI crawlers, but your web server never reads that file. The rules have no effect at all. - Your robots.txt is a file, so WordPress cannot change it
medium Your site serves a real robots.txt file from disk. Any robots setting in any plugin is being bypassed. - The crawler self-test could not tell you what the internet sees
info The check ran, but from a place where its answer would not mean anything. Here is why, and what to do instead. - This run doesn't count — your own site slowed down our test for sending too many requests too quickly
info The normal browser request we send for comparison got different results before and after the crawler requests, so no comparison from this run can be trusted. - We cannot tell you whether your security plugin turns real crawlers away
info Rules blocking AI crawlers exist on your site, but our test got a normal page — because it comes from an address your security plugin trusts. - Your robots.txt is a real file, written by your SEO plugin
info Not a problem — but it means edits made anywhere else will not take effect.