Definition
Indexability describes whether a page, once fetched, is eligible to be stored in an index and returned in results. Crawlability is the step before it, covering whether a bot could reach and read the page at all. A page can be crawled every day and still be kept out of the index by a single tag.
At a glance
- CategoriesTechnical
- Related fieldsSEO, Technical
- DifficultyIntermediate
At a glance
- Indexability is decided after the fetch, by tags and signals carried on the page itself.
- A noindex meta tag removes a page from the index even though the crawler read it happily.
- A canonical tag pointing elsewhere tells the index to keep the other page instead.
- Search Console’s page indexing report names every URL that was fetched and not kept.
The signals that decide whether a fetched page is kept
Once a crawler has your HTML, a second set of decisions runs.
The meta robots tag goes first. A noindex value is absolute: the page was read and it will not be stored. Right for thank-you pages and internal search results, wrong for anything you want found.
The canonical tag comes next. It nominates which URL among near-duplicates should be kept. Point five variants at one canonical and you get one indexed page, which is usually the intent.
Quality signals come last and are the fuzzy part. A page duplicating another, or carrying almost nothing of its own, can be fetched and quietly dropped with no tag asking for that.
A sitemap helps with discovery, not with any of this. Listing a noindexed URL in one sends two contradictory instructions.
Faceted URLs multiply until nothing is the page
Ecommerce is where this breaks at scale. A single category generates hundreds of URLs through filters, sort orders and tracking parameters, each a near-copy of the rest.
Nothing is blocked. Everything gets crawled. The index then has to choose which version represents the category, and with no canonical tag saying so, the choice is arbitrary. Plenty of sites end up with a sorted-by-price variant standing in as the real page, while the real one competes with its own filtered copies.
There is a related trap on the rendering side. A page whose content appears only after JavaScript runs can be fetched, scored as thin and dropped, because the indexer read an empty shell. Server-side rendering takes that risk off the table.
Find the pages that were fetched and thrown away
Search Console does most of this for free.
- Open the page indexing report and read the “not indexed” reasons. They are specific: excluded by noindex, alternate page with canonical, crawled and currently not indexed.
- Check the noindex list against reality. Any commercially important URL sitting there is a bug, usually a template default that survived a launch.
- Audit canonical tags on one template. Self-referencing on the page you want kept, pointing at it from every variant.
- Strip parameters out of the sitemap. Google’s sitemap guidance is to list canonical, indexable URLs and nothing else.
- Re-check after any migration. Redirect chains and stale canonicals are the two things that survive a replatform completely intact.
Why a crawled page does not get kept
| Signal | What it tells the index | When it is the right call |
|---|---|---|
noindex |
Do not store this page | Thank-you pages, internal search results |
| Canonical elsewhere | Keep the other URL instead | Filtered and parameterised duplicates |
| Thin or duplicate content | Nothing here worth storing | Almost never deliberate |
| Soft 404 | This page is effectively empty | Retired products with no replacement |
Frequently asked questions
-
Is indexability the same as crawlability?
No. Crawlability is about access: can a bot reach and read the page. Indexability is about eligibility: having read it, will the system keep it. Every indexed page had to be crawlable first, and plenty of crawlable pages are excluded on purpose.
-
How do I check whether a specific page is indexed?
Use the URL inspection tool in Search Console, which reports the status and the reason behind it. A site: query gives a rough answer but is not reliable enough to act on. No AI surface offers an equivalent tool, which is why the Search Console check remains the best proxy.
-
Does being indexed by Google mean AI assistants can use my page?
Not necessarily, and treating the two as the same causes confusion. Assistants build their own retrieval sets, some using search results and some their own crawls. Google indexing is a reasonable signal that your page is reachable and readable. It is not a guarantee that any assistant has it.
-
Should every page be indexable?
No, and trying is a mistake. Checkout steps, account pages, internal search results and thin tag archives all belong out of the index. A smaller set of pages that each say something worth keeping beats a large set competing with itself, and structured data on the ones you keep makes their facts unambiguous.