Index Coverage
Index coverage is the share of your pages engines have actually indexed. Learn how to read the report and what the common exclusion reasons mean.
TL;DR
Index coverage is the share of your pages that search engines have actually included in their index, and the reasons the rest were left out. In Google Search Console it appears as the page indexing report, splitting URLs into indexed and not indexed with a reason attached to every exclusion. It answers a question most teams never ask: is the content we published actually eligible to be found.
Why index coverage matters
Publishing is not the same as being indexed, and the gap between the two is invisible unless you look at it deliberately.
- Eligibility floor: A page that is not indexed cannot rank, cannot be retrieved, and is far less likely to be cited in AI answers.
- Reason codes: Exclusions come with diagnoses, which turns a vague suspicion into a specific fix.
- Quality signal: Large numbers of crawled-but-not-indexed pages usually indicate thin or duplicative content rather than a technical fault.
- Change detection: A sudden drop in indexed pages is the fastest warning of a deployment error.
How to read the index coverage report
Compare indexed against submitted
The gap between your sitemap URL count and your indexed count is the number worth watching over time.
Group exclusions by reason
Each reason points at a different cause. Treating them as one number hides which problem you actually have.
Separate intentional from accidental
Noindexed thank-you pages should be excluded. Your product pages should not.
Investigate crawled but not indexed
Google fetched the page and chose not to include it, which is nearly always a content quality or duplication judgement.
Check discovered but not crawled
Google knows the URL exists and has not fetched it, which points at crawl capacity or perceived low value.
Validate fixes and monitor
After correcting an issue, request validation and watch whether the affected group actually shrinks.
Index coverage vs. crawl budget
Index coverage: How many fetched pages made it into the index, and why the others did not. A quality and configuration question.
Crawl budget: How many pages get fetched at all. A capacity and attention question.
The distinction determines your fix. Pages excluded as crawled but not indexed were seen and rejected, so more crawling will not help. Pages sitting in discovered but not crawled were never seen, so content improvements will not help until they are.
Indexing problems produce no error page and no alert, so they surface only when someone checks. Findrix runs a 31-point technical audit covering index directives, canonicals and crawler access. Every gap comes with the fix already written: technical, content and off-site. The audit is free, takes about a minute, and requires no signup.
Common exclusion reasons
- Crawled, currently not indexed: Fetched and judged not worth including, usually thin or duplicative.
- Discovered, currently not indexed: Known but not yet fetched, often a crawl capacity signal.
- Duplicate without user-selected canonical: Google found duplicates and chose a different version than you would have.
- Alternate page with proper canonical tag: Working as intended, since the page canonicals elsewhere.
- Excluded by noindex tag: Intentional if you meant it, alarming if you did not.
- Blocked by robots.txt: Never fetched, so nothing on the page was ever read.
What crawled but not indexed usually means
This is the exclusion reason that generates the most anxiety and the most wasted effort. Teams read it as a technical fault and start auditing headers, when the page was fetched successfully and engines simply decided it did not earn a place.
The usual causes are unremarkable: the page duplicates something else on the site, it is thin relative to what already ranks, or it is one of two hundred near-identical location or category pages generated from a template.
The fix is editorial rather than technical. A smaller index of pages worth including beats a large one full of material engines have already declined.
Frequently asked questions
Why are my pages crawled but not indexed?
Google fetched them and judged them not worth including, which usually means thin content, duplication or low perceived value against what already ranks. It is a quality signal rather than a technical error.
How long does indexing take?
Anywhere from hours to weeks, depending on site authority, crawl frequency and how much engines want the content. New sites wait longer. Requesting indexing in Search Console helps for individual urgent URLs.
Does index coverage affect AI visibility?
Substantially for retrieval-based engines, which lean on indexed content when assembling answers. A page missing from the index is far less likely to be retrieved or cited, so coverage is a precondition for the visibility work above it.