Discovered, Currently Not Indexed: Why It Happens and How to Fix It
Open the Pages report in Google Search Console, scroll to the “Why pages aren’t indexed” section, and there it is: a row labeled “Discovered, currently not indexed” with a number next to it that will not go down. You submitted the pages. Google knows they exist. But weeks pass and they never make it into the index. No error, no penalty, just a quiet refusal that gives you nothing to act on.
This is one of the most common and most confusing states in technical SEO, and the forums are full of the same story: pages stuck as “Discovered, currently not indexed” for six weeks or more while everything else indexes fine. The good news is that this status is a signal, not a verdict. It tells you something specific, and once you read it correctly, the fix is usually within reach.
Discovered vs Crawled: Two Different Problems
Before you fix anything, you have to know which of two very similar statuses you are looking at, because they mean opposite things.
Discovered, currently not indexed means Google found the URL, usually through your sitemap or an internal link, but has not crawled it yet. It chose to wait. The page has never been fetched, so this is not about your content quality at all. It is about Google deciding the page is not worth the crawl right now.
Crawled, currently not indexed means Google did fetch the page, looked at it, and decided not to index it anyway. This one is about the page itself: its content, its uniqueness, its value relative to what is already indexed.
The distinction matters because the cures are completely different. “Discovered” is a crawl-priority and site-health problem. “Crawled” is a page-quality problem. Treating one like the other is the most common reason people spend weeks fixing the wrong thing.
Why Pages Stay “Discovered, Currently Not Indexed”
When Google discovers a URL but keeps choosing not to crawl it, it is making a bet that the crawl will not be worth it. A few things push that bet against you.
Site-level quality and trust. Newer sites and sites with a lot of thin content get a smaller share of crawl attention. Google crawls conservatively until a site proves it is worth more. If you just launched, or just added thousands of pages, “Discovered, not indexed” is often just Google pacing itself.
Crawl budget spent elsewhere. If low-value URLs are soaking up your crawl attention, the pages you actually care about wait in line. This is the direct link to crawl budget: every request wasted on a filter combination is a request not spent on your new page. We cover this fully in why low-value pages get crawled more.
Weak internal linking. A URL that sits in your sitemap but is barely linked from anywhere looks unimportant. Google uses internal links to judge priority, and a near-orphan page signals “not urgent.” Strengthening the links into a page is one of the most reliable ways to move it out of this state.
Perceived duplication or low uniqueness. Even before crawling, Google can guess from URL patterns and known templates that a page is likely a near-duplicate of something it already has. Why crawl the ten-thousandth thin variant?
Why Pages Stay “Crawled, Currently Not Indexed”
If your status is the “Crawled” variant instead, Google has already seen the page and passed. The usual reasons:
- Thin or unhelpful content. The page exists but does not say enough that is useful or distinct to earn a spot.
- Duplication. The content closely matches another page, yours or someone else’s, so Google keeps the one it already has.
- Weak search intent match. The page does not clearly answer a query anyone is asking, so there is no slot for it.
- Template-heavy, value-light pages. Lots of structure, navigation, and boilerplate wrapped around very little unique substance.
The fix here is not technical plumbing. It is making the page genuinely worth indexing, or accepting that it is not and removing it from the crawl path.
Diagnose It with a Crawl
Search Console tells you the status but not the cause. To find the cause, you need to see your pages the way a crawler does. A full-site crawl surfaces the patterns behind both statuses:
- Find the orphans and near-orphans. Crawl your site and look at how many internal links point to each affected URL. Pages with zero or one internal link are prime “Discovered, not indexed” candidates, the priority signal is missing.
- Spot the thin and duplicate pages. Sort by word count and by content similarity. The pages clustered at the bottom are the ones Google is most likely to crawl and skip.
- Check your sitemap against reality. A clean XML sitemap should list only canonical, indexable pages. If it is full of redirects, noindex pages, or duplicates, you are diluting the signal of what matters.
- See where crawl attention is going. If your crawl reveals thousands of low-value URLs, that is where your budget is leaking, and why new pages wait. Pair this with the crawl budget optimization guide.
The goal is to turn an opaque Search Console label into a concrete list: these pages are orphaned, these are thin, these are duplicates, this sitemap is noisy.
How to Fix It
Once you know the cause, the actions are straightforward:
- Strengthen internal links to important pages. Link to your stuck pages from relevant, well-crawled pages. This is the single highest-leverage fix for “Discovered, not indexed.” Our internal linking guide goes deeper.
- Cut the crawl waste. Block parameter junk and infinite spaces so crawl attention flows to real pages instead of filter combinations.
- Make crawled-but-skipped pages worth indexing. Add unique substance, merge near-duplicates into one strong page, or match the page to a real query. If it cannot be made valuable, remove it.
- Keep the sitemap honest. List only the canonical pages you genuinely want indexed, nothing that redirects, 404s, or carries noindex.
- Request indexing, but do not lean on it. The Inspect URL tool can nudge a single important page, but it does not scale and does not fix the underlying signal. Fix the cause, and indexing follows.
Common Mistakes
- Requesting indexing over and over. Hitting “Request indexing” repeatedly does nothing if the page is orphaned or thin. You are treating the symptom.
- Confusing the two statuses. Rewriting content to fix “Discovered, not indexed” wastes effort, that status is about crawl priority, not content. The page was never even read.
- Panicking on a new site. A young site with pages in this state is often just being paced. Keep publishing, keep linking internally, and the index catches up.
- Ignoring crawl budget on a large site. On a site with tens of thousands of URLs, this status is frequently a crawl-budget symptom in disguise.
How Seodisias Helps
The thing Search Console will not tell you is why a page is stuck, and that answer lives in your site’s structure: which pages are orphaned, which are thin, which are duplicates, and where crawl attention is actually going. Seodisias is a free, cross-platform desktop crawler that walks your entire site the way a search engine does and surfaces exactly these patterns. You see the near-orphan pages that lack internal links, the thin and duplicate clusters Google is skipping, and the low-value URLs soaking up the crawl budget your new pages are waiting on. From there the fix is concrete instead of guesswork. No account, no URL limit, and your crawl data never leaves your machine.
The Bottom Line
“Discovered, currently not indexed” is not a punishment and not a dead end. It is Google telling you a page is not worth crawling yet, and the cure is to change that calculation: stronger internal links, a cleaner crawl path, and a sitemap that only points at pages worth having. If your status is the “Crawled” variant instead, the message is about the page itself, and the cure is to make it genuinely useful or let it go. Either way, the move is the same: stop guessing from a Search Console label, crawl your own site, and read the structure that the label is hiding.
Want to see which of your pages are orphaned, thin, or eating crawl budget? Crawl your site free with Seodisias.