"Discovered - currently not indexed" in Google Search Console means Google has found the URL, usually through your sitemap or a link, but has not crawled it yet. Google decided to postpone the fetch. Unlike its sibling status, this is not a judgment about your content, because Google has not read it. Discovered currently not indexed is about crawl priority: Google does not think the URL is worth fetching right now, or it thinks your server cannot handle more requests.
Discovered vs Crawled: Which Problem Do You Have?
The two statuses look similar but need different fixes:
| Discovered - currently not indexed | Crawled - currently not indexed | |
|---|---|---|
| Has Google fetched the page? | No | Yes |
| Main cause | Crawl priority, crawl budget, server capacity | Content quality, duplication, weak signals |
| Main fixes | Faster server, fewer junk URLs, stronger internal links | Better content, merge duplicates, internal links |
If Google has crawled the page and still left it out, follow our guide to crawled currently not indexed instead.
Why Google Leaves URLs as Discovered Currently Not Indexed
- Your server is slow or erroring. Google reduces its crawl rate when responses are slow or return 5xx errors. When Search Console says it postponed the crawl "because it expected the site to be overloaded", this is the reason.
- Too many low-value URLs. Faceted navigation, sort and filter parameters, session IDs, calendars and endless pagination can create millions of URLs. Google spends its crawl budget on those and leaves the important ones as discovered currently not indexed.
- Weak internal linking. URLs that are only in the sitemap, with few or no internal links, look unimportant.
- A new or low-authority site. Google crawls new sites cautiously. Publishing thousands of pages at once on a young domain almost guarantees a long discovered currently not indexed list.
- Site-wide quality signals. If many of the pages Google already crawled were thin or duplicated, it becomes less eager to crawl more URLs from the same site.
How to Fix Discovered Currently Not Indexed
1. Check crawl stats and server health
Open Settings, then Crawl stats in Search Console. Look at average response time, the share of 5xx responses and host status. If response times are high or errors spiked, fix the server first: Google will not raise its crawl rate on a struggling host. Our guide to reducing TTFB covers the server side.
2. Cut the junk URLs
Stop wasting crawl budget on URLs that should never be crawled. Block parameter and faceted URLs in robots.txt where appropriate, remove links to them where you can, and make sure filter combinations do not generate crawlable links by default. Fewer junk URLs means more of Google's attention goes to pages stuck in discovered currently not indexed.
3. Fix redirect chains and broken links
Every hop in a redirect chain and every link to a 404 costs a crawl. Point internal links straight at final URLs. See the redirect chain guide and test with the redirect checker.
4. Strengthen internal links to the stuck URLs
Link to important pages from your homepage, category hubs and related articles. A URL that is three clicks from the homepage gets crawled sooner than one reachable only through the sitemap.
5. Keep the sitemap clean and current
List only canonical, indexable URLs that return 200, and keep lastmod dates honest. A clean sitemap helps Google prioritize. Check it with the sitemap checker; the robots.txt and sitemap guide explains the rules.
6. Publish at a sustainable pace
On a newer site, release content in batches Google can keep up with, and make sure each page is strong enough to earn its crawl. Quality per URL beats URL count.
7. Request indexing for the few that matter most
URL Inspection's "Request indexing" works for a handful of priority pages. It does not scale to thousands; for that, the structural fixes above are the only lever.
How Long Does It Take?
After fixing server speed and crawl waste, most sites see Google work through discovered currently not indexed URLs over several weeks. Watch the Crawl stats report: rising total crawl requests and falling response times are the leading indicator that the list will shrink.
How Scanverra Helps
The Scanverra SEO Optimizer checks the signals that affect discovery: whether robots.txt blocks a page, whether a sitemap exists, redirect behavior, noindex and canonical tags. Its multi-page crawl (up to 25 pages) reports sitemap URLs that internal links never reached, which is a short list of likely orphan pages to link up. It does not see your server logs or Search Console crawl stats, so it cannot measure crawl budget directly; use it to find structural causes, and Search Console to watch Google's crawl rate. Then run the technical SEO audit checklist across the rest of the site.