Discovered – currently not indexed: a crawl priority problem
Google has the URL on a list and has not got to it. Unlike the 'crawled' status, this one is genuinely responsive to what you do — but the effective actions are about priority, not volume.
The distinction from crawled – currently not indexed is the whole diagnosis. There, Google looked and declined. Here, Google has not looked yet.
Why the URL is waiting
- Server responsiveness. Crawl rate adapts to how a site handles load. Slow or error-prone responses reduce it, and Google's crawl budget documentation covers this directly.
- Low internal link weight. A URL reachable only from a sitemap, or from one link five clicks deep, gets low priority.
- A URL space larger than the site's crawl capacity. Faceted navigation, session parameters, calendar pages and filter combinations generate URLs faster than any crawler will fetch them.
- Sitemap noise. A sitemap listing every URL as changed today, or containing redirects, 404s and noindexed pages, degrades its usefulness as a priority signal.
The four levers, in order of effect
- Cut the URL space. Parameter handling, canonicals, robots rules on filter paths. Removing 80,000 junk URLs does more for the 400 you care about than any submission campaign.
- Raise internal link depth. Get the waiting URLs within two or three clicks of an indexed, frequently crawled page. Hub pages and honest related-content blocks, not footer link dumps.
- Fix response time. Sustained TTFB improvements show up in Crawl Stats within weeks.
- Clean the sitemap. Only canonical, indexable, 200-status URLs. Honest
lastmod.
Where submission fits
This is the status where asking for a crawl is genuinely on-target, because the bottleneck is attention rather than assessment. It is also the status where volume discipline matters most: a domain already failing to keep up with its own URL space will not benefit from thousands more requests arriving at once. Spreading them is the point of drip-feed.
When to ignore it
A share of URLs sitting here is normal and healthy on any site above a few thousand pages. It becomes a problem when the count is rising, when it affects pages that make you money, or when the affected URLs share a recognisable pattern.
Questions
Does submitting a sitemap fix this status?
It helps with discovery, which this status has already passed. If the URLs are in the sitemap and still waiting, the constraint is crawl priority, and sitemap changes alone will not shift it.
How long can a URL stay in this state?
Indefinitely. There is no timeout after which Google is obliged to crawl a URL, which is why treating it as a queue that will eventually drain is a mistake.
This is the status submissions were made for
Attention is the bottleneck here, and paced requests are how you buy it without dumping thousands at once.
Submit a paced batch