Every site owner meets the same moment: a page you published weeks ago is nowhere in Google, and Search Console shows a status you have never seen. The Page Indexing report is where the answer lives, but it only helps if you read it the way Google means it. This guide explains what the report actually tells you, what each important status means, how to check a single URL properly, and how to fix causes in the right order, including the two honest rules that save the most wasted effort: a page being in your sitemap does not mean it is indexed, and requesting indexing never guarantees indexing.
What the Page Indexing report actually tells you
The Page Indexing report, under Indexing in Google Search Console, lists every URL Google knows about on your site and sorts them into two broad groups: Indexed, and Not indexed, with a reason given for each group of unindexed URLs. Google samples and groups URLs by pattern, so you will often see a reason applied to a set of similar pages rather than a judgement on one page alone.
Read the report as a diagnosis tool, not a score. A healthy site always has some unindexed URLs: redirects, alternate versions, and deliberately excluded pages belong there. The question is never “why is this number not zero” but “are any pages I care about sitting in the wrong group, and does the stated reason point to a cause I control”.
Two distinctions from Google’s own documentation are worth memorising before you touch anything. Crawling, indexing, and ranking are three separate steps; a page can be crawled and still not indexed, and indexed without ranking well. And the report reflects Google’s decisions over time, so a fix you make today appears in the report when Google next processes those URLs, not instantly.
The statuses that matter and what each one means
Discovered, currently not indexed
Google knows the URL exists, usually from your sitemap or a link, but has not crawled it yet. For a new page on a small site this often resolves on its own. If it persists for important pages, the usual causes are crawl priorities: the site publishes faster than Google chooses to crawl it, internal links to the page are weak, or overall site quality signals make Google patient. The fix is importance, not pleading: link the page from relevant live content and make sure it belongs in the sitemap.
Crawled, currently not indexed
Google visited, read the page, and decided not to include it for now. This is a quality and distinctiveness judgement more than a technical error. Thin content, near-duplicate pages, and pages that add nothing beyond what is already indexed land here. Substantial improvement, merging duplicates into one stronger page, or accepting that the page does not merit indexing are the honest options. Resubmitting an unchanged page changes nothing.
Excluded by noindex tag
The page carries a noindex instruction. Sometimes that is exactly right: thank-you pages, account pages, and internal landing pages should be excluded. Sometimes it is a leftover from a staging setting or an SEO plugin default that survived a migration. Check whether the exclusion is deliberate before removing anything, and if you remove a noindex, confirm the change on the live page rather than trusting the settings screen.
Alternate page with proper canonical tag
Google found a duplicate and chose the canonical version you pointed to. This status is normally correct behaviour, not a problem. It becomes a problem only when the URL listed is the one you actually wanted indexed, which means your canonical signals disagree with your intentions: fix the canonical, the internal links, or the sitemap so they all name the same preferred URL.
Duplicate without user-selected canonical
Google found near-identical pages and picked a canonical for you. If its choice is your preferred version, leave it. If not, differentiate the pages properly or consolidate them, and signal your preference consistently. Canonical confusion often starts with mixed signals from crawlers and templates, the same territory covered in our report on websites blocking AI agents and the crawl rules sites now publish.
Not found (404), soft 404, and redirect errors
A 404 for a page that never should have existed is fine and needs no action. A 404 for a page that moved needs a redirect to its replacement. A soft 404 means the URL returns a success code but looks like an error page to Google, often an empty category, a search results page, or a thin placeholder; give it real content, redirect it, or let it return a true 404. Redirect errors, chains, and loops should be shortened to a single hop to the final URL.
Blocked by robots.txt and page blocked due to other 4xx or 5xx issues
Robots blocks are configuration, so verify they are intentional; our robots.txt and AI training opt-out guide walks through deliberate blocking done properly. Server errors in the report mean Google met a sick site at crawl time; if your host had an outage or an aggressive security layer, the errors may already be history, which the validation step below is designed to confirm.
Checking one URL properly with URL Inspection
For a single important page, use the URL Inspection tool. Paste the full URL and read three things. First, the verdict: whether the URL is on Google, and if not, the reason, which mirrors the report but for this exact page. Second, the crawl details: when Google last crawled it, whether robots allowed it, and what canonical Google selected versus the one you declared; a disagreement between those two canonicals is one of the most informative findings in all of Search Console. Third, use Test Live URL when you have just changed something: it fetches the page as Google sees it now, which separates “Google has old information” from “the page really is broken”.
If the live test succeeds and the indexed version is stale, a indexing request is reasonable. If the live test fails, fix the page first; requesting indexing for a page that still fails is wasted effort.
Fixes by cause: noindex, canonicals, redirects, thin pages, crawl waste
Noindex causes: remove the tag or the plugin setting, verify on the live page with URL Inspection’s live test, then request indexing once.
Canonical causes: make the declared canonical, your internal links, and your sitemap all name the same URL. Mixed signals are the cause; consistency is the fix.
Redirect causes: point every old URL directly at its final destination, remove chains, and never redirect everything to the homepage, which Google treats as a soft 404 pattern.
Thin page causes: merge, expand with genuinely useful material, or deliberately noindex utility pages. Time spent here beats any technical trick, because “crawled, currently not indexed” is usually a content verdict.
Crawl waste causes: faceted navigation, internal search URLs, and parameter duplicates can consume a small site’s crawl attention. Block or canonicalise the patterns, and keep the sitemap limited to pages you want indexed, which is exactly the curation discipline Search Console rewards. The wider context of how AI-driven search is changing what gets surfaced is covered in our analysis of AI search traffic trends, and our guide to Google AI Mode ads shows where indexed pages now compete for attention.
When to request indexing and when to leave it
Request indexing when a page is new and important, when you have fixed the specific cause that kept it out, or when you have substantially improved it. The request is a crawl priority hint. It does not guarantee indexing, it does not speed up a quality decision, and repeating it daily does not stack the effect; Google’s documentation is clear that the tool does not change whether a page qualifies.
Leave it alone when the status is correct behaviour, such as alternate pages with proper canonicals, when you have not changed anything since the last crawl, and when the page is low value. Patience is a legitimate fix for discovered pages on growing sites, provided the internal links are in place.
After fixing a whole class of URLs, use the Validate Fix button on that issue in the report. Validation tells Google to recheck the group, and Search Console reports back how many now pass. That, not the request button, is the proper tool for site-wide problems.
A monthly indexing review routine
- Open the Page Indexing report and compare the indexed count with last month. Investigate drops, celebrate nothing yet.
- Scan the Not indexed reasons by volume. Open any reason that grew sharply and sample its URLs.
- Pick your ten most important pages and confirm each one is indexed through URL Inspection.
- Check the sitemap status for errors or a stale discovered count.
- Review any manual actions or security issues notices, which live in their own Search Console sections, the same day you see them.
- Log what you fixed and what you deliberately left alone, so next month’s review starts from knowledge rather than archaeology.
Indexing problems feel mysterious mainly because the feedback is slow. The report, read monthly and acted on by cause, turns that mystery into a short list of ordinary maintenance, which is all it ever was.
Sources and Further Reading
- Google Search Central, Page Indexing report documentation: support.google.com
- Google Search Central, URL Inspection tool documentation: support.google.com
- Google Search Central, Ask Google to recrawl your URLs: developers.google.com
