Discovered - currently not indexed

What’s actually happening

In Search Console's Page indexing report, the URL is known to Google — it's in your sitemap or linked somewhere — but Google hasn't fetched it. No crawl, no index, no rankings. It usually means Google chose to hold off, often because it's wary of overloading your server or doesn't think the page is worth the crawl right now. On big sites it piles up into thousands of URLs stuck in limbo.

Common causes

• Crawl-budget limits — the site has more URLs than Google wants to crawl, so low-priority pages wait
• Google throttling the crawl because the server was slow or returned 5xx/timeouts before
• Thin or low-value pages Google deprioritizes (faceted/filter URLs, near-empty tag pages)
• Weak internal linking — the page is buried deep with few or no links pointing to it
• A brand-new or low-authority site that Google crawls conservatively

How to fix it

1. Make the server fast and stableCheck the Crawl Stats report (Settings → Crawl stats) for slow responses or host errors. If average response time is high or there were 5xx spikes, Google backs off. Fix TTFB and eliminate timeouts so it crawls more aggressively.
2. Strengthen internal links to the pageLink to it from pages that already get crawled often — your homepage, hub/category pages, related posts. A URL that's only in the sitemap with no internal links is easy for Google to defer.
3. Prune or consolidate low-value URLsIf the report is flooded with filter params, thin tags, or duplicates, noindex or canonicalize them and tighten the sitemap to your real pages. A leaner URL set lets crawl budget reach the pages that matter.
4. Request indexing for priority URLsUse URL Inspection → Request Indexing for the important pages to nudge a crawl. It doesn't scale to thousands, but it works for the handful you care about most.