Indexability
Whether a page is eligible to be added to the index: Googlebot not blocked, HTTP 200, indexable content. Meeting these requirements never guarantees indexing.
Reviewed by Alexander Yarovenko · Updated: 2026-10-08
Indexability is whether a page is able to be added to a search engine’s index. Google does not use the word; it describes eligibility. A page is eligible to be indexed by Google if Googlebot is not blocked, the page works and returns HTTP 200, and the page has indexable content. Meeting these requirements does not mean the page will be indexed: indexing is never guaranteed.
What it is and where the boundary lies
Indexability is about permission and technical fitness, not about quality or importance. A page can be perfectly indexable and still not be indexed, because Google decides what to keep. Conversely, a page that blocks any of the three requirements has no chance. Do not confuse it with crawlability: crawlability is whether Googlebot can reach the page, one of the three requirements, while indexability covers the whole chain up to being eligible.
How it differs from similar terms
| Term | What it is | Relation to indexability |
|---|---|---|
| Indexability | eligibility to be added to the index | the subject here |
| Crawlability | whether Googlebot can reach and read the page | a precondition for indexability |
| Noindex | a rule telling Google not to index a page | makes a page non-indexable on purpose |
| robots.txt | a file controlling crawling | blocks crawling, not indexing by itself |
| Canonical tag | a signal for the preferred URL among duplicates | affects which duplicate is kept |
Why it matters
A page that is not eligible cannot appear in results, however good it is. Most unintended exclusions come from a short list of causes, all visible to you: a robots.txt rule, a noindex left over from a staging site, an error status instead of 200, content behind a login, or a page that carries no indexable text. These are the cheapest to fix, so check them before anything about content quality.
How to check it
- Can Googlebot reach the page? Pages behind a login are not crawled, and pages blocked by robots.txt are unlikely to show in results. Use the URL Inspection tool to see whether crawling is allowed.
- Does it return HTTP 200? Google indexes only pages served with a success status; client and server error pages are not indexed.
- Is there an indexing block? Look for a noindex meta tag or an X-Robots-Tag header. Remember that a noindex placed in robots.txt is not supported by Google.
- Is there indexable content? The text must be in a file type Google supports and must not violate the spam policies.
- Is the canonical what you intended? URL Inspection shows the canonical you declared and the one Google selected.
- Read the Page indexing report. It lists pages where Googlebot found a noindex rule and gives a reason for every URL that is not indexed.
Practical example
| Page | Situation | Reading |
|---|---|---|
| /guide/ | public, returns 200, no blocks | eligible to be indexed; not guaranteed |
| /old-offer/ | returns 404 | not indexed: an error page |
| /private/ | noindex meta tag, crawling allowed | dropped from results once crawled |
The readings apply Google’s stated requirements to simple cases.
Common mistakes
- Blocking in robots.txt and adding noindex: if Googlebot cannot crawl the page, it never sees the noindex, and the URL can still appear.
- Putting noindex in robots.txt: Google does not support it there.
- Leaving noindex after a launch: a staging rule that stays on the live site keeps pages out.
- Treating indexable as indexed: Google says meeting the requirements does not guarantee indexing.
- Expecting instant removal after adding noindex: Google must crawl the page again, which can take months for some pages.
How to validate the result
Inspect the URL in the URL Inspection tool and read crawl allowed, page fetch and indexing allowed. Open the crawled page to see the HTML Googlebot actually received, including any noindex. After fixes, request indexing for important pages and watch the Page indexing report, allowing time for recrawling.
More questions
If a page is indexable, will Google index it?
Not necessarily. Google says that meeting the technical requirements does not mean a page will be indexed.
Does robots.txt stop indexing?
It stops crawling. Google says a blocked URL might still appear in results; to keep a page out, use noindex and allow crawling.
How do I make a page non-indexable?
Use a noindex meta tag or an X-Robots-Tag header, or protect the page with a login or remove it.
Next practical step
List your ten most important pages and inspect each: crawl allowed, HTTP 200, indexing allowed, canonical as intended. Fix any that fail. Then read about crawlability.
Related concepts
- Crawlability — whether Googlebot can reach a page.
- Noindex — telling Google not to index a page.
- robots.txt — controlling crawling.
- Canonical tag — the preferred URL among duplicates.
- URL Inspection tool — checking a single URL.