"Discovered - currently not indexed" means Google knows a URL exists but has not crawled it yet. Google says it rescheduled the crawl, often to avoid overloading the site. For a small site, the usual fixes are to link the page internally, keep it in your sitemap, improve server speed, and request indexing.
What does "Discovered - currently not indexed" mean?
It is a status in the Page indexing report in Google Search Console. Google's report documentation describes it as a page "found by Google, but not crawled yet." The crawl was rescheduled, which Google says typically happens because the crawl "was expected to overload the site." That is why the last crawl date for these URLs is blank.
This is a different status from crawled, currently not indexed. There, Google fetched the page and chose not to index it. Here, Google has not fetched it at all. The two have different causes, so do not apply the same fix.
Is it a problem?
Not always. A brand-new page can sit in this state for a short time. It becomes a problem when important URLs stay there for weeks, or when a large share of your pages are in it. A handful of low-value URLs, such as filtered or parameter pages, may be fine to leave.
Check first whether the URL deserves to be indexed. If it is a duplicate, a thin page or something you do not care about, the right move may be to leave it, consolidate it, or remove it.
Do you need to worry about crawl budget?
Usually not. Google's crawl budget guide is aimed at large sites with 1 million or more unique pages that change about weekly, or sites with 10,000 or more pages that change daily. It calls these numbers a rough estimate, not exact thresholds. It also says that if your pages tend to be crawled the same day they are published, you likely do not need the guide. It does list a large share of URLs in "discovered - currently not indexed" as a sign a site is in its audience. Our explainer on crawl budget covers who this applies to.
For a small site, a stuck page is more often a signal problem: Google found the URL but nothing suggests it is worth crawling soon.
How do you fix it?
Work down this list in order. Each step is cheap, and the earlier ones solve most small-site cases.
- Confirm the page is reachable. Open it in a private window. It should return a normal page with a 200 status, not an error or a redirect. Use the URL Inspection tool in Search Console to see what Google sees. If you are unsure how, see how to check if a page is indexed.
- Link to it from pages that matter. A page with no internal links is an orphan page. Add links from your home page, a category page or related posts, using descriptive anchor text. See our guide to internal linking.
- Put it in your sitemap. Google says it reads your sitemap regularly, so include everything you want crawled, with a
<lastmod>date for updated content. If you have not set one up, read how to submit a sitemap. - Speed up the server. Google recommends optimizing server response times and resources so pages load faster, and using HTTP caching with 304 responses. Slow responses are one reason it may hold back crawling.
- Request indexing. Google's documentation says you can reduce indexing lag by requesting indexing. Use the URL Inspection tool for a few key URLs. It is a request, not a guarantee, and it does not scale to thousands of pages.
What if hundreds of URLs are stuck?
Then the cause is usually the volume of low-value URLs. Google advises eliminating duplicate content so crawling focuses on unique content rather than unique URLs. For pages you cannot consolidate, it suggests blocking them with robots.txt, and it warns against using noindex for this purpose, because Google still has to request a page to see the tag. For help choosing between them, see robots.txt vs noindex.
Typical sources of URL bloat are filter and sort parameters, internal search results, tag archives and duplicate versions of the same page. Fix those at the source and the real pages tend to be crawled sooner.
How long should you wait?
Give a new page a couple of weeks after it is linked and in the sitemap. If it is still stuck after you have done the steps above, the problem is probably the page itself: ask whether it adds anything the pages already in the index do not. Google's guidance on helpful content asks whether a page offers original information or analysis and whether readers will leave feeling they learned enough, and a page that cannot say yes to those is a weak candidate for a quick crawl.
Frequently Asked Questions
Is "discovered - currently not indexed" the same as "crawled - currently not indexed"?
No. Discovered means Google has not fetched the page yet. Crawled means it fetched the page and decided not to index it.
Will requesting indexing fix it?
It can help for a few important URLs, but it is a request. If the page has no links and thin content, expect it to return to the same status.
Does it hurt the rest of my site?
Google does not say that stuck URLs lower the rankings of indexed pages. The cost is that the stuck pages cannot appear in search.
Should I delete pages in this status?
Only if they have no value. Merge or redirect duplicates, remove thin pages, and keep and strengthen the ones that matter.
How is this connected to the server?
Google says the crawl is often rescheduled because it was expected to overload the site, so a slow or fragile server can contribute. Faster responses help.