Robots meta
Read robots and Googlebot meta directives from the returned HTML.
Free noindex checker / live response
Check whether a page is telling search engines not to index it.
Enter any public URL to inspect robots meta directives, Googlebot directives, X-Robots-Tag behavior, a site-wide wildcard robots block, and the final HTTP response. No account or email required.
✓ No signup✓ Live public response✓ Read-only
Livepublic response
HTML + headerdirective sources
robots.txtblanket block check
$0no signup required
Find the public directive behind an indexability problem.
A page can look normal in a browser while its source or response header says noindex. The checker extracts the specific public signals RankLatch can verify without CMS or Search Console access.
X-Robots-Tag
Include noindex directives delivered through the HTTP response header.
Blanket robots block
Check whether the wildcard crawler group blocks the entire site with Disallow: /.
Final response
Follow safe redirects and report whether the destination returns a healthy status.
What the result does—and does not—prove.
- ✓Public robots and Googlebot meta directives
- ✓Public X-Robots-Tag directives
- ✓A wildcard site-wide robots.txt block
- ✓The final HTTP response and destination
- —Google’s actual index selection
- —URL Inspection or coverage data
- —Signals inserted only after JavaScript execution
- —A crawl of every page on the website
Current check → continuous protection
A clean result is useful now. Monitoring tells you if it changes tomorrow.
RankLatch can preserve the approved public directive and compare it daily. If a page gains noindex later, the incident contains the exact previous and current state plus a restoration step.
See noindex change monitoring →Straight answers
Before you check.
One live request can verify important public signals. It cannot replace Search Console or prove how a search engine will ultimately treat the page.
01What noindex signals does this checker inspect?+
It reads robots and Googlebot meta directives from the public HTML, the X-Robots-Tag response header, and the equivalent none directive. It also checks for a wildcard robots.txt rule that blocks the entire site.
02Does a clear result guarantee Google will index the page?+
No. It means this live public response did not expose the specific indexability blockers checked here. Google can still exclude a page for duplication, quality, crawling, canonicalization, or other reasons reported through Search Console.
03Does the checker render JavaScript?+
No. RankLatch reads the server response rather than operating a full browser. A directive injected only after client-side JavaScript runs may not appear in the result.
04Is robots.txt Disallow the same as noindex?+
No. A robots.txt rule controls crawling, while noindex controls index inclusion when a crawler can read the directive. This checker reports a dangerous blanket wildcard block separately instead of treating the two concepts as identical.
05Do you store or change the page?+
The free check is read-only and does not edit the website. It returns a current result; continuous monitoring requires an account and an approved baseline.
06What should I do after removing an accidental noindex?+
Publish the corrected directive, verify the live page again, then use Search Console to request indexing where appropriate. Monitoring can alert you if the public directive changes again.