Noindex found
The response contains a robots or Googlebot noindex directive, including the “none” shorthand. The result shows whether it came from the HTML or an HTTP header.
Noindex Checker
Find out whether a public page returns a noindex directive. Check the evidence in its HTML and HTTP headers, follow redirects and review Googlebot crawl rules.
Ready when you are.
What the result meansCheck the instruction.
Check the instruction.
Understand the limits.
A noindex check answers one specific question. Google’s indexing decision depends on more than this directive.
No noindex found
No applicable noindex directive was found in the response we could inspect. This does not confirm that the page is indexed or eligible to appear in Google.
Unable to confirm
A blocked request, error, incomplete response or inaccessible site can prevent a reliable check. The tool reports the limitation instead of guessing.
A few useful answers
Beyond the tag.
Does robots.txt Disallow mean noindex?
No. Robots.txt controls crawling. A crawl block can prevent Google from seeing a noindex instruction, and a blocked URL may still appear in results. The checker reports the Googlebot crawl rule separately.
Does this check JavaScript changes or Google’s index?
No. It checks the HTML and headers returned to our checker, without executing JavaScript, logging in or impersonating Googlebot. Use Google Search Console’s URL Inspection for a property you manage to investigate Google’s crawl and indexing view.
What happens to the URL I submit?
The checker requests the public URL and its robots.txt file to produce your result. It does not save a scan history or submit the URL to Google. Use public pages; private addresses, credentials and nonstandard ports are not accepted.
Can I check PDFs and other files?
HTTP X-Robots-Tag headers can apply to non-HTML files too. The checker inspects those headers and makes clear when HTML meta tags are not applicable.
Reference: Google’s robots meta tag and X-Robots-Tag documentation