Start with the question the report can answer
The Pages report in Google Search Console shows how Google has handled URLs it knows about on your site. Its main distinction is between indexed pages, which may be eligible to appear in Google Search, and pages that are not indexed. It is a diagnostic report, not a list of every URL on your server or a measure of how much search traffic a page receives.
Open the report for the property you intend to review, then check its overall trend and the reasons listed under indexed and not indexed. Before treating a change as a problem, consider whether the site recently added pages, removed old URLs, changed its navigation, or updated its sitemap. Report labels and layouts can change, but the underlying questions remain useful: Which important pages are indexed, and do the explanations for other URLs make sense?
Decide which exclusions are expected
A URL does not need to be indexed simply because Google found it. Login screens, duplicate filter combinations, retired pages, and URLs that redirect visitors elsewhere may be better left out of search results. A page marked as a redirect, for example, may be behaving exactly as intended. Likewise, a deliberate noindex directive is not a technical fault if the page was never meant to appear in search.
Canonicalization also affects what you see. If several URLs contain substantially similar content, Google may index one preferred version and exclude the others. Check whether the selected version is the one you want people to find. An exclusion becomes more urgent when it affects a useful, unique page that you expect search users to reach, such as a main service page, a product category, or a substantial guide.
Do not judge the site by the percentage of known URLs that are indexed. A site with many intentional redirects or duplicate URL variations can have a large not-indexed count without losing useful search pages. Evaluate the affected URLs by their purpose instead.
Investigate the reason, then inspect a URL
Select a reason in the report and look at example URLs. The reason gives you a starting point, not necessarily a complete diagnosis. Use URL Inspection for an important example to review what Google reports about that specific address, including its indexing status, crawl information when available, and canonical details. Compare those findings with the page you can actually access in a browser.
For a page blocked by robots.txt or marked noindex, ask whether that instruction is intentional. For a missing page, check whether it should return a not-found response, redirect to a genuinely relevant replacement, or exist again. For a soft 404, examine whether the page offers substantial content or merely presents an empty or unhelpful result. If a URL is listed as discovered or crawled but not currently indexed, check its internal links, content usefulness, duplication, and technical accessibility before assuming that submitting it again will solve the issue.
Some details can lag behind changes to your site, and a successful live test does not guarantee indexing. Inspect a small sample of URLs with the same reported reason rather than assuming they all share one cause. If the examples differ, separate them into groups before choosing a fix.
Prioritize fixes by page value and pattern
Start with important pages that should be indexed but are not. A single excluded cornerstone page may matter more than hundreds of intentionally excluded parameter URLs. Look for patterns across affected pages: Are they all in one directory, linked only from a sitemap, using the same template, or pointing to another canonical URL? A shared pattern can suggest a sitewide cause that is more efficient to address than individual URLs.
Make the change that fits the cause. That might mean removing an accidental noindex directive, repairing internal links, updating an incorrect canonical, restoring a page that should exist, or improving a thin page so it serves a clear purpose. Keep your XML sitemap focused on canonical URLs you want indexed; a sitemap helps Google discover URLs but does not require Google to index them. Avoid requesting indexing repeatedly without changing the underlying issue.
Use the report as an ongoing check
After a fix, record what you changed and which URL group it affected. Where the report offers a validation option, you can use it to ask Google to check a resolved issue. Continue watching the relevant reason and inspect representative URLs later; crawling, processing, and report updates may take time. A changing count alone does not prove that your fix worked, especially if the site is also adding or removing URLs.
For a useful summary, report on important page groups rather than presenting the indexed total without context. Note which exclusions are intentional, which issues need action, what was changed, and what remains uncertain. Pair indexing checks with separate performance data when you want to discuss clicks or visibility. The goal is not to make every discovered URL appear in search; it is to make valuable pages accessible, understandable, and eligible for indexing.
