Discovered: Currently Not Indexed: Causes and Fixes

What the "Discovered - currently not indexed" status means

This status appears in the Page Indexing report when Google has found a URL (typically through your sitemap or a link) but has not crawled it. Because Google never fetched the page, it has no content to index. The page sits in a queue, waiting for Google to decide it is worth the request.

That decision is the key point. Google does not crawl every URL the moment it discovers one. It estimates how valuable a page is likely to be and how much load crawling it will put on your server. When a site shows signals of thin content, heavy duplication, or slow responses, Google often defers crawling lower-priority URLs. So this status is rarely a single technical error. It is a judgment that the page has not yet earned a crawl.

Common causes

• Thin or low-value content. Pages that look templated, sparse, or near-duplicate signal low value before Google even reads them, especially when similar URLs already exist.
• Weak internal linking. A URL buried deep in the site, with few or no internal links pointing to it, reads as low priority. Google leans on internal links to gauge importance.
• Crawl budget on large sites. On sites with many thousands of URLs, Google allocates a finite crawl budget. Low-priority pages can wait a long time in the discovered queue.
• Slow server response. If your server is slow or returns errors under load, Google throttles crawling to avoid overwhelming it, and discovered URLs stall.
• Too many similar pages. Faceted navigation, tag archives, pagination, and parameter URLs can flood the queue with near-identical pages that dilute the value of any single one.

How to diagnose

Start in Search Console. Open the Page Indexing report, click the "Discovered - currently not indexed" row, and review the example URLs. Look for a pattern: are they all blog tags, product filters, or paginated pages? A pattern points to a structural cause rather than a content one.

Next, run the affected URL through the URL Inspection tool to confirm the status and check whether the page is reachable and returns a clean 200 response. Verify the URL is not accidentally blocked or set to noindex. Our robots.txt complete reference covers how to confirm a page is crawlable.

Then check the Crawl Stats report (Settings, then Crawl stats) for slow average response times or spikes in server errors. Finally, audit internal linking: count how many internal links point to the stalled URLs, and how many clicks from the homepage it takes to reach them.

How to fix

• Improve content quality and uniqueness. Expand thin pages with substantive, original information that answers a real query. Merge or remove pages that say almost the same thing.
• Strengthen internal links. Add contextual links from relevant, already-indexed pages to the stalled URL. Pull important pages closer to the homepage in your site structure.
• Improve site speed and server response. Faster, more stable responses encourage Google to crawl more. Address slow database queries, caching gaps, and resource limits.
• Reduce thin and duplicate pages. Consolidate, canonicalize, or noindex low-value pages so crawl budget flows to the URLs you actually want indexed. Be careful not to confuse these with soft 404 errors, which need a different remedy.
• Request indexing for priority URLs. For a handful of important pages, use URL Inspection and click "Request indexing" to nudge Google. Use this sparingly; it does not scale and will not fix an underlying quality or budget problem.

Discovered vs Crawled - currently not indexed

These two statuses look similar but mean different things. "Discovered - currently not indexed" means Google has not fetched the page at all, so the issue is about getting Google to crawl it. "Crawled - currently not indexed" means Google did fetch and read the page but decided not to index it, so the issue is about the page itself meeting Google's quality bar.

In short: discovered is a crawling and prioritization problem, while crawled is a content quality and value problem. With discovered URLs, focus on crawl budget, server speed, and internal links. With crawled URLs, focus on making the content genuinely more useful and distinct than what is already indexed.

FAQ