Discovered - currently not indexed: what it means, and how long our pages waited

The short version

• It means found, not fetched. Google has the address but hasn’t downloaded the page, so it hasn’t read a word of it. It isn’t a verdict on what you wrote.
• On a new page, it is usually a queue. Our post of 4 October read this way on 7 October and was crawled on 10 October, six days after it went up.
• It can last weeks. Another of our posts waited 57 days for its first crawl.
• Check a few things once, ask once, then wait. The page loads, nothing tells Google to stay away, and another page links to it. Then press Request indexing one time.
• Watch the last crawl date, not the label. One of our pages changed its status four times between 7 and 13 October without Google crawling it once.

What "Discovered - currently not indexed" means

Google’s Page indexing report help defines it like this: "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."

Three things follow from that.

• Found means Google has the address, usually from your sitemap or from a link on another page.
• Not crawled means Google hasn’t downloaded the page. It can’t have judged what’s on it, because it hasn’t read it.
• Rescheduled is Google’s word, and the definition starts with "Typically". Overload is the usual reason Google gives, not the only possible one.

The report also has a Source column, which shows whether the source of each issue is Google or your website. Google’s help says that, in general, you can fix only the issues whose source is the website. It’s worth looking at which one your report shows for this status.

Our three pages, with dates

We check our own pages with Google’s URL Inspection API, which gives the same information as the URL Inspection tool in Search Console, and we log every reading with the date. Three of our blog posts have sat in Discovered - currently not indexed. All three load normally and are in our sitemap.

The jobs-market row is a selection: we checked that page every couple of days for weeks. Here is what we take from those dates.

• Six days is within what Google says. Its recrawl guidance says: "Crawling can take anywhere from a few days to a few weeks." Our hallucination post sits at the short end of that. The jobs-market post, at 57 days, is at the long end or beyond it.
• It wasn’t the whole site. Every other post we published between 3 and 10 October had been crawled by the third day after it went up. Google was visiting the site; it just hadn’t got to these two pages.
• The label moves on its own. The AI Mode post has gone from unknown to Discovered, back to unknown, back to Discovered and, on 13 October, back to unknown again, with no crawl in between. Google’s URL Inspection help says of "URL is unknown to Google": "This means that Google hasn't seen this URL before." That doesn’t sit easily with the same page having been reported as found before; on 9 October the gap was two and a half hours. So treat any one label as a single reading, not a verdict.
• The last crawl date is the honest number. Google’s API reference describes it as "Absent if the URL was never crawled successfully." Once a date appears, Google has been, and the date only moves forwards after that.
• We don’t know why these pages waited. Google’s explanation is overload. Our site is small, about 135 pages, and posts published either side of these two were crawled within days, so overload doesn’t obviously fit. But we can’t see Google’s side, and we aren’t going to make up a reason.

What to check while you wait

None of this needs a developer. Check each one once.

• The page loads. Open it in a private browser window. An error, a login screen or a blank page is the first thing to fix. In Search Console, the URL Inspection tool’s live test checks the same thing from Google’s side.
• Nothing tells Google to stay away. URL Inspection’s live test shows this as two answers, "Crawl allowed?" and "Indexing allowed?". A "No" to the first points to a rule in your robots.txt file, and a "No" to the second to a noindex tag on the page. Both are on your own site, so both are yours to fix.
• It’s in your sitemap, and another page links to it. Google’s recrawl guidance calls a sitemap "an important way for Google to discover URLs on your site". A link from a related page on your own site helps people and Google find it. Neither is a guarantee: our jobs-market post was in the sitemap and on our blog index for 57 days before Google crawled it.
• Your hosting isn’t struggling or blocking Google. Google’s explanation of this status is overload, so this is where to look if many pages are stuck. In its section on server errors, the Page indexing help says: "Make sure your site's hosting server is not down, overloaded, or misconfigured." It also warns that firewalls and protection systems can block Google by mistake, "because Googlebot often makes more requests than a human user, it can trigger these protection systems".

Then press Request indexing, once. In Search Console, inspect the page’s address and click Request indexing. The Page indexing help says: "When you add new content, it can take a few days for Google to index it. You can reduce the indexing lag by requesting indexing." The recrawl guidance adds: "Keep in mind that 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." Our dates aren’t a test of the button, so we can’t tell you how much it helps.

Validation passed, but the page still isn’t indexed?

If you clicked Validate fix in the report, it helps to know what Google is checking. Its help says an issue is marked as fixed for a URL "When the URL is crawled and the issue is no longer found on the page". It also says: "Validation typically takes up to about two weeks, but in some cases can take much longer". And you don’t have to start one at all: "Even if you never click Start validation Google can detect fixed instances of an issue."

For a page that is only waiting to be crawled, there may be nothing on your side to fix, so the last crawl date in URL Inspection tells you more than the validation status. We haven’t run a validation ourselves, so this part is Google’s description only.

Crawled - currently not indexed is a different problem

The sibling status sounds similar and isn’t. Google’s definition: "The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling."

Here Google has read the page and, for now, hasn’t indexed it. Asking for another crawl doesn’t change what it read, and Google says there is no need. It happened to one of our posts in August: it was in search results for twelve days and then dropped out. We wrote that up in our post on when Google looks at a page again. Google crawled it again on 9 September, and it read "Submitted and indexed" on 11 September. We had added a link to it from a new post on 8 September, so we can’t tell you whether that helped or Google changed its mind on its own.

What argues the other way

• Most of the time, it sorts itself out. Our hallucination post was crawled six days after it went up. Don’t rebuild a site over a page that has been waiting a week.
• Three pages on one small site isn’t a survey. It’s what happened to us, with dates. A large site, or one with thousands of similar pages, may behave differently.
• Google’s explanation may be right even for us. We can’t see what Google counts as overload, or how it decides what to crawl first.
• A single reading proves little. The status can change with nothing happening, so look more than once before you act on it.

Sources, and what we checked

• Google Search Console Help: Page indexing report, for the definitions of Discovered and Crawled - currently not indexed, the Source column, validation and the server-error advice; and URL Inspection tool, for "URL is unknown to Google", "Crawl allowed?", "Indexing allowed?" and Request indexing. Both read on 11 and 13 October 2026.
• Google Search Central: Ask Google to recrawl your URLs (last updated 10 December 2025), for the crawl timescale, the sitemap line and the repeat-request note.
• Google Search Console API reference: UrlInspectionResult, for the definition of the last crawl time.
• Our own readings: Google’s URL Inspection API for lolasquared.com, run by us between 3 September and 13 October 2026 and logged with dates. Times are UTC.
• Every quotation above was tested automatically against the text of its source before publication.