The Google Search Console Page Indexing Report Explained (2026)

The Page Indexing report in Google Search Console, formerly called the Index Coverage report, shows which pages Google has indexed and why the rest are not. You find it under Indexing then Pages in the left menu. It splits your URLs into two groups, indexed and not indexed, charts them over time, and lists the specific reason behind every excluded page. Read correctly, it is the single most useful diagnostic Google gives you, because it turns a vague worry that pages are missing into a named, fixable cause for each one.

Google renamed the old Index Coverage report to Page Indexing a while back, and plenty of people still search for the old name or for alternatives to it. It is the same report with clearer labels. If you have ever stared at a green-and-gray chart wondering what discovered, currently not indexed actually means for your money pages, this walkthrough is for you.

Where is the Page Indexing report in Search Console?

Open Search Console, select your property, and in the left navigation click Indexing, then Pages. The top of the report is a chart with indexed pages in green and not-indexed pages in gray, and you can overlay impressions to see whether the pages Google skipped were ones that would have earned traffic. Below the chart sits the part that matters: a list of reasons, each with a count and a set of example URLs.

The report is not real time. Google refreshes it on its own cadence, and during 2026 the data lagged by a couple of weeks at one point before Google fixed it, so do not panic if a change you made yesterday has not moved the numbers yet. Treat the report as a trend and a diagnosis tool, not a live dashboard.

What does indexed versus not indexed mean?

Indexed means Google crawled the page, rendered it, and added it to the index, so it is eligible to appear in search results. Not indexed means Google knows the URL exists but has chosen not to store it, for one of many reasons the report names. Neither number is a target on its own. A healthy site has plenty of not-indexed URLs on purpose, because tag pages, filtered URLs and old redirects should not be in the index.

The question is never how do I get to zero not-indexed pages. It is which of my important pages are not indexed, and why. A single money page stuck in the not-indexed bucket matters far more than a thousand paginated URLs Google correctly ignored. Filter your attention to the URLs that should rank and were excluded anyway.

What do the not indexed reasons mean, and how do I fix each one?

This is the heart of the report. Each reason points to a different problem with a different fix, and the most common ones behave very predictably once you know what they signal.

Two of these deserve extra attention because people constantly confuse them. Discovered, currently not indexed is a crawling problem: Google has not looked yet, so the answer is to make the page easier to reach and more clearly worth crawling. Crawled, currently not indexed is a content problem: Google looked and passed, so no amount of resubmitting will help until the page itself gets better.

Why is crawled, currently not indexed so common?

Because it is Google's polite way of saying the page did not earn a spot. On content sites it usually traces back to thin or near-duplicate posts, pages that restate what stronger pages already cover, or programmatically generated URLs with almost identical bodies. The fix is editorial rather than technical. Merge overlapping pages, add first-hand detail a template cannot produce, and give each page a clear reason to exist that its neighbors do not.

When a large share of your not-indexed pages are stuck on quality, the real lever is producing content genuinely worth indexing rather than more of it. Teams that scale their publishing with an AI tool that researches and drafts SEO articles still have to hold the quality bar, because Google's crawled-not-indexed judgment is exactly the filter that catches thin output. Volume without depth just fills this bucket faster.

How do I use the URL Inspection tool with this report?

The Page Indexing report tells you what is happening across the whole site; the URL Inspection tool tells you what is happening on one specific page. Use them together. When a reason in the report surprises you, click into an example URL and inspect it to see Google's exact verdict, the canonical it selected, when it last crawled the page, and whether it can fetch the current version. That per-URL detail is what confirms your diagnosis before you spend time on a fix.

Once you have fixed the underlying cause, use the same tool to request indexing on the corrected page, and validate the fix in the report so Google recrawls the whole affected group. If you need to confirm status across hundreds of pages rather than one at a time, the URL Inspection API returns the same verdict at up to 2,000 queries per day per property. For the practical side of confirming coverage, see our guide on how to check if a page is indexed.

How often should I check the Page Indexing report?

For most sites, a weekly look is enough to catch problems while they are small, with a closer check after any big change such as a migration, a template update or a bulk publish. Watch the trend of the not-indexed line rather than the absolute number. A slow, steady climb in crawled, currently not indexed usually means content quality is slipping, while a sudden spike in blocked by robots.txt or excluded by noindex almost always means a deploy shipped the wrong configuration to production.

The report rewards regular attention because indexing problems compound quietly. Pages do not announce that they fell out of the index; they simply stop earning impressions, and the Page Indexing report is where that shows up first. Make reading it a habit, fix the causes rather than the symptoms, and keep your most important pages on the indexed side of the chart. For a focused view of getting individual pages in, our page indexing resource covers the submission side in depth.