Discovered - Currently Not Indexed: What It Means

Discovered - currently not indexed means Google knows your page exists and has not read it yet. It is a position in a queue, not a verdict on your writing, and Google's own definition is explicit that the crawl was rescheduled rather than refused.

The reason Google gives for that rescheduling is where most advice goes wrong. The documentation blames server load, which is a plausible story for a site with a million URLs and an implausible one for a blog with forty. Below is what the documentation actually says, word for word, what part of it applies to a small site, and what the same status looks like on our own domain today.

TL;DR

Google's definition: "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."
Nothing has been read, so nothing has been judged. Rewriting a page at this stage changes a document nobody has opened.
Google's crawl budget guide tells small sites to stop reading it: "If your site doesn't have a large number of pages that change rapidly, or if your pages seem to be crawled the same day that they are published, you don't need to read this guide."
What is left is demand, not capacity: "For Googlebot, demand varies based on a site's size, update frequency, page quality, and relevance, compared to other sites."
Asking again does not help. Google states there is "a quota for submitting individual URLs and requesting a recrawl multiple times for the same URL won't get it crawled any faster".
On our own domain on 16 September 2026, 36 of the 42 URLs in our sitemap are indexed. The oldest straggler has been waiting since 24 July.

Discovered, currently not indexed: what Google's definition says
The three states people mix up
Why the official explanation rarely fits a small site
Crawl budget: the part that applies to you
Demand is the lever, and it is not a setting
What Google says you can actually do
What does not work
What this looks like on our own domain
What to do while the queue moves
FAQ
Where this leaves you

Discovered, currently not indexed: what Google's definition says

The Search Console help page defines the status in three sentences: "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."

Read each clause separately, because each one closes a question.

Found. Discovery worked. Your sitemap or a link did its job, so the URL is in Google's list. Whatever else is wrong, it is not that Google cannot see the page.

Not crawled yet. No robot has opened the file. No paragraph has been read, no title evaluated, no comparison made with the pages already ranking for your subject.

The last crawl date is empty. That is how you confirm you are reading the right status rather than guessing. In the URL Inspection tool, an empty crawl date and this label together mean the page is waiting, not failing.

The practical consequence is the one people find hardest to accept: at this stage your content has not been judged. Improving it is still a good idea, and it will change nothing about the queue today, because the version Google has read is no version at all.

The three states people mix up

Three different messages get treated as one problem. They are not, and the difference tells you what has actually happened.

What Search Console says	What has happened	What has been judged
URL is unknown to Google	"Google hasn't seen this URL before"	Nothing. The page is not even in the list
Discovered - currently not indexed	Google has the address, the crawl was rescheduled	Nothing. No content has been read
Crawled - currently not indexed	"The page was crawled by Google but not indexed"	The content. It was read and not kept, for now

Only the third one is feedback about your page. Google adds, for that case, that it "may or may not be indexed in the future; no need to resubmit this URL for crawling". If you are trying to read every early signal a young site produces, we went through the full ladder in signs SEO is working before the first clicks.

Why the official explanation rarely fits a small site

The stated cause is load: the crawl "was expected to overload the site". That sentence was written for the sites Google worries about, the ones with millions of URLs and servers that genuinely buckle.

Two things in the same documentation suggest a small site is in a different situation. Google describes the capacity side as deliberately cautious for everyone: "Every site starts with the same default, conservative crawl capacity limit. If there is demand to crawl more and the site remains healthy, Google's systems will automatically adjust this limit over time." And the crawl budget guide opens by sending most site owners away: "If your site doesn't have a large number of pages that change rapidly, or if your pages seem to be crawled the same day that they are published, you don't need to read this guide."

So if your forty pages are static files on a CDN, hunting for a server problem is unlikely to be the answer. The queue you are in is explained better by the other half of the budget.

Crawl budget: the part that applies to you

Google's guide, last updated on 22 July 2026, names the sites it is written for:

"Large sites (1 million+ unique pages) with content that changes moderately often (once a week)"
"Medium or larger sites (10,000+ unique pages) with very rapidly changing content (daily)"
"Sites with a large portion of their total URLs classified by Search Console as Discovered - currently not indexed"

It then adds a caveat worth keeping: "The numbers given here are a rough estimate to help you classify your site. These are not exact thresholds."

Notice the third bullet. Google itself treats a pile of pages stuck at this status as a signal worth investigating, even on a site far below the size thresholds. One page waiting is normal. Half your library waiting is information.

Two more lines from the same page matter for small publishers. For Google Search specifically, "keeping your sitemap up to date and checking the Page Indexing report regularly is adequate", which is the whole technical checklist for most sites. And "Google's crawling infrastructure defines a site as a unique hostname", so a blog on a subdomain does not inherit the history of your main domain, it builds its own.

Demand is the lever, and it is not a setting

Google summarises the budget as two forces: "Google defines a site's crawl budget as the set of URLs that Google can and wants to crawl. Even if the crawl capacity limit isn't reached, if crawl demand is low, Google will crawl your site less."

Capacity is what your server can take. Demand is whether Google wants to come back. For a small site the first is rarely binding, so the second is the whole story. The documentation is unusually direct about what drives it: "For Googlebot, demand varies based on a site's size, update frequency, page quality, and relevance, compared to other sites."

Two of the named factors are worth sitting with. "Popularity: URLs that are more popular on the Internet tend to be crawled more often to keep them fresher in our systems." And staleness: "Our systems want to recrawl documents frequently enough to pick up any changes."

None of that is a button. It is the slow business of being worth returning to, which is also why cadence alone does not buy attention, a point we argued in how often to publish without a team.

What Google says you can actually do

The documentation on asking for a recrawl, last updated on 10 December 2025, lists exactly two methods: the URL Inspection tool for a few URLs, and a sitemap for many. That is the full official surface. Everything else circulating on the subject is somebody's theory.

Both come with stated limits. On timing: "Crawling can take anywhere from a few days to a few weeks." On outcome: "Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all." On priority: "Our systems prioritize the fast inclusion of high quality, useful content." And on repetition: "there's a quota for submitting individual URLs and requesting a recrawl multiple times for the same URL won't get it crawled any faster".

The Search Console help is equally plain about the baseline: "It can take a week or so for Google to start crawling and indexing a new page or site", and "Indexing is never instant, even when you submit a crawl request directly".

Join the waitlist

What does not work

Rewriting the page. At Discovered, nothing has been read. Editing changes a draft only you have seen. Keep the rewrite for a page stuck at Crawled - currently not indexed, where the content genuinely was the thing that got judged.

Asking again, then again. Google says the repeated request does not speed anything up, and the quota is real.

Publishing more to feed the robot. Nothing in the crawl documentation supports volume as an accelerant, and demand is described as relative to other sites, not to your own output. On our domain, publishing a pair every few days grew the queue rather than emptying it.

Reading a delay as a penalty. The word Google uses is "rescheduled". A penalty would say something else, and would show up elsewhere in Search Console.

What this looks like on our own domain

We run this blog on a domain that went live in July 2026, and we publish a French and English pair every few days, so we are a fair test case for the impatient founder. Here is the Search Console reading for distrify.ai on 16 September 2026.

Of the 42 URLs in our sitemap, 36 are indexed and 6 are not. Three sit at Discovered - currently not indexed, published 4, 8 and 16 days ago. Three are still "URL is unknown to Google", which Google defines as "Google hasn't seen this URL before", and one of those three has been online since 24 July 2026, which is 54 days. Four of the six are French.

The useful part is what it rules out. Same sitemap, same template, same hosting, same internal linking pattern, same day of publication for the pairs. Whatever separates the 36 from the 6 is not a setting we forgot to switch on. Crawl dates across the site run from 25 July to 15 September, so Googlebot does come back regularly. It is selective rather than absent.

We cannot tell you why those six and not six others, and nobody honestly can. What we can tell you is that the delay is normal enough to be boring, that it is uneven within a single site, and that language matters more than a template does. If you publish in several languages, one page per market has consequences on the indexing side too.

What to do while the queue moves

A page waiting for Googlebot is invisible in one channel and perfectly readable in every other one. That is the part worth acting on, because you control it today.

Send the page where there is no queue. Your newsletter, your social accounts, the communities where the question gets asked. We wrote the full list in what to do after publishing a blog post, and the strategy behind it in our content distribution strategy.

Check that the assistants can read you, because their crawlers are separate from Googlebot and follow their own rules, which we sorted in blocking AI crawlers and what it costs you. A page Google has not crawled can still be fetched by an assistant answering a question right now, which is one more reason to understand how brands get mentioned in ChatGPT and where buyers actually search.

Then keep writing pages worth returning to. That is the only input to demand you actually own, and it is the thread running through our complete guide to generative engine optimization.

FAQ

Is Discovered - currently not indexed a penalty? No. Google's definition says the crawl was "rescheduled" because it "was expected to overload the site". It describes a queue, not a sanction, and no content has been evaluated at that point.

How long should I wait? Google gives two ranges: "It can take a week or so for Google to start crawling and indexing a new page or site", and after a request, "Crawling can take anywhere from a few days to a few weeks". On our own domain one page has waited 54 days, so treat several weeks as unremarkable on a young site.

Should I request indexing again? Once is reasonable. Beyond that, Google states plainly that "requesting a recrawl multiple times for the same URL won't get it crawled any faster", and that a quota applies.

Should I rewrite the page? Not for this status. Nothing has been read yet. Rewriting is the right response to Crawled - currently not indexed, where Google says the page "was crawled by Google but not indexed" and "may or may not be indexed in the future".

Will every page get indexed eventually? No, and Google says so twice: "Google doesn't guarantee that all pages everywhere will make it into the Google index", and "Don't expect every URL on your site to be indexed."

Does being indexed mean I will get traffic? No. In the URL Inspection tool, "URL is on Google means that the URL is eligible to appear in Search results, but is not guaranteed to be there." Indexing is a filing decision, not a ranking.

Where this leaves you

Discovered - currently not indexed is the least actionable message in Search Console, and that is the honest answer rather than a disappointing one. The page is in a queue whose order depends on how much Google wants to come back to your site, which is built over months and not toggled in an afternoon.

So do the two things that survive the wait. Keep the sitemap clean and check the report, which the documentation calls adequate for a site your size. And stop treating Google as the only door: publish, then distribute, so a page in the queue is already working somewhere else.