Both are evaluated against robots.txt. The report shows them separately when the answers differ.

Is Search Console the source of truth?

For actual index state, yes. This page is a technical check at fetch time.

Does nofollow block indexing?

Not in this verdict. We look at noindex, robots.txt, status, and canonical target.

What is Mixed signals?

Usually the page is allowed, but the canonical points away from the URL you asked us to fetch.

Are SPA shells a problem?

A 200 with empty HTML can still look indexable here. Heading and content tools will look thin on the same URL.

Why did a missing robots.txt look allowed?

If robots.txt returns 404 or the fetch fails, paths are treated as allowed for * and Googlebot. example.com does that and still shows Indexable when status is 200 and there is no noindex. A Disallow only applies when the file is read.

What does Away on Canonical mean?

The link rel=canonical href normalizes to a different URL than the one we fetched (hash stripped, trailing slash ignored). That warning alone makes the verdict Mixed. Google usually indexes the target, not this URL, even when robots.txt allows the path.

Can I paste a list of URLs?

No. This checker fetches one public URL per run, plus that origin's robots.txt. There is no Page URL list and no paste-text mode. Repeat the run for each path, about 20 checks per minute on your network.

Does Analyze execute JavaScript?

No. It reads the first HTML and headers the server sends. A noindex injected after render is missed, so a client-only app can show Indexable while the painted page is noindexed. Use view-source, not DevTools Elements, to confirm.

Indexability Checker

Loading tool…

About Indexability Checker

Paste a URL and click Analyze. We fetch the page and robots.txt for that host, then combine HTTP status, robots.txt for * and Googlebot, meta robots noindex, X-Robots-Tag noindex, and whether the canonical points away. The verdict is Indexable, Blocked, or Mixed signals, plus a reason list.

If robots.txt is missing (404) or the fetch fails, paths are treated as allowed. nofollow is not treated as blocked. A 200 with empty HTML can still look indexable technically. Search Console remains the record of what Google actually indexed.

When to use it

Use it when Search Console says Crawled, currently not indexed, or when you just shipped a noindex, an X-Robots-Tag, or a robots.txt Disallow and need to see which of those five signals is the one that fires on this exact URL.

Also use it after a host or CMS cutover, when the live URL might still canonicalize to the old host. It is a fetch-time technical check, not a coverage report.

How to use Indexability Checker

1Enter the URL. Use the exact URL you care about, including https and www if that is the live host.
2Click Analyze. We fetch the page and robots.txt for that origin.
3Read the verdict chip. Indexable, Blocked, or Mixed signals.
4Follow the reason list. Each factor is listed with Ok, Blocked, or Away.

Signals in the verdict

Blocked means a hard noindex or a robots.txt disallow for the agents we test. Mixed usually means the page looks allowed but the canonical points at a different URL. Indexable means none of those blocks fired on this fetch.

We show * and Googlebot separately when they differ. JavaScript-only noindex in a later render is missed. Soft 404 (status 200 with thin content) is not classified as 404 here.

How to read the results

The header chip is Indexable, Blocked, or Mixed. Fact boxes across the top are Status, robots.txt, Meta robots, X-Robots-Tag, and Canonical. The Signals table repeats those rows with Detail and Status: Ok, Blocked, or Away.

Fix Blocked rows first. A 4xx or 5xx status, a Disallow for * or Googlebot, meta noindex, or X-Robots-Tag noindex each force Blocked. Canonical Away alone is Mixed, not Blocked. Needs work lists the failing issues. Passing checks appears when the verdict is Indexable and includes Technically indexable.

Why this matters

Google usually indexes the canonical target, not the URL you fetched. A self-looking page that points elsewhere is why Mixed exists: robots and status can be clean while this URL is still treated as a duplicate.

A noindex in X-Robots-Tag applies even when the HTML has no robots meta. A robots.txt Disallow can hide that noindex from Googlebot, which is a different problem than a 200 that looks Indexable here. A missing robots.txt (404) is treated as allow, which is why example.com can still show Indexable.

Limits and privacy

Public URLs only. Localhost and private addresses are blocked. About 20 checks per minute on your network. This is a fetch-time technical check, not Search Console. No account.

Common mistakes

Reading Indexable as proof Google has the URL in the index. The pass row says Technically indexable. Search Console remains the record of what was actually kept.

Testing www when the live host is the apex. robots.txt and the canonical are fetched for the host you typed, so the chip can disagree with the URL users hit.

Expecting a thin 200 to show Blocked. Soft 404s stay Indexable here. Wikipedia Special:Search is Blocked because robots.txt and meta noindex both fire, not because the HTML is thin.

FAQs

Googlebot vs *?: Both are evaluated against robots.txt. The report shows them separately when the answers differ.
Is Search Console the source of truth?: For actual index state, yes. This page is a technical check at fetch time.
Does nofollow block indexing?: Not in this verdict. We look at noindex, robots.txt, status, and canonical target.
What is Mixed signals?: Usually the page is allowed, but the canonical points away from the URL you asked us to fetch.
Are SPA shells a problem?: A 200 with empty HTML can still look indexable here. Heading and content tools will look thin on the same URL.
Why did a missing robots.txt look allowed?: If robots.txt returns 404 or the fetch fails, paths are treated as allowed for * and Googlebot. example.com does that and still shows Indexable when status is 200 and there is no noindex. A Disallow only applies when the file is read.
What does Away on Canonical mean?: The link rel=canonical href normalizes to a different URL than the one we fetched (hash stripped, trailing slash ignored). That warning alone makes the verdict Mixed. Google usually indexes the target, not this URL, even when robots.txt allows the path.
Can I paste a list of URLs?: No. This checker fetches one public URL per run, plus that origin's robots.txt. There is no Page URL list and no paste-text mode. Repeat the run for each path, about 20 checks per minute on your network.
Does Analyze execute JavaScript?: No. It reads the first HTML and headers the server sends. A noindex injected after render is missed, so a client-only app can show Indexable while the painted page is noindexed. Use view-source, not DevTools Elements, to confirm.