SEO

Page Indexing Report

Also called Index Coverage report, coverage report

The Search Console report that shows which of your pages Google has indexed and gives a reason for each page it has not.

Quick facts: Page Indexing Report

Category
SEO
Also called
Index Coverage report, coverage report
Level
Intermediate
Affects
Indexing, crawl efficiency, visibility of new and updated pages
Where to see it
Google Search Console Page indexing report, URL Inspection tool, Sitemaps report
In this article4
  1. How the Page indexing report works
  2. Why it matters
  3. Common mistakes
  4. How to act on it

The Page indexing report is a report in Google Search Console that shows how many of your known URLs Google has indexed, and lists a reason for every URL it has left out. Before 2022 it was called the Index Coverage report, and many guides still use that name. You find it under Indexing, then Pages.

How the Page indexing report works

The report starts with a chart of indexed and not indexed pages over time. Below it, the “Why pages aren’t indexed” table groups the excluded URLs by reason. Clicking a reason shows example URLs (up to 1,000 per reason) and lets you inspect each one.

The reasons fall roughly into three groups:

Deliberate exclusions, usually fine

  • Page with redirect The URL forwards elsewhere, so the destination is indexed instead.
  • Alternate page with proper canonical tag Google has accepted your canonical tag pointing to another version.
  • Excluded by noindex tag You asked Google not to index the page. Fine if intended, serious if not.

Errors to fix

  • Server error (5xx) and Not found (404) on pages that should exist.
  • Blocked by robots.txt on pages you want in search.
  • Soft 404 The page returns a normal status but looks empty or like an error to Google.

Google’s own judgement

  • Discovered, currently not indexed Google knows the URL but has not crawled it yet, often a sign of a large site or weak internal links.
  • Crawled, currently not indexed Google fetched the page and chose not to index it, usually because it judged the content thin, duplicated or not useful enough.
  • Duplicate, Google chose different canonical than user Google disagreed with your canonical tag and picked another version.

You can filter the whole report to the URLs in a submitted sitemap, which is the most useful view: it shows how many of the pages you actually care about are indexed.

Why it matters

A page that is not indexed cannot appear in search at all, however good it is. For a new UK site, this report is often the first place a serious launch problem shows up, such as a staging noindex left on or a robots.txt rule blocking a whole section. On an established site, a sudden rise in “Crawled, currently not indexed” can be an early warning that Google is losing confidence in a template or a block of content.

Common mistakes

  • Trying to reach zero excluded pages. Most sites have many correctly excluded URLs, such as redirects, parameter URLs and alternate versions with a canonical elsewhere.
  • Treating every reason as an error. Only exclusions affecting pages you want indexed need action.
  • Clicking “Validate fix” before fixing. Validation re-checks the URLs; if nothing changed, it fails and you have wasted weeks.
  • Requesting indexing page by page as a strategy. If Google will not index a page, the cause is usually content or linking, and resubmitting does not change that.
  • Reading the data as live. The report lags by several days.

How to act on it

Filter the report to your XML sitemap so you are looking at intended pages only. For each reason affecting those pages, open a few example URLs with the URL Inspection tool to confirm what Google sees.

Fix errors first: remove stray noindex tags, correct robots.txt, repair broken templates and server faults. Then deal with the judgement calls. For pages crawled but not indexed, improve or merge thin content and strengthen internal links; for canonical disagreements, remove the duplicate signals that confuse Google. Only when the cause is fixed should you click Validate fix and let Google re-check.

If the reasons point to something structural, such as thousands of filter URLs or a template producing near-duplicate pages, my technical SEO service works through exactly this report as a starting point.

Do and do not

Do

  • Filter the report to your submitted sitemap
  • Inspect example URLs before deciding on a fix
  • Fix the cause before clicking Validate fix

Do not

  • Aim for zero excluded pages
  • Treat every exclusion reason as an error
  • Rely on repeated indexing requests instead of fixing content

Questions people ask about this

What does "Crawled, currently not indexed" mean?

Google has visited the page and decided not to add it to the index for now. The usual reasons are thin or duplicated content, a page that adds little beyond others on your site, or weak signals that it matters. Improving the content, merging overlapping pages and adding relevant internal links are the fixes that tend to work.

Is the Page indexing report the same as the Index Coverage report?

Yes. Google renamed and redesigned the Index Coverage report as the Page indexing report in 2022. The reason labels changed slightly, but the purpose is the same: showing which known URLs are indexed and why others are not.

How long does Validate fix take?

Google says validation typically takes up to about two weeks, sometimes longer, because it re-crawls the affected URLs on its own schedule. You can keep working while it runs. If validation fails, open the remaining example URLs to see which still show the problem.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.