What Is the Page Indexing Report (formerly the Index Coverage Report)

The Page indexing report — renamed from the Index Coverage report in 2022 — is the Google Search Console section that shows which of your site's URLs Google has indexed and exactly why it left specific pages out. Every URL Google knows about appears here with either an Indexed or Not indexed status, and every Not indexed URL gets a named reason.

Google redesigned GSC navigation announced at Google I/O in May 2022. The "Coverage" nav section became "Pages"; the report became the "Page indexing report." Google's live help article is titled Page indexing report — confirming the rename is the current canonical name, first reported in May 2022. Both names remain in active use: "index coverage report google search console" generates 150 searches per month (Ahrefs, June 2026) — this article uses both names so it surfaces for either search.

The report displays two tabs. Indexed means Google crawled, rendered, and added the URL to its index — those pages are eligible to appear in search results. Not indexed means Google knows the URL exists but has not indexed it. Every Not indexed URL carries a named reason drawn from a taxonomy of 14 labels — the core reference this article documents. The report lives under Indexing > Pages in current GSC navigation. For broader context on what GSC tracks and why, see the Google Search Console overview and the foundational core SEO concepts like canonicalization and crawl budget.

The report is a triage tool, not a to-do list. The most common mistake is treating every Not indexed URL as a defect. "Alternate page with proper canonical tag," "Excluded by noindex tag," and "Page with redirect" are expected healthy outcomes of deliberate site architecture. The diagnostic value is in the unexpected exclusions: "Crawled - currently not indexed" on pages you want ranking, a growing "Discovered - currently not indexed" count signaling crawl budget pressure, or a submitted-vs-indexed gap pointing to a content quality problem.

Key Takeaways

• Sort statuses before fixing. Three buckets: Expected (no action), Investigate, Fix immediately. Most Not indexed URLs in a healthy site are Expected.
• "Crawled - currently not indexed" is a quality signal. Google visited the page and chose not to index it — no technical fix applies. Improve content depth and uniqueness.
• Validate fix does not speed up recrawling. It starts a reporting window in GSC. To accelerate recrawl: use the URL Inspection tool > Request indexing or resubmit your sitemap.
• Track the submitted/indexed ratio, not the raw count. The Sitemaps report ratio (indexed ÷ submitted × 100%) is the ongoing health metric. A declining ratio signals worsening content quality assessment.
• "Discovered - currently not indexed" at scale means crawl budget, not quality failure. On large sites, Googlebot hasn't reached those URLs yet.
• Canonicalization statuses are errors only when Google chose wrong. "Alternate page with proper canonical tag" = healthy. "Duplicate, Google chose different canonical than user" = act.

Crawled vs. Discovered: The Two Most Searched Indexing Statuses

The two most searched indexing statuses in Google Search Console are "Crawled - currently not indexed" and "Discovered - currently not indexed." They look similar but represent fundamentally different problems with different fix paths.

The distinction matters because the fix path is opposite. "Crawled - currently not indexed" means Google already looked at the page and made a quality judgment — submitting it to a sitemap or clicking Request indexing does not change that judgment. "Discovered - currently not indexed" means Google hasn't gotten there yet — the sitemap and Request indexing are precisely the right tools. Misdiagnosing which status you have leads to wasted effort.

For large sites (100K+ pages), a count of thousands of "Discovered - currently not indexed" URLs is often a crawl budget allocation problem, not a content quality problem. The Sitemaps & URL Inspection guide covers the specific tools — sitemap submission and Request indexing — that apply to this status. MB Adv Agency has found that on content-heavy sites, the "Crawled - currently not indexed" count spikes most reliably after content culls or CMS template changes that reduce per-page uniqueness — the clearest signal that the content, not the technical setup, is the variable.

Why Pages Aren't Indexed: The Complete Status Reference (Page Indexing / Index Coverage Report)

The Page indexing report (formerly the Index Coverage report) groups all Not indexed URLs by reason. The table below documents every named reason in the current GSC UI, what each means, its typical cause, and how to triage it. Three triage categories: Expected (no action needed), Investigate (audit before acting), and Fix immediately.

When you open the Page indexing report, sort the Not indexed reasons into three buckets before acting on anything. Expected (Alternate page with proper canonical tag, Excluded by 'noindex' tag, Page with redirect): these confirm your architecture is working — only act if a URL should NOT be excluded. Investigate (Crawled - currently not indexed, Discovered - currently not indexed, Duplicate without user-selected canonical): cross-reference with recent site changes, content quality, and crawl budget signals before deciding on a fix. Fix immediately (Server error 5xx, Blocked due to access forbidden 403 when unintentional, Soft 404 on pages that should return real content): these block Google from content you want indexed and need direct resolution.

"Submitted and indexed" is a separate positive status in the Sitemaps report — not to be confused with "Indexed, not submitted in sitemap" in the Page indexing report. Cross-referencing indexation data with the Performance report shows whether indexed pages are actually generating clicks and impressions, which is the downstream measure that matters. Full reason definitions appear in Google's official documentation at support.google.com/webmasters/answer/7440203 and support.google.com/webmasters/answer/156336.

The Submitted vs. Indexed Gap: Reading the Sitemaps Report

The Sitemaps section of Google Search Console shows two numbers for each submitted sitemap: Submitted (URLs parsed from the sitemap file) and Indexed (how many of those Google chose to index). The gap between these two numbers — and how it changes over time — is one of the most useful indexing health signals GSC provides.

The Sitemaps view does not break down the gap by reason — for that, open the Page indexing report and filter by the specific sitemap. Applying that filter shows which reason labels account for the submitted-but-not-indexed URLs, turning a raw gap into an actionable diagnosis. Full documentation for the Sitemaps report is at Google Help, Sitemaps report.

A widening gap over time — where the submitted count stays constant but the indexed count declines — is the strongest signal that Google is progressively devaluing the content corpus. A sudden drop correlates almost always with a site change. Tracking the ratio in a simple spreadsheet monthly is a sufficient monitoring cadence for most content sites. Use the Performance report to track organic traffic trends alongside indexation — a declining indexed count that does not correspond to a traffic drop can mean the lost pages were not generating clicks anyway, which changes the priority of the fix.

Validate Fix in Google Search Console: States, Timelines, and What It Actually Does

Validate fix is the mechanism in the Page indexing report for confirming that an issue category has been resolved. After fixing an indexing problem — removing an accidental noindex, correcting a robots.txt block, fixing a server error — you click Validate fix on the affected reason category to start GSC's tracking window. The critical clarification: clicking Validate fix does not make Google recrawl your pages faster.

"Validate fix does not speed up recrawling." John Mueller confirmed this directly: the button "will only track how things are being reprocessed and won't speed up reprocessing itself" (Search Engine Roundtable). The validation timeline — "two weeks or more depending on crawl frequency" per Google Help — is determined entirely by Googlebot's normal crawl schedule for the site. Practitioners who click Validate fix and then observe recrawl activity within hours are seeing Googlebot's scheduled crawl, not a validation-triggered crawl.

To actually accelerate recrawling of specific fixed pages, use these two mechanisms: (1) URL Inspection tool > Request indexing for individual priority pages — this sends a signal to Googlebot's crawl queue, subject to a daily quota that Google does not publish; (2) Resubmit your sitemap containing the fixed URLs — this gives Googlebot a refreshed priority signal for the URL set. Use Validate fix for its actual purpose: audit trail and issue-resolution confirmation. The URL Inspection and sitemap tools are the correct mechanism for accelerating recrawl. Full documentation on requesting recrawl is at Google Search Central.

Canonicalization Statuses in the Page Indexing Report

Four Page indexing report statuses relate directly to canonicalization — Google's process of selecting a single preferred URL when multiple pages share near-identical content. These statuses are Google's canonicalization decisions made visible. They are only errors when Google chose the wrong canonical, not when Google and the site owner agree.

Google selects the canonical based on its own quality signals, which can differ from the rel="canonical" hint provided by the site. The canonical hint is not a directive — it is a signal. Signals Google uses: which URL appears in sitemaps, which URL has more internal links, which has stronger external backlink signals, which is served on the preferred protocol (HTTPS vs HTTP), and which has better performance and quality signals overall. Full guidance on canonical consolidation is at Google Search Central: Consolidate duplicate URLs. For a broader treatment of SEO concepts like canonical tags and duplicate content, the glossary covers the foundational principles.

Temporary and Permanent URL Removal: Using the GSC Removals Tool

The URL Removals tool in Google Search Console handles two distinct use cases: temporary removal of a URL from search results (for urgent situations requiring up to six months of suppression) and removing outdated cached content or snippets. Neither option is a permanent deletion mechanism — permanent removal requires server-side action.

The temporary removal tool does not prevent Googlebot from crawling the URL — Googlebot continues to crawl and index the content in Google's internal systems during the blackout period. The ~6-month duration is the only confirmed timeline from Google documentation. Plan permanent fixes (correct server response or noindex tag) within that window. Full documentation is available at Google Help, Removals and SafeSearch reports tool and Search Engine Land's guide to Google's removal tools.

Diagnosing Indexing Issues: A Symptom-by-Symptom Framework

Indexing issues manifest in several distinct patterns, each pointing to a different starting point in GSC. The table below maps the symptom to the correct report section and what to look for — avoiding the common trap of opening the URL Inspection tool for every indexing question when a report-level view is more efficient.

The URL Inspection tool — accessible via the search bar at the top of GSC or the Inspect URL link in the Page indexing report — is the fastest single-page check. It shows the last-crawled HTML, the canonical Google selected, and the current coverage status with its reason label. For bulk diagnosis, the Page indexing report's filter-by-sitemap and filter-by-reason combination is faster than inspecting URLs individually. Core Web Vitals issues can affect how Google prioritizes crawling and are a secondary signal worth reviewing when "Crawled - currently not indexed" counts rise without a clear content explanation. Full URL Inspection tool documentation is at Google Help, URL Inspection tool.

Crawl Budget and 'Discovered - Currently Not Indexed' at Enterprise Scale

On sites with tens of thousands or hundreds of thousands of pages, 'Discovered - currently not indexed' is the indexing status most directly tied to crawl budget — Googlebot's allocation of resources to a specific site. Botify's analysis of enterprise client data (sites with 1M+ pages) quantifies the gap between what large sites have and what Google actually crawls.

These figures explain why "Discovered - currently not indexed" counts in the thousands or tens of thousands are routine on large enterprise sites — not an indication of a content quality problem, but a reflection of how Googlebot allocates its crawl budget across a large URL space. For sites of this scale, improving the crawl ratio requires structural changes: flatter internal link architecture, sitemap segmentation by priority, crawl-rate adjustments via GSC settings, and elimination of low-value URL parameters consuming crawl budget. Full enterprise crawl budget analysis is available at Botify, All About Crawl Budget Optimization and Botify, Crawl Ratio, Render Ratio, and Why They Matter for SEO.

MB Adv Agency has found that on large e-commerce and publisher sites, addressing crawl budget waste — specifically by removing or canonicalizing low-value parameter URLs that consume Googlebot's attention — reliably reduces the 'Discovered - currently not indexed' count over a 60-90 day window. The mechanism is freeing up crawl capacity for the URLs that matter.

For SMB content sites (under 10,000 pages), crawl budget is not a limiting factor. A "Discovered - currently not indexed" count in the hundreds on a small site points to content quality or internal linking, not crawl allocation. The Botify enterprise data does not apply to sites at that scale. For large-scale indexing monitoring, GSC API and automation for large-scale indexing monitoring covers the programmatic approach to tracking crawl coverage across high-page-count sites.

Data sources used for this article: Ahrefs keyword data (June 2026, US market, operator-supplied); IndexCheckr, “Google Indexing Study: Insights from 16 Million Pages” (2024, indexcheckr.com/resources/google-indexing); Botify, crawl budget and crawl ratio research (enterprise client dataset, 2024–2025, botify.com/blog/crawl-budget-optimization); Google Search Console Help documentation (support.google.com/webmasters); Search Engine Land and Search Engine Roundtable (2022–2026 coverage); Google Search Central developer documentation (developers.google.com/search). Submitted/indexed ratio thresholds are practitioner benchmarks and are not published by Google. Last updated: June 2026. Reviewed by MB Adv Agency, June 2026.