How to Read the Search Console Pages Report Without Panicking About Not Indexed

Open Search Console, click Indexing, click Pages, and you will probably see a number that looks like a disaster. Forty-three pages indexed, ninety-two not indexed. Almost every business owner who sees this for the first time concludes the site is broken. Usually it is not.

The Pages report is the single most useful screen in Search Console and the most commonly misread. Here is how to read it in the order that matters.

Not indexed is not an error category

The first thing to understand is that Not indexed is a bucket, not a verdict. It contains pages Google deliberately chose not to index, pages it has not got to yet, pages you told it to skip, and pages that genuinely failed. Those four groups need completely different responses, and the report tells you which is which if you scroll down to the reasons table.

The reasons that are fine and need no action

Page with redirect. This is a URL that 301s somewhere else. It is working exactly as intended. On a site that has ever changed its URL structure, this is often the largest single bucket and it is entirely healthy.

Alternate page with proper canonical tag. Google found a duplicate and correctly followed your canonical to the version you wanted. This is the system working.

Excluded by noindex tag. Fine if you meant it: thank-you pages, internal search results, filtered views. Worth one check that nothing important is in this list, and then ignore.

Blocked by robots.txt. Same logic. Check the list for anything that should be public, then move on.

On most sites, these four account for the large majority of the Not indexed total. Which means the scary ratio is usually mostly redirects and canonicals.

The reasons that actually matter

Discovered - currently not indexed. Google knows the URL exists and has chosen not to crawl it yet. This is the most important line in the report. It usually means one of three things: the page has no internal links pointing at it, the site has a crawl budget constraint, or Google has judged the page unlikely to be worth the fetch. The fix is almost always internal linking plus making the page substantially better, not resubmitting it.

Crawled - currently not indexed. Google fetched the page, read it, and decided not to index it. This is a quality judgment. Thin pages, near-duplicate location pages, auto-generated tag archives and product variants all end up here. Resubmitting does nothing. Merging, expanding or removing the pages does.

Duplicate without user-selected canonical and Duplicate, Google chose different canonical than user. These say your canonical strategy is not being believed. Worth investigating properly, because it often means two pages are competing for the same term.

Soft 404. The page returns 200 but looks empty or like an error to Google. Common on out-of-stock product pages and on search-results templates with no matches.

Server error (5xx) and Not found (404). These are real. A 404 in this list that used to rank is a lost page that needs a redirect.

The number to actually watch

Not the ratio. The trend line on the indexed count.

A site whose indexed pages are climbing steadily is a site where new content is being found and trusted. A site where the indexed count is flat while you publish weekly has a discovery or quality problem. A site where the indexed count is falling has something to investigate urgently.

The ratio between indexed and not indexed tells you very little on its own, because it depends almost entirely on how many redirects and canonicals your site generates.

A practical thirty-minute pass

Sort the reasons table by page count. Ignore everything in the first group above. Open Crawled - currently not indexed and Discovered - currently not indexed and export both. Look at what they have in common, which is usually one template, one section, or one batch of thin pages. Fix the pattern, not the individual URLs.

Then check whether any page you care about commercially is in the Not indexed bucket at all. If your main service pages are indexed and ranking, a large not-indexed count made up of redirects and tag archives is cosmetic.

What moves the number

Three things, in order of effect: internal links from pages that already have authority, genuinely distinct content on each page, and a clean sitemap that lists only canonical, indexable URLs. Everything else accelerates discovery slightly but does not change whether Google wants the page.

If your indexed count has been flat for months and you want to know which of the three is the bottleneck on your own site, you can see the full service breakdown here.

Related: why so many Indian websites stall at position 15, which is usually the same quality signal showing up in rankings instead of indexing.