The server sends a noindex header
4.8%
of the 3,044 free scans considered in the last 30 days raised this finding. That is 145 scans across 145 distinct sites. 95% interval 2.3% to 9.5%.
What it means
X-Robots-Tag can block indexing even when the page markup looks fine: a header a crawler reads before it sees the HTML.
How to fix it
Remove the X-Robots-Tag: noindex header from your server or CDN config for the paths you want indexed. It overrides the page markup, so a clean <head> will not save you.
How to check it yourself
Run curl -sI https://example.com and look for an X-Robots-Tag line containing noindex in the response headers.
What fixed looks like
The curl response headers carry no X-Robots-Tag: noindex line for the pages you want indexed.
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.