Every URL Google knows about on your site lands in one bucket of the Page indexing report — indexed, or not indexed with a named reason. It is the closest thing SEO has to an X-ray, and the most misread screen in Search Console: most “errors” it shows are routine, and some of its calmest-looking rows hide real problems. This guide decodes every status group, tells you which ones deserve action, and gives you the monthly workflow that catches regressions early.
How the Report Is Organized
The report splits all known URLs into two groups — Indexed and Not indexed — with the not-indexed group broken down by reason. Each reason row expands into a URL list (capped at 1,000 per view) with a chart of the trend over time. The trend line matters more than the absolute count.
Two framing facts keep the report sane. First, “not indexed” is not an error category: redirects, deliberate noindex, and canonicalized duplicates are all healthy exclusions. Second, the report only covers URLs Google discovered — pages nobody links to and no sitemap lists simply do not appear, which is why pairing it with your XML sitemap (and the report’s sitemap filter) is the only way to audit coverage of the pages you actually care about.
Every Status, Decoded
The statuses sort into four families: deliberate exclusions (you asked for this), canonicalization (Google merged duplicates), crawl-side decisions (not fetched or not kept), and hard errors (something is broken). The family determines the response.
| Status | What it means | Typical action |
|---|---|---|
| Excluded by ‘noindex’ tag | You told Google not to index it | Verify it is intentional; otherwise remove the tag |
| Page with redirect | URL forwards elsewhere; target gets indexed | None — healthy bookkeeping |
| Alternate page with proper canonical tag | Duplicate correctly pointing at its canonical | None — working as designed |
| Duplicate without user-selected canonical | Google picked a canonical for you | Declare the winner yourself |
| Crawled — currently not indexed | Fetched and declined — a quality/selection verdict | Improve or consolidate |
| Discovered — currently not indexed | Known but not yet fetched — a priority verdict | Strengthen links, sitemap, server |
| Blocked by robots.txt | Crawl forbidden by your rules | Check the rule is intentional |
| Soft 404 | Page returns 200 but looks like “not found” | Return a real 404, or add real content |
| Not found (404) / Server error (5xx) | Hard failures at fetch time | Fix or redirect; investigate 5xx clusters |
Note the robots.txt subtlety: blocking crawling does not block indexing — a blocked URL with external links can still be indexed without content. Actual de-indexing requires noindex or removal, as our robots.txt guide explains.
Which Statuses Deserve Action
Prioritize by one question: are pages that should earn traffic sitting in an exclusion bucket? A thousand redirected URLs matter zero. Five money pages in “Crawled — currently not indexed” matter enormously. Volume is not severity.
The practical triage: cross-reference each non-indexed bucket against your list of pages that exist to rank. Anything from that list in a crawl-side or duplicate bucket goes on the fix queue — the linked guides above cover each fix. Anything in deliberate-exclusion buckets gets a spot-check with the URL Inspection tool to confirm the exclusion is actually deliberate; accidental noindex tags from staging pushes and plugin settings are a classic silent killer, and general reachability issues trace back to the paths in the crawlability guide.
The Monthly Indexing Workflow
Fifteen minutes, monthly: (1) scan the trend charts for any bucket that changed slope, (2) diff the “Why pages aren’t indexed” table against last month’s, (3) inspect two or three URLs from any grown bucket, (4) log the counts. A spike after a deploy, migration, or template change is your early-warning system.
Slope beats snapshot. Every site carries a steady-state population in most buckets; what signals trouble is acceleration — a redirect bucket that doubles after a URL change (check your redirect strategy), a noindex bucket that jumps after a plugin update, a crawled-not-indexed line that climbs while you publish. Pair the check with your Performance report review — indexing regressions show up here weeks before they show up as traffic loss — as part of the routine in the Search Console pillar.
Fix Validation, Honestly
The “Validate fix” button asks Google to recrawl a sample of affected URLs and track their status over roughly two weeks. It is a monitoring convenience, not a lever — validation succeeds when the underlying fix was real, and fails (or stalls) when it was not.
Use it after pattern-level fixes — a template correction, a canonical alignment, a robots rule change — so you get a tracked before/after instead of manually rechecking. Do not use it as a retry button on unchanged pages; that is the same ritual as re-requesting indexing and produces the same nothing. If validations keep failing across buckets and you cannot see why, the report is telling you the problem is structural — the point where an expert audit saves you a quarter of guessing.
- “Not indexed” is not an error list — redirects, proper canonicals, and deliberate noindex are healthy exclusions.
- Judge buckets by slope, not size: a stable 1,000-URL bucket is bookkeeping; a doubling one is a signal.
- Severity = should-rank pages in exclusion buckets. Cross-reference against your money-page list monthly.
- robots.txt blocks crawling, not indexing — de-indexing requires noindex or removal.
- Validate fix is a monitor, not a retry button: it confirms real fixes and stalls on wishful ones.
Frequently Asked Questions
What percentage of my pages should be indexed?
There is no universal healthy ratio — a lean site might index 95% of known URLs while a large commerce site healthily indexes 30%. The meaningful metric is coverage of pages you want ranking: that list should be at or near 100%, and everything else is housekeeping.
Why did my indexed count suddenly drop?
Check what grew in the not-indexed table at the same date — the drop always has a matching rise somewhere. Common culprits: a deploy that shipped noindex tags, a canonical change consolidating variants (often fine), a robots.txt edit, or a migration whose redirects moved indexing to new URLs.
Are “Page with redirect” entries a problem?
Almost never — they are how consolidation is supposed to look, and the count naturally grows over a site’s life. Investigate only if URLs that should serve content appear there (an accidental redirect) or the bucket spikes without any URL change on your side.
How do I get a full list when the report caps at 1,000 rows?
The UI export carries the same cap per view. For bigger sites, filter by sitemap to segment the data, or use the URL Inspection API and the bulk data export to BigQuery for complete coverage — the scaled setup we cover in the Search Console cluster.
Does fixing indexing statuses improve rankings?
Indexing is binary admission, not a ranking factor: fixing exclusions gets pages into the game but does not move them up. The ranking benefit is indirect — consolidating duplicates concentrates signals, and pruning junk improves sitewide quality perception.
The Bottom Line
The Page indexing report rewards a calm read: most of it is Google’s bookkeeping, a little of it is your early-warning system, and the skill is knowing which is which. Keep the monthly slope check, chase only the buckets holding pages that deserve traffic, and let the linked status guides in this cluster handle the deep fixes. Indexing is admission to the game — the Performance report tells you how you are playing it.
Further reading & sources
- Page Indexing report — Google Search Console Help
- Block Search indexing with noindex — Google Search Central
See how your site actually shows up in AI search. An AI visibility audit maps where you’re cited, where you’re invisible, and what to fix first — in plain English.
Get your AI visibility auditTry the free SEO tools →
Prefer self-serve? The interactive checklists turn guides like this one into a working to-do list.
Keep reading in Google Search Console
Get one email when something genuinely changes
AI search moves fast and most of it is noise. We send one short email when a real shift is worth your time. Unsubscribe anytime.
Published by Plain Intelligence — practical AI SEO, GEO, and technical SEO, documented in plain English. About Plain Intelligence →
↑ Back to Google Search Console · Explore all articles · Free tools & resources · Glossary