Discovered, Currently Not Indexed: Why Google Won't Crawl

What "Discovered, currently not indexed" actually means

Open the Page Indexing report in Google Search Console and this is one of the statuses that trips people up the most. Google's own definition is short: the page was found by Google, but not crawled yet. Typically Google wanted to crawl the URL but this was expected to overload the site, so Google rescheduled the crawl.

Read that twice, because the important part is easy to skim past. The page has not been crawled at all. Google knows the URL exists, usually because it saw the link in your sitemap or on another page, but Googlebot never actually fetched it. Nothing about the page's own content has been judged yet, because Google hasn't looked at it.

That's the whole difference between this status and its more famous sibling, "Crawled, currently not indexed," which Google defines as: the page was crawled by Google but not indexed. One is a crawling problem. The other is an indexing decision made after the crawl. If you treat them the same way, you'll pour effort into rewriting content when the real issue is that Googlebot never showed up.

This guide is about the first one: pages Google discovered but chose not to crawl, and how to change its mind.

Why Google skips a page it already found

Google doesn't crawl every URL it knows about, and it never has. It spends what it calls crawl budget, which the crawl-budget docs describe as the set of URLs that Google can and wants to crawl. Two forces decide that. Crawl capacity is the ceiling: the maximum number of parallel connections Googlebot will open, plus the delay between fetches. Crawl demand is the appetite: how much Google actually wants your URLs, which varies based on a site's size, update frequency, page quality, and relevance compared to other sites.

"Discovered, currently not indexed" is what you see when demand for a specific URL is low or capacity is tight. A few concrete things push a page into that bucket:

• Your server is slow or shaky. Crawl capacity moves with your response times. If the site responds quickly for a while, the limit goes up. If it slows down or throws server errors, the limit goes down. A struggling server tells Google to back off, and new URLs sit in the discovered queue.
• Google is guessing your page is low value before it ever loads it. This is the counterintuitive one. Since Googlebot hasn't crawled the page, it estimates quality from the rest of your domain and from similar URL patterns it has already seen. If the neighbourhood is thin or templated, the new URL inherits that reputation and gets deprioritized.
• The URL is weakly linked. Google pays less attention to URLs that don't have enough internal links pointing at them. A page that only exists in the sitemap, with no real links from your own site, reads as low priority.
• You're wasting the budget elsewhere. If many of the URLs Google can see are duplicates, or pages you don't actually want crawled, that wastes a lot of Google's crawling time. Spend it on faceted-navigation variants and session-ID URLs, and there's less left for the pages you care about. Google is blunt about the consequence: if it spends too much time crawling URLs it shouldn't, its crawlers might decide it's not worth looking at the rest of your site.

Notice that none of these are "your content is bad." Discovered-not-indexed is almost always a signal about your site's structure and health, not about the individual page's words.

First, decide whether it's even a problem

Before you fix anything, look at which URLs are actually in the report. A handful of low-priority pages sitting in "Discovered, currently not indexed" is normal, and on a big site it's expected. Google will get to some of them eventually and quietly drop others it never wanted.

You have a real problem when one of these is true:

• Important, money pages are stuck in the bucket.
• The count is climbing week over week rather than holding steady.
• The affected URLs share a pattern: one template, one directory, one parameter.

That third case is the useful one, because a pattern points straight at a cause. If every stuck URL lives under /products/ with a ?color= parameter, you're looking at a crawl-budget and duplication issue, not a content issue. Export the list from Search Console and sort it before you touch anything. A crawl of your own site, so you can see the internal-link count and depth of each stuck URL, tells you in minutes whether these pages are orphaned or buried ten clicks deep.

The fixes, in the order we'd actually try them

Most advice online jumps straight to "click Request Indexing." That's backwards. Request Indexing is a nudge for a few URLs, not a fix for a systemic pattern, and if the underlying cause is still there the pages fall back out. Work the causes first.

1. Get real internal links to the stuck pages. This is the highest-leverage move and the one people skip. Link to the discovered URLs from pages that already get crawled often: your homepage, hub and category pages, and popular posts. Use plain <a href> links with descriptive anchor text, not buttons wired up in JavaScript. Pages with strong internal links get crawled faster because the links are how Google rediscovers and re-prioritizes them. If you're not sure where your link equity pools, our guide on internal linking strategy walks through finding those hub pages.

2. Stop wasting crawl budget on junk URLs. Every duplicate, parameter permutation, and infinite-scroll variant you let Google crawl is capacity not spent on the pages you want indexed. Consolidate duplicates with canonical tags, block genuinely useless URL patterns, and keep your sitemap to canonical, indexable URLs only. Check what you're actually allowing with a robots.txt tester before you assume the file does what you think. Our crawl budget optimization guide goes deep on trimming the crawl surface on large sites.

3. Fix server response time. If your logs show slow responses or 5xx errors when Googlebot visits, crawl capacity is being throttled and no amount of internal linking will help until you fix it. Pull your access logs and look at what Googlebot actually experienced. That's exactly what log-file analysis is for: it shows you the real fetch history, the response codes Googlebot got, and whether it's even reaching the URLs in question.

4. Raise the quality signal of the surrounding pages. Because Google is estimating the stuck page's value from its neighbours, thin or near-duplicate pages in the same section drag it down. Improve or prune the low-value pages around it. Sometimes the fastest win is deleting a hundred thin URLs so the good ones look better by comparison.

5. Then, and only then, request indexing. Once the structural cause is handled, use URL Inspection and Request Indexing on your priority pages to jump the queue. Now it sticks, because you've given Google a reason to keep the page instead of just a one-time poke.

How long it takes, and when to stop worrying

There's no fixed timer. After you add internal links and clean up the crawl surface, Googlebot has to come back, notice the changes, and re-evaluate. On a healthy site that's days. On a slow or sprawling site it can be weeks. Watch the report's trend line, not any single URL. If the count is falling and your important pages are getting crawled and indexed, it's working, even if a few low-value URLs stay behind forever. Those stragglers are Google doing its job.

If you're new to reading this report at all, our walkthrough on how to fix crawl errors in Search Console covers the other statuses you'll run into alongside this one.

Quick answers

Is "Discovered, currently not indexed" a penalty? No. It's a prioritization decision. Google found the URL and decided not to spend crawl budget on it yet. Penalties are a different thing entirely.

Should I just request indexing for all of them? No. If there's a pattern of stuck URLs, requesting indexing one by one treats the symptom. Fix internal linking and crawl budget first, then request indexing for your priority pages.

How is this different from "Crawled, currently not indexed"? Discovered means Google never fetched the page, so it's a crawl-priority problem. Crawled means Google fetched it and chose not to index, which is usually a quality or duplication problem with the page itself.

Can crawl budget really matter for a small site? It matters less, but crawl efficiency still bites at any size. A small site that floods Google with parameter URLs and slow responses can absolutely park its good pages in the discovered queue.

Discovered-not-indexed looks scary because it sounds like Google rejected your page. It didn't. It just hasn't bothered to look yet, and everything above is about giving it a reason to.