It pulls together every signal that decides whether Google can index a URL into one verdict. It reads the page's meta robots tag for noindex, the X-Robots-Tag HTTP response header, your robots.txt rules for that path, the rel=canonical destination, and the HTTP status code. Any single blocking signal — a noindex, a disallow, a non-200 status, or a canonical pointing elsewhere — can keep a page out of the index, so checking them in isolation is misleading. This tool resolves them together and tells you the net outcome.

Not always, and that surprises people. A robots.txt disallow blocks crawling, but Google can still index a disallowed URL if it finds links to it elsewhere, showing it with no description. Conversely, if you disallow a page, Google can never see a noindex tag on it because it cannot fetch the page. The checker flags this exact conflict — a disallowed page that also carries a noindex — because the noindex will be ignored and the URL may linger in the index.

They do the same job — controlling indexing and following — but live in different places. Meta robots is an HTML tag inside the page's head, so it only works for HTML responses. X-Robots-Tag is an HTTP response header, so it can apply noindex to non-HTML files like PDFs and images, and it is applied even before the body is parsed. Either one declaring noindex will deindex the page, so this tool reads both and reports whichever is blocking.

A canonical tag tells Google which URL is the preferred version of a set of duplicates. If a page canonicalizes to a different URL, Google will usually index the canonical target instead of the page you tested, effectively dropping the tested URL from results. That is intended for duplicates but is a problem when a templating mistake points many pages at one canonical. The checker shows whether the canonical is self-referencing or points elsewhere so you can tell intentional consolidation from an accidental deindex.

Yes. Only pages that return a 200 OK are eligible for indexing. A 404 or 410 tells Google the page is gone, a 301 or 302 hands ranking to the redirect target rather than the page itself, and a 5xx server error stops indexing until the page recovers. The tool reports the final HTTP status after following redirects so you can confirm the URL you care about actually resolves to an indexable 200 response.

No tool can guarantee indexing — Google also weighs content quality, duplication, crawl budget, and site authority, none of which a single technical check can measure. A green verdict means there are no technical blockers stopping indexing, which is a necessary first step. If a page still is not indexed despite a clean verdict, the cause is usually quality or duplication, and you would investigate that in Search Console's URL Inspection tool.

Run it whenever you launch a new page, migrate a site, change a CMS setting, or notice a URL missing from search. Staging environments and CMS templates are notorious for shipping noindex tags or robots.txt disallows into production by accident, so a quick check after any deploy that touches templates or headers is worthwhile. There is no usage limit, so you can re-test as often as you need.