Discovered – Currently Not Indexed
A Search Console status: Google knows the URL but has not crawled it yet. A queue state, not an error or a verdict.
Reviewed by Alexander Yarovenko · Updated: 2026-10-04
Discovered – currently not indexed is a Search Console status meaning Google knows the URL exists but has not crawled it yet. Google says it may reschedule crawling to avoid overloading the site. The page has not been fetched, so Google has formed no view of its content. It is a queue state, not a verdict.
What it is and where the boundary lies
The status sits earlier in the pipeline than “crawled – currently not indexed”. Here nothing has been downloaded; the URL is only known, for example from a sitemap or a link. Google’s own crawl-budget guide treats a large share of such URLs as one sign that a site may need to manage its crawling. A small site with a handful of these URLs is not in that situation, and the status does not prove a crawl-budget problem.
How it differs from similar terms
| Status | Was the page fetched? | First question |
|---|---|---|
| Discovered – currently not indexed | no | why has Google not crawled it yet |
| Crawled – currently not indexed | yes | why did Google not keep it |
| Soft 404 | yes | does the page look empty or like an error |
| Blocked by robots.txt | not allowed | is the block intended |
Why it matters
A URL that is not crawled cannot be indexed, so it cannot earn impressions. If the URLs are pages you want in Search, such as new products or articles, the delay costs visibility. If they are filters, parameters or old duplicates, leaving them uncrawled is acceptable and often desirable.
What Google documents and what it does not
- Documented: the page was found but not crawled yet; Google may reschedule crawling so as not to overload the site; crawl budget depends on the capacity limit and on crawl demand; duplicates, soft 404s and unimportant URLs waste crawling.
- Not documented: a fixed wait after which the page is crawled, or a way to force crawling by resubmitting.
What to check first
- Is the URL meant to be in Search? Filters and internal search results usually are not.
- Is it linked? A page found only in a sitemap, with no internal links, signals little importance (internal linking, orphan pages).
- Is the server fast and stable? Slow or erroring responses lower how much Google crawls. Read the Crawl Stats report (Crawl Stats report).
- Does the site generate endless URLs? Duplicates and parameter variants compete for crawling with pages that matter (duplicate content).
- Is the sitemap clean? List only canonical URLs you want indexed, with accurate
lastmoddates (sitemap). - Does the page load efficiently? Heavy pages cost more crawl time (page speed).
Practical example
| Group | URLs | Decision |
|---|---|---|
| filter and parameter variants | 420 | stop linking to them, block crawling if not needed |
| old removed products | 50 | return 404 or 410, remove from the sitemap |
| new product pages | 30 | link from category pages, keep in the sitemap |
420 + 50 + 30 = 500. Only 30 URLs are real candidates for indexing; the other 470 are inventory to clean up, which also frees crawling for the 30.
Common mistakes
- Requesting indexing for hundreds of URLs: the cause is usually in discovery, links or inventory, not in the request.
- Assuming a crawl-budget problem on a small site: Google describes that guide for large sites.
- Leaving junk URLs in the sitemap: they compete with pages that matter.
- Blocking in robots.txt to hide pages from the index: robots.txt manages crawling, not indexing.
- Ignoring server speed: slow responses lower the crawl rate.
How to validate the result
Pick a few URLs from the important group and inspect them with the URL Inspection tool: the status should move to crawled and then indexed. Watch the size of the group in the Page indexing report and the crawl requests in the Crawl Stats report over several weeks. Judge success by the important URLs, not by the total.
More questions
How long until Google crawls the page?
Google gives no fixed time. Crawling can take from days to weeks.
Is this the same as a crawl-budget problem?
Not necessarily. It can be one sign on large sites, but links, server speed and inventory matter first.
Will the status go away if I resubmit the URL?
Repeated requests do not speed crawling. Improve discovery and efficiency instead.
Next practical step
Export the URLs with this status, split them into groups like the table above and decide which belong in Search. The technical indexing audit shows how to turn the groups into a queue.
Related concepts
- Crawl budget — how much crawling a site receives.
- Index coverage — the report where the status appears.
- URL Inspection tool — checks one URL.
- Crawled – currently not indexed — the later-stage status.