Discovered – Currently Not Indexed Means Google Rescheduled the Crawl

"Discovered – currently not indexed" reads like a judgement about your page. It's a note in Google's crawl schedule, and on a small site most of the standard fixes go after the wrong problem.

I've spent September watching this status on our own site, where new and rewritten URLs have sat in it or next to it, while Reddit's SEO forums filled up with the same complaint.

What Google says it means

Google's Page indexing report defines it in two 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. [1]

Google knows the URL exists but hasn't requested it. The status says nothing about the content, because Google hasn't seen the content yet. It's a different problem from "Crawled – currently not indexed", where Google fetched the page and decided against indexing it. We covered that one separately.

On a small site, it isn't crawl budget

The standard advice treats this status as a crawl budget problem. Google's crawl budget guide lists who the guide is for: sites with more than a million unique pages that change weekly, sites with more than 10,000 pages that change daily, and sites with a large share of URLs in this exact status [2].

A site with a few hundred pages is nowhere near the first two. The overload explanation in the definition doesn't fit either, since a small site isn't close to being overloaded by one extra request.

What the guide describes instead is demand. Google says crawl demand varies "based on a site's size, update frequency, page quality, and relevance, compared to other sites" [2]. On a small site, "Discovered – currently not indexed" usually means Google has decided the URL can wait. The fix is to give Google a reason to fetch it sooner, and a bigger crawl budget doesn't do that.

The status is less stable than it looks

On our site, one rewritten article showed "Discovered – currently not indexed" in URL Inspection on 14 September. Two days later the same URL showed "URL is unknown to Google", with no referring sitemap and no crawl date.

The article itself didn't change between those two readings. A site owner on r/TechSEO reported the same flip, and noted that the two inspection results listed different information about the sitemap [3].

Don't treat either label as a precise diagnosis. Both mean Googlebot hasn't fetched the page, and which one shows up on a given day tells you very little.

Resubmitting the sitemap doesn't fix it

Google's own sitemap documentation is blunt about this. Submitting a sitemap "is merely a hint: it doesn't guarantee that Google will download the sitemap or use the sitemap for crawling URLs on the site" [4].

We saw exactly that. As of 16 September, Search Console's Sitemaps report said Google had last downloaded our sitemap on 7 September. At that point the file listed 57 URLs. It now lists 71. Everything we published in the nine days in between was invisible to Google through the sitemap.

One page did get indexed in that window. An article we published on 11 September was crawled and indexed by the 13th, without the sitemap. That article appeared in our blog index, which Google recrawls often. Our new WiFi QR generator, published on the 15th, was still unknown to Google a day later. One day is too early to read anything into, but it's the comparison we're watching.

Requesting indexing doesn't fix it either

The most useful evidence here comes from server logs. The r/TechSEO poster checked theirs after a new URL went a week without a crawl [5]. Googlebot kept recrawling their existing pages, including pages that link to the new URL, within about 30 minutes of a request. It never requested the new URL itself.

The only fetches of the new page came from Google-InspectionTool, the agent behind Search Console's live test. Two weeks later, regular Googlebot still hadn't asked for the page [3].

A successful live test proves the page can be indexed. It doesn't queue the page for Googlebot, and repeating it won't either.

What does move it

Link to the URL from pages Googlebot already fetches often. Having internal links isn't enough on its own. They need to sit on pages Google recrawls frequently. URL Inspection shows the last crawl date for any indexed page, so check your home page and your main listing pages, and put the new link on the ones crawled most recently. In a mature-site case on r/bigseo, the most practical reply said the same thing: link from pages with real traffic and authority, rather than relying on hub pages that exist for navigation [6].

Keep the list of URLs Google knows about short and real. Google's guide calls this perceived inventory. If Google knows about many duplicate or unimportant URLs, it spends time on them [2]. Parameter variants, thin tag pages and old redirects all compete with your new page for attention.

Make sure the page earns a crawl when it gets one. Once Google fetches it, the question becomes whether it's worth indexing. A tool that works, or an article with information the search results lack, gives the next crawl a reason to happen.

Then wait a fixed amount of time, and write the date down. Two weeks is a reasonable line. If a page is still unknown after that, go back through the list above rather than repeating the same request.

September 2026 may be a Google-side slowdown

Some of this month's cases don't look like site problems. On the first r/TechSEO thread, other people replied that they were seeing the same thing. One said manual indexing requests that usually took hours had gone days without action. Another said pages had been getting indexed almost immediately until about a week earlier [5].

A slowdown in how Google handles new URLs would explain healthy sites, with clean logs and fast recrawls of existing pages, suddenly waiting weeks for a first crawl. It's a hypothesis. It's also a reason not to rebuild a site's architecture over one slow month.

While we waited on Google, Bing moved. Pages in Bing's index for our site went from 88 to 102 between 8 and 13 September. If Google is slow to discover a page, it's worth checking whether Bing has already found it. That at least confirms the page is reachable and linked.

A short checklist

1. Confirm the page returns 200, has a self-referencing canonical and isn't blocked, using URL Inspection's live test.
2. Check your server logs for Googlebot, not Google-InspectionTool.
3. Link the page from the pages Google recrawled most recently.
4. Remove or consolidate URLs you don't want crawled.
5. Wait two weeks from the date you did steps 3 and 4.
6. Don't resubmit the sitemap or repeat the indexing request in the meantime. Neither is likely to change the result.

If you want to confirm your sitemap only lists live, final URLs before any of this, our sitemap checker fetches every entry and reports anything that returns something other than 200.

Sources

1. Google Search Console Help, Page indexing report.
2. Google for Developers, Crawl Budget Management.
3. r/TechSEO, Update: New URLs still not crawled after more than two weeks, while existing pages are recrawled quickly, 14 September 2026.
4. Google Search Central, Build and submit a sitemap.
5. r/TechSEO, Googlebot has not crawled a new URL after 7 days despite sitemap and internal links, 6 September 2026.
6. r/bigseo, Old, well-established site with perfect internal linking/sitemap — new pages stuck in "Discovered - currently not indexed" for months, 21 August 2026.

First-party figures come from this site's Google Search Console URL Inspection and Sitemaps reports and Bing Webmaster Tools, pulled on 16 September 2026.