Google Search Console Indexing Issues: A Guide to the Page Indexing Report
- Filed November 10, 2026
- Crawling and indexing, guide 5 of 16
The Page indexing report shows how many of a site’s known URLs Google has indexed and groups the rest by the reason they are not indexed. The most important thing to know before reading it: a “not indexed” status is not automatically an error. Google’s help page says that some reasons, such as URLs blocked by robots.txt, are “probably intentionally blocked”, and that “It might not always make sense to fix and validate a specific issue on your website” (Page indexing report help). The report’s value lies in spotting patterns that do not match your intent: important pages in the wrong bucket, or sudden jumps in a reason that used to be small.
What the report shows
- The chart: indexed and not-indexed URL counts over time.
- Why pages aren’t indexed: a table of reasons, each with a count of affected URLs and examples.
- Improve page appearance: for indexed pages, issues that may affect how they appear.
The report covers URLs Google knows about, whether discovered through links, sitemaps or other means. It is a site-level view. Investigating a single URL is the job of the URL Inspection tool.
You can filter the report to URLs submitted in a specific sitemap, which is the fastest way to see whether pages you asked Google to consider are being indexed.
Reading the reasons: a diagnostic matrix
The table below lists reasons with Google’s meaning, whether they call for action, and the next investigation step. Quoted definitions come from Google’s help page.
| Reason | What Google says it means | Action needed? | Next step |
|---|---|---|---|
| URL marked 'noindex' | Google found a <!–INLINECODE0–> rule and did not index the page | Only if the page should be indexed | Check where the <!–INLINECODE1–> comes from (template, plugin, header) |
| Blocked by robots.txt | Google could not crawl the URL | Only if the page should be indexed | Remember a blocked URL can still be indexed without content if linked; if it should be removed, unblock and use <!–INLINECODE2–> |
| Not found (404) | The URL returned 404 | Only if the URL should exist | Restore, redirect to a relevant replacement, or leave as 404 |
| Soft 404 | The page looks like an error page but returns 200 | Yes, either fix the content or return a real 404 | Inspect the URL and view the rendered page |
| Page with redirect | A non-canonical URL that redirects; it "will not be indexed" | No, if the redirect is intended | Make sure internal links and sitemaps point to the destination |
| Alternate page with proper canonical tag | An alternate that correctly points to its canonical (Google's definition covers AMP, mobile and desktop alternates) | No | None, if the canonical target is indexed |
| Duplicate without user-selected canonical | A duplicate with no declared canonical; Google chose another page as canonical | Sometimes | Declare a canonical if Google's choice is wrong |
| Duplicate, Google chose different canonical than user | You declared one canonical; Google chose another | Yes, if Google's choice is wrong | Compare the two pages; align signals (links, redirects, sitemaps) |
| Crawled, currently not indexed | Crawled but not indexed; Google says this "doesn't necessarily indicate an issue that needs attention" | Only for important pages | Inspect the URL; assess whether the page adds unique value |
| Discovered, currently not indexed | Found but not crawled yet; "typically" rescheduled because crawling "was expected to overload the site" | Only if persistent for important pages | Check server capacity, crawl stats and internal linking |
| Server error (5xx) | Google received a server error | Yes | Check server logs at the reported times |
| Redirect error | A chain that was too long, a loop, a redirect URL that exceeded the maximum URL length, or a bad or empty URL in the chain | Yes | Trace the redirect chain |
| Blocked due to unauthorized request (401) | The page asked Googlebot for authorization | Only if the page should be public | Remove the authorization requirement for public pages |
| Blocked due to access forbidden (403) | Google notes Googlebot never provides credentials, so a 403 here is returned incorrectly | Only if the page should be public | Check firewall and bot-blocking rules |
Two statuses that are easy to misread
Crawled, currently not indexed. Google’s help page says the page “was crawled by Google but not indexed”, that Google “doesn’t index all pages across the web, so this is a common message for many sites”, and that for important pages you should use URL Inspection and other tools to diagnose problems. The status tells you what happened, not why. Possible reasons range from duplication and thin content to rendering problems; the report does not say which.
Discovered, currently not indexed. Google found the URL but has not crawled it. Its help page says that typically Google wanted to crawl the URL “but this was expected to overload the site; therefore Google rescheduled the crawl”, which is why the last crawl date is empty. Some URLs in this state do not by themselves indicate a problem. A large and growing number on a site with fast servers points to crawl demand, internal linking or URL proliferation questions.
Prioritizing what to fix
- Start with the indexed count trend. A sudden drop in indexed pages, or a sudden rise in a not-indexed reason, is more important than a stable backlog.
- Filter to your sitemap. Pages you submitted are pages you want indexed; reasons affecting them matter more than reasons affecting parameter URLs nobody intended to index.
- Separate intended from unintended. For each reason, sample the example URLs and ask whether that outcome was the plan.
- Group by template. If 4,000 product pages share one reason, look first at the template or a site-wide setting, not at 4,000 separate pages.
- Fix, then validate. After fixing a real issue, use the report’s Validate fix button to ask Google to recheck the affected URLs. Google’s help page says validation “typically takes up to about two weeks, but in some cases can take much longer”, and asks site owners not to click Validate fix again until validation has succeeded or failed.
Changes over time
The chart is where problems appear first. Things to look for:
- A step change in “URL marked ‘noindex'” right after a deployment: a template or plugin added
noindex. - A rise in “Server error (5xx)” alongside crawl stats spikes in failed requests: hosting capacity or firewall problems.
- A rise in “Page with redirect” after a migration: expected, as old URLs redirect; confirm the destinations are indexed.
- A slow rise in “Crawled, currently not indexed” after a large content expansion: Google may be judging the new pages less useful than expected.
What the report does not tell you
- It is not a complete URL list. Example URLs are samples.
- It does not explain quality judgments. “Crawled, currently not indexed” is a state, not a reason.
- It is not a ranking report. An indexed page can still get no impressions.
- It reports Google’s view at the time of the last crawl. A fix shows up only after recrawling.
2,000 city pages and what the report showed
Suppose a publisher adds 2,000 city-specific pages generated from one template. Six weeks later the report shows:
- indexed pages up by 300;
- “Crawled, currently not indexed” up by 1,400;
- “Discovered, currently not indexed” up by 300.
Inspection of sample URLs shows the pages differ only by city name and a few local figures. The report did not say the pages were low value; the pattern, combined with reading the pages, suggests it. The decision is to merge the city pages into regional guides with substantive local information and remove or noindex the rest, rather than to resubmit them: resubmitting the same pages does not change what makes them less useful.
Using the report with URL Inspection
The Page indexing report shows the pattern; URL Inspection explains one URL. A typical workflow: find a reason affecting important pages in the report, open an example URL, inspect it, and read the indexed status, the Google-selected canonical and the crawl details. If a fix applies to the template, fix once, then validate in the report.
Read the report as a description of Google’s decisions about your URLs. Where those decisions match your intent, there is nothing to fix. Where they do not, the reason and the example URLs tell you where to start looking.