Discovered - currently not indexed: why Google has not crawled the page yet
Google knows the URL but has not crawled it yet, typically because more crawling might overload your site. Check server errors, speed, links and sitemap.
The message in Search Console
Discovered - currently not indexed
Page indexing report, group "Not indexed". Spelling as in Google's help page for the report.
By the Crawlerpeek editorial team · Sources checked · Updated · Editorial standards
What Google says
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.
Source: Google Search Console Help: Page indexing report, read 2026-10-30.
Common causes
- The server cannot take more crawling. Google's crawl capacity limit is about how much time your server spends holding connections open for Google, and Google slows down when it sees server errors (crawl budget guide).
- Low crawl demand. Google says crawl demand varies with a site's size, update frequency, page quality and relevance compared to other sites.
- Many low-value URLs compete for the same crawling, such as endless filter and parameter combinations. Google says soft 404 pages keep being crawled and waste crawl budget, and that long redirect chains have a negative effect on crawling.
- The site is new or the URLs are new, and few links point to them yet.
How to check
- Open the Crawl Stats report in Search Console to see Googlebot's crawling history for your site (troubleshooting crawling errors).
- If URL Inspection shows "Hostload exceeded", Google says that means Googlebot can't crawl as many URLs from your site as it discovered.
- Look in your access log for Googlebot requests that got a 5xx or 429, and confirm the IP addresses are Google's with verify a crawler IP; a user agent alone can be forged.
- Make sure the URLs you want are not blocked and the junk you do not want is: the sitemap robots.txt check tests every sitemap URL, and the robots.txt generator writes the rules. Google says blocking URLs with robots.txt prevents crawling them, while noindex pages are still requested.
- Keep your sitemap up to date and link new pages from pages that are already indexed.
When to fix it and when to leave it
On a small or new site a few URLs in this status usually need links and time more than technical work. Google's crawl budget guide is written for large sites (1 million+ unique pages changing about weekly, or 10,000+ changing daily) and for sites with a large share of URLs in this status; Google calls those numbers a rough estimate. Act when important pages stay here for weeks or the count keeps growing. Once Google has fetched a URL and still not indexed it, the status becomes Crawled - currently not indexed.
AI crawlers and AI search
Until Google crawls and indexes the page, it cannot be a supporting link in AI Overviews or AI Mode, which Google says requires an indexed page eligible for a snippet (AI features and your website). AI crawlers from other companies send their own requests to the same server, so a slow or overloaded server is worth fixing for all of them. Our bot traffic data shows which crawlers reach our own server.
Questions
How long does "Discovered - currently not indexed" last?
Google does not give a time. It says it rescheduled the crawl; how soon depends on your server's capacity and Google's crawl demand for the site.
Does submitting a sitemap fix it?
A current sitemap helps Google find the URLs, but this status means Google already knows them. Server health, internal links and fewer low-value URLs help Google get to them.
Should I return 429 or 503 to slow Google down?
Only for a short emergency. Google says to return 503 or 429 temporarily when the server is overloaded, warns that doing it for more than a few days can make Google permanently slow or stop crawling, and says not to use 401 or 403 to limit the crawl rate.
Related messages
- Crawled - currently not indexed · Google fetched the page but chose not to index it for now. No error is reported: check the page's text, duplicates and links, improve it, and give Google time.
- Server error (5xx) · Your server answered Googlebot with a 500-level status, so the page was not indexed. Find the failing requests in your logs, fix the cause, then validate.
- Soft 404 · The page returns 200 OK but looks like an error or empty page to Google. Send a real 404 or 410 if it is gone, a 301 if it moved, or fix what failed to load.
- Search Console Crawl and Indexing Errors
Sources
Google's documentation, each page read on 2026-10-30. Google updates these pages; if its wording has changed since, Google's page is the reference.
- Google Search Console Help: Page indexing report (checked 2026-10-30)
- Google Search Central: Crawl budget management for large sites (checked 2026-10-30)
- Google Search Central: Troubleshoot Google Search crawling errors (checked 2026-10-30)
- Google Search Console Help: URL Inspection tool (checked 2026-10-30)
- Google Search Central: How HTTP status codes and network errors affect Google Search (checked 2026-10-30)
- Google Search Central: AI features and your website (checked 2026-10-30)
Check the URL: robots.txt per bot, HTTP status, noindex and the HTML a crawler gets.Run the checker