The Page Indexing Report in Google Search Console, Explained

The Page Indexing report in Google Search Console tells you which of your pages are in Google's index, which are not, and the specific reason behind every not-indexed URL. It is the single best place to diagnose why pages are missing from search, and it replaced the older report many people still call the index coverage report. If you want to act on what it shows by pushing URLs back at Google, you can also submit them through URL Indexer, but reading the report correctly comes first, because the right fix depends entirely on the reason status next to each URL.

This guide walks through the two top-line numbers, the reason statuses that matter most, and a simple way to decide what to fix first instead of chasing every line.

Where do you find the Page Indexing report?

You find the Page Indexing report under the Indexing section in the left sidebar of Google Search Console, labeled "Pages". It only shows data for properties you have verified, so it covers sites you own. The report opens on a chart with two stacked totals, "Indexed" and "Not indexed", followed by a table of reasons for the not-indexed URLs. The data lags real time by a day or two, so a page you just fixed will not flip status instantly.

What do the indexed and not indexed counts mean?

The "Indexed" count is the number of your URLs Google has crawled and chosen to keep in its index, and the "Not indexed" count is everything Google knows about but is not currently indexing. A high not-indexed number is not automatically a problem. Plenty of URLs belong in that bucket on purpose: redirects, pages you set to noindex, alternate versions handled by canonical tags, and duplicates. The job is not to drive not-indexed to zero. It is to confirm that the important pages are indexed and that the not-indexed list contains only URLs you are happy to leave out.

What do the not indexed reason statuses mean?

Each not-indexed URL is grouped under a reason status that explains why Google left it out, and these are the lines you actually act on. Some are signals you set yourself, some are technical blocks, and a few are judgment calls Google made. Here are the ones you will see most.

• Discovered, currently not indexed: Google knows the URL exists but has not crawled it yet, often a sign of crawl-budget or quality hesitation. See discovered, currently not indexed.
• Crawled, currently not indexed: Google crawled the page and chose not to index it, usually a content-quality or duplication signal. See crawled, currently not indexed.
• Excluded by noindex tag: the page carries a meta noindex or X-Robots-Tag, so Google obeys it and keeps the page out. Working as intended only if you meant to add it.
• Blocked by robots.txt: your robots.txt stops Google from crawling the URL. Note that this blocks crawling, not indexing, so a blocked URL can still appear in search without a description.
• Page with redirect: the URL redirects elsewhere, so it is not indexed on its own. Normal for moved or consolidated pages.
• Alternate page with proper canonical tag: Google sees this as a duplicate and indexes the canonical instead. Usually fine.
• Duplicate without user-selected canonical and Duplicate, Google chose different canonical than user: Google picked its own canonical, which may not match yours. Worth a look if it picked wrong.
• Soft 404 and Not found (404): Google reached a page that looks empty or returns a not-found status. Fix or remove these.
• Server error (5xx): Google could not load the page because your server errored. Fix the hosting or app issue.

Which not indexed reasons should you fix first?

Fix the reasons that keep pages you want indexed out of the index, and ignore the ones that describe pages you never wanted indexed in the first place. Sorting the list this way turns an intimidating report into a short, ordered to-do list. The fastest way to triage is to put every reason status into one of three buckets.

1. 1Fix now: server error (5xx), soft 404, not found (404) on URLs that should exist, and noindex or robots.txt blocks you did not intend. These are clear technical mistakes that hide real pages.
2. 2Investigate: discovered or crawled currently not indexed, and duplicate-canonical issues where Google chose a URL you disagree with. These are quality and consolidation signals that need judgment, not a one-line fix.
3. 3Leave alone: redirects, intentional noindex pages, and alternate pages with a proper canonical. These belong in the not-indexed bucket and need no action.

How do you confirm a fix worked?

Confirm a fix by using the URL Inspection tool on a sample URL and by running Validate fix on the reason group, then waiting for Google to recrawl. Inspection gives you the live status of a single URL, including whether it is indexable right now, while Validate fix tells Google to re-evaluate the whole group and emails you when it finishes. Neither is instant. Recrawling and re-indexing can take days to a couple of weeks, and Google still makes the final call on whether a fixed page earns a place in the index.

What if a page is fixed but still not indexed?

If a page is technically clean but stays out of the index, the issue is usually discovery or perceived value rather than a blocking error. Make sure the URL is linked internally and sits in your sitemap so Google has a clear path to it, and check that the content is substantial and distinct. For a broader checklist of causes and remedies, read why your page is not indexed. You can also send a fresh indexing-request signal by submitting the URL through URL Indexer, which works even for pages and backlinks on sites you do not own, with no Search Console access required and up to 10 URLs per day free.