What does "Excluded" mean in Google Search Console Pages report?
Indexing Issues
"Excluded" was the name the old Coverage report gave to URLs that Google knew about but did not index, usually on purpose. The current Page indexing report folds them into a single Not indexed group, each with a reason. Most of those reasons are normal on a healthy site: redirects, duplicates pointing to a canonical, pages you marked noindex. The job is to confirm that every URL there is one you expect.
Expected, or a problem?
| Reason | Usually | Check that |
|---|---|---|
| Page with redirect | Expected | The redirect is intended, and you link to the target rather than the old URL |
| Alternate page with proper canonical tag | Expected | The canonical it points to is indexed |
| Duplicate without user-selected canonical | Expected, but worth a look | Google picked the URL you would have picked; add a canonical tag if not |
| Duplicate, Google chose different canonical than user | Worth a look | Your signals agree: links, sitemap, redirects. See canonical URLs |
| URL marked 'noindex' | Expected if you added it | No important page carries the tag by mistake, often after a launch from staging |
| URL blocked by robots.txt | Expected if intended | The rule does not block pages or resources you need |
| Not found (404) | Expected after removals | Nothing important links to it; redirect moved content |
| Soft 404 | A problem | The page has real content, or returns a real 404 |
| Crawled – currently not indexed | Worth a look | The pages are worth indexing. See this reason |
| Discovered – currently not indexed | Worth a look in volume | Your server and URL inventory are healthy. See this reason |
Two subtleties catch people out. A page blocked by robots.txt can still be indexed if other sites link to it, because Google never sees a noindex it is not allowed to fetch: to keep a page out of results reliably, allow crawling and use noindex. And a noindex page that is also blocked in robots.txt keeps the tag invisible, so the block defeats the tag.
How to review the list quickly
- In Indexing > Pages, filter by your sitemap. A sitemap should list only pages you want indexed, so any of its URLs under Not indexed deserves a reason.
- Open each reason and scan the examples for patterns: a folder, a parameter, a template.
- Inspect one example per pattern in URL Inspection to see the canonical Google chose and whether indexing is allowed.
- Fix the pattern once, at the source, and use Validate fix where the report offers it.
An unexpected jump in one reason is the clearest warning sign. A release that adds noindex to a template, or a redirect rule that swallows a section, appears here as a step change days before traffic data shows it. See Coverage / Pages errors for the reasons that are outright errors.
How AutoPSEO helps
Search Console shows today's counts, not which of your important pages just left the index. AutoPSEO's Index Tracker inspects the URLs you choose every day, imported from your sitemaps or your top pages by clicks, and an index-flip alert posts to Slack, Teams or a webhook when a tracked page moves between indexed and not indexed. For one-off audits, bulk URL Inspection shows the coverage state and canonical of a whole list at once.
Sources: Google's Page indexing report help and URL Inspection tool help.
More in Indexing Issues
Put your SEO content on autopilot
Connect Search Console and your site. AutoPSEO scans it and plans the first topics right away. No credit card needed.