Google's definition is short: the page was found but not crawled yet. Its help page says Google rescheduled the crawl because it expected crawling to overload the site, so the last crawl date is empty. Wait a few days to a few weeks for new URLs. If a URL is older than that, check that Google can reach it through your sitemap and internal links, and that your server answers fast.
What the status says, and what it does not
A URL passes through stages before it can appear in results. Google must discover it, crawl it, then decide whether to index it. "Discovered" is stage one. Google got the address from a sitemap or a link and put it in a queue.
Because nothing has been fetched, advice about thin content or duplicates does not apply yet. That belongs to the crawled but not indexed status, which is a different problem with a different fix.
Wait or act: a triage table
Open the URL in the URL Inspection tool and compare it with this table. The signals come from the fields Google documents in that tool.
| What you see | Likely meaning | Do this |
|---|---|---|
| URL is days old, sitemap lists it | Normal queue time | Wait. Google says a crawl can take a few days to a few weeks. |
| No sitemap and no referring page shown under Discovery | Google may know the URL from an old source only | Add it to the sitemap and link to it from a crawled page. |
| Hundreds of similar URLs share the status | Google sees more URLs than it wants to fetch | Look for a URL pattern (parameters, archives, filters) and reduce it. |
| Status appears after traffic or deploys that slowed the site | Crawl capacity dropped; slow responses, 5xx and 429 lower it | Fix server speed and errors, then give it time. |
| URL is months old and still never crawled | Weak discovery signals | Add internal links from strong pages, then request indexing for the one or two that matter. |
Why Google delays a crawl
Google's crawl budget guide splits crawling into two parts. The crawl capacity limit is how much connection time Google can use without hurting your server. It rises when the site answers quickly and falls with slowdowns, 5xx errors and HTTP 429 responses. Crawl demand depends on how many URLs Google knows about, how popular they are and how stale they look.
Two practical points follow. First, a fast server helps more than any setting in Search Console. Second, the biggest lever you control is how many URLs Google knows about. Google's guide says duplicates and unwanted URLs waste crawl time. Check the response time of a typical page:
curl -s -o /dev/null -w "status %{http_code} first byte %{time_starttransfer}s\n" https://example.com/your-page/
Run it a few times at different hours. Seconds, rather than fractions of a second, to the first byte on a plain page is worth fixing. Google also says that supporting 304 Not Modified saves it from re-downloading unchanged pages.
Check how Google can reach the URL
- Look at Discovery. In URL Inspection, the Discovery section lists sitemaps that include the URL and may show a referring page. Empty fields mean Google has little reason to hurry.
- Link to it from somewhere that gets crawled. A page that only appears in a sitemap is a weak case. A link from your home page, a hub page or a recent post is a stronger one. Count the internal links pointing at the URL; zero is common for new programmatic pages.
- Keep the sitemap honest. Google uses
lastmodonly if it is consistently accurate, and ignorespriorityandchangefreq. Google also calls a sitemap a hint, not a command. Our sitemap checker flags broken and redirected entries. - Rule out a block. A robots.txt disallow or a stray noindex would give a different status, but check anyway with the noindex checker.
Reduce what Google has to fetch
If the list is long, group the URLs by pattern in Search Console's export. The patterns usually point to the cause. Example: a WordPress blog with 60 posts can show hundreds of Discovered URLs when tag, date and author archives and paginated pages are all linked from every page. A Next.js or Webflow site can do the same with filter parameters or locale routes that nobody linked on purpose.
Google's guide recommends consolidating duplicates, returning 404 or 410 for pages that are gone for good, fixing soft 404s and avoiding long redirect chains. It also says to block unimportant URLs with robots.txt rather than noindex, because Google still has to request a noindex page to see the tag.
When to use Request Indexing
The button is a quick way to put one URL in front of Google. It does not guarantee indexing, repeating it for the same URL does not make the crawl faster, and a quota applies. Read how that limit behaves in the quota exceeded guide. Use the request for the pages that earn money, after the checks above, and leave the rest to the sitemap.
Google does not publish a wait time or a count after which this status turns into a problem. Treat the few-days-to-few-weeks range from its recrawl page as the only official guide, and judge older URLs by the checks above instead of a fixed deadline.
Questions people ask
How long does Discovered - currently not indexed last?
Google gives no fixed time. Its recrawl documentation says crawling can take anywhere from a few days to a few weeks. A new URL older than that, with no crawl date at all, deserves a closer look.
Should I click Request Indexing on every URL in the list?
No. Google says a request does not guarantee indexing, repeating it does not speed anything up, and there is a quota. Fix what makes the URL hard to reach first, then request only the few pages that matter most.
Does this status mean my content is low quality?
Google has not fetched the page, so it cannot have judged the content from a crawl. If Google has fetched it and still skipped it, you are looking at the other status, covered on the crawled-but-not-indexed page.
Is a big Discovered list a crawl budget problem?
Only on large sites. Google's crawl budget guide is aimed at sites with roughly a million pages, or ten thousand that change daily, or many URLs in this status. Google calls those figures a rough estimate.
Related
Sources
- Search Console Help: Page indexing report, accessed 2026-11-12.
- Google Search Central: Managing crawl budget for large sites, accessed 2026-11-12.
- Google Search Central: Ask Google to recrawl your URLs, accessed 2026-11-12.
- Search Console Help: URL Inspection tool, accessed 2026-11-12.
- Google Search Central: Build and submit a sitemap, accessed 2026-11-12.