Noindex Checker
The Noindex Checker detects noindex directives in a page’s meta robots element and X-Robots-Tag HTTP headers. It reports the exact directive, source, crawler applicability and fetch state for up to 10 URLs.
What the Noindex Checker checks
Inspect every applicable robots meta element in the fetched HTML, including its crawler name and exact directive value, rather than inferring indexability from page content or a rendered preview.
Read every supported HTTP X-Robots-Tag field on the fetched response, including crawler-qualified values and non-HTML resources where a meta element cannot supply the directive.
Separate general robots instructions from crawler-specific directives, then show which values apply to the selected crawler so a Googlebot result is not presented as universal crawler behavior.
Keep blocked, unavailable and unsupported responses distinct from confirmed index or noindex evidence. An unsuccessful fetch remains inconclusive instead of being mislabeled as an indexable page.
When to use this tool
Run the Noindex Checker when a page is unexpectedly absent from search or before a template change that affects indexing directives.
Example
Example: inspect https://example.com/checkout to learn whether its fetched HTML or HTTP headers declare noindex for Googlebot.
Issues and fixes
When the evidence identifies a meta robots noindex value, remove it from the responsible page or shared template only if the URL should be eligible for indexing. Fetch the published page again to confirm the directive is gone rather than relying on a source-code change alone.
When X-Robots-Tag supplies the noindex instruction, correct the application, server, proxy or CDN configuration that added the header. Changing HTML will not remove HTTP evidence, so retest the deployed response and verify every applicable header value.
A robots.txt block and a noindex directive answer different questions. If Googlebot cannot crawl the URL, use the Robots.txt Tester to inspect the winning rule; do not treat this checker’s successful diagnostic fetch as proof that Googlebot can read the directive.
What the result includes
The report identifies applicable directives, their HTML or HTTP source, conflicts, robots.txt context and any indeterminate fetch state.
Limitation: The Noindex Checker reads raw fetched HTML and HTTP headers for up to 10 public URLs. It does not execute page JavaScript, reproduce every crawler’s cached response or prove whether a search engine has indexed the URL. Redirect, network, authentication, content-type and response-limit failures remain fetch evidence, not an SEO verdict. A result without noindex means only that no applicable supported directive was found in the inspected response; it does not guarantee crawling, canonical selection or indexing.
Frequently asked questions
Can robots.txt stop Google from seeing a noindex directive?
Yes. When robots.txt blocks Googlebot from fetching a URL, Googlebot cannot read a page-level meta robots directive or response header from that fetch. The report keeps robots.txt access separate from noindex evidence; test crawl access with the Robots.txt Tester before treating an unavailable directive as absent.
What happens when index and noindex both appear?
The Noindex Checker lists the applicable directives and flags the conflict. A restrictive noindex instruction takes precedence for the reported response, but the correction is to remove the contradictory declaration at its HTML or HTTP source and retest the fetched URL.
Monitor URLs over time
Turn a one-off diagnostic into ongoing index monitoring and change alerts.