Discovered - currently not indexed: what it means and how to fix it

Google knows the URL exists but has not crawled it yet. It is usually because of crawl budget or server load, weak internal links, or low-value URL patterns. This status is a crawling delay, not a penalty and not a judgement that the content is poor.

You will see it in Google Search Console under Indexing → Pages. Start with the URLs you actually want in search, because filter, parameter and other duplicate URLs can appear here without anything being wrong.

What does Discovered - currently not indexed mean?

Discovered means Google found the URL through a link, sitemap or another source, but Googlebot has not fetched the page. The URL is therefore not indexed, and there may be no last crawl date in the report.

Google's Page indexing report help says this typically happens when Google wanted to crawl the URL but expected that to overload the site, so it rescheduled. Since no fetch has happened, this status does not tell you whether Google likes the content. Our Search Console Page indexing report guide shows where this status fits among the other indexing reasons.

Discovered vs Crawled - currently not indexed

Discovered means Google has not fetched the URL; Crawled means Google fetched it but chose not to index it for now. That is why Discovered usually calls for crawl and discovery fixes, while Crawled usually calls for content, quality and canonical checks.

If Search Console says the page was crawled, use the Crawled - currently not indexed guide instead. Do not repeatedly rewrite a Discovered page before Google has even fetched it.

Why Google delays crawling a URL

Google delays crawling when the site looks slow or unreliable, when the URL seems unimportant, or when other URLs look like a better use of crawl capacity. Google's crawl budget guide explains that slow responses and server errors reduce crawling, while duplicate and low-value URLs can waste it.

• Slow server responses or 5xx errors. If pages take too long to answer or often fail, Googlebot slows down to avoid overloading the server.
• Too many near-duplicate or parameter URLs. Filters, sorting, tracking parameters and session URLs can create a long crawl queue without adding useful pages.
• Orphan pages and weak internal links. A URL listed only in a sitemap has fewer discovery signals than one linked from useful, indexed pages. Use the orphan pages feature to find URLs with no internal links.
• A sitemap full of low-value URLs. Redirects, duplicates, noindex pages and error URLs dilute the list of pages you are asking Google to crawl.

A brand-new URL can also sit here simply because Google has not reached it yet. One isolated Discovered URL does not prove a crawl-budget problem.

How to fix it step by step

Work in this order: make crawling reliable, strengthen links to important pages, reduce wasted crawls, then request indexing for the few URLs that matter most.

1. Speed up server response and fix 5xx errors

   Check several affected URLs and watch response times and server logs. Fix application errors, add sensible caching and make sure the server can handle Googlebot's requests. A fast, reliable response lets Google crawl more without putting the site under load.

2. Add internal links from strong pages

   Link to the affected URL from a relevant indexed page, topic hub or popular guide using descriptive anchor text. Use ordinary HTML links rather than links that only appear after a click. Our internal linking guide explains how to choose sources and anchors; remove any orphan page's isolation by giving it a real place in the site structure.

3. Trim the sitemap to canonical indexable URLs

   List only live URLs that return 200, are allowed to be indexed and have themselves as the canonical. Remove redirects, errors, noindex pages and duplicates. Keep important Discovered URLs in the clean sitemap; our XML sitemap guide covers the format and checks.

4. Consolidate thin and duplicate URLs

   Merge pages that serve the same need, use canonical tags for genuine duplicates, and redirect removed versions to the closest live page. Limit unnecessary parameter and filter URLs where you control the application. This gives Google fewer low-value choices and leaves a clearer set of pages to crawl.

5. Request indexing for a few key URLs

   After fixing a priority page, paste its URL into Search Console's URL Inspection tool, run a live test and choose Request indexing once. Use this for a small number of important pages, not the whole backlog. Google's recrawl guide says repeated requests for the same URL do not make crawling faster.

6. Check crawl stats and recheck the report

   Open Settings → Crawl stats in Search Console. Look for slow average response times, rising 5xx responses and large numbers of requests going to duplicate or low-value paths. Recheck after your changes; look for a falling Discovered count and important URLs moving to Indexed.

How long it takes to clear

There is no fixed time: a crawl can happen within days, but a large backlog or ongoing server and quality problems can leave URLs here for weeks or longer. Clearing the status means Google crawls the URL; it does not guarantee that Google will then index it.

Check Crawl stats after server changes and the Page indexing report after link, sitemap and consolidation work. If you use Validate fix, Google says validation can take up to about two weeks or longer. A page that next becomes Crawled - currently not indexed has been fetched, so the next job is to improve its reason to be indexed rather than its crawl access.

Questions and answers