Noindex Checker: Meta Robots & X-Robots-Tag

How to use

1. Enter the URL and select Analyze.
2. Read the verdict at the top: indexable, or blocked by noindex.
3. Check the sources below it: meta tags per crawler and response headers.

What this tool does

It reads meta name=”robots” and crawler-specific tags such as googlebot, plus every X-Robots-Tag response header, and lists the directives they contain (noindex, nofollow, none, noarchive, nosnippet, max-snippet and others). It also reports the HTTP status, because error pages are not indexed either.

Why it matters

A forgotten noindex left from a staging site is one of the most common reasons a page disappears from search. The header version is invisible in the page source, which makes it easy to miss.

Common uses

• Checking pages after launching from staging.
• Confirming that thank-you and account pages are noindexed on purpose.

Tips

• robots.txt blocks crawling, not indexing. To keep a page out of search results, use noindex and allow crawling so the tag can be seen.

Limitations

The page is read as the server sends it. Content that is added later by JavaScript (common on React, Vue or Angular sites and some page builders) is not seen. If results look empty, view the rendered page in your browser and use a paste-HTML tool instead.

Troubleshooting

• “Could not connect” or “took too long”: the site may be down, slow, or blocking automated requests. Try again later or check it in your browser.
• “Certificate could not be verified”: the HTTPS certificate is expired, self-signed or issued for another domain. Visitors’ browsers will show a warning too.
• “Private or reserved network address”: the address points to a local or internal network, which this tool never contacts.
• “Limit reached”: checks are rate-limited to keep the service free and to avoid overloading other websites. Wait a few minutes.