Google Search Console 101: How to Fix Discovered Currently Not Indexed
- Harold Bell
- Jul 23
- 6 min read
Updated: Jul 25
Key takeaways
|
Discovered currently not indexed is the waitlist. Google learned your URL exists, from your sitemap or a link, and then decided the visit could wait. For a new post you were proud of, that postponement reads as an insult, but it is really a scheduling decision, and scheduling decisions respond to signals you control.
This status is the earlier stage sibling of crawled currently not indexed. One means Google has not visited yet. The other means Google visited and declined. The distinction decides your fix, so confirm which one you are actually looking at before touching anything.
What does discovered currently not indexed mean
It means Google found your URL, typically through your sitemap or a link, but has not crawled it yet. No visit has happened, so no indexing decision has been made. The page is queued, and Google keeps postponing the visit. |
You will find it in the Pages report in Google Search Console among the not indexed reasons. Google’s documentation frames the typical cause as crawl scheduling, saying it postpones visits to avoid overloading a site, though Onely’s analysis of the status notes rescheduling is one of several causes rather than the whole story. In practice, on small and mid sized B2B sites, server overload is almost never the real reason. Priority is.
How is it different from crawled currently not indexed
Discovered means Google has not visited the page. Crawled means Google visited and declined to index. Different stages of the pipeline, different fixes. Discovery problems respond to stronger signals. Crawl verdicts require content changes. |
Confirm the current state before diagnosing, because the Pages report lags. Paste the URL into the URL Inspection tool and check the live status and last crawl date. Pages regularly graduate from discovered to crawled or indexed before the report updates, and there is no point fixing a problem that already resolved itself.
Why does Google keep postponing the crawl
Because it predicts the visit will be low value. URLs with no internal links, URLs that pattern match to duplicates, and sites with a history of thin pages all get deprioritized in the crawl queue. |
The URL is orphaned. A sitemap entry with zero contextual links from indexed pages gives Google discovery without endorsement. The engine knows the page exists and has no evidence anyone, including you, considers it important.
The URL pattern smells like duplication. Google recognizes patterns of near duplicate URLs and skips crawling variations when it believes it already holds a version. Parameter URLs, pagination, and templated pages trigger this constantly.
Your site’s track record argues against the visit. A history of thin or redundant pages teaches the crawler that your new URLs are usually not worth priority treatment. Site level reputation shapes URL level scheduling.
How do you fix discovered currently not indexed
Link the URL from your strongest indexed pages, confirm it appears in a clean sitemap, and request indexing through URL Inspection to jump the queue. For patterned URLs, fix the duplication signal rather than pushing harder. |
For a priority page, the play is straightforward. Add three or more in body links from indexed pages with descriptive anchors, exactly the discipline covered in my internal linking strategy guide, and then use Request Indexing to move the URL to the front of the line. Links change the value prediction. The request changes the timing. You want both, in that order.
For URL patterns, more pushing makes things worse. Consolidate parameter variants with canonicals, prune templated thin pages, and keep the sitemap limited to URLs you genuinely want indexed. Every junk URL you feed the queue lowers the predicted value of your next real one. The full sequencing across engines lives in my guide to getting your website indexed by Google and Bing.
When should you just wait
A small, stable count of discovered pages on a healthy site is normal and usually resolves within days to weeks. Intervene when the count trends upward, when priority pages are affected, or when URLs sit in the status for more than a month. |
This status has a natural background level, especially right after publishing. The signal worth acting on is the trend. A rising line means your discovery signals are weakening or your URL inventory is bloating, and either one compounds. A single stuck launch post means one page needs links and a request. Know which problem you have before spending a week on it.
Does Bing have an equivalent status
Bing does not use the same label, but the same gap between discovery and crawl exists, and IndexNow closes it. Pushing URLs to Bing the moment they publish removes the discovery wait entirely on Microsoft’s side. |
On the Bing side, you do not have to wait for a crawler to prioritize you. The IndexNow protocol pushes new and updated URLs directly, which is why my guide to getting pages into Bing’s index treats it as the default rather than an optimization. Google has no equivalent push protocol for regular content, which makes internal links and clean URL hygiene the whole game on Google’s side.
Pages stuck in the queue for weeks? A discovery audit takes my team about an hour and names the exact signal holding your URLs back. Book 30 minutes with MQL Magnet and we’ll run it together. |
Frequently asked questions
What does discovered currently not indexed mean?
Google knows your URL exists, usually from a sitemap or link, but has not crawled it yet. No indexing decision has been made because no visit has happened. The URL is queued and repeatedly postponed.
How is discovered currently not indexed different from crawled currently not indexed?
Discovered means no crawl has happened yet. Crawled means Google visited the page and declined to index it. They sit at different pipeline stages and require different fixes.
How do I fix discovered currently not indexed?
Add contextual internal links from indexed pages, keep the URL in a clean sitemap, and request indexing through URL Inspection. Links raise the predicted value of the crawl, and the request moves it up the queue.
How long does discovered currently not indexed take to resolve?
On healthy sites, days to a few weeks without intervention. With internal links and an indexing request, priority pages often get crawled within days. URLs stuck beyond a month need diagnosis.
Is discovered currently not indexed caused by crawl budget?
Rarely on small and mid sized sites. Google frames the status around not overloading your server, but for most B2B sites the real driver is priority. The engine predicts the crawl is not worth making yet.
Should I request indexing for discovered currently not indexed pages?
Yes, for priority pages, and after adding internal links. The request jumps the queue, but without links the crawl can still end in a decline, trading one exclusion status for another.
Why do my new blog posts sit in discovered currently not indexed?
Most often because they published without links from established pages. Batch publishing posts that only reference each other creates an orphaned cluster with discovery but no endorsement.
Can too many low quality URLs cause discovered currently not indexed?
Yes. Parameter variants, thin templated pages, and bloated sitemaps lower the predicted value of crawling your next URL. Pruning the junk raises priority for the pages that matter.
Does discovered currently not indexed affect AI search visibility?
Yes, upstream. A page Google never crawls cannot enter the index that feeds AI Overviews, and the same weak signals usually slow Bing, which supplies ChatGPT and Copilot retrieval.
Will resubmitting my sitemap fix discovered currently not indexed?
No. The sitemap already did its job, which is discovery. The gap is between discovery and crawl, and it closes with internal links, cleaner URL inventory, and targeted indexing requests.
Comments