Key takeaways
- Discovered – currently not indexed means Google knows the URL but has not crawled it yet; Crawled – currently not indexed means it was crawled but is not in the index.
- Inspect a representative URL's live response, canonical, indexability and main content before changing the site.
- A sitemap or indexing request helps discovery and review; neither guarantees indexing.
Two Search Console status labels can look similar while pointing to different next checks. For “Discovered – currently not indexed,” start by asking why the URL has not been fetched. For “Crawled – currently not indexed,” focus on what Google received and whether the page is worth indexing.
The Page indexing report is a diagnostic view, not a target where every submitted URL should be green. Faceted filters, duplicate variants and retired pages may correctly remain out. Use this decision tree on pages you genuinely want found in search.
Table of contents
Start with one representative URL
Open Search Console → Indexing → Pages, select the relevant reason and inspect examples. The report groups URLs by the reason Google currently shows; counts and example lists can change as Google recrawls. Pick a valuable page, copy its exact URL and use URL Inspection to see the last crawl, selected canonical and indexing details. Then run a live test to see what Google can fetch now.
Record both the report status and the live result. A live test reflects today's accessibility; it does not by itself prove that the URL is indexed. Google's Page indexing and URL Inspection documentation describe these different views.
If the URL is discovered but not crawled
Check that the page actually exists at a stable URL, returns a working response, is linked from an appropriate page and appears in a clean XML sitemap if it is a canonical page you want indexed. Review server logs or monitoring for Googlebot fetch attempts and server errors. On a large site, avoid generating thousands of low-value parameter or filter URLs that compete for crawl attention.
Do not repeatedly submit the same page and expect a fixed deadline. Google may defer crawling for many reasons, including site load and perceived URL value. Prioritize a small set of important, linked pages, then wait for the report and inspection data to update. If a URL is intentionally not public, remove it from the sitemap instead of trying to force it into the index.
If the URL was crawled but not indexed
Open the page as a visitor and inspect the rendered content. Does it contain the promised answer, product or service, or is it mostly a template with a swapped city name? Check for an accidental noindex, a canonical that points elsewhere, a redirect, thin or duplicate content, and essential content loaded only after client-side scripts run. Compare the page with the URL Google selected as canonical.
Ask whether this URL truly deserves a separate result. Two nearly identical pages for one task may be better combined; a useful page with missing main content needs a rendering or content fix. A query-to-page analysis can show which existing URL already serves the search intent. Do not change all excluded URLs at once: fix one representative pattern and verify its live output.
Use the decision table and verify later
| Observation | Action | Verification |
|---|---|---|
| Important URL not fetched | Repair links, sitemap and server access | Live test, server logs, later crawl date |
| Fetched page is blank or broken | Fix rendering or response | Rendered inspection shows main content |
| Fetched page duplicates another | Clarify purpose, consolidate or canonicalize | Google-selected canonical after recrawl |
| URL should not be indexed | Keep it out of the sitemap and use the appropriate status/directive | Report reflects intended state |
After a meaningful fix, use URL Inspection to request indexing when appropriate, and monitor later. Google explicitly does not promise that a requested URL will be indexed. Keep the change date in your log so you can tell whether Google has recrawled the updated version.
Work through a batch without chasing every URL
If a report contains hundreds of excluded URLs, group them by template and URL pattern before investigating. A thousand filter combinations may have one cause; ten unique service pages may each need attention. Sample a few URLs from each group and record their status, canonical, HTTP response, last crawl and rendered main content. This turns a long list into a manageable set of decisions.
Prioritize pages that customers need and that have distinct content. Fix a shared template issue once, then inspect another sample after release. If a page is intentionally excluded, document why so someone does not “repair” it later. Compare the same group after Google recrawls; Search Console reporting may lag the live test. A falling excluded count alone is not a success measure if the site has removed useful pages.
Sources and further reading
Need help identifying why an important page stays out of search?
Get in touch