“Discovered - currently not indexed” in Google Search Console means Google knows your URL exists, usually from a sitemap or a link, and has not crawled it yet. Google’s own definition: 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.” So the page has no last crawl date, Googlebot has never fetched its HTML, and nothing on the page itself can be the cause. The cause sits at the site level: how much crawling your server can take, and how much of your site Google thinks is worth crawling. A few URLs in this state on a healthy site usually clear on their own. Thousands of them, stuck for weeks, is a crawl priority problem you fix with server health, internal links and fewer junk URLs.
Discovered - currently not indexed
A Google Search Console index status meaning a URL has been discovered (usually via sitemap or internal link) but Google has deferred crawling it, so the URL has no crawl date and is not in Google’s index.
What “not indexed” means here
“Not indexed” means the URL is absent from Google’s index, so it cannot rank or appear in any search result, AI Overviews included. The status is not a penalty and it does not affect the rest of your site. It tells you where the URL is in Google’s pipeline: discovered, waiting for a crawl, with indexing a later step that has not started.
You will see the status in two places. The Page indexing report (the old Index Coverage report) lists it under “Why pages aren’t indexed”, and the URL Inspection tool shows “Page is not indexed: Discovered - currently not indexed” for a single URL, with the Last crawl field reading N/A. Our guide on how to check when Google last crawled a page explains that field.
Why Google discovers a page and skips the crawl
Every URL Google knows about competes for a share of your crawl budget, which Google sets from two inputs: crawl capacity (how much fetching your server handles without slowing down) and crawl demand (how much Google wants your URLs, judged on the site’s size, quality, freshness and popularity). A URL waits in “Discovered” when one of those runs short. The usual triggers:
- Server capacity. This is the reason Google’s definition names. Slow responses, timeouts and 5xx errors lower the crawl rate Google allows itself, and the queue backs up behind the limit.
- Too many low-value URLs. Google tries to crawl most of the URLs it knows about, so duplicates, parameter variants, faceted filters and thin tag pages spend the crawl that your real pages need.
- A weak pattern. When a large share of a template’s pages are thin or near duplicates, new pages from the same template earn less crawl demand. This is the classic case on programmatic builds that shipped quantity first.
- Weak internal linking. Pages buried deep, or reachable only from a sitemap, look unimportant. Orphaned content with zero internal links lands here often.
- A new or low-authority domain. Fresh sites with few backlinks get a conservative crawl until they earn more demand.
Google’s crawl budget guide is written for three kinds of site: those with over a million pages changing weekly, those with over 10,000 pages changing daily, and sites with “a large portion of their total URLs classified by Search Console as Discovered - currently not indexed”. If you are in the third group, the size thresholds stop mattering.
Spamming “Request Indexing” treats the symptom. A URL that Google rescheduled because the site looked expensive to crawl goes straight back into the same queue.
Discovered vs. Crawled - currently not indexed
These two statuses get conflated constantly, and they call for different responses.
| Signal | Discovered - currently not indexed | Crawled - currently not indexed |
|---|---|---|
| Did Googlebot fetch the page? | No, there is no crawl date | Yes, it was fetched |
| Where is the bottleneck? | Crawl capacity and crawl demand | Google’s decision about the crawled page |
| Primary causes | Server limits, URL bloat, weak links, a weak template pattern | Thin, duplicate or low-value content |
| First move | Server health, cut junk URLs, strengthen internal links | Improve or consolidate the page itself |
| Request Indexing useful? | Marginally, after the real fixes | Google says there is no need to resubmit |
If a URL is in “Crawled - currently not indexed”, Google fetched it and left it out. Google’s note on that status says it “may or may not be indexed in the future”, and the fix is the content: see thin content and run a proper SEO content audit. If it is in “Discovered”, the page was never fetched, so the levers are the crawl itself: server speed, the number of URLs competing for it, and the links that tell Google which pages matter.
How to find the affected URLs
Open Indexing → Pages in Search Console, scroll to “Why pages aren’t indexed” and click the “Discovered - currently not indexed” row. The table shows example URLs and is capped at 1,000 rows, so on a large site it is a sample. Two tricks make it useful:
- Filter by sitemap. The dropdown at the top of the report switches from “All known pages” to your submitted sitemaps or a single sitemap. One sitemap per template (products, locations, articles) shows you which page type is stuck.
- Look for the pattern. Sort the examples by folder. If one directory or URL parameter dominates, the problem is that template or that parameter, and fixing URLs one at a time will not move it.
How to fix “Discovered - currently not indexed”
Work in this order. Jumping to step 5 (Request Indexing) without steps 1 to 4 is the most common wasted effort.
1. Check the server
Open Settings → Crawl stats and read the host status, average response time and the share of 5xx responses. Google’s crawl capacity rises when the site stays fast and error-free and falls when it slows down or returns server errors. Rising response times or a spike of 5xx errors is the first thing to fix, because no internal link compensates for a server that Googlebot has learned to go easy on.
2. Rule out accidental blocks
Before Google tries again, make sure nothing would stop the crawl when it happens:
- Check that
robots.txtdoes not disallow the path. - Confirm no
noindexin the meta robots tag or the X-Robots-Tag HTTP header. - Verify the page returns a clean 200 OK (no 404, soft 404 or redirect chain).
- Make sure the canonical points to this URL and avoids a duplicate canonical elsewhere.
Run Test Live URL in URL Inspection to check all of this in one pass. The live test does not add the page to the index.
3. Cut the URLs that compete for the crawl
Google spends crawl time on every URL it knows about, so fewer junk URLs means more crawl for the pages you care about.
- Block faceted filters, sort orders and internal search results you never want indexed, and stop linking to parameter URLs from your own navigation.
- Consolidate or remove thin and near-duplicate pages; 301 the dead ones to their strongest equivalent.
- Keep the XML sitemap to indexable, canonical, 200-status URLs with honest
lastmoddates.
Our Lab study of 12.3 million programmatic pages found 96.7% of them got 100 organic visits a month or fewer. On the nine sites we measured, most of each template’s pages earned little or nothing, and pages like those are the first candidates to cut.
4. Strengthen internal linking and the pattern
Google infers importance from how your own site references a page.
- Crawl the site (Screaming Frog, Sitebulb or Ahrefs Site Audit) and list URLs with zero or few internal inbound links.
- Add contextual, in-body links from pages that are already indexed and earn traffic: the homepage, pillar pages and category hubs. Build out topic clusters so related pages link to each other.
- Keep important pages within two or three clicks of the homepage, and audit your site structure for orphans.
- If a whole template is stuck, raise the quality of the template: unique data on each page, real answers, specific examples. Improving one URL does nothing for a cohort Google judges as a group.
5. Then, and only then, prompt Google
- Resubmit the cleaned sitemap.
- Earn a few real backlinks to the hub pages; links from other sites raise crawl demand.
- Use Request Indexing in URL Inspection for a handful of priority URLs. It moves a URL up the queue, and Google’s decision about the site still applies.
When “Discovered - currently not indexed” becomes a business problem
A few dozen URLs in this state on a small site usually clear within weeks. If the stuck URLs are tag archives or filter pages you never wanted indexed, you have nothing to fix, so leave them.
It costs money when the stuck URLs are the pages you built to earn traffic: a programmatic launch where most of a template never gets a crawl date, a product or location catalog whose “Discovered” count grows every week while the indexed count stays flat, or a site that slowed down and saw crawling fall with it. That is a build problem: server capacity, URL count, templates and internal links, fixed together. Our programmatic SEO service does that work. On Prawomat’s launch, a young domain, Google clicks grew 12x from April to November 2025 with no pages added after the 1,125 we published by April.
Frequently Asked Questions
What does “Discovered - currently not indexed” mean?
It means Google found the URL, usually in a sitemap or through a link, and has not crawled it yet. Google says it typically rescheduled the crawl because crawling was expected to overload the site, which is why the last crawl date is empty. The page is not in the index, so it cannot rank yet.
How long does “Discovered - currently not indexed” take to resolve?
There is no fixed timeline. A few new URLs on a healthy site often move within days or weeks. A large backlog clears only after the cause is fixed (server capacity, URL bloat, weak internal links), and then at the pace Google recrawls the site, which on big sites takes weeks to months.
Does “Discovered - currently not indexed” hurt my rankings?
Not directly. The status is not a penalty, and pages already indexed keep their rankings. The URLs in it cannot rank or earn traffic until they are crawled and indexed, and the causes behind a large backlog (slow servers, thin templates, weak linking) usually hold back the rest of the site too.
Will Request Indexing fix “Discovered - currently not indexed”?
Rarely on its own. Request Indexing moves one URL up the crawl queue and has a daily limit, so it cannot clear a backlog. If you request indexing before fixing server health, URL bloat and internal links, the page often lands right back in the same status.
Why are my programmatic pages stuck in “Discovered - currently not indexed”?
Usually because the template produces more URLs than Google wants to crawl: many of the pages are thin or near duplicates, internal links are weak, or the server slows down under crawl load. Google then defers the whole cohort. The fix is structural: cut the pages with no unique value, link related pages to each other, and make each remaining page worth a visit.
Is “Discovered - currently not indexed” the same as “Crawled - currently not indexed”?
No. “Discovered” means Googlebot never fetched the page; it is a crawl problem you fix with server health, fewer junk URLs and stronger internal links. “Crawled” means Google fetched the page and left it out of the index, a decision about the page that you fix by improving or consolidating the content.