You publish a page, submit your sitemap, and a few weeks later Search Console files it under a frustrating label: "Discovered – currently not indexed". Google knows the URL exists. It just has not bothered to fetch it.
A handful of URLs in this bucket is normal on any site. Thousands of them, especially important product or article pages, usually point to a deeper problem: a server Google is cautious about, a site that generates far more URLs than it deserves, or pages that look too unimportant to prioritise.
This guide explains exactly what the status means, how it differs from "Crawled – currently not indexed", the most common causes, and a step-by-step process to get the pages that matter crawled and indexed.
Key Takeaways
- "Discovered – currently not indexed" means Google found the URL but has not crawled it yet.
- Google says it typically wanted to crawl but expected doing so to overload the site, so it rescheduled.
- Common causes are slow or erroring servers, too many low-value URLs competing for crawling, and weak internal linking.
- Fix it by improving server capacity, cutting URL waste, strengthening internal links and keeping sitemaps clean.
- Requesting indexing helps for a few key URLs but does not fix a site-wide pattern.
What the Status Means
The status appears in the Page indexing report under "Why pages aren't indexed". Google's own definition is short:
“The page was found by Google, but not crawled yet.”
— Search Console Help, Page indexing report
Google's help page adds that, typically, Google wanted to crawl the URL but this was expected to overload the site, so the crawl was rescheduled. That is why the "last crawled" date in the URL Inspection tool is usually empty for these URLs. It also explains why Google's crawl budget documentation names this status as a sign that a site may benefit from crawl budget work.
Discovered vs Crawled – Currently Not Indexed
These two statuses sound similar but point to different problems.
| Discovered – currently not indexed | Crawled – currently not indexed | |
|---|---|---|
| Has Google fetched the page? | No | Yes |
| Main question | Why is Google not crawling it? | Why did Google decide not to index it? |
| Typical causes | Server capacity, crawl prioritisation, URL waste, weak linking | Quality, duplication, thin content, low value |
| First place to look | Server performance, Crawl Stats, internal links | Content quality and duplication |
| Our guide | This post | Crawled – currently not indexed |
Common Causes
- Server capacity. If your server slows down or returns errors, Google lowers its crawl rate. Google documents that 5xx server errors and 429 responses cause its crawlers to slow down.
- Too many URLs. Faceted navigation, parameters, tag archives and other auto-generated pages compete with your important URLs for crawling. This is the classic index bloat pattern.
- Weak internal linking. Pages linked only from a sitemap or from deep pagination look unimportant. See our internal linking guide.
- Large volumes of new pages at once. Programmatic launches of thousands of similar pages are often discovered faster than Google chooses to crawl them.
- Perceived low value. If similar pages on the site have previously been crawled and not indexed, Google may deprioritise URLs that look the same.
How to Diagnose the Problem
- Size the issue. Note how many URLs are affected and whether the number is growing. Export the examples from the report.
- Group URLs by pattern. Are they products, filters, tags, paginated pages or new articles? A pattern usually reveals the cause.
- Decide which ones matter. If the affected URLs are parameter or filter pages you do not want indexed, the status is harmless; focus on removing the waste instead.
- Check server health. Open the Crawl Stats report. Look at host status, average response time and the share of server errors.
- Inspect a few important URLs. Use URL Inspection to confirm they are allowed in robots.txt, have no noindex and have a self-referencing canonical.
- Check internal links. Crawl the site and see how many internal links each affected URL receives and how many clicks it is from the homepage.
- Review logs if available. Log file analysis shows exactly where Googlebot spends its time instead.
How to Fix It
| Cause | Fix |
|---|---|
| Slow or unstable server | Upgrade hosting, add caching or a CDN, fix slow database queries, resolve 5xx spikes |
| Crawl wasted on low-value URLs | Block infinite URL spaces in robots.txt, consolidate duplicates, return 404/410 for removed content |
| Weak internal links | Link important pages from navigation, category pages, hubs and related content |
| Sitemap noise | Include only canonical, indexable, 200-status URLs; keep lastmod accurate |
| Mass launch of thin pages | Launch in batches; make each page meaningfully unique before publishing |
Google's crawl budget guidance recommends keeping sitemaps up to date, avoiding long redirect chains and eliminating duplicate content, and it notes that noindex does not save crawling because Google still requests the page before dropping it. If your server is the bottleneck, our guide to web hosting and SEO covers what to look for.
Should you use "Request indexing"?
For a small number of high-priority URLs, the Request indexing button in URL Inspection can help. It has a quota, though, and it does not change the conditions that caused the backlog. For sites that also want Bing and other engines to pick up changes faster, see our IndexNow guide.
How to Prioritise Affected URLs
On a large site, you cannot fix every URL at once, and you should not try. Sort the affected URLs into three buckets:
- Must index: revenue-driving products, core service pages and new articles you are actively promoting. Give these strong internal links from high-traffic pages and include them in a dedicated, clean sitemap so you can track them separately.
- Nice to index: supporting content such as older blog posts or long-tail categories. Improve their linking over time and merge any that overlap.
- Should not exist in search: filters, sort orders, internal search and session URLs. Here the goal is the opposite: stop generating crawlable links to them so Google stops discovering them at all.
Tracking the "must index" bucket on its own sitemap makes progress visible in Search Console, because you can filter the Page indexing report by sitemap and watch the count move from discovered to indexed.
Common Mistakes
- Mass-submitting URLs through URL Inspection instead of fixing the cause.
- Treating every URL in the report as a problem, including filters and parameters you never wanted indexed.
- Adding noindex to save crawl budget, which Google says does not work that way.
- Ignoring server performance because pages load fine for human visitors at quiet times.
- Launching tens of thousands of near-duplicate pages and expecting them all to be crawled quickly.
- Relying on the sitemap alone without internal links pointing to the new pages.
- Overlooking wider crawl blockers such as blocked resources or redirect loops; our checklist of crawlability issues covers them.
Related Guides
- 5xx Server Errors and SEO: How to Diagnose and Fix Them
- Excessive DOM Size: Why It Hurts Performance and How to Fix It
- How to Set Up 301 Redirects in .htaccess
Frequently Asked Questions
How long does "Discovered – currently not indexed" last?
There is no fixed time. Some URLs are crawled within days; others stay for months if Google sees little reason to prioritise them or is limiting crawling on the site.
Is "Discovered – currently not indexed" an error?
No. It is a status, not an error. It becomes a problem only when important pages stay in it for a long time.
Will requesting indexing fix it?
It can help for a few key pages, but it is limited by a quota and does not address site-wide causes such as slow servers or URL bloat.
Does this status affect small sites?
Yes, it can, but on small sites it is more often caused by weak internal linking or perceived low value than by crawl capacity.
What is the difference between discovered and crawled not indexed?
Discovered means Google has not fetched the page yet. Crawled means Google fetched it and decided not to index it, usually for quality or duplication reasons.
Conclusion
"Discovered – currently not indexed" is Google saying "not yet". Make the answer "now" by giving Google a fast, reliable server, fewer low-value URLs to wade through and clear internal signals about which pages matter.
If important pages are stuck, our technical SEO team can diagnose crawl and indexing problems as part of our SEO services. Request a free quote today.
