
What the Index Coverage Report is
The Index Coverage report, now labeled the Pages report inside Google Search Console, tells you which of your URLs Google has indexed, which it hasn't, and the reason for every non-indexed page. If a page isn't in the index, it can't rank for anything, so this report is where most real indexing problems get caught before they cost you traffic.
It sits under Indexing → Pages in Search Console. The top of the report splits your known URLs into two buckets: Indexed and Not indexed. Below that, the "Why pages aren't indexed" table breaks the not-indexed pile down by cause, and each cause opens a list of example URLs you can export.
The key states, and what they actually mean
The report shows a lot of statuses. Most people only need to understand a handful of them, because those are the ones that either indicate a real problem or get misread as one. Here's the practical breakdown.
| Status | What Google is telling you | Is it a problem? | What to do |
|---|---|---|---|
| Indexed | The page is in the index and eligible to rank. | No | Nothing. Confirm the count roughly matches your real page count. |
| Crawled – currently not indexed | Google fetched the page but chose not to index it. | Often yes | Usually a quality signal. Improve depth, uniqueness, and internal links; merge thin pages. |
| Discovered – currently not indexed | Google knows the URL exists but hasn't crawled it yet. | Sometimes | Points to crawl-budget or priority issues on large sites. Strengthen internal linking and sitemaps. |
| Excluded by ‘noindex’ tag | The page carries a noindex directive. | Only if unintentional | Confirm you meant to noindex it. If not, remove the tag and request indexing. |
| Alternate page with proper canonical tag | Google indexed a different URL you pointed it to as canonical. | No, usually correct | Nothing, if the canonical target is the version you want ranked. |
| Duplicate without user-selected canonical | Google found duplicates and picked its own canonical, not yours. | Yes | Add an explicit canonical so you control which version wins. |
| Duplicate, Google chose different canonical than user | You set a canonical, but Google overrode it. | Worth checking | Your signals conflict. Align internal links, sitemaps, and canonicals on one URL. |
| Page with redirect | The URL redirects elsewhere, so it isn't indexed itself. | No, if intentional | Nothing, unless important URLs are redirecting by accident. |
| Not found (404) | The URL returns a 404. | Depends | Fine if the page is genuinely gone. Redirect if it moved and has value or links. |
| Blocked by robots.txt | Your robots.txt is stopping the crawl. | Only if unintentional | Check the disallow rule. Note: robots block prevents crawling, not indexing, so use noindex to keep a page out. |
| Soft 404 | Page returns 200 but looks empty or "not found" to Google. | Yes | Add real content or return a true 404/410 and redirect if appropriate. |
| Server error (5xx) | The server failed during crawl. | Yes | Investigate hosting, timeouts, or rate limiting. Recheck after the fix. |
A real example: reading the "not indexed" spike
Say you push 400 new tag-archive pages and a week later the Pages report shows this movement. The pattern tells you the story faster than any single URL does:
Not indexed (why pages aren't indexed)
Crawled - currently not indexed .......... +260 ← quality flag on the new tag pages
Excluded by 'noindex' tag ................ +120 ← expected, you noindexed paginated tags
Discovered - currently not indexed ....... +20 ← crawl queue, will resolve
Duplicate without user-selected canonical +0The 260 "Crawled – currently not indexed" is the one to worry about: Google looked at those tag pages and decided they weren't worth indexing. That's a content-value verdict, not a bug. The 120 noindexed pages are doing exactly what you told them to.
How to check it on your own site
- Open Search Console and go to Indexing → Pages.
- Look at the Indexed count and sanity-check it against how many pages you actually publish. Wildly high means junk URLs got indexed; wildly low means real pages aren't getting in.
- Scroll to "Why pages aren't indexed" and sort by the largest counts. Big numbers are where your time pays off.
- Click a status to open its example URL list, then export to CSV. The list is a sample, not every URL, so treat it as a diagnostic.
- Spot-check a few URLs with the URL Inspection tool to see the live vs. indexed state and the exact reason Google gives.
- Fix the cause, then hit Validate Fix on that status so Google re-crawls the affected set and reports back.
- Re-check in two to four weeks. This report lags real changes, so don't expect same-day movement.
Common mistakes and how to fix them
- Treating "Crawled – currently not indexed" as a technical bug. It's almost always a quality signal. Chasing crawl settings won't fix it; better, more distinct content will.
- Blocking a page in robots.txt to remove it from the index. A robots block stops crawling, so Google may still index the URL from links without seeing your noindex. Use a noindex tag and leave the page crawlable.
- Panicking over "Excluded by noindex" and "Page with redirect." These are often intentional. Confirm intent before you "fix" anything.
- Ignoring "Duplicate, Google chose different canonical than user." That means your signals contradict each other. Line up your canonical tags, internal links, and sitemap on one URL.
- Reading the example URL list as complete. It's a capped sample. For a full picture, crawl the site yourself and match it against the report.
FAQ
Where did the old "Index Coverage" report go?
Nowhere, it was renamed. Google now calls it the Pages report under Indexing. The data and statuses are the same; the label changed.
How long until a fix shows up here?
Usually two to four weeks. After you fix a cause and click Validate Fix, Google re-crawls a sample and updates the status. Large sites move slower.
Why is my indexed count higher than my page count?
You're probably getting parameter URLs, pagination, or duplicate paths indexed. Crawl the site, find the junk, and canonicalize or noindex it. See crawl budget for why this matters on bigger sites.
Does "Discovered – currently not indexed" hurt me?
Not directly, but at scale it signals Google is deprioritizing your URLs. Improve internal linking to the affected pages and make sure they're in your sitemap.
Can I force a page to be indexed?
You can request indexing via URL Inspection, but you can't force it. Google decides based on quality and value. If a page keeps getting rejected, that's feedback about the page. For the deeper workflow, see how to read and fix the Page Indexing report and the guide to finding and fixing coverage errors.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.







