"Discovered - Currently Not Indexed": Why Google Isn't Crawling Your Pages
Google knows the URL exists but hasn't fetched it yet. Usually that's a signal about server capacity, low-value URLs or weak internal links. Here is how to fix it.
By DigitalUs Media teamPublished 4 min read
“Discovered - currently not indexed” means Google knows a URL exists but hasn’t crawled it yet. Google says it usually postponed the crawl because fetching the page was expected to overload your site, which is why the report shows no last crawl date.
In practice, it’s a priority signal: Google has decided other URLs are more worth its time. The fix is to make crawling your site cheaper and to make your important pages look important.
What Google says it means
From Google’s Page indexing report documentation: “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.”
So the URL is in Google’s queue. Google found it in a sitemap or a link, and then deprioritized it. Unlike crawled - currently not indexed, Google hasn’t judged the content yet, because it hasn’t seen it.
Is it a problem?
Look at the example URLs in the report first.
- Parameter URLs, filters, internal search results, tag pages: usually not a problem. Better still, stop generating links to them.
- New articles, products or service pages: a problem if they stay there for weeks.
- Thousands of URLs on a small site: a sign that the site produces far more URLs than it has real pages.
The usual causes
1. The server is slow or returns errors
Google adjusts how fast it crawls to what your server can handle. If responses are slow or it gets 5xx errors and timeouts, it crawls less. Google’s documentation on HTTP and network errors explains how errors like 500, 503 and 429 slow crawling down.
Check: Search Console’s Crawl stats report (Settings → Crawl stats) shows average response time and host status. Test response time yourself:
curl -s -o /dev/null -w "TTFB %{time_starttransfer}s\n" https://example.com/new-article/
For reference, when we moved our own site from WordPress to a static site, the time to first byte on a service page went from about 1.5 seconds to under 0.2 seconds. In our view, anything consistently over a second is worth fixing before you look at anything else.
2. Too many low-value URLs
Faceted navigation, sorting parameters, session IDs, calendar pages, printer versions and auto-generated tag pages can multiply a 200-page site into tens of thousands of URLs. Google has to discover and prioritize all of them.
Fix: stop linking to URLs you don’t want crawled, block crawl traps in robots.txt where appropriate, and canonicalize or consolidate duplicates. Google’s crawl budget guide lists the main culprits.
3. Weak internal linking
A URL that’s only in the sitemap, with no internal links, tells Google little about its importance. Sitemaps help discovery, but internal links signal priority.
Fix: link to new pages from the home page, a hub or category page, and two or three related articles. Make sure the links are real <a href> elements, as Google’s crawlable links guide requires, not buttons or script-only navigation.
4. A new site with little authority
New sites and sites with few links get crawled less, because Google has less evidence that their pages are worth fetching. Publishing many pages at once makes the queue longer.
Fix: publish fewer, stronger pages and link them well. Our rule of thumb for new sites: get the first 20 pages crawled and indexed before publishing the next 200.
5. The sitemap is full of noise
A sitemap that lists redirects, noindex pages or duplicates wastes the signal. Google’s sitemaps overview says to list the canonical URLs you want in search.
Fix: list only canonical, indexable 200 URLs, and keep lastmod honest.
Does crawl budget matter for your site?
Probably not. Google’s crawl budget guide is written for large sites (roughly 1 million+ unique pages that change weekly), medium or larger sites (10,000+ pages) whose content changes daily, and, notably, sites where a large share of all URLs sits in “Discovered - currently not indexed”. Google calls those numbers a rough estimate. If your site has a few hundred pages and only some of them are in this status, the cause is almost always one of the issues above, not a budget limit.
How to fix it, in order
- Check server health in the Crawl stats report and fix slow responses and errors.
- Clean the URL inventory: remove links to parameter and filter URLs, consolidate duplicates.
- Clean the sitemap so it only lists pages you want indexed.
- Link to the important pages from relevant, already-indexed pages.
- Request indexing in URL Inspection for a handful of the most important URLs. It doesn’t scale, but it helps for key pages.
- Wait and watch the trend. Re-check the report in two to four weeks.
If the same pages then move to “crawled - currently not indexed”, Google has now seen them and the question becomes one of quality.
For a full check of crawling and indexing, work through our technical SEO audit checklist, or ask us to run it as part of our technical SEO service.
Frequently asked questions
What does "discovered - currently not indexed" mean?
Google has found the URL, usually through a sitemap or a link, but hasn't crawled it yet. Google says it typically postponed the crawl because crawling was expected to overload the site, which is why the report shows no last crawl date.
How long do pages stay in "discovered - currently not indexed"?
There is no set time. Pages with strong internal links on a fast site usually move on within days or weeks; low-value URLs on a slow or very large site can stay there indefinitely.
Is it a crawl budget problem?
Usually only on large sites. Google's crawl budget guide targets sites with very many pages or fast-changing content, and sites where a large share of all URLs is in this status. On a small site, look at server speed, internal links and page quality first.
What's the difference between "discovered" and "crawled - currently not indexed"?
"Discovered" means Google hasn't fetched the page yet. "Crawled" means it fetched the page and decided not to index it. The first is mostly about crawl priority; the second is mostly about the page itself.
Related guides
Technical SEO and Indexing
"Crawled - Currently Not Indexed" in Search Console: Causes and Fixes
Google visited the page and decided not to index it, for now. Here is how to tell whether that's a problem, what usually causes it and what to fix.
5 min read
Technical SEO and Indexing
Technical SEO Audit Checklist: 40 Checks, in the Order We Run Them
A technical SEO audit checks whether Google can crawl, render and index your site. These are the 40 checks we run, in order, with examples from our own site.
8 min read
