What is indexability? How to check if a page can be indexed

Indexability is the most basic question in technical SEO: is Google even allowed to put this page in its index? It's easy to skip past — you write the content, you build the links — but if a page isn't indexable, none of that matters. It can never rank, because it never enters the index in the first place.

Indexability vs. indexed — the difference that trips people up

These sound the same and aren't. Indexable means nothing technical is stopping Google from adding the page to its index. Indexed means Google has actually crawled the page and chosen to keep it. A page can be perfectly indexable and still not indexed — Google crawls on its own schedule and skips pages it judges thin or duplicate. So the two questions need two different tools: an indexability checker answers "can this be indexed?", and the URL Inspection API answers "is this indexed right now?"

What determines whether a page is indexable

Google runs through a short checklist before a page is eligible for the index. All of these have to pass:

1. HTTP 200. The URL has to return a success status. A 404, 410, 5xx, or a soft 404 (a "not found" page that still returns 200) is not indexable.
2. Crawlable in robots.txt. No Disallow rule can match the URL — if Google can't crawl it, it can't index it.
3. No noindex in the meta robots tag. A <meta name="robots" content="noindex"> in the HTML head keeps the page out.
4. No noindex in the X-Robots-Tag header. The same directive can live in the HTTP response header, where it's easy to miss — it's often set once at the server or CDN and applied to whole path patterns.
5. A self-referencing canonical. The page's canonical link should point to itself. A canonical pointing at another URL tells Google to index that URL instead of this one.
6. Not an unintended redirect. A URL that 301/302s elsewhere isn't indexed — the destination is.

How to check if a page is indexable

1. Run it through a free indexability checker. Paste the URL and get a live verdict across all the signals above at once — the fastest way to see which one (if any) is the blocker.
2. Use URL Inspection in Search Console. For a property you own, it shows Google's own view: the coverage state, whether the page is indexable, and the last crawl date.
3. Check the headers by hand with curl -I https://example.com/page. Look at the status line and any X-Robots-Tag — a noindex there is the one people miss most, because it's invisible in the page source.
4. Crawl the whole site with a tool like Screaming Frog when you need to audit indexability at scale rather than one URL at a time.

Common reasons a page isn't indexable — and the fix

• An accidental noindex — a stale draft tag or a CMS/CDN header. Find and remove it, then request a recrawl.
• A robots.txt disallow that's too broad — a leftover staging rule, or a Disallow: / that leaked to production.
• A non-200 status or a soft 404 — the page returns 200 but has no real content, so Google treats it as missing.
• An off-page canonical — the canonical points at a different URL, so Google indexes that one instead of this page.
• JavaScript-only rendering — the initial HTML is empty and content only appears after JS runs, which single-page apps hit often.
• "URL is not on Google" in inspection — the page is unknown to Google or was dropped; a fresh crawl request usually resolves it.

Does indexability affect rankings?

Only as a gate. Indexability isn't a ranking factor — Google doesn't rank a page higher for being indexable. But it's a hard prerequisite: a non-indexable page has a ceiling of zero, because it can't be shown at all. Fix indexability first, then compete on content and links. If a page is indexable but still not indexed, that's a crawl-priority or quality problem, not an indexability one.