Indexability X-Ray
One URL, every indexability signal at once — robots.txt, noindex, canonicals, redirects — synthesized into a single verdict, with the contradictions called out by name.
Why one signal is never enough
“Why isn’t this page indexed?” is rarely answered by a single check, because indexability signals interact — and sometimes cancel each other out. The classic: a page blocked in robots.txt and marked noindex. Google can’t crawl it, so it never sees the noindex, so the URL can linger in the index anyway. Or: a noindex page that canonicals to its live twin — a signal Google mostly ignores, because a page excluded from the index makes a poor canonical source.
This tool reads all the signals together and tells you the effective outcome, not just the list.
What it detects
- Robots.txt blocking (evaluated for Googlebot, with the matching rule shown)
noindexin meta robots and in theX-Robots-Tagheader — and disagreements between them- Canonicals — tag and HTTP header — including whether the canonical target itself is live, redirecting, or broken (a canonical pointing at a 404 is a surprisingly common way to deindex yourself)
- Redirects: the URL you asked about may simply consolidate somewhere else
- The paradox cases: robots-block + noindex, noindex + canonical-elsewhere, index/noindex conflicts between sources
A clean bill of health means indexable — whether Google chooses to index it is a different fight.
The tool fetches your live robots.txt, evaluates it for Googlebot per RFC 9309, fetches the page, and reads meta robots, X-Robots-Tag, canonical tags and headers, and the redirect chain. When the page canonicals elsewhere, the canonical target is fetched too. Nothing is stored.