Discovered not indexed in Google Search Console means Google knows your URL exists but has not crawled it yet.
The fastest fix that works for most pages is to link that specific page from another page which is indexed and then open the URL Inspection tool in Search Console, click the Request Indexing button.
And after that you will see a message that the URL was added to the priority crawl queue.
You have to then wait 3 to 7 days for Google bots to check the page again.
If that does not work, the page is stuck for a deeper reason. Google has put your URL in a queue and decided it is not worth crawling yet. So in this guide I’m going to share the diagnostic process you need to figure out why your URL is stuck in line, and what to actually do about it.
If the URL moves to indexed, you are done. If it stays discovered and not indexed even after a week, the problem is structural, not a scheduling delay. Keep reading.
What “Discovered Not Indexed” Actually Means
Google’s Page Indexing report documentation describes the status this way: the page was found by Google, but not crawled yet. Typically Google wanted to crawl the URL, but doing so was expected to overload the site, so the crawl was rescheduled.
That official explanation is one possible reason. In practice, there are more. Based on what Google’s own crawling documentation has shared publicly, a URL can sit in this status for any of these reasons:
- Your server response time made Google back off to avoid overloading you.
- Your site is new and Google has not built enough trust to prioritize crawling it heavily.
- Similar URLs on your site have been judged low value, so Google deprioritizes the rest of that pattern.
- Google has crawl capacity, but your URL has too few signals (internal links, sitemap presence, external mentions) to earn priority.
- The sitemap is bloated with junk URLs, and Google is rationing what it actually crawls from it.
It is different from crawled currently not indexed. In most projects I work on, the first thing I check is which of these patterns matches the stuck URLs. The fix changes completely depending on the answer.
The Real Causes (When the Quick Fix Does Not Work)
I’m going to share the exact step by step order for you that you have to follow if you are seeing this error in GSC and it’s important that you follow the same order.
1. Your Site Is Simply Too New
If your site is under six months old, this status is normal. Because Google takes time to build trust signals on a new domain before it starts crawling. A new blog publishing weekly might have half its archive stuck in ‘Discovered currently not indexed’ for the first two or three months.. That is not a problem to fix. It is a phase to wait out.
A pattern I see often on new sites: the homepage and a few cornerstone posts get indexed quickly, then everything else lags by weeks. That is Google sampling your content before committing to crawl more. The fix is to keep publishing, keep building real internal links, and earn one or two genuine external mentions if you can. Most of the backlog clears on its own.
When I would not bother fixing this: If your site is under three months old and fewer than 30 percent of pages are in this status, leave it alone.
2. Weak Internal Linking to the URL
A page with zero internal links from anywhere on your site is telling Google the page does not matter. The same applies to pages buried five or six clicks deep from the homepage. According to Google’s crawl documentation that internal links are part of how it discovers and prioritizes URLs, and most site audits confirm it.
The most common version of this on content sites: a post gets one internal link from the category archive when it is published, and nothing newer links to it for the next twelve months. From Google’s view, that URL never gained importance after launch.
Fix: Add 2 to 4 internal links from related pages that already get organic traffic. Use descriptive anchor text. Aim for the page to be reachable in three clicks from your homepage or a major hub page. Skip the sidebar widgets and “related posts” auto-generated blocks. Real in-body links carry more weight.
3. A Pattern of Similar URLs Google Has Already Skipped
This one is structural and easy to miss. If Google has already crawled and decided not to index a chunk of your URLs that follow a pattern (say, tag archives, faceted filter pages, programmatic location pages, or thin product variants), it tends to deprioritize new URLs that match the same pattern.
A SaaS blog I reviewed had this exact issue. The team rolled out 200 location pages using near-identical templates. Google indexed around 30 and ignored the rest. Soon after, even genuine blog posts on the same domain started struggling to get crawled because the site had already published a large volume of thin pages.. The fix was not to push harder for indexing on the new posts. It was to noindex or remove the weak location pages first.
John Mueller has discussed this directly, noting that adding or removing pages does not help much unless you are actually improving the quality of the site overall. The point is not the page count. It is the share of the site Google considers worth indexing.
Fix: Find the weak pattern. Noindex it, merge it, or remove it from the sitemap. Then resubmit the sitemap and wait. On larger sites, this is almost always the biggest unlock.
4. Slow Server or Crawl Capacity Issues
Google’s crawl budget documentation is clear that Google calculates a crawl capacity limit based on how your server responds. A slow server means fewer crawl requests per day. A site that times out or returns 5xx errors during Googlebot visits will see crawl rates drop further.
If your time-to-first-byte (TTFB) is consistently over 600 milliseconds, or if your Crawl Stats report (Settings → Crawl stats in Search Console) shows clusters of 500 or 503 errors, this is likely a real factor.
The fix here is hosting and infrastructure, not content. Talk to your developer or hosting provider with timestamps from the Crawl Stats report.
When this is the cause: A site with hundreds of URLs stuck in this status, where the Crawl Stats report shows declining total requests and rising error rates, almost always has a server problem first and a content problem second.
5. A Bloated or Messy Sitemap
Your XML sitemap should only contain URLs you actually want indexed. Each one should return a 200 status code. Including redirected URLs, noindexed pages, or 404s sends mixed signals to Google and can make it ration what it crawls from your sitemap.
Per Google’s sitemap documentation, the hard limits are 50 MB uncompressed and 50,000 URLs per sitemap file. Sites that hit either limit and stuff everything into one file often see crawl prioritization suffer.
Fix: Open your sitemap. Remove any URL that redirects, returns a 404, or has a noindex tag. Split large sitemaps by content type (posts, products, categories) so Google can crawl them in parallel. Resubmit in Search Console.
One common mistake I see: site owners include their entire URL inventory in the sitemap, including tag pages, author archives, and search result URLs that have no business being there. A clean sitemap of 800 strong URLs almost always outperforms a messy sitemap of 8,000 mixed URLs.
The Page Itself May Not Look Worth Crawling
Google does not always need to crawl a page fully to estimate whether it is likely to add value to the index. If your site repeatedly publishes thin articles, scaled AI pages, doorway pages, or near-duplicate content, Google may slow discovery crawling across the entire domain.
Common signals:
- Extremely similar titles across many URLs
- Low original insight
- Template-heavy pages with minimal unique information
- Programmatic SEO pages without meaningful differentiation
- Pages targeting keywords with no real search intent
Fix: Improve uniqueness, consolidate overlapping pages, and focus on publishing fewer stronger URLs instead of scaling volume.
This is the framework I have consistently used over the last eight years.
How I Would Triage This in a Real Audit
But if the website is older, already established, and still showing ‘Discovered – currently not indexed,’ below is the exact process I follow.”
- Export the affected URLs. Go to Indexing → Pages → Discovered – currently not indexed in Search Console. Export the sample list (capped at 1,000 URLs).
- Cluster the URLs by pattern. Group by directory, template, or URL parameter. Most sites show 3 to 5 distinct patterns. You are looking for the cluster that dominates the count.
- Decide each cluster’s fate before touching anything. For each pattern, the answer is one of four: keep and improve, merge into a stronger page, noindex, or delete. Most patterns I find on large sites should be noindexed or deleted, not fixed.
- For the “keep” cluster, check internal links and click depth. Pages with zero internal links or buried five-plus clicks deep get attention first. This is usually the fastest win.
- Check the Crawl Stats report. If error rates are high or total crawl requests are declining, the server or infrastructure is the bottleneck. No amount of page-level work fixes that.
- Clean the sitemap. Remove redirected, noindexed, and 404 URLs. Split large sitemaps by content type.
- Request indexing on a few representative URLs from the “keep” cluster. Not all of them. Just enough to test whether the structural fixes are working.
- Wait 2 to 4 weeks before doing anything else. Indexing changes are slow. Most people make changes, panic on day three, and start changing more things on top, which makes diagnosis impossible.
The biggest single mistake I see is people running fix-rewrite-resubmit cycles on individual URLs when the real problem is a whole URL pattern Google has lost interest in.
Why This Status Feels Worse in 2026
Discovered not indexed has been around for years. What has changed is how often it sticks. Reports across the SEO community in 2026 suggest Google is becoming more selective about which URLs it bothers to crawl in the first place, not only about which crawled URLs it indexes.
The likely reasons, based on what Google has shared publicly and what site owners are observing:
- The web is producing more URLs than Google can reasonably store. Indexing is more competitive than it was three years ago.
- AI-generated content has flooded search results. Google is filtering more aggressively at the discovery stage to save resources.
- Indexed pages also feed into surfaces like AI Overviews and generative search results. The bar for being included has gone up because the cost of including weak content has too.
The practical implication: the “publish and wait” model that worked in 2020 is weaker now. You need a clean sitemap, real internal linking, and a site that does not have large sections Google considers weak. That is the bar in 2026.
Final Thoughts
The quick fix works for most cases. When it does not, the deeper issue is almost never the content itself. It is the signals around it: internal links, sitemap quality, server speed, and the patterns of URLs Google has already judged as low value on your site.
Work the structural fixes in order. Wait two to four weeks between changes. And if a URL pattern keeps getting skipped, ask whether those URLs should be in the index at all. Sometimes the right answer is to noindex them and let Google focus on the pages that actually deserve a spot.
