"Discovered – Currently Not Indexed": Why Google Hasn't Crawled Your Pages Yet

"Discovered – currently not indexed" means Google knows the URL exists but has not crawled it yet. Google's own explanation is that crawling was expected to overload your site, so it rescheduled. On a small site this is usually about priority and server response, not a crawl budget you have used up, and it often clears as the site earns trust. Here is what the status means, what to check first, and what is a waste of time.

Published: 2026-10-16 · 6 min read · Satelo

What Google says the status means

Google's Page indexing report documentation defines it in two sentences: "The page was found by Google, but not crawled yet." And: "Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl."

Three points follow:

• Discovery worked. Google found the URL through a sitemap, an internal link or an external link.
• Nothing has been judged yet. Google has not fetched the page, so it cannot have rejected the content. That is the key difference from "Crawled – currently not indexed".
• It is not a penalty. The same help page reminds site owners: "Don't expect every URL on your site to be indexed."

Discovered vs. Crawled – currently not indexed

If your problem is the second column, our guide to Crawled – currently not indexed covers that diagnosis in detail.

Is it crawl budget? Usually not on a small site

"You have run out of crawl budget" is the most common answer on forums, and for most small sites it is the wrong one. Google's crawl budget guide says it is written for "large sites (1 million+ unique pages)" with content that changes weekly, or "medium or larger sites (10,000+ unique pages)" with content that changes daily. Google calls those figures "a rough estimate". It also lists sites with "a large portion of their total URLs classified by Search Console as Discovered - currently not indexed" among the audience, so a big share of this status is worth reading about even on a mid-sized site.

The guide is still useful for the two ideas it defines:

• Crawl capacity limit: how much Google will crawl without straining your server. If the site responds quickly for a while, the limit goes up; if it slows down or returns server errors, "the limit goes down and Google crawls less."
• Crawl demand: how much Google wants to crawl your site, based on size, update frequency, and page quality and relevance compared with other sites.

On a 50-page blog, capacity is rarely the bottleneck unless the hosting is genuinely slow. Demand is: a new or little-known site simply is not high on Google's list yet.

Check 1: server speed and errors

Because Google's definition names server load, start here. It takes ten minutes.

1. Open Settings → Crawl stats in Search Console. Look at average response time and any spikes in server errors or timeouts.
2. Run a few affected URLs through URL Inspection → Test live URL. Failures or very slow fetches are a signal.
3. Check your host's resource limits. Cheap shared plans sometimes throttle bursts of requests, which is exactly what a crawler produces.
4. Make sure the URLs return a plain 200 without long redirect chains.

Our guide to Core Web Vitals for small sites covers the speed basics that also help crawlers.

Check 2: internal links and sitemap

A URL known only from a sitemap is a weak candidate for crawling. A URL linked from your homepage and several related posts tells Google it matters.

• Link new posts from somewhere crawled often: the homepage, a hub page or a category page near the top of your navigation.
• Add contextual links from two or three related articles that are already indexed.
• Keep the sitemap clean. Google's sitemap documentation says Google ignores <priority> and <changefreq> and uses <lastmod> only if it is "consistently and verifiably" accurate. List only canonical, indexable URLs with honest dates.
• Remember a sitemap is a hint, not an order. The same page notes that submitting one does not guarantee Google will use it.

Check 3: how many URLs you are asking Google to crawl

Small sites can still generate a lot of URLs: tag archives, filters, search pages, parameter variants, auto-generated profiles. Every one of them competes for the same limited attention.

• Noindex or remove thin archives you would not want as a search result.
• Stop linking to internal search results and endless filter combinations.
• Consolidate near-duplicate pages into one stronger page.

Fewer, better URLs make it easier for Google to get to the ones you care about.

Check 4: external signals

Crawl demand rises when a site is referenced elsewhere. For a new site that means honest visibility: being mentioned in relevant communities, getting featured by related blogs, listing on directories your audience actually uses. Our guide to link building for new websites covers safe ways to start. This is the slowest lever and the one you control least, so do it alongside the technical checks, not instead of them.

What to do, and what not to do

The quote above is from Google's recrawl documentation, which also notes a quota on individual URL submissions and recommends a sitemap when you have many URLs.

About "Validate fix"

You can click Validate fix on the issue in the Page indexing report. Google says validation "typically takes up to about two weeks, but in some cases can take much longer." It is marked Passed when "all known instances of the issue are gone (or the affected URL is no longer available)" and Failed when "a certain threshold of pages still contain this issue." A pass means Google has now crawled those URLs; it does not promise they will all be indexed. A failed validation on a young site often just means Google has not got to everything yet.

Our own numbers: satelo.io

Satelo launched in early October 2026. On October 16, 2026, our Search Console Pages report showed 97 pages indexed and 137 not indexed. Of those 137, 23 were "Discovered – currently not indexed". Most of the rest, 111, were pages we had deliberately marked noindex.

Between our internal audit on October 9 (2 pages indexed) and October 16, we submitted a sitemap, linked the blog from the homepage, fixed a wrong canonical, noindexed thin bulk pages and requested indexing for a handful of key URLs. We cannot tell you which of those steps mattered; Google's help page also says it "can take a week or so" to start crawling a new site. The full timeline is in our Crawled – currently not indexed case. The point here is simpler: 23 discovered URLs on a two-week-old site is normal, and we are treating it as a priority question, not a technical emergency.

What to do next

1. Open Crawl stats and rule out slow responses and server errors.
2. Pick your five most important discovered URLs and link each from the homepage or a hub page plus two related posts.
3. Remove thin URLs from the sitemap and navigation.
4. Request indexing once for those five, then wait two to three weeks before judging.

Want to see how your site looks from the outside? The free Quality Score check shows page speed, domain age, Common Crawl coverage and other open signals, with the evidence behind each number, in about 30 seconds. If your problem is visibility rather than speed, Satelo's article exchange can get your site written about on related blogs, with labeled, rel="sponsored" links.

FAQ

What does "Discovered – currently not indexed" mean?

Google found the URL but has not crawled it yet. Google says it typically rescheduled the crawl because crawling was expected to overload the site.

How do I fix Discovered – currently not indexed?

Check server response times and errors, link the pages from your homepage and related posts, keep the sitemap clean, trim thin URLs and request indexing once for key pages.

How long does Discovered – currently not indexed last?

There is no fixed time. Google says new sites can take a week or so to start being crawled, and validation of a fix typically takes up to about two weeks.

Is it a crawl budget problem?

Rarely on small sites. Google's crawl budget guide targets sites with roughly 10,000 to over a million pages, though it also mentions sites with many discovered but uncrawled URLs.

What does "validation passed" mean for this issue?

Google says validation passes when all known instances of the issue are gone or the URLs are no longer available. It means the pages were crawled, not that every one was indexed.

Should I keep clicking Request indexing?

No. Google says requesting a recrawl multiple times for the same URL won't get it crawled any faster, and there is a quota for individual URLs.

Read next

"Crawled – Currently Not Indexed": What It Means and What We Did on a New SiteWhat "Crawled – currently not indexed" means in Google Search Console, how to diagnose it step by step, and the real indexing timeline of our new site.

How Long Does It Take a New Website to Rank? Sandbox, Data and a Real TimelineHow long a new website takes to rank on Google: what Ahrefs data shows, what Google says about the sandbox, a realistic timeline and what to do while you wait.

How to Speed Up Indexing in Yandex (and Bing) with IndexNowHow to speed up indexing in Yandex and Bing: set up IndexNow on WordPress or a static site, use Yandex page recrawl, fix sitemaps and link new pages properly.

Anchor text for SEO: types, official rules, and how to pick itAnchor text SEO without myths: anchor types, what Google and Yandex actually say, why exact-match anchors look like link schemes, and how to check your own.