Ad / Affiliate · pre-result
Check If Your Page Is Indexable
A page can be perfectly built and still be invisible to Google if a single directive tells search engines to stay away. A stray noindex — often a staging setting shipped to production — removes a page from search results entirely, and the traffic loss is silent until it is severe.
Our Indexability Checker fetches any public URL and reconciles the meta robots tag with the X-Robots-Tag HTTP header, applying the most-restrictive-wins rule Google uses, and returns a clear indexable-or-not verdict in plain language.
No sign-up, nothing stored, results in seconds.
No need to type http:// — just the domain works. One server-side fetch, nothing stored. Public URLs only.
What this tool checks
Meta robots tag
The meta robots directive is read for noindex, nofollow and related values that control whether the page may be indexed and its links followed.
X-Robots-Tag header
The X-Robots-Tag HTTP header is read, since this header can apply noindex at the server level even when the HTML looks clean.
Conflict reconciliation
The tag and the header are reconciled using the most-restrictive-wins rule, because that is how Google resolves a disagreement between the two.
Bot-specific rules
Bot-specific directives such as a googlebot meta tag are surfaced, since they can override the generic robots rule for that crawler.
Clear verdict
A single plain-English verdict is produced so the indexable-or-not answer is unambiguous.
Why it matters for SEO
Indexability is the precondition for every other SEO effort: a page that cannot be indexed cannot rank, no matter how good its content or links are. The most damaging cases are silent — a noindex left on after a site launch, or a server header nobody checked — and they are usually discovered only after traffic has already collapsed. A noindex directive also interacts with robots.txt in a counterintuitive way that this tool explains, so the real cause is not missed.
How to fix common issues
Unexpected noindex
An unexpected noindex is fixed by removing the noindex value from the meta robots tag or the X-Robots-Tag header on pages that should rank.
Staging noindex shipped live
A staging noindex on production is fixed by auditing the deployment so the noindex used to hide a staging site is stripped before launch.
Header overrides clean HTML
A noindex coming from the X-Robots-Tag header is fixed at the server or CDN configuration, since the header wins even when the HTML has no noindex.
Unintended nofollow
An unintended nofollow is fixed by removing nofollow from the robots directive so the page's links pass ranking signals normally.
Blocked and noindexed together
A page that is both noindexed and blocked in robots.txt is fixed by unblocking it in robots.txt, because Google must be able to crawl the page to even see the noindex.
Frequently asked questions
What does indexable mean?
Indexable means a page is allowed to appear in search results, with no noindex directive from the meta robots tag or the X-Robots-Tag header.
What is the difference between the meta robots tag and the X-Robots-Tag header?
The meta robots tag lives in the page HTML, while the X-Robots-Tag is an HTTP response header. Both can set noindex, and the more restrictive of the two wins.
Why is my page not in Google even though it looks fine?
A page that looks fine but is missing from Google is frequently carrying a noindex in the X-Robots-Tag header, which is invisible without inspecting the response.
Does noindex remove a page immediately?
A noindex directive removes a page once Google recrawls it and sees the directive. The page must be crawlable for the noindex to take effect.
Can robots.txt and noindex conflict?
Blocking a URL in robots.txt prevents Google from crawling it, so Google never sees the noindex and may keep the URL indexed without a snippet.
Is this indexability checker free?
Our Indexability Checker is free, with no sign-up, no limits, and nothing stored. The page you submit is fetched server-side, analyzed, and then discarded.
Related tools