Quick answer: “Discovered – currently not indexed” means Google knows the URL exists but has not crawled it yet. Google says this often happens when it expected crawling to overload the site and rescheduled it. Common causes are weak internal linking, a large number of low-value URLs, slow or unstable servers and new sites with little authority. Fix it by linking important pages from strong pages, reducing low-value URLs, improving server speed and making sure the pages are worth indexing.
This status is often confused with “Crawled – currently not indexed”. The difference matters. With “crawled”, Google looked at the page and chose not to index it. With “discovered”, Google has not looked at it at all yet.
What Google says
The Page indexing report documentation explains that the page was found but not crawled yet. Typically, Google wanted to crawl the URL but expected it to overload the site, so it rescheduled the crawl. That is why the last crawl date in the report is empty for these URLs.
Crawled vs discovered
| Discovered, not indexed | Crawled, not indexed | |
|---|---|---|
| Has Google fetched the page? | No | Yes |
| Usual cause | Crawl priority, capacity, internal linking | Quality, duplication, relevance |
| Main fix | Make the page easier and more worth crawling | Make the page more worth indexing |
For the second status, see my guide to crawled, currently not indexed.
Common causes
Weak internal linking
URLs only found in a sitemap, or linked from deep, rarely crawled pages, get low priority. This is the cause I see most on small sites.
Too many low-value URLs
Filter combinations, parameters, tag archives and auto-generated pages can create far more URLs than Google wants to crawl. Important pages wait in the same queue.
Server capacity
Slow responses or frequent server errors make Google crawl less. The Crawl stats report in Search Console shows response times and errors.
A new or small site
New sites with few links get crawled less often. Patience and a few quality links help.
Large numbers of similar pages
If Google has crawled a sample of a template and found it low value, it may deprioritize the rest. Thin city pages and near-duplicate products often end up here.
How to fix it
- Check that the pages deserve indexing. If they are thin, improve or consolidate them first.
- Link to them from strong pages such as the homepage, main navigation, category pages and popular posts. See internal linking.
- Reduce crawl waste by noindexing, canonicalizing or blocking low-value URL patterns.
- Improve server response with better hosting, caching and fewer errors.
- Keep the sitemap clean, listing only indexable, canonical URLs. See XML sitemaps.
- Request indexing for a few key URLs with URL Inspection after fixing the above.
When not to worry
- The URLs are parameter variations, feeds or pages you do not need indexed.
- The numbers are small and the pages are new.
- Your important pages are indexed and performing.
The report is a list of URLs Google found, not a list of failures. Focus on whether the pages that matter are indexed.
On large sites
For sites with many thousands of pages, this status is often a crawl budget issue. Google’s guide to managing crawl budget explains how capacity and demand interact.
If a large share of your important pages sits in this status, a technical SEO review can find whether the cause is structure, server capacity or content quality.
Frequently asked questions
How long do pages stay in “Discovered – currently not indexed”?
It varies from days to months. Better linking and fewer low-value URLs usually speed it up.
Will requesting indexing fix it?
It can help for a few pages. It does not fix the underlying cause for many.
Does a sitemap guarantee crawling?
No. Sitemaps help discovery, but Google still decides when to crawl.
Is this status a penalty?
No. It is a crawl scheduling status.
Sources: Search Console Help: Page indexing report; Google Search Central: Large site owner’s guide to managing your crawl budget.




