Is your page allowed to be indexed?

The fastest way to find an accidental noindex. Checks the meta robots tag and the X-Robots-Tag header on your live page, plus what robots.txt allows.

Measuring rankings in

Runs the full audit on your live site. Your report opens in your dashboard.

What this checks

This reads the meta robots tag in the HTML and the X-Robots-Tag header in the response, and reports whether either one carries noindex or nofollow. Both are checked because they are set in completely different places, one in a template and one in server or CDN configuration, and a page can easily carry a directive that nobody working on the template can see. It also confirms the page actually responded with a usable status code, since a noindex on a page that returns a server error is the smaller of two problems.

Why it matters

noindex is the most effective way to remove a page from search, which makes an accidental one the most expensive single mistake in technical SEO. It is also the hardest to notice: the page loads, looks right, and behaves normally for every human who visits it. The classic cause is a staging site launched with its blocking configuration intact, and the classic symptom is traffic that never arrives for reasons nobody can explain.

How to read a bad result

noindex present is scored as a straight failure with no partial credit, because the consequence has no gradient. Check whether it came from the meta tag or the header before changing anything, since fixing the wrong one leaves the page blocked and looking fixed. Once removed, the page has to be recrawled before it returns, so request indexing in Search Console rather than waiting.

A noindex is a straight failure with no partial credit, and the audit treats it that way. Where it goes further is scope: an edge rule setting this header is almost always applied to a path prefix, so it is a section rather than a page, and a crawl is what shows you the size of it.

All 36 checks, free Plans

A failing result, and what it costs

A pricing page that disappeared from search with no change to the site. The directive is not in the template and never was.

A 200, a perfectly normal page, and a header telling every search engine to drop it. Nobody working in the CMS can see this, because it is set at the edge — a CDN rule, a reverse proxy config, or a hosting platform's preview protection that was applied to a path pattern and never narrowed. This is why the check reads the header and the meta tag separately: fixing the one you can see leaves the page blocked and looking fixed, which costs another cycle of waiting to find out.

$ curl -sI https://example.com/pricing/
HTTP/2 200
content-type: text/html; charset=utf-8
x-robots-tag: noindex, nofollow
cache-control: public, max-age=3600

How to fix it

Find out which of the two carries it.The meta tag lives in a template. The header lives in server, proxy or CDN configuration. They are edited by different people and a page can carry both.
Check the path pattern, not the page.Edge rules are almost always applied to a prefix. If one page has it, look at what else matches the same rule before declaring it fixed.
Confirm with a fresh request.Cached responses at the edge can serve the old header after the rule is gone. Bust the cache and read the headers again.
Request indexing rather than waiting.The page has to be recrawled before it returns, which is days on an established site and can be weeks on a new one. Submitting the URL shortens it considerably.

Questions people ask

Why is my page not in Google?

In order of likelihood: it carries a noindex, robots.txt blocks the crawl, it is too new to have been crawled, or the content is duplicated elsewhere and Google chose the other URL. This tool settles the first two immediately.

What is the difference between noindex and Disallow?

noindex says do not show this page in results and requires the crawler to read the page to see it. Disallow says do not fetch this page at all. Combining them cancels the noindex, because the crawler never reads the instruction.

How long does removing a noindex take?

As long as it takes for the page to be recrawled, which is days for an established site and can be weeks for a new one. Requesting indexing through Search Console for the important URLs shortens it considerably.