Discovered – Currently Not Indexed: What It Means and How to Fix It

"Discovered – currently not indexed" is one of the most common statuses in Google Search Console, and one of the most misdiagnosed. It means Google found your URL but hasn't bothered to crawl it yet. For a handful of tag pages or parameter URLs, that's normal queue behavior. For your product pages or top blog posts, it means zero chance of ranking, zero AI Overview visibility, and zero organic traffic until you fix whatever is blocking the crawl.

To build this guide, I reviewed the top five articles ranking for this query and cross-referenced every recommendation with Google's official indexing documentation and John Mueller's public statements. The gap was consistent: every guide jumps straight to fixes without helping you figure out whether you even have a problem worth fixing.

This guide starts with triage so you skip the noise, then walks through root cause diagnosis, a prioritized fix workflow, copy-paste templates you can hand to a developer, and monitoring timelines so you know when your changes are working. Here's the workflow.

Who this guide is for: SEO practitioners and site owners who see "Discovered – currently not indexed" in Google Search Console and need to decide whether to act on it — and if so, how.

How this guide was built: Reviewed the top-ranking articles on this topic, cross-referenced with Google's official indexing documentation and John Mueller's public statements, and organized diagnosis patterns from hands-on site audit experience.

What "Discovered – Currently Not Indexed" Means

"Discovered – currently not indexed" is a page status in Google Search Console that means: Google found your URL but hasn't crawled it yet. The page is sitting in Google's crawl queue, waiting its turn.

You'll find it under Indexing → Pages → Why pages aren't indexed in GSC. If you inspect one of these URLs, you'll notice the "Last crawl" field is empty — because Google hasn't fetched the page at all.

Here's where it sits in Google's indexing pipeline:

1. Discovery — Google learns the URL exists (via sitemap, internal link, or external link)
2. Crawling — Googlebot fetches the page content ← stuck here
3. Indexing — Google processes and stores the content
4. Serving — The page appears in search results

Your page made it past step 1 but is stuck before step 2. Google knows the page exists but hasn't decided it's worth visiting yet.

Discovered vs. Crawled – Currently Not Indexed

These two statuses look similar but mean completely different things. Misidentifying which one you're dealing with leads to the wrong fix.

The bottom line: If you're seeing "Discovered," focus on making the page easier and more worthwhile for Google to reach. If you're seeing "Crawled," focus on the page content itself. The rest of this guide covers "Discovered" — for "Crawled," see our guide to fixing Crawled – Currently Not Indexed.

Should You Fix It? Triage First

Not every "Discovered – currently not indexed" URL needs your attention. Before you spend hours diagnosing and fixing, determine whether you're looking at normal queue behavior or a real problem.

Likely normal — monitor but don't act:

• Fewer than ~50 affected URLs on a site under 10,000 pages
• Affected URLs are low-priority pages (tag pages, filtered views, parameter variants)
• Pages were published within the last 1–2 weeks
• The count is stable or slowly declining over time

Investigate now:

• Revenue-generating pages (product pages, landing pages, key blog posts) are stuck
• The count is growing week over week
• Pages have been in this status for 4+ weeks
• A large percentage of your total pages are affected

As John Mueller explained: when Google sees this status, it often means the site appeared overloaded, so Google rescheduled the crawl for later. For smaller sites with good content, this typically resolves on its own.

Triage Checklist

Copy this and work through it before touching anything else:

TRIAGE: Discovered – Currently Not Indexed
==========================================
□ How many URLs are affected?           ____
□ What % of total site pages?           ____
□ Are any revenue/important pages stuck? Y / N
□ How long have they been stuck?        ____
□ Is the count growing, stable, or declining? ____
□ Any recent site changes? (migration, redesign, new sections) Y / N

VERDICT:
→ <50 URLs, all low-value, <2 weeks → MONITOR (check again in 2 weeks)
→ Important pages, growing count, or 4+ weeks → INVESTIGATE (continue below)

Root Causes and How to Diagnose Them

When triage says "investigate," the next step is figuring out why Google isn't crawling these pages. The cause determines the fix — and applying the wrong fix wastes time.

Sample 10–20 affected URLs and look for patterns. Then use this reference table:

Pattern → Cause → Fix Reference

In practice: most sites under 100K pages are dealing with an internal linking or content quality issue, not a crawl budget problem. True crawl budget constraints are rare outside of large-scale sites.

How to Fix "Discovered – Currently Not Indexed" Step by Step

Work through these in order. Each step addresses a different root cause, starting with the highest-impact fixes.

Step 1: Audit the Affected URLs

Before fixing anything, understand what you're working with:

1. Go to Indexing → Pages → "Discovered – currently not indexed" in GSC
2. Export the full URL list
3. Look for patterns: same directory? Same template? Parameter URLs? All recent content?
4. Cross-reference with your XML sitemap — are these URLs included?
5. Check internal link counts for a sample of 10–20 affected URLs using a crawler (Screaming Frog, Sitebulb, or Ahrefs Site Audit)

The pattern you find points to the cause. Use the reference table above to match.

Step 2: Clean Up Crawl Waste

Every URL Google crawls that doesn't deserve indexing takes crawl capacity away from pages that do. Eliminate the waste first.

Block crawl traps with robots.txt:

• Faceted navigation URLs (/products?color=red&size=large)
• Internal search result pages (/search?q=...)
• Session ID or tracking parameter URLs
• Deep pagination beyond a useful threshold

Fix redirect chains:

Redirect chains (A → B → C) force Googlebot to make multiple requests to reach the destination. Googlebot typically gives up after 5 hops. Update internal links to point directly to the final 200 OK URL.

Remove or noindex low-value pages:

Empty category pages, thin auto-generated pages, and duplicate pages that serve no unique purpose should be removed (404/410) or noindexed.

robots.txt vs. noindex — which saves crawl budget?

If your goal is to save crawl budget, use robots.txt. If the page needs to be crawled for some reason but shouldn't appear in search, use noindex.

Step 3: Fix Server Performance

When Googlebot gets slow responses or 5xx errors, it reduces its crawl rate to avoid overloading your server. This means fewer pages get crawled per visit.

Diagnose it:

1. Go to GSC → Settings → Crawl stats
2. Look for response time spikes that correlate with crawl rate drops
3. Check the 5xx error rate — even small percentages trigger aggressive throttling

Fix it:

• Enable server-side caching or a CDN
• Optimize slow database queries, especially for dynamic pages
• Upgrade hosting if response times consistently exceed 500ms

Check Googlebot's behavior in your server logs:

# Count Googlebot requests by HTTP status code
grep "Googlebot" access.log | awk '{print $9}' | sort | uniq -c | sort -rn

# Find the slowest Googlebot requests (if your log format includes response time)
grep "Googlebot" access.log | awk '{print $NF, $7}' | sort -rn | head -20

# Count Googlebot requests per day to spot crawl rate changes
grep "Googlebot" access.log | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

If you see a high percentage of 5xx responses or declining daily request counts, server performance is likely throttling your crawl rate.

Step 4: Strengthen Internal Linking

Internal links are how Google discovers pages and determines their importance. On most sites under 100K pages, weak internal linking is the single most common cause of "Discovered – currently not indexed."

What to do:

• Eliminate orphan pages. Every important page needs at least one internal link — ideally several. Pages that exist only in the XML sitemap with zero internal links are prime candidates for this status.
• Keep important pages within 3 clicks of the homepage. Pages buried deep in site architecture receive less crawl priority.
• Add contextual in-content links. Links within article body text from high-traffic, frequently-crawled pages carry more weight than links in navigation menus or footers.
• Remove nofollow from internal links. Internal nofollows prevent link equity from flowing to the target page, signaling low importance.

Common mistakes to avoid:

• Using JavaScript click handlers (onClick()) instead of <a href="..."> links — Googlebot may not follow JavaScript-based navigation
• Relying solely on XML sitemaps without any internal links (sitemaps suggest URLs but don't pass authority)
• Excessive links in sidebars/footers that dilute priority signals across hundreds of pages

Step 5: Address Content Quality (Site-Wide)

Here's what most guides underemphasize: Google evaluates content quality at the domain level, not just per individual page.

If previous crawls revealed thin, duplicate, or unhelpful content elsewhere on your site, Google reduces its overall crawl demand for your domain. New pages get queued indefinitely because Google doesn't expect to find value.

What to audit:

• Identify duplicate content clusters. Look for sections with URL variants (www/non-www, HTTP/HTTPS, trailing slashes, parameter versions) that serve identical content. Set canonical tags or redirect to the preferred version.
• Find and consolidate thin pages. Tag pages, empty categories, auto-generated pages with minimal content — these teach Google that many of your URLs aren't worth crawling.
• Review AI-generated content. Since Google's March 2024 core update, domains relying on mass-produced AI content without genuine human editing and expertise have seen crawl and indexing drops. Every page needs demonstrable unique value.
• Prune what can't be improved. Pages that genuinely add nothing should be removed (404 or 410), not just noindexed. Pruning concentrates Google's attention on your valuable pages.

As John Mueller has noted: "If we've discovered a lot of these duplicate URLs, we might think we don't actually need to crawl all of these duplicates because we have some variation of this page already."

Step 6: Submit a Clean XML Sitemap

Your sitemap is a priority signal for Googlebot. A dirty sitemap — full of redirects, errors, and non-canonical URLs — teaches Google to ignore it.

Sitemap hygiene rules:

• Include only URLs that return a 200 status code
• Exclude URLs with noindex tags, redirect destinations, or robots.txt blocks
• Include only canonical versions — no parameter variants, session IDs, or duplicates
• Keep each sitemap under 50,000 URLs (split into multiple sitemaps if needed)
• Update <lastmod> dates only when the page content actually changes

After cleaning your sitemap, resubmit it in GSC under Indexing → Sitemaps.

Step 7: Request Indexing (Last Step, Not First)

Most guides list this as step 1. It should be your last step — requesting indexing for a page that still has crawl-priority problems usually just moves it to "Crawled – currently not indexed."

The right workflow:

1. Fix the underlying issues (steps 2–6)
2. Go to URL Inspection in GSC
3. Enter the affected URL
4. Click Live Test to verify the page is accessible, renders correctly, and has no blocking tags
5. If everything checks out, click Request Indexing

Practical limits:

• You can submit roughly 10–15 URLs per day via manual Request Indexing (unofficial limit)
• For larger batches, use the Validate Fix button in the Page Indexing report — this prompts Google to reassess multiple URLs at once
• Request Indexing doesn't guarantee indexing — it only bumps the URL's crawl priority

Dev Ticket Template

When the diagnosis points to technical fixes that need developer involvement, use this template:

TICKET: Fix "Discovered – Currently Not Indexed" Issues
========================================================
Priority: [High / Medium / Low]
Affected URLs: [count] pages in [directory/section]

ROOT CAUSE: [from diagnosis — e.g., "Orphan pages with 0 internal links
in /blog/ section" or "Redirect chains averaging 3 hops on /products/"]

TASKS:
□ [Primary fix — e.g., "Add contextual internal links to all
   /blog/ posts from related category pages"]
□ [Secondary fix if applicable]
□ Verify: all affected URLs return 200 status
□ Verify: affected URLs have ≥2 internal links each
□ Verify: affected URLs are included in XML sitemap
□ Verify: no robots.txt rules block affected URLs
□ Resubmit XML sitemap in GSC after deploying changes

SUCCESS CRITERIA:
- "Discovered – currently not indexed" count for [section]
  decreases by 50%+ within 4 weeks
- Affected URLs transition to indexed status in URL Inspection

MONITORING:
- Check GSC Page Indexing report weekly for 6 weeks
- Review crawl stats (Settings → Crawl stats) for response
  time and crawl rate changes after deployment

How to Monitor Progress

After implementing fixes, give Google time to recrawl and reprocess. Here's what to watch:

Track the count weekly. In GSC → Indexing → Pages, check whether "Discovered – currently not indexed" is declining. A consistent downward trend means your fixes are working.

Watch for status transitions. Pages may move to "Crawled – currently not indexed" before reaching fully indexed status. That's normal forward progress through Google's pipeline — not a new problem.

Monitor crawl stats. In Settings → Crawl stats, verify that crawl rates are stable or increasing and that response times are stable or decreasing after your changes.

Expected timelines:

When to escalate: If the count hasn't improved after 4 weeks of fixes — or is still growing — you need a deeper investigation. That typically means server log analysis (examining Googlebot's actual crawl behavior), rendering audits for JavaScript-heavy sites, or a comprehensive content quality review at the domain level.

Why Indexing Matters More With AI Search

Here's an angle most indexing guides miss: pages that aren't indexed don't just lose organic rankings — they're invisible to AI search entirely.

Google's AI Overviews pull exclusively from indexed content. The same applies to other AI-powered search tools that rely on Google's index. If your pages are stuck in "Discovered – currently not indexed," they can't appear in any AI-generated answer.

With AI Overviews appearing in a growing share of search results, getting pages indexed isn't just about traditional blue-link rankings anymore. It's about being part of the AI answer layer too.

Frequently asked questions

What does the "Discovered – currently not indexed" status mean in Google Search Console?

It means Google found your URL through a sitemap, internal link, or external link but hasn't crawled it yet. The page is sitting in Google's crawl queue. No content has been fetched or evaluated, so there's no "last crawl" date in the URL Inspection tool.

Is it normal for pages to stay in "Discovered – currently not indexed" for weeks?

For low-priority pages on healthy sites, a few weeks in the queue is common. Google schedules crawls based on perceived value, so tag pages, filtered views, or newly published content often wait. If important pages (product pages, landing pages) stay stuck beyond four weeks or the total count keeps growing, that signals a real problem worth investigating.

How is "Discovered – currently not indexed" different from "Crawled – currently not indexed"?

"Discovered" means Google never fetched the page at all — it's a crawl-priority issue. "Crawled – currently not indexed" means Google fetched the content but chose not to add it to the index — that's typically a content quality or duplication issue. The root causes and fixes are different, so confirm which status you're looking at before troubleshooting.

Should I request indexing right away for affected pages?

Not as your first move. Requesting indexing before fixing the underlying cause (weak internal links, crawl waste, server issues) usually just moves the page from "Discovered" to "Crawled – currently not indexed." Fix the root cause first, then use Request Indexing as a final nudge. You're also limited to roughly 10-15 manual submissions per day.

Does crawl budget cause this issue on small sites?

Rarely. For sites under 10,000 pages, Google can technically crawl the entire site without hitting capacity limits. The bottleneck is usually crawl demand, not crawl budget. Google doesn't see enough reason to fetch those pages. Focus on strengthening internal links, cleaning up your sitemap, and improving domain-level content quality instead of optimizing for crawl budget.

Can too many low-value pages cause this status across my whole site?

Yes. When Google discovers large numbers of thin, duplicate, or auto-generated URLs, it reduces crawl demand for your domain overall. That means even your good pages get queued longer. Pruning or blocking low-value URLs (parameter variants, empty category pages, internal search results) helps concentrate crawling on the pages that matter.

What's the fastest way to tell if I need to act or just wait?

Run a quick triage: count the affected URLs, check what percentage of your total pages they represent, and see whether any revenue-generating pages are stuck. If fewer than 50 low-priority URLs are affected and the count is stable or declining, monitor it for two weeks. If important pages are stuck, the count is growing, or pages have been queued for four-plus weeks, start diagnosing.

Will fixing internal linking alone resolve this status?

On most sites under 100K pages, internal linking is the single most common cause. Adding contextual links from well-linked pages, eliminating orphan pages, and keeping important content within three clicks of the homepage often moves pages out of the queue within two to four weeks. But if server performance, crawl waste, or domain-level quality issues are also present, internal linking alone won't be enough.

If you're working through indexing issues and want to see which pages are actually driving traffic vs. which are stuck, SEO Heatmap visualizes your Google Search Console data so you can prioritize the pages that matter most. Give it a try — it's free.