Index Coverage
Also known as: Page Indexing report, index status
Index coverage refers to which of a site's URLs a search engine has crawled and included in its index, and the reasons others are excluded. Google Search Console's Page Indexing report groups URLs by status such as indexed, crawled but not indexed, and excluded.
Key Takeaways
- Index coverage refers to which of a site's URLs a search engine has crawled and included in its index, and why others are excluded.
- Google Search Console's Page Indexing report groups URLs by status such as indexed, crawled but not indexed, and excluded.
- A page cannot rank in search if it is not indexed, so coverage problems directly cost traffic.
- High indexed counts are not the goal; the right pages indexed matters more than the most pages indexed.
- Thin, duplicate, or auto-generated pages can bloat the index and dilute overall site quality.
How It Works
Index coverage reflects the outcome of crawling and indexing. Search engines discover URLs, crawl the ones they can reach, and decide whether each is worth adding to the index. Google Search Console's Page Indexing report shows the result, grouping URLs by status and listing reasons for exclusion, such as duplicate, noindex, or crawled but not indexed.
Several factors shape coverage. Limited Crawl Budget can leave lower-priority pages uncrawled on large sites. A Canonical Tag can consolidate duplicates so only one version is indexed. Rules in Robots.txt can block crawling entirely, which prevents indexing of those paths.
Discoverability also matters. An Orphan Page with no internal links is hard for crawlers to find, so it may never enter the index. Monitoring coverage regularly surfaces valuable pages that are silently excluded and low-value pages that pad the index, letting you fix causes before they cost rankings.
Why It Matters
A page cannot rank if it is not indexed. Monitoring coverage reveals when valuable pages are silently excluded or when low-value pages bloat the index, so you can fix the causes before they cost traffic.
Example
A blog owner notices organic traffic slipping and checks the Page Indexing report. Several key articles show crawled but not indexed, and dozens of thin tag-archive pages are indexed instead. They improve internal linking to the important posts, add noindex to the thin archives, and resubmit. Over the following weeks the valuable pages get indexed and the index bloat clears.
Common Mistake
Treating high indexed counts as success. Thin, duplicate, or auto-generated pages padding the index can dilute site quality; the goal is having the right pages indexed, not the most pages indexed.
Frequently Asked Questions
Why is my page crawled but not indexed?
Google crawled the page but judged it not worth indexing, often due to thin or duplicate content, weak internal linking, or low perceived value. Improving content depth, uniqueness, and internal links usually helps the page qualify for indexing.
How do I check my index coverage?
Open Google Search Console and view the Page Indexing report. It shows how many URLs are indexed versus not indexed and groups the not-indexed pages by reason, so you can prioritize which issues to fix first.
Is more indexed pages always better?
No. Indexing thin, duplicate, or auto-generated pages can dilute site quality and waste crawl resources. The goal is having your valuable pages indexed, not maximizing the raw count of indexed URLs.
How do I get a page indexed faster?
Ensure it is crawlable, linked internally, and not blocked by robots.txt or noindex. Submit it in Search Console and include it in your XML sitemap. Strong, unique content and internal links improve the odds of quick indexing.