The Page Indexing report groups URLs Google knows about into indexed and non-indexed states. Its purpose is not to drive every non-indexed count to zero. The objective is to confirm that important canonical pages are indexable and that excluded URLs are excluded for the intended reason.
What to review first
Look for sharp changes rather than the absolute excluded count. A decline in indexed pages becomes concerning when it affects valuable canonical URLs or coincides with a rise in server, redirect, robots, noindex, or access errors.
Large groups of alternate, duplicate, redirected, and intentionally noindex URLs can be healthy. Filter by a submitted sitemap to focus on URLs that are supposed to be canonical and indexable.
How to investigate an issue
- Open the affected status and inspect its trend and example URLs.
- Decide whether those URLs are expected to be indexed.
- Inspect representative URLs to compare indexed evidence with the current live page.
- Check the response, robots rules, indexing directives, declared canonical, and Google-selected canonical.
- Fix the underlying template or platform rule rather than individual examples when the issue is systematic.
- Start fix validation only after representative live tests show the intended result.
Why reports can disagree
The Page Indexing report reflects Google's last processed state and can lag behind a recent fix. A live URL Inspection checks the current fetchable page, but it does not reproduce every indexing decision. In particular, the live test does not determine duplicate or canonical selection in the same way as Google's indexing systems.
Official source
See Google's Page Indexing report documentation.