Discovered – Currently Not Crawled
Discovered – currently not crawled is a Google Search Console page status meaning Google knows the URL — from links or a sitemap — but has not fetched it yet. The page sits in the crawl queue, sometimes indefinitely.
Discovered – currently not crawled appears in Google Search Console's Pages report (Indexing → Pages) when Google holds the URL in its crawl queue but Googlebot has not attempted the fetch. Google learned the URL exists — from an internal link, an external link, or an XML sitemap — and then deferred crawling it. Nothing about the page's content has been evaluated, because none of it has been seen.
Google's documentation attaches one explanation: the crawl was scheduled, then postponed because fetching was expected to overload the site's server. In practice the status is as much a crawl-demand problem as a capacity one — it concentrates on URLs Google has decided are not yet worth a fetch: sections with weak internal linking, sites with little authority, and URL inventories so large they dilute crawl budget across low-priority pages. It is the signature status of two site profiles: new domains (no crawl history, few links) and large e-commerce catalogs (parameters and pagination multiplying the URL inventory).
The status has no fixed duration and no automatic resolution — URLs sit in it for days or months, and on weak sites some never leave. What moves a URL out is raised crawl demand: stronger internal links, a cleaner sitemap, higher site quality, or direct submission into Google's crawl systems. Waiting alone is not a strategy; the full diagnostic and repair workflow is in How to Fix "Discovered – Currently Not Crawled".
Quick facts
What causes Discovered – currently not crawled?
Google defers the crawl for four reasons: anticipated server overload, low crawl demand, weak internal linking, and an oversized URL inventory.
- 1Anticipated server overload — Google's stated reason: the fetch was scheduled, then postponed to avoid stressing the server
- 2Low crawl demand — the site or section lacks the authority and link signals that make Google prioritize a fetch
- 3Weak internal linking — the URL is buried deep in the architecture or is a near-orphan page reachable only through the sitemap
- 4Oversized URL inventory — faceted navigation, parameters, and pagination inflate the crawlable URL count until the queue outgrows the site's crawl budget
On new sites the dominant factor is missing crawl history and links; on large e-commerce sites it is inventory dilution.
How is it different from Crawled – currently not indexed?
The fetch. Discovered – currently not crawled means Googlebot never requested the URL, so nothing is known about the page; Crawled – currently not indexed means the fetch and render completed and Google then declined to index the result — a quality judgment.
The distinction decides the fix: a Discovered URL needs crawl demand (links, submission, authority), while a Crawled-not-indexed URL needs a stronger page. The two statuses also sequence — resolving Discovered moves a URL forward to be fetched, after which it is either indexed or parked in Crawled – currently not indexed.
How do you get Discovered URLs crawled?
You raise the URL's crawl demand above the queue's cutoff — Google fetches when demand justifies it, so the levers are links, sitemap hygiene, quality, and direct submission. In order of speed:
- 1Submit the URL directly — the URL Inspection tool's Request Indexing for single URLs, bulk submission channels for many
- 2Strengthen internal links — link the stuck URLs from the site's most-crawled pages
- 3Tighten the sitemap — list only index-worthy URLs, and validate it with the XML Sitemap Validator
- 4Shrink the competing inventory — cut parameter and duplicate URLs draining the same crawl budget
The step-by-step workflow, including which lever fits which site profile, is in How to Fix "Discovered – Currently Not Crawled".
Frequently Asked Questions
How long do URLs stay in Discovered – currently not crawled?+
Anywhere from days to indefinitely — no timeout forces a crawl. URLs leave the status when their crawl demand rises: authoritative sites clear the queue in days, while the same URLs on a new domain can sit for months untouched.
Is Discovered – currently not crawled an error or a penalty?+
Neither. It is a scheduling status: Google confirms the URL is known and queued. It becomes a problem when revenue-relevant pages accumulate in it, which signals the site's crawl demand is running below its publishing rate.
Does requesting indexing fix it?+
For individual URLs, usually — the request queues a priority fetch that jumps the natural schedule. At the scale of hundreds of Discovered URLs, per-URL requests cannot keep up; the structural levers — internal links, inventory cleanup, bulk submission — do the work.