“Discovered – currently not indexed” means Google knows the URL exists, usually from a sitemap or a link, but has not crawled it yet. Nothing has been assessed, because nothing has been fetched.
This is fundamentally a crawl capacity problem rather than a content problem, which makes it different from Crawled – currently not indexed and means the remedies are different too.
Why Google delays crawling a known URL
- Crawl capacity is being spent elsewhere. On large sites, low-value URLs consume the budget that new pages need.
- The server is slow or unreliable, so crawl rate is throttled to avoid overloading it.
- The URL looks low priority, because nothing links to it except a sitemap.
- A large number of URLs appeared at once, such as after a catalogue import, and they are queued.
- Similar URLs have historically proved low value, so the pattern is deprioritised.
The strongest signal: how many URLs are affected
- A handful: usually normal queuing. Wait.
- Hundreds or thousands: a crawl efficiency problem. Something is consuming capacity.
- Concentrated in one URL pattern: that pattern is being deprioritised, which usually means it looks low value.
- Growing steadily: you are publishing faster than the site earns crawling.
Diagnosing it
- Check Search Console crawl stats for total requests and average response time.
- Compare crawl requests against the size of your genuine page inventory.
- Sample server logs if available, and segment requests by URL pattern.
- Identify what is being crawled instead: filters, parameters, redirects and soft 404s are the usual culprits.
- Check whether affected URLs have any internal links at all.
Fixing it
Recover wasted crawl capacity
- Prevent crawling of filter, sort and parameter URLs at source.
- Flatten redirect chains so each resolves in one hop.
- Return proper status codes instead of soft 404s, which keep getting re-requested.
- Remove dead URLs from sitemaps.
- See crawl budget for the full treatment on large catalogues.
Improve server response
Crawl rate adapts to what your server sustains. A slow site is crawled less, which directly limits how quickly new pages are discovered and fetched.
Make the URLs look worth crawling
- Link them from pages that are crawled frequently, such as category or hub pages.
- Reduce click depth, since deep pages are crawled less often.
- Keep sitemaps accurate and segmented, so priority content is distinguishable.
- Publish at a rate the site can support rather than in large bursts.
What does not work
- Repeatedly requesting indexing for large numbers of URLs.
- Resubmitting the same sitemap unchanged.
- Adding more URLs while the existing ones are queued.
- Removing the sitemap, which makes discovery harder rather than faster.
Frequently asked questions
How long before a discovered URL gets crawled?
Days to weeks on a healthy site. Indefinitely on a site where crawl capacity is consumed by low-value URLs. The number of affected URLs tells you which situation you are in.
Does this mean my content is bad?
No. Nothing has been read yet. This status is about crawl prioritisation, not about quality. If quality were the issue, the status would be “Crawled – currently not indexed” instead.
Should I submit URLs individually?
For a small number of important pages, it can help. For hundreds, it will not, and it does not address the underlying capacity problem.
Will a bigger sitemap help?
No. Sitemaps aid discovery, and discovery has already happened. The constraint is crawling, which sitemaps do not increase.
Consulting CTA
If large numbers of your URLs are discovered but never crawled, book an SEO consultation for a crawl efficiency review.