Page Indexing (Index Coverage) Report

What the Page Indexing report (formerly Index Coverage) in Google Search Console means, every 'Not indexed' reason explained, and how to fix them.

First published: Jun 23, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #8 in Search Engine Tools#11 in Tools#193 in Technical SEO#267 on the site
AIAuthored byAI v2
1 evidence signal on this page

The Page Indexing report (renamed from Index Coverage in 2022) covers URLs Google already knows about — not a full site inventory — and shows which are indexed, which aren't, and why, using a capped sample of example URLs per reason. The key skill is reading it: most not-indexed reasons are pages working as intended (canonicalized dupes, redirects, intentional noindex), so don't chase 100% indexing. Two reasons matter most — 'Crawled - currently not indexed' is most often a quality verdict, 'Discovered - currently not indexed' is most often a crawl-capacity problem — but treat each as the leading hypothesis to confirm against your own pages, not a certain diagnosis. Use Validate fix after you've fixed the cause; passing it doesn't guarantee indexing, rankings, or traffic. Pair the report with the URL Inspection tool and Sitemaps filtering.

TL;DR — The Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason. (renamed from IndexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. Coverage at Google I/O in May 2022) covers URLs Google already knows about — not a full site inventory — and splits them into Indexed and Not indexed, then buckets the not-indexed ones by reason using a capped sample of example URLs per issue, not a complete export. Reading it well means knowing that most reasons are pages working as intended — Google says “Don’t expect every URL on your site to be indexed.” The two reasons worth real attention are “Crawled - currently not indexed” (most often a quality/value verdict — fix at the site level, not page-by-page) and “Discovered - currently not indexedA Google Search Console Page Indexing status meaning Google knows the URL exists but hasn't crawled it yet — the Last Crawl date is empty. Often a crawl-capacity or crawl-demand (site-quality) signal.” (most often a crawl-capacity/importance problem — fix crawl health and internal links); treat either label as the leading hypothesis to test against the actual pages, not a certain diagnosis. Use Validate fix after fixing the cause; it samples pages and can take ~two weeks, and passing it confirms the report caught up with reality — it doesn’t guarantee indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., rankings, traffic, or AI-search visibility. Pair the report with the URL Inspection toolA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. and SitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. filtering.

Evidence for this claim The current Page indexing report shows which known pages Google has indexed and why other known pages are not indexed. Scope: Current Search Console Page indexing report and terminology. Confidence: high · Verified: Google Search Console: Page indexing report Evidence for this claim Validate Fix starts a recrawl-based validation process after an issue is fixed; examples in the report are not a complete URL inventory. Scope: Current validation workflow and report limits. Confidence: high · Verified: Google Search Console: Validate and fix issues

What the report is, and the rename

The Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason. is Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s answer to “which pages can Google find and index on my site, and what’s stopping the rest?” In Google’s own words, it lets you “See which pages Google can find and index on your site, and learn about any indexing problems encountered.”

Google previewed the renamed “Pages” / “Page indexing” report at Google I/O in May 2022, retiring the old “Index Coverage” name. The data itself had been overhauled a year earlier: on January 11, 2021 Google shipped a set of Index Coverage data improvements, announced as “significant improvements to this report so you’re better informed on issues that might prevent Google from crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. and indexing your pages.” As of this writing, Google’s UI and Help docs use only “Page indexing” — I still call out “Index Coverage” because a large share of people search that legacy name, not because the two names are still interchangeable in Google’s own documentation.

Indexed vs Not indexed is descriptive, not a scorecard

Before looking at any totals: the report only covers URLs Google already knows about in the property — it’s not a guaranteed inventory of every URL on your site — and the example URLs listed under each reason are a capped sample (up to 1,000 for the Indexed list, per current Help text), not a complete export. Keep that scope in mind whenever you read a count.

The report sorts every known URL into Indexed (eligible to appear in Search) and Not indexed (everything Google is holding back, grouped by reason). The mistake I see constantly is treating that “Not indexed” count as a problem to drive to zero. It isn’t. Google is explicit: “Don’t expect every URL on your site to be indexed.” A healthy site has a large pile of intentionally not-indexed URLs — canonicalized duplicates, redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., deliberately noindexed utility pages, gated content. Many of the “errors” in this report are pages working exactly as designed.

So before fixing anything, ask which bucket a reason falls into: working as intended, a directive you set, or an actual problem.

Every “Not indexed” reason — what it means and what to do

Most competing articles only cover the two “currently not indexed” reasons. Here’s all twelve, with Google’s verbatim definitions, in the Cheat Sheets tab as a “reason → meaning → fix” table. The short version, grouped by bucket:

Working as intended (usually no action):

  • Alternate page with proper canonical tagA Google Search Console Page Indexing status meaning a page is a duplicate or alternate version that correctly points its canonical at another, indexed page. It's normal, healthy behavior — Google says there is nothing you need to do. — “This page correctly points to the canonical page, which is indexed, so there is nothing you need to do.”
  • Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\"). — the URL itself won’t be indexed; the redirect target might or might not be. Verify the target is right, otherwise leave it.
  • Excluded by ‘noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed.’ tag — Google found a noindex directive and obeyed it. Only “fix” this if the page was meant to be indexed. (The report UI shows “Excluded by ‘noindex’ tag”; older Help text phrased it “URL marked ‘noindex’” — match whichever you see.)
  • Blocked due to unauthorized request (401) — expected for genuinely gated content; a problem only if a public page got locked behind auth.

CanonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. (decide if Google chose right):

  • Duplicate without user-selected canonicalA Google Search Console Page Indexing status: Google found this page to be a duplicate, you didn't declare a canonical, so Google chose a different page as the canonical — and this URL isn't indexed. — Google picked another page as canonical and won’t serve this one. Set an explicit canonical / consolidate.
  • Duplicate, Google chose different canonical than userA Google Search Console Page Indexing status: you declared a canonical for this URL, but Google overrode your choice, picked a different page as the canonical, and indexed that one instead. — your canonical signal was overridden. This is common and not a mistake on your part; strengthen signals (canonical, internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them., content) toward your preferred URL.

Actual problems (fix if the page should exist):

  • Not found (404) — “404 responses are not necessarily a problem, if the page has been removed.” Fix only if the URL should resolve.
  • Soft 404A soft 404 is a URL that returns a success status code (usually 200 OK) even though the page is empty, missing, or shows a 'not found' message. It isn't a status code a server sends — it's a label search engines apply after comparing the response code against the rendered content, and they treat the page like a 404 for indexing. — the page returns a “not found” message but a 200 status code. Return a real 404/410, or add genuine content.
  • Blocked by robots.txtA Google Search Console Page Indexing status: the URL was excluded from indexing because your robots.txt disallows crawling it. Usually intentional and benign — robots.txt blocks crawling, not indexing. — unblock if it should be crawled. Remember robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. blocks crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., not indexing.
  • Server error (5xx) — your server returned a 500-level error. Investigate hosting; often transient or load-related.

The two that need their own section — Crawled - currently not indexed and Discovered - currently not indexed — below.

Crawled vs Discovered — the distinction to nail

These two labels look like twins and Google’s own reason documentation tells you to review the specific reason and the page’s context rather than assume one fixed cause — so treat what follows as the most likely explanation to test against your actual pages, not a universal diagnosis that applies to every URL carrying the label.

“Discovered - currently not indexed” is most often a capacity problem. Google knows the URL exists but hasn’t crawled it yet. Google’s definition: the page “was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site.” In the Ahrefs guide on “Discovered - currently not indexed” (which I reviewed), we put it plainly: “‘Discovered - currently not indexed’ means Google knows about the URL but hasn’t yet crawled or indexed it.” The commonly cited drivers are crawl budget and perceived importance — “If your crawlable URLs exceed your crawl budget, you may see the ‘Discovered - currently not indexed’ warning,” and “Google often sees URLs without any or many internal links as unimportant and may not index them.” Those are hypotheses to check, not a checklist that applies identically to every URL: look at the specific page’s internal links, crawl logs, and server response before picking a fix. Reduce crawl waste, speed up the site, and add internal links (and, for the pages that truly matter, request indexing and build links) once you’ve confirmed which of those is actually happening.

“Crawled - currently not indexed” is most often a quality/value verdict. Google’s definition: the page “was crawled by Google but not indexed. It may or may not be indexed in the future.” In other words — Google saw it and passed. In the Ahrefs guide on “Crawled - currently not indexed”: “Google has successfully visited your page but has chosen not to include it in its search index,” and it “typically points to some kind of quality issue.” That’s a strong pattern, not a certainty for every affected URL — some pages carry the label for reasons closer to duplication or timing than quality. The single most useful reframe here comes from John Mueller: this is rarely about one page. As he put it, “you can’t force pages to be indexed — it’s normal that we don’t index all pages on all websites. It’s not an issue with ‘that page’, it’s more site-wide. Creating a good site structure and making sure the site is of the highest quality possible is essentially the direction.” So start by inspecting a sample of the actual affected pages, then work at the site level: raise overall quality, consolidate thin pages, improve structure — not patch one URL and move on.

The clean mental split, as a starting hypothesis rather than a fixed rule: Discovered = crawl-budget/capacity (Google hasn’t gotten to it). Crawled = quality/value (Google got to it and declined). Confirm against your own examples before committing to a fix.

TIP Resolve observable eligibility conflicts before guessing about Google's index

This check reports live response, redirect, noindex, and canonical signals. It cannot query Google's private index state, so confirm that separately in URL Inspection.

Preflight a URL’s indexability signals with my free Google Index Checker Free

  1. Test an affected URL and separate response, redirect, robots, and canonical observations.
  2. Fix only the signals that conflict with the page’s intended index state.
  3. Use URL Inspection and the Page Indexing report to verify Google’s observed canonical and index status after recrawl.
Several observable signals can explain one excluded URL; resolve them as a system before requesting another crawl.

The result lists four observable signals: the URL is not a live 2xx response because it returned 404, the request followed one redirect, a noindex directive was observed, and the canonical points to a different preferred URL.

A real audit pattern

When you see “Crawled - currently not indexed” at scale, treat it as a site-wide audit, not a page-by-page chase. I’ve done this on the Ahrefs blog — thousands of crawled pages, working through which low-value or outdated ones to prune, consolidate, or improve rather than trying to force every URL into the index. That pruning mindset is the practical expression of Mueller’s “it’s more site-wide” point: when a chunk of your site reads as low value, the lever is the site, not the individual URL.

How to use Validate fix

When a reason represents a genuine problem and you’ve fixed the underlying cause, click Validate fix on that issue. The mechanics matter:

  • It samples, not exhaustively. “When you click Validate Fix, Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. immediately checks a few pages.”
  • It can surface unrelated issues mid-run. “If validation finds other unrelated issues, these issues are counted against that other issue type and validation continues.”
  • It’s slow. “Validation typically takes up to about two weeks, but in some cases can take much longer.”
  • The state machine runs Started → Passed / Failed / Looking good.

The cardinal rule: fix the underlying cause first. Clicking Validate before you’ve actually fixed anything just burns two weeks ending in “Failed.”

One more thing to be clear on: a passed validation, a favorable report status, a successful URL Inspection, or a submitted sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. — none of these guarantee indexing, rankings, traffic, or AI-search visibility/citation. They only confirm that the specific signal they check (a directive, a status, a canonical) now matches what you intended. Indexing is necessary for a page to compete in Search; it’s never sufficient on its own.

The sampling caveat, and the sibling reports

One limitation to internalize: the report shows only a capped sample of example URLs per issue, not the full list. The counts are complete, but the example URLs aren’t — so don’t assume the dozen URLs shown are the only ones affected.

That’s exactly why you pair this report with two siblings. The URL Inspection tool is how you check the live index state of a single URL — the report gives you the pattern, URL Inspection confirms one page (and is where you request indexing or a re-crawl). And you can filter the report by a specific sitemap from the Sitemaps reportThe Google Search Console report where you submit sitemaps and watch how Google processes them — type, last read date, status, and how many URLs were discovered. It confirms Google read your list; it doesn't prove anything got indexed. to scope it to just the URLs you actually care about, which cuts through the noise on large sites. The report is the diagnosis layer of the broader indexing picture; these two narrow it down.

A few myths worth killing

  • “100% indexed is the goal.” No — “Don’t expect every URL on your site to be indexed.”
  • “Crawled - currently not indexed is a penalty or bug.” No — it’s a value judgment; fix site-wide quality.
  • “robots.txt disallow and noindex do the same thing.” No — robots.txt blocks crawling; a blocked page can still be indexed URL-only. To remove a page, allow crawling and use noindex.
  • “Repeatedly clicking Request indexing forces indexing.” It can’t force indexing of low-value or duplicate pages.
  • “A 404 in the report is always bad.” 404s for removed pages are fine and expected.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.