What Does "Discovered - Currently Not Indexed" Mean?

"Discovered - currently not indexed" is a Google Search Console status: Google knows your page exists but has not crawled it yet, so it is not in the index. Google's own explanation is that it wanted to crawl the URL but held back to avoid overloading your site. The common causes are a slow server, thin pages, and weak internal linking. Many URLs clear on their own; a slow site or a thin page needs a fix.

What does "Discovered - currently not indexed" mean?

The status means Google has found your page but has not fetched it, so it cannot be indexed yet. Google learned the URL exists, usually from a link or your sitemap, and put it in the queue to crawl later.

Google describes it plainly. The page was found by Google, but not crawled yet (Google Search Console Help). Google adds that it wanted to crawl the URL, but expected this to overload the site, so it rescheduled.

That is why the report shows an empty last-crawl date here. Google has not visited the page even once.

So the page is not blocked in robots.txt and not penalized. It is simply waiting in line.

Why does Google discover a page but not crawl it?

Google defers crawling when a fetch looks expensive or low-priority. The most common reason is server capacity: if your host responds slowly, Google slows its crawling to protect the site, and low-priority URLs wait longest.

There is a mechanism behind this. Google spends a limited crawl budget on each site. A slow server response signals that every fetch is costly, so Google throttles back rather than risk overloading the site.

Perceived value is the second factor. A page with thin content or few internal links looks less worth fetching, so it sinks down the queue.

Site size matters too. On a site with thousands of URLs, more pages compete for the same limited crawling, so more of them sit in "discovered" at any moment.

How is it different from "Crawled - currently not indexed"?

The two statuses describe different stages, and the difference points to different fixes. "Discovered" means Google has not fetched the page yet. "Crawled" means Google fetched it but chose not to index it.

Google's wording for the second, on the same help page, is direct. The page "was crawled by Google but not indexed," and "may or may not be indexed in the future," with no need to resubmit it.

Status	What happened	Usual cause
Discovered - currently not indexed	Found, not yet crawled	Slow server, low crawl priority
Crawled - currently not indexed	Crawled, not chosen for index	Thin, duplicate, or low-value content

So "discovered" usually points at capacity and priority. "Crawled" usually points at content quality. Reading which status a URL sits in tells you where to look first.

How do you fix "Discovered - currently not indexed"?

Fixing it means making the page quicker to crawl and clearly worth indexing. A few moves cover most cases.

Speed up your server response first. On low-cost shared hosting that slows under load, faster hosting or caching often lets Google resume clearing the backlog.

Strengthen internal links to the page next. A page linked from strong, frequently-crawled pages gets prioritized faster than a near-orphan.

Improve the content, and confirm the URL sits in your sitemap. Then request indexing for important URLs, but sparingly, because Google recrawls on its own.

Picture a 2,000-page catalog on an entry shared plan. Google discovers new product URLs from the sitemap, but meets slow responses and queues most of them (an illustrative pattern, not a client result).

In our experience, a pile-up of "discovered - currently not indexed" URLs on a larger site usually traces back to a slow server response, not the content itself.

When should you just leave it alone?

Some URLs in this status are normal and need no action. Google says not being indexed is not necessarily bad, and that only your canonical pages need to be indexed.

A few discovered-but-not-indexed URLs on a healthy site are routine. The signal to act is a large or growing share of important pages stuck in the status.

Judge it by which pages are affected. A stuck product or service page matters; a stuck tag archive or filtered URL usually does not.

Frequently asked questions

Is "discovered - currently not indexed" always bad?

No, a small number of URLs in this status is normal. Google says not being indexed is not necessarily an error, and that only your canonical pages need to be indexed. It becomes a problem when important pages stay stuck for weeks, or when the count keeps climbing. That usually points to a slow server or thin content.

How long until the page gets indexed?

There is no fixed time; it ranges from a few days to several weeks or longer. Google crawls on its own schedule, prioritizing pages it judges valuable and quick to fetch. You can speed things up by improving server speed and internal links, then requesting indexing for your most important URLs. The final timing is Google's to decide.

Will requesting indexing in Search Console fix it?

Sometimes, for a few important URLs, but it is not a bulk fix. Requesting indexing nudges Google to look at a page sooner. It does nothing about the underlying cause, so if a slow server or thin content is the reason, the URLs drift back into the status. Fix the cause first, then request indexing for priority pages.

Does this status mean my content is low quality?

Not necessarily, because "discovered" means Google has not even crawled the page yet. Low quality is more the story behind "crawled - currently not indexed," where Google fetched the page and passed. For "discovered," the likelier causes are a slow server and low crawl priority. Content still matters, but check speed and internal linking first.

How many pages in this status is normal?

There is no fixed number; it scales with site size. A large site will always have some URLs waiting in the queue, which is expected. What matters is the proportion of pages you care about. If your key pages index fine and only minor URLs wait, the site is healthy.

Get your important pages out of the queue

Storming Solutions runs SEO, AEO, and GEO for Malaysian businesses from Kuala Lumpur. Clearing indexing backlogs, usually by fixing server speed and internal linking, is standard work in our technical audits.

We would rather fix why Google is holding back than keep hitting request-indexing on pages that stall again.

Have important pages stuck in "discovered - currently not indexed"? Message us on WhatsApp or start with the SEO in Malaysia pillar. Our SEO, AEO, and GEO work gets your best pages crawled and indexed.