Discovered - Currently Not Indexed: Causes and Fixes
What does “Discovered - currently not indexed” mean?
It means Google knows the URL exists but hasn't crawled it yet. Search Console says Google usually postponed the crawl because it expected to overload your site.
- •That's why the report shows no last crawl date for these URLs.
- •Google hasn't read the page, so it hasn't judged the content yet.
- •The levers are server health, fewer low-value URLs, and stronger links.
- •A few new URLs here is normal; a large, stuck share is a crawl budget problem.
What the Status Means
Google found the URL, usually in your sitemap or through a link, and put it on its list. It hasn’t fetched the page yet. Search Console’s help gives the typical reason: Google wanted to crawl the URL, but expected that doing so would overload the site, so it rescheduled the crawl. That’s also why these URLs show no last crawl date in the report.
Two things follow from that. First, Google hasn’t read the page, so this isn’t a verdict on its content. Second, the cause sits at the level of the whole site: how much crawling Google thinks your server can take, and how much it wants to crawl. Its sibling status, “Crawled - currently not indexed,” is the opposite case: Google did fetch the page and chose not to index it.
Why It Happens: Crawl Capacity and Crawl Demand
Google’s crawl budget guide is written for three kinds of sites. One of them is sites with “a large portion” of their URLs in this exact status. The guide describes crawl budget as two things combined:
- Crawl capacity: how hard Google can crawl without overloading your server. Every site starts with the same conservative limit. If your server responds steadily and its response times hold or improve, the limit goes up. If it slows down, or returns 5xx errors or 429 “too many requests,” the limit goes down.
- Crawl demand: how much Google wants to crawl. The guide says it depends on the site’s size, update frequency, page quality and relevance compared with other sites. The factors you can influence are your URL inventory (duplicates and unwanted URLs waste crawl time; Google calls this the factor you can control most), popularity (URLs that are more popular on the web get crawled more often), and staleness.
Even when your server could handle more, Google crawls less if demand is low. So “Discovered - currently not indexed” can mean a slow server, a site full of URLs Google doesn’t want, or simply a site Google doesn’t see much reason to crawl yet.
One detail that surprises people: Google treats each hostname as its own site. www.example.com and shop.example.com each get their own crawl budget.
Is It a Problem?
Not always. Freshly published URLs often pass through this status before their first crawl. It’s worth acting on when the share is large, when it keeps growing, or when your most important pages are stuck in it rather than low-value ones.
How to Diagnose It
1. Look at which URLs are waiting
In Search Console, open Indexing > Pages and click “Discovered - currently not indexed.” Sort the examples into groups. Are they key pages (products, guides), or parameter URLs, filter combinations, tag archives and old redirects? The mix tells you whether to fix capacity or inventory.
2. Check your crawl health
Open Settings > Crawl stats. Check the average response time trend, the host status, and the breakdown by response code. Rising response times, 5xx errors or 429s are exactly the signals the crawl budget guide says lower your crawl capacity.
3. Check what your sitemap is feeding Google
Every URL in your sitemap is a request for a crawl. If it lists redirects, 404s, noindexed pages or duplicates, you’re spending crawl demand on URLs you don’t want. Splitting a large sitemap by section (products, categories, articles) also helps you monitor: in the Sitemaps report you can open each file’s page indexing data separately and see which section is stuck.
How to Fix It
Shrink the URL inventory
This is the lever Google says you control most. Merge duplicate pages and 301 the extras. Keep URLs you never want crawled, such as internal search results and endless filter combinations, out with robots.txt. Remove redirects and dead links from your sitemap and internal links. Don’t rely on noindex to save crawling: the crawl budget guide notes that Google still requests a noindexed page before dropping it.
# robots.txt: keep crawl-wasting URL spaces out User-agent: * Disallow: /search Disallow: /*?sort= Disallow: /*?sessionid=
Check patterns like these against your own URLs first. A wildcard that also matches real pages will block them.
Keep the server fast and stable
Watch response times and errors in Crawl stats. Cache pages, fix slow database queries, and make sure your firewall or CDN isn’t answering Googlebot with 429s or 5xx errors. Capacity recovers as responses stay healthy.
Make important URLs look important
Link to them from pages Google already crawls often, such as your home page, hubs and popular articles, not only from the footer or the sitemap. Links from other sites help too: the guide says popular URLs are crawled more often.
Give honest lastmod dates
Google’s sitemap guide says it uses <lastmod> only when the dates are consistently and verifiably accurate. Update the date when the main content, structured data or links change, not on every deploy.
Request indexing for a few key pages
URL Inspection’s Request indexing works for individual URLs, within a quota. Google’s recrawl guide says crawling can take a few days to a few weeks, a request doesn’t guarantee indexing, and asking again for the same URL doesn’t speed it up. For hundreds of URLs, the fixes above matter more.
Slow down if most new pages land here
If nearly every new page waits in this status, publishing faster only makes the queue longer. Strengthen and consolidate what you have, then publish at a pace your crawl rate supports.
FAQ
How long can a page stay in “Discovered - currently not indexed”?
There’s no set limit. New URLs often move on once Google crawls them; on sites with low crawl demand, pages can wait much longer. Track a few important URLs in URL Inspection rather than the report total.
Does it mean my page is low quality?
Not that page, directly: Google hasn’t fetched it. But crawl demand reflects the site as a whole, including page quality and relevance compared with other sites, so a site with many weak pages can see more of its URLs wait here.
Will “Request indexing” fix it?
For a handful of important URLs it can help, within Google’s quota. It won’t fix a site-wide backlog; capacity and inventory will.
Should I remove these URLs from my sitemap?
Only the ones you don’t want indexed. Keep your important pages in the sitemap, and take out duplicates, redirects and low-value URLs so the sitemap points Google at what matters.
Check Your Sitemap
The free sitemap finder reads your robots.txt, loads your sitemap, and tests 30 of its URLs for 404s, redirects, noindex tags, canonical mismatches and slow responses: the kind of dead weight that spends crawl demand on the wrong URLs.