Blog

Discovered - Currently Not Indexed: Why Google Waits and How to Fix It

Google found the URL but has not crawled it. Read crawl health in Search Console, cut wasted URLs, and get queued pages crawled.

TL;DR: "Discovered - currently not indexed" is a Google Search Console status meaning 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 the crawl was rescheduled. Fix it by making your server fast and error free for Googlebot, cutting the low value URLs that compete for crawls, and linking important pages from pages Google already crawls.

Discovered currently not indexed is the status for a URL that Google has found, through a link or a sitemap, but has not fetched. Google's Page indexing report documentation defines it this way: "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; therefore Google rescheduled the crawl. This is why the last crawl date is empty on the report." Because Google has never seen the content, content quality cannot be the direct reason. The status is about crawl scheduling: how much Google is willing and able to crawl on your site, and how much it wants this particular URL.

What does "Discovered - currently not indexed" mean in Google Search Console?

It means the URL is in Google's crawl queue but has not reached the front of it. In Search Console you see it under Indexing > Pages, in the "Why pages aren't indexed" table, with source Google systems. Inspect one of the URLs with the URL Inspection tool and the "Last crawl" field reads N/A.

How it differs from the related statuses:

• Crawled - currently not indexed: Google fetched the page and then chose not to index it. That is a judgment on the page. See our guide to crawled currently not indexed.
• Discovered - currently not indexed: Google has not fetched the page. That is a crawl capacity or crawl demand problem.
• URL is unknown to Google: Google has not found the URL at all. That is a discovery problem: no links, no sitemap entry.

For a brand new site or page, a few days in this status is normal. Google says a new page or site can take "a week or so" to be crawled and indexed.

Why does Google discover a page but not crawl it?

Google's crawl budget guide explains the two inputs that decide how much of your site is crawled:

• Crawl capacity limit. How many parallel connections Googlebot uses and how long it waits between fetches. Every site starts with the same conservative limit. It rises when the site responds quickly and consistently, and falls when "the site slows down", or "responds with server errors (5xx HTTP status codes) or rate-limiting signals (such as HTTP 429)".
• Crawl demand. How much Google wants to crawl your URLs, based on perceived inventory, popularity, and staleness. Duplicate and low value URLs dilute it.

Google states that its crawl budget guide is aimed at sites with 1 million or more pages that change weekly, sites with 10,000 or more pages that change daily, and "sites with a large portion of their total URLs classified by Search Console as Discovered - currently not indexed". That last group is the one this status belongs to, at any size.

In practice the usual causes are:

1. A slow or overloaded server. Long response times or 5xx errors make Google back off. Shared hosting, cold serverless starts and heavy uncached pages are common culprits.
2. Too many URLs for the site's crawl demand. Faceted navigation, calendar pages, session IDs, sort parameters and infinite pagination can produce many times more URLs than real pages.
3. Publishing in large batches. Thousands of new programmatic or product URLs released at once on a site Google crawls lightly.
4. Weak internal linking. URLs found only in a sitemap, with no links from crawled pages, get low priority.
5. A site that Google does not value much yet. New domains and sites with mostly thin content get less crawl demand overall.

How do you check your site's crawl health?

Open the Crawl Stats report: in Search Console go to Settings > Crawl stats. The Crawl Stats report help lists what to read:

• Host status. Should be green. If it is red, open the details for robots.txt availability, DNS resolution and host connectivity failures.
• Average response time. Each resource counts as a separate response. A rising line here usually comes before a drop in total crawl requests.
• By response. A visible share of 5xx, 429 or timeouts is the clearest reason Google reschedules crawls.
• By purpose. "Discovery" is crawls of new URLs, "Refresh" is recrawls of known ones. If discovery is a tiny share while you publish lots of new pages, new URLs are waiting in the queue.

Our free URL health checker gives a quick read on status code, redirects and response time for any URL.

How do you get the queued pages crawled?

Work from the server outwards. Each step either raises the crawl capacity limit or increases demand for the URLs that matter.

Make the server fast and reliable for Googlebot

Get typical server response time down and keep 5xx and 429 responses near zero. Cache HTML at the edge, warm serverless functions, and do not rate limit verified Googlebot. Support conditional requests: Google's guide recommends returning 304 Not Modified for unchanged pages, which saves crawls for new ones.

Cut the URLs that waste crawls

• Return 404 or 410 for removed pages. Google calls a 404 "a strong signal not to crawl that URL again".
• Fix soft 404s, which Google says "will continue to be crawled, and waste your budget".
• Block faceted and parameter URLs you never want crawled in robots.txt. Google advises against using noindex for this, because Google "will still request, but then drop the page", which still costs a crawl.
• Remove long redirect chains, which Google says have "a negative effect on crawling".

Our robots.txt checker shows which paths a given rule blocks before you deploy it.

Link to the waiting pages from pages Google already crawls

Add links from the homepage, category hubs, and recent posts to the URLs stuck in the queue. A link from a page Google recrawls daily is the cheapest way to raise demand for a new URL.

Keep sitemaps clean and accurate

List only canonical URLs that return 200. Keep <lastmod> honest: Google's sitemap documentation says it uses lastmod only when it is "consistently and verifiably" accurate and ignores <priority> and <changefreq>. Split large sitemaps by section so you can filter the Page indexing report per sitemap; each file can hold up to 50,000 URLs or 50MB uncompressed. Our sitemap validator checks every URL inside a sitemap.

Release large batches gradually

If you generate thousands of pages at once, publish them in waves over days or weeks and link each wave from crawled hubs. This matches the crawl capacity Google has assigned rather than asking for a jump.

Request indexing for a few key pages

For your most important URLs, use "Request indexing" in the URL Inspection tool. Google's recrawl documentation notes a quota per property and says repeated requests for the same URL do not speed it up. It is a nudge for a handful of pages, not a fix for thousands.

How long does a URL stay in this state?

There is no fixed duration. Google says crawling "can take anywhere from a few days to a few weeks". After server and URL hygiene fixes, watch the Crawl Stats report: total crawl requests should rise and the Discovery share should grow within a few weeks. If URLs stay discovered for months while crawl health is green, crawl demand is the limit, and internal links plus fewer low value URLs matter more than anything else.

What about Bing, ChatGPT search and other crawlers?

Google's queue is only one queue. Bing, which ChatGPT search draws on, and Yandex, Naver, Seznam and Yep accept IndexNow notifications of up to 10,000 URLs per request, so new pages can be crawled there without waiting for Googlebot. Read what IndexNow can and cannot do first: Google does not participate.

IndexLinks sends each new or updated page on your own site to those engines, to your Search Console, and to the AI crawlers, and records a receipt for every verified crawl within 24 hours. It guarantees the crawl, not indexing. To spot the signals that keep pages out of the index, run the free site check on the IndexLinks homepage.

FAQ

Is "Discovered - currently not indexed" a penalty? No. It is a scheduling state. Google has not looked at the content yet.

Should I use the Google Indexing API to get these pages crawled? No. Google limits the Indexing API to pages with JobPosting or BroadcastEvent structured data, and spam policies apply to what you submit. See our guide to the Google Indexing API.

Will backlinks fix it? External links can raise crawl demand for a URL, but server health and internal links are faster and fully in your control.

Does deleting and republishing the page help? Changing the URL creates a new URL that enters the same queue. It can also leave a 404 or redirect behind. Fix the queue, not the URL.

Can a small site have this status? Yes. On small sites it most often points to a slow host, URLs found only through the sitemap, or a new domain with little crawl demand.

Use this information as a starting point, then verify the page-level evidence available to you.