Indexability checker
One verdict from the four signals that decide whether a page can appear in Google: robots.txt (parsed with Google's own matching rules), meta robots, the X-Robots-Tag header, and the canonical — including the trap where a noindex sits behind a robots.txt block and never gets seen.
What gets checked
robots.txt is fetched and evaluated the way Google documents it: the most specific user-agent group applies (never combined with *), the longest matching path rule wins, ties go to Allow, and status codes matter — a 404 robots.txt means no restrictions, while a 500 means Google treats the whole site as temporarily off-limits. Directives combine most-restrictive-wins across meta robots, meta googlebot and X-Robots-Tag headers.
Rules last verified against Google Search's robots.txt spec and robots meta documentation 2026-08-19
FAQ
Why is my noindexed page still in Google?
The classic cause: the page is also blocked in robots.txt. Google can't crawl it, so it never sees the noindex — and the URL can linger in results as a bare listing. Unblock crawling, keep the noindex, and the page drops out on the next crawl. This checker flags exactly that combination as an error.
Does Disallow in robots.txt remove a page from Google?
No. Disallow stops crawling, not indexing — URLs other sites link to can still appear as URL-only results. To remove a page from the index, use noindex (crawlable), a 404/410, or Search Console's removal tool.
Is a canonical a directive?
No — Google calls it a strong hint and may override it when other signals disagree. That's why this checker reports "signals consolidate elsewhere" as a note rather than a block: the page stays indexable, but its ranking signals flow to the canonical target.