Discovered – Currently Not Indexed: How to Fix It

"Discovered – currently not indexed" is one of the most frustrating statuses in Google Search Console: Google knows your page exists but has decided not to crawl it yet. This guide explains exactly what "discovered – currently not indexed" means, why it happens, and the practical fixes that get those pages crawled and into the index.

Table of contents

• What "Discovered – currently not indexed" actually means
• Discovered vs Crawled – currently not indexed
• Why Google leaves pages "discovered"
• 8 fixes that get pages crawled and indexed
• When to act vs when to wait
• FAQ
• The bottom line

What "Discovered – currently not indexed" actually means

When you see "discovered – currently not indexed" in the Pages report, Google is telling you something specific: it has found the URL — usually from your sitemap or from an internal or external link — but it has not crawled the page yet. The page hasn't been fetched, so its content hasn't been evaluated and it isn't in the index.

This is a crawl decision, not a quality rejection. Google has the URL in its queue but has chosen, for now, not to spend the resources fetching it. That's an important distinction. Nothing about your page's content has been judged and found wanting. Google simply hasn't gotten around to it, or has decided the URL isn't worth crawling right now given everything else competing for attention on your site.

In other words: "discovered" is a priority problem. Google scheduled the URL and then deprioritized it. Your job is to give Google more reasons to bump that URL up the queue and to remove anything that's making your site harder to crawl.

For the wider picture across every indexing status, see the full guide to Google indexing problems. This post goes deeper on the "discovered" case specifically.

Discovered vs Crawled – currently not indexed

These two statuses look similar but mean opposite things, and the fix for each is different.

Discovered – currently not indexed means Google has the URL but has not fetched it. The page was never read. This is a crawling and prioritization issue. The solutions are about making the URL easier and more worthwhile to crawl.

Crawled – currently not indexed means Google did fetch the page, read the content, and then chose not to index it. This is a quality judgment. Google saw what's on the page and decided it wasn't worth adding to the index — often because the content is thin, near-duplicate, or doesn't add anything new.

So the order of events tells you what to do:

• Discovered → Google hasn't looked yet → improve crawl signals (links, speed, sitemap quality).
• Crawled → Google looked and passed → improve the page itself (depth, uniqueness, value).

If you're chasing the wrong status, you'll waste effort. Confirm which one Search Console is reporting before you start fixing.

Why Google leaves pages "discovered"

Several root causes push URLs into the "discovered" bucket. Most sites have more than one in play.

Crawl budget pressure. On large sites, Google allocates a limited number of fetches per visit. If you have tens of thousands of URLs, lower-priority pages get pushed back in the queue. Here's how crawl budget works and why it matters most at scale.

Slow server response. If your server is slow to respond, Google crawls fewer pages per session to avoid overloading it. A sluggish site directly shrinks how much Google is willing to fetch.

Thin or low-value pages. A site stuffed with thin pages lowers Google's overall confidence in the site. When site-wide quality signals drop, Google becomes more conservative about crawling new or borderline URLs.

Orphan pages. A URL with no internal links pointing to it looks unimportant. If the only place Google found it is your sitemap, it has little reason to prioritize the crawl.

A bloated sitemap. A sitemap full of non-indexable URLs — 404s, redirects, noindex pages, parameter junk — dilutes the trust Google places in that sitemap. When the list is noisy, Google treats every URL in it with more skepticism, including your good ones.

A brand-new site. New domains have little authority and a short crawl history. Google crawls them cautiously until they prove themselves, so newly published URLs can sit in "discovered" for a while.

Near-duplicate content. If a page looks almost identical to others Google already knows, it may deprioritize the crawl because it expects little new value.

8 fixes that get pages crawled and indexed

Work through these in order. The early ones are the levers you fully control.

1. Add internal links to the affected URLs

Internal links are the strongest crawl signal you control. A URL linked from your homepage, a category hub, or a popular post looks far more important than one sitting only in your sitemap. Find the stranded pages and link to them from relevant, well-crawled pages. Use descriptive anchor text. This single change moves more URLs out of "discovered" than anything else.

2. Speed up your server

Aim for a server response time under 200ms. Faster responses let Google crawl more pages per session, which directly increases how many of your "discovered" URLs get fetched. Check your hosting, database queries, and caching. A slow Time to First Byte is a silent crawl killer on large sites.

3. Prune or consolidate thin pages

Every thin, low-value page competes for crawl attention and drags down site-wide quality signals. Audit your pages. Merge overlapping ones, expand the ones worth keeping, and remove or noindex the rest. A smaller, stronger site is crawled more confidently than a large, shallow one.

4. Keep your sitemap clean and current

This is the lever you most directly control. Your sitemap should list only indexable, canonical URLs — no 404s, no redirects, no noindex pages, no parameter duplicates. A clean sitemap earns Google's trust; a noisy one wastes crawl attention and casts doubt on every URL in it. This is exactly the job Indexly handles: it crawls your site, generates a sitemap that contains only live, indexable, canonical URLs, and keeps it current automatically, so Google never wastes a crawl on a dead link. Learn how to keep your sitemap clean and valid.

5. Earn a few external links

A handful of quality external links raise your site's authority and signal that pages are worth crawling. You don't need hundreds — a few relevant, credible links can lift crawl priority across the site, especially for newer domains trying to build trust.

6. Request indexing via URL Inspection — sparingly

For a small number of important URLs, use the URL Inspection tool to request indexing. This can nudge Google to crawl a page sooner. But it's a manual, rate-limited nudge, not a strategy. Don't submit hundreds of URLs this way — fix the underlying crawl signals instead. Use it for your few highest-priority pages.

7. Differentiate near-duplicate content

If affected pages look almost identical to existing ones, give Google a reason to crawl them. Add unique content, distinct intent, or information the other pages don't have. If two pages truly serve the same purpose, consolidate them and canonicalize to one.

8. Be patient with genuinely new sites

If your site is new, some "discovered" URLs just need time. Keep publishing, keep building internal links, keep your sitemap clean, and let crawl history accumulate. Authority compounds. The same URLs that sit in "discovered" on a month-old site often index without intervention once the domain matures.

When to act vs when to wait

Not every "discovered" URL needs a fix. Use judgment.

Act now if the affected pages are important — money pages, key landing pages, content you actively promote — and they've sat in "discovered" for weeks. Act if the count is large and growing, which points to a structural problem like crawl budget waste, slow response times, or a bloated sitemap. Act immediately if you find non-indexable URLs sitting in your sitemap, because that's diluting trust across the board.

Wait if the site is genuinely new and still building authority, or if the affected URLs are low-priority pages you wouldn't miss. A few "discovered" URLs on a healthy site is normal — Google can't crawl everything instantly, and minor pages naturally wait their turn. Don't burn manual indexing requests on pages that don't matter.

The smart move: fix the structural levers once — internal links, server speed, sitemap quality — and most "discovered" URLs resolve themselves over the following crawls.

FAQ

How long does "discovered – currently not indexed" last? There's no fixed timeline. On established sites with good crawl signals, pages can move out within days. On new or low-authority sites, it can take weeks. Improving internal links, server speed, and sitemap quality shortens the wait considerably. Genuinely low-priority pages may stay there indefinitely.

Does requesting indexing fix "discovered – currently not indexed"? It can nudge Google to crawl a specific URL sooner, but it's a manual, rate-limited tool, not a real solution. If you request indexing without fixing the underlying crawl signals, the page may slip back. Use it for a few important URLs, then address the root causes.

Is "discovered – currently not indexed" a penalty? No. It's not a penalty or a quality rejection. Google has simply found the URL and hasn't crawled it yet. It's a prioritization decision. Your content hasn't been judged at all — the page hasn't even been fetched. Improve crawl signals and the status usually clears.

Why are sitemap URLs stuck in "discovered"? Listing a URL in a sitemap tells Google it exists but doesn't force a crawl. If those URLs have no internal links, sit on a slow site, or share a sitemap cluttered with dead URLs, Google deprioritizes them. A clean sitemap of only indexable pages, plus internal links, helps them get crawled.

Will a clean sitemap fix "discovered – currently not indexed"? A clean sitemap is one of the few levers you fully control, and it removes a common cause: a sitemap full of dead or non-indexable URLs that erodes crawl trust. It won't fix slow servers or orphan pages on its own, but combined with internal links and speed, it meaningfully helps.

The bottom line

"Discovered – currently not indexed" is a crawl priority problem, not a verdict on your content. Google has the URL and just hasn't fetched it yet. Give it reasons to: link to the page internally, speed up your server, prune thin pages, and — critically — keep your sitemap to only indexable, canonical URLs so you never waste a crawl on a dead link.

That last lever is the one you control most directly, and it's exactly what Indexly automates. Indexly crawls your site, builds a sitemap of only live, indexable URLs, keeps it current, and alerts you the moment URLs are added or removed — so the list Google sees is always accurate. Pair that with how often your sitemap should update and you remove one of the biggest causes of "discovered" URLs for good.

Start free at indexly.dev and give Google a sitemap worth crawling.