Bulk up to 100 • Meta robots + X-Robots-Tag

Noindex Page Checker

Paste URLs — we’ll follow redirects and detect noindex in meta robots and X-Robots-Tag.

Paste up to 100 URLs (one per line)
Tip: noindex can be set in HTML meta or in the HTTP header X-Robots-Tag. Header usually wins in practice.

Results

Host Page HTTP Hops Time Issues
Run a check to see results here.
“NOINDEX detected” means the page asks crawlers not to index it.

Quick interpretation

Noindex blocks indexing. It’s often used for admin pages, duplicates, and thin content.

  • OK no noindex found (likely indexable)
  • Warning noindex/nofollow present, odd content-type, hop limit
  • Error fetch errors, loops, HTTP 4xx/5xx
Indexability signals

Noindex Page Checker: find pages blocked from Google

A page can look fine but still be blocked from indexing by noindex. This tool checks the two most common sources: HTML meta robots and the HTTP header X-Robots-Tag.

What can trigger “noindex”

  • Meta robots: <meta name="robots" content="noindex">
  • X-Robots-Tag: X-Robots-Tag: noindex (often on PDFs or server rules)
  • Googlebot-specific meta: name="googlebot" can override generic robots

FAQ

What does “noindex” mean?

Noindex is a directive telling search engines not to include a page in their index. A page can still be accessible to users, but it won’t appear in search results if crawlers respect the directive.

Where can “noindex” be set?

This tool checks the two most common sources:

  • Meta robots in HTML, e.g. <meta name="robots" content="noindex">
  • X-Robots-Tag HTTP header, e.g. X-Robots-Tag: noindex (often used for PDFs and server rules)

It also reads meta name="googlebot", which can override generic robots directives for Google.

If it says “INDEXABLE (no noindex found)”, is indexing guaranteed?

No. “Indexable” here only means the tool did not detect noindex in meta robots or X-Robots-Tag on the final URL. Indexing still depends on crawl access, canonical rules, duplicates, internal linking, quality signals, and whether bots can fetch the page.

What’s the difference between “noindex” and “nofollow”?

Noindex is about indexing the page itself. Nofollow is about how crawlers treat links on the page (it may reduce link crawling/weight).

This tool flags nofollow as an informational warning because it’s often present together with noindex.

Which one “wins”: meta robots or X-Robots-Tag?

In practice, search engines typically treat both as valid signals. If either the HTML meta or the HTTP header includes noindex, you should assume the page is blocked.

Headers are especially common for non-HTML files and for site-wide rules (server/CDN).

Why do I see “odd content-type”?

The tool expects HTML-like responses for meta parsing. If a page returns something unusual (like a download, JSON/XML, or a misconfigured content type), meta parsing may be incomplete.

In those cases, rely more on X-Robots-Tag and the final HTTP status, or test the real page in a browser.

Why do redirects matter for noindex checks?

The tool follows redirects and evaluates the final URL, because that’s the page Google will typically see. Sometimes the input URL is indexable, but it redirects to a noindex page (or a non-200 response).

If you’re migrating URLs, redirects + noindex mistakes are a common reason pages drop out of search.

How do I remove a “noindex” block safely?

Typical fixes:

  • Remove noindex from meta robots (and meta googlebot if present)
  • Remove noindex from the server/CDN rule that sets X-Robots-Tag
  • Ensure the final URL returns 200 and has a correct canonical
  • Then request re-crawl in your search console (if available) and monitor indexing