Noindex Tag Test
The No-Index Checker scans any URL for the meta robots noindex directive, the X-Robots-Tag HTTP response header, and any other signal that tells Google to keep the page out of its search index. Accidental noindex is the single most common cause of "page is suddenly not in Google" support tickets — usually introduced by a staging environment promoted to production with a noindex tag still in place. This tool catches it in seconds.
What This Tool Checks
- <meta name="robots" content="noindex"> in the <head>
- X-Robots-Tag HTTP response header (server-side noindex)
- Bot-specific noindex (googlebot, bingbot)
- Conflicting indexable signals (canonical, sitemap)
- noindex on URLs that are explicitly listed in the sitemap
- Disallow rules in robots.txt that prevent the noindex from being seen
- Combination of nofollow + noindex (impact on link equity)
Why It Matters for SEO
A single noindex tag removes a page from Google completely. On a page that should rank, this is catastrophic. The most common cause is staging infrastructure deployed to production with the noindex still in place — entire ecommerce sites have lost millions in revenue from a single line of HTML. Even when intentional (thank-you pages, internal search results), it must be paired with a crawlable URL, otherwise Google never sees the directive and may index the page anyway.
How to Fix It
Remove any unintended <meta name="robots" content="noindex"> from production templates and any X-Robots-Tag: noindex headers from the CDN or origin server. For pages you genuinely want kept out of search, leave the page crawlable but add the noindex directive — and remove it from the sitemap.
How It Works
We fetch the URL with Googlebot's user-agent, parse both the rendered <head> for meta robots tags and the response headers for X-Robots-Tag, and report every directive that affects indexability. We also cross-check against your sitemap and canonical to detect contradictions Google would silently resolve in the wrong direction.
Common Mistakes to Avoid
- Staging-environment noindex tag promoted to production
- Blocking the URL in robots.txt AND adding noindex (Google never sees the noindex)
- noindex on a URL listed in the sitemap (sends conflicting signals)
- Trying to use noindex to hide private content (use authentication instead)
- Forgetting that some CDNs / waf rules inject X-Robots-Tag automatically
Quick Checklist
- No accidental noindex in production HTML
- No X-Robots-Tag noindex header from CDN / origin
- Pages with intentional noindex are NOT in the sitemap
- Pages with noindex are crawlable (not blocked in robots.txt)
- Search Console > Coverage shows no unexpected "Excluded by noindex"