AI crawlers are blocked in robots.txt
1%
of the 3,044 free scans considered in the last 30 days raised this finding. That is 31 scans across 31 distinct sites. 95% interval 0.1% to 12.8%.
What it means
A robots.txt rule blocking AI crawlers keeps the site out of anything those systems answer from, whether or not that was deliberate.
How to fix it
Allow the answer-engine crawlers in robots.txt (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) if you want to appear in AI answers. Blocking them is a choice worth making deliberately.
How to check it yourself
Open example.com/robots.txt and look for Disallow lines naming AI or answer-engine crawlers specifically, rather than a blanket rule for all bots.
What fixed looks like
Opening example.com/robots.txt shows no Disallow line naming AI or answer-engine crawlers.
How we measured this
Go Voltic scans a site and records which findings it raises. The share above is over every free four-page scan in the last 30 days that loaded at least one page, which is 3,044 scans. Deep scans of paid reports and of the research sweep read a site at a different depth and are a separate population, never in this denominator. It is not a survey and it is not an estimate: it is a count of what our own scanner found. Sites are counted once each in the distinct-sites figure, so a site scanned twice does not weigh double there.
The interval is a 95% Wilson interval. A share printed without its sample size reads as certainty and is indistinguishable from a guess, so both are always shown. Figures on this page were computed on 2026-09-08.
The same share sits beside every other finding on the benchmarks page, which also carries the whole table as CSV and JSON and says how to cite it.
Check your own site
The free scan reads four pages and reports every finding it raises, including this one. It takes about ten seconds and asks for nothing but the address.