The Website Indexability Checker tests whether a public URL has obvious technical signals that can prevent or redirect search-engine indexing.
What the indexability checker tests
The tool fetches the page and checks its HTTP response, meta robots directive, X-Robots-Tag header, canonical link element and a basic evaluation of the site’s robots.txt rules for the requested path. It also reports sitemap declarations found in robots.txt.
What “indexable” really means
Technical eligibility is only the first step. A page can be crawlable and free of noindex directives and still remain unindexed because a search engine considers it duplicate, low value, soft-404-like, canonicalized elsewhere or simply not worth storing. The tool therefore reports obvious indexing blocks, not a promise that Google has indexed the page.
Common reasons a page is not indexable
Typical blockers include a 4xx or 5xx response, a meta robots noindex directive, an X-Robots-Tag noindex header, or a robots.txt Disallow rule. A canonical pointing to another URL is not exactly the same as noindex, but it can tell search engines that another page should be treated as the preferred version.
How to troubleshoot an indexing problem
Fix hard blocks first. Then confirm the preferred canonical, include the page in an appropriate XML sitemap, link to it internally, and inspect the URL in Google Search Console. If the technical signals are clean, evaluate duplication, thin content and search intent.
Related tools
Use the SEO & GEO Page Analyzer for broader on-page analysis and the Schema Markup Checker for structured data.
Frequently asked questions
Does robots.txt noindex a page?
No. robots.txt controls crawling, while noindex is an indexing directive. Blocking crawling can also prevent a search engine from seeing a noindex tag on the page.
Why is my page still not indexed after passing?
Passing means the checker did not find a common technical block. Search engines still decide whether to crawl, canonicalize and index the URL.