Index Coverage

A page that is not indexed cannot rank in Google, regardless of how good the content is. Index coverage is how you know which of your pages are in contention for rankings — and which are being silently excluded and why.

What is index coverage?

Index coverage is a measure of how fully a website's pages have been added to a search engine's searchable database. A page must pass through three stages before it can rank: discovery (Google finds the URL), crawling (Googlebot fetches and reads the page), and indexing (the page is stored and made eligible for rankings).

Google Search Console's Pages report (formerly the Coverage report) shows the outcome of all three stages for every URL Google has encountered on your site. The report is updated daily and broken into four top-level statuses.

Why index coverage matters for SEO

Four practical reasons every SEO monitors this report:

1. Identify technical blockers before they worsen. A server error on a key landing page may go unnoticed in analytics (no traffic = no data) but shows immediately as an "Error" in the Pages report.
2. Validate sitemap submissions. After submitting a sitemap, coverage data confirms whether Google found and processed the URLs you submitted.
3. Monitor index bloat. A sudden rise in "Valid" page counts — without you publishing new content — often signals auto-generated or duplicate URLs being indexed unintentionally.
4. Track indexing trends over time. A steady decline in "Valid" pages after a site update is an early warning of a configuration change that is excluding content unintentionally.

How the Google Search Console Pages report works

The report organises every URL into four status categories. Each category has specific sub-reasons that identify the exact cause.

Error sub-reasons

• Server error (5xx) — page returned a 500+ HTTP response when Googlebot requested it
• Redirect error — a redirect chain or loop prevents Googlebot from reaching the final URL
• Submitted URL blocked by robots.txt — sitemap includes a URL that robots.txt disallows crawling
• Submitted URL marked noindex — sitemap includes a URL with a noindex directive (contradictory signal)
• Soft 404 — page returns 200 OK but serves a "not found" or near-empty response

Excluded sub-reasons

• Crawled — currently not indexed — Google read the page but excluded it, usually due to thin or duplicate content
• Discovered — currently not indexed — URL found but not yet crawled, often due to low crawl priority
• Duplicate without canonical selected — Google found duplicate content and chose a different URL as canonical
• Canonical to different page — page explicitly points to another URL as canonical; that URL is indexed instead
• Blocked by robots.txt — intentional exclusion via robots.txt disallow
• Excluded by noindex tag — intentional exclusion via meta robots or X-Robots-Tag
• Alternate page with proper canonical tag — working as intended for canonicalised duplicates

How to improve index coverage — step by step

Work through the report in priority order. Errors first, then warnings, then excluded pages worth recovering.

1. Fix all Error pages first. These are pages Google wants to index but cannot. Server errors need infrastructure fixes. Redirect errors need chain cleanup. Soft 404s need content or status code corrections.
2. Resolve Valid with Warnings. The most common warning is "Indexed, though blocked by robots.txt" — the page is indexed despite a crawl block, which creates uncertainty. Remove the robots.txt block or add a noindex directive to clarify intent.
3. Investigate Excluded pages selectively. Not all exclusions are problems. "Excluded by noindex" is correct for pages you intentionally hid. "Crawled — currently not indexed" for your top landing pages is a problem — improve content depth. "Discovered — currently not indexed" for important pages means you need more internal links to those URLs.
4. Prune low-value indexed pages. Pages in "Valid" status that receive zero clicks and serve no user need should be noindexed to improve overall site quality signals.
5. Keep XML sitemaps clean. Your sitemap should contain only Valid pages. Remove Errored or Excluded URLs from the sitemap — contradictory signals slow Google's processing.

Real index coverage scenarios and fixes

1. "Crawled — currently not indexed" on key blog posts

A marketing agency found 40% of their blog posts in "Crawled — currently not indexed" status. Investigation revealed the posts averaged 300–400 words with minimal unique data. After rewriting each post to 800–1,200 words with original statistics and examples, 85% were indexed within three weeks. The remaining 15% were consolidated into stronger pillar articles.

2. "Discovered — currently not indexed" on new product pages

An e-commerce site launched 200 new product pages that remained "Discovered — currently not indexed" for six weeks. The pages had no internal links — they existed only in the sitemap. Adding 3–5 internal links per page from existing category pages resolved the status for 90% of pages within two crawl cycles.

3. Sudden drop in "Valid" pages after plugin update

A site went from 340 Valid pages to 180 Valid pages after installing a new SEO plugin that accidentally applied noindex to all category pages. The Pages report flagged the change within 48 hours. Rolling back the plugin setting restored Valid page counts within four weeks of Googlebot recrawling the affected pages.

Index coverage vs. index bloat — understanding both sides

Index coverage and index bloat are two sides of the same problem.

7 best practices for healthy index coverage

1. Review the Pages report weekly for active sites. A coverage drop is easier to diagnose and fix when caught early.
2. Prioritise Error fixes before any other SEO work. A page in Error status earns zero organic traffic regardless of content quality or backlinks.
3. Keep your XML sitemap current. Submit only pages you want indexed. Remove Errored and Excluded URLs from sitemaps immediately.
4. Use canonical tags consistently for all duplicate variants. Filter pages, tracking parameter URLs, and paginated archives all need canonical tags pointing to the primary version.
5. Monitor coverage after every site change. CMS updates, plugin installs, and template changes are common sources of unexpected noindex or robots.txt directives.
6. Combine coverage data with analytics. A Valid page with zero organic clicks may be ranking for no queries — a signal the content needs improvement despite being indexed.
7. Investigate sudden Valid-page drops immediately. A 10%+ drop in Valid pages within a week almost always indicates a configuration change or technical error that needs urgent attention.

Common index coverage mistakes to avoid

• Ignoring "Crawled — currently not indexed" at scale — if 30%+ of your content is in this status, site-wide content quality is the issue, not individual pages.
• Accepting "Discovered — currently not indexed" without action — these pages need internal links; the status will not self-resolve on authority-building alone.
• Fixing errors without root-cause analysis — a single misconfigured template can generate thousands of error URLs. Fix the template, not each URL individually.
• Not checking coverage after site migrations — URL structure changes during migration frequently cause mass exclusion events that go undetected without active GSC monitoring.
• Treating all Excluded pages as problems — pages excluded by intentional noindex or canonical directives are correctly excluded; investigating them wastes time.

Frequently asked questions

Related glossary terms

Sources