Free scanTools…

Indexability checker

Paste a URL and we fetch it live, then run every technical signal Google uses to decide whether a page can be indexed: HTTP status, redirects, the X-Robots-Tag header, <meta robots>, the canonical, and robots.txt. One plain-English verdict, no sign-in.

The short answer

A page is indexablewhen nothing technical stops Google from adding it to its index: it returns HTTP 200, isn't disallowed in robots.txt, carries no noindex (in a <meta robots> tag or the X-Robots-Tag header), and its canonical points to itself. Paste a URL above and this checker tests every one of those signals live, then returns a single plain-English verdict.

Indexable vs. indexed

This tool checks indexability, meaning whether anything technical is stopping Google. That's different from being indexed, which is Google's own decision after it crawls. To check whether a URL is already in Google's index, connect your Search Console and use the Google index checker, which reads the official URL Inspection API.

Using it as a noindex checker

A noindex can sit in two places, and a page only has to carry it in one to stay out of Google. The first is the <meta name="robots" content="noindex"> tag in the HTML head. The second is the X-Robots-Tag HTTP response header, which is the one people miss: it never shows up in view-source, so a page can look completely clean and still be blocked by a header set at the CDN or in a server config. This checker reads both on every run and tells you which one is responsible, so you know whether the fix belongs in your template or in your infrastructure.

What "indexability status" means

The status is the single verdict for a URL: indexable when all six signals pass, or not indexable when at least one blocks it. The six are the HTTP status code, the redirect chain, the X-Robots-Tag header, the <meta robots> tag, the canonical link, and your robots.txt rules. The verdict names the blocking signal rather than just failing, because which one it is decides where the fix goes.

If a signal is red

A single noindex or a robots.txt disallow is enough to keep a page out of Google. Fix the blocker, then push a recrawl so Google re-reads it fast. connect your own Search Console and submit the URL. Stuck on a specific Search Console error? See the indexing fixes.

FAQ

What is indexability?
Indexability is whether a page is technically allowed to enter a search engine's index. A page is indexable when nothing blocks it: it returns 200, isn't disallowed in robots.txt, carries no noindex (in a meta robots tag or the X-Robots-Tag header), and points its canonical at itself rather than another URL.
What does this indexability checker test?
It fetches the URL live and runs every technical signal Google uses to decide if a page can be indexed: HTTP status, redirect chain, the X-Robots-Tag response header, the <meta robots> tag, the canonical link, and your robots.txt rules. Then it returns one plain-English verdict.
Is indexable the same as indexed?
No. Indexable means nothing technical is blocking the page. Indexed means Google has actually crawled it and chosen to keep it in the index. A page can be perfectly indexable and still sit unindexed. For live index status, connect Search Console and use the Google index checker.
What does "indexability status" mean?
Indexability status is the summary verdict of whether a page can be indexed: 'indexable' when every technical signal passes, or 'not indexable' when at least one blocks it: a noindex directive, a robots.txt disallow, a non-200 status, or a canonical pointing at another URL. This checker returns that status per URL along with the exact signal responsible, so you know precisely what to fix.
A signal is red. What now?
Fix the specific blocker the verdict names (remove the noindex, narrow the robots.txt rule, correct the canonical, or resolve the redirect), redeploy, then request a recrawl so Google re-evaluates the page quickly.
Do I need to sign in?
No. The indexability check runs against any public URL with no account. Search Console only comes into it for the separate index-status check via the URL Inspection API.
Why does Google say my app or site is not indexable?
The usual culprits: the page is rendered entirely by JavaScript so the initial HTML is empty (common in single-page apps), it sits behind a login or interstitial, it returns a non-200 status, or a stray noindex / robots.txt rule blocks it. App-store links and deep links into native apps aren't web pages, so Google can't index them at all. You need a public web URL. Run the URL through this checker to see which signal is the blocker.
How do I check a page for a noindex tag?
Paste the URL above. The checker reads both places a noindex can live — the <meta name="robots"> tag in the HTML head and the X-Robots-Tag HTTP response header — and reports which one carries it. Checking by hand means viewing source for the meta tag and running curl -I for the header, and it is the header people miss, because it never appears in the page source. Either one alone keeps the page out of Google.
How do I check indexability?
Paste the URL into the box above and read the verdict. Behind it are six checks, run live against the page: the HTTP status code, the redirect chain, the X-Robots-Tag response header, the <meta robots> tag, the canonical link, and the matching robots.txt rules. A page is indexable only when all six pass; when one does not, the verdict names it. For a whole site, run the pages you care about one at a time, or connect Search Console and use the Google index checker for bulk status.
How do I check the X-Robots-Tag header?
This checker reads the X-Robots-Tag response header on every run, as one of the signals in the verdict. To check it by hand, run curl -I https://example.com/page and look for an X-Robots-Tag line: 'noindex' there keeps the page out of Google even if the HTML has no meta robots tag.

Related free tools

Google index checker

Bulk-check which of your URLs Google has indexed, via the URL Inspection API on your own Search Console.

Canonical & meta finder

Extract canonical, robots meta, title, OG, and JSON-LD from a page's HTML.

Robots.txt tester

Test whether a URL is crawlable under a robots.txt for a given User-Agent.