DigitalRoop guide to fixing "Discovered – currently not indexed" in Google Search Console, showing the discovered-to-indexed progress path

Discovered – Currently Not Indexed: How to Fix It (2026)

Quick Answer

Google found this URL but hasn’t crawled it yet — that’s what “Discovered – currently not indexed” means. It isn’t a penalty, and not every affected URL needs action. If an important page remains in this state, start by checking internal links, sitemap inclusion, crawlability, and server health before requesting indexing.

If you only remember one thing: discovery and indexing are two separate steps, and this status means you’re stuck between them.

Table of Contents

  1. If You’re Not Technical: Start Here
  2. What Does “Discovered – Currently Not Indexed” Mean?
  3. The Four States People Confuse (Not Just Two)
  4. Why Does This Status Happen? (Root Causes)
  5. How Serious Is the Problem? (Triage First, Fix Second)
  6. Discovered – Currently Not Indexed: Diagnostic Decision Tree
  7. How to Fix “Discovered – Currently Not Indexed” (Step by Step)
  8. How to Fix It on WordPress (Click-by-Click)
  9. What NOT to Do
  10. Do You Actually Need Every URL Indexed?
  11. How Long Does It Take to Resolve?
  12. Does This Affect AI Overviews and AI Search?
  13. How to Prevent This in the Future
  14. “Discovered – Currently Not Indexed” Fix Checklist
  15. Frequently Asked Questions
Definition

“Discovered – currently not indexed” is the Google Search Console status showing that Google knows a URL exists but has not yet crawled it. Until Google crawls the page, it cannot evaluate the fetched content for indexing.

If You're Not Technical: Start Here

If you’re not an SEO or a developer, you probably don’t need the full technical guide below — most of the time, this status quietly fixes itself. Try this short path first:

Quick Checks First
  1. If the page is new, give it some time. Google says new pages can take a few days to appear, and crawling/indexing timing varies — don’t touch anything yet.
  2. Check just one page, not the whole report. In Search Console, use the search bar at the top labeled “Inspect any URL,” paste in your page’s exact web address, and press Enter. If it says “URL is on Google,” you’re already fine — the report was just outdated. (Note: “URL is on Google” means the page is eligible to appear in results, not that it’s guaranteed to rank or show for every relevant query.)
  3. Link to the page from somewhere on your own site. Find another post or page on your site that gets some traffic, and add a normal text link to the new page inside a paragraph (not just the menu). This is one of the most useful things a non-technical site owner can do.
If That Doesn't Fix It
  1. If you use WordPress, check two settings (full walkthrough below): that your site isn’t accidentally hidden from Google, and that your sitemap is submitted in Search Console.
  2. Then click “Request Indexing.” In the same URL Inspection box from step 2, click the “Request Indexing” button. This asks Google to crawl the URL — it does not guarantee faster crawling or indexing.
  3. Give it a reasonable amount of time before worrying further. If it’s still not indexed after that, and it’s an important page, that’s when the deeper technical checks below (or hiring help) start to make sense.

If steps 1–5 don’t feel doable on your own, that’s a completely reasonable point to hand this off to a developer or an SEO freelancer — the rest of this article is written for them.

What Does "Discovered – Currently Not Indexed" Mean?

Google’s own documentation describes this status as a page that was found but not yet crawled, usually because crawling it at that moment risked overloading the site, so Google rescheduled the crawl for later. That’s also why the “last crawl date” field is empty for pages in this state — there’s nothing to show, because no crawl has happened yet.

You can read Google’s own explanation of this and every other page-indexing status in the official Page Indexing report documentation and the URL Inspection Tool help page.

In plain terms:

  • Google has added the URL to its known-URL list (through your sitemap, an internal link, an external link, or a redirect).
  • Google has not fetched the page’s content.
  • Because it hasn’t fetched the content, Google can’t evaluate or index it yet.

This status does not automatically mean: –

  • A manual penalty
  • A quality problem with that specific page
  • A robots.txt block (that would show a different status)
  • Duplicate content (though duplicate URL patterns often contribute)

Where to Find It in Google Search Console (2026 UI)

Go to Search Console → Indexing → Pages → “Why pages aren’t indexed” and look for “Discovered – currently not indexed” in the list of exclusion reasons. Click it to see the full sample of affected URLs.

(If you see older articles referencing an “Index Coverage report,” that’s the previous name for this same report — Google folded it into the current “Page indexing” report.)

The Four States People Confuse (Not Just Two)

Most guides only compare “Discovered” and “Crawled.” Four URL states are especially useful to understand when diagnosing indexing problems — note that “URL is unknown to Google” is primarily a URL Inspection status rather than a Page Indexing report state equivalent to the other three:

Comparison of Google's 4 URL states — unknown, discovered–currently not indexed, crawled–currently not indexed, and indexed
State Google knows the URL? Crawled? Indexed? What it usually means
URL is unknown to Google
No
No
No
Google’s official definition: Google hasn’t seen this URL before. (Third-party research and a public comment from Google’s Gary Illyes have documented cases where previously-crawled URLs later show this state — see below.)
Discovered – currently not indexed
Yes
No
No
Google knows it exists but hasn’t crawled it yet — a queue/priority issue
Crawled – currently not indexed
Yes
Yes
No
Google fetched the page but isn’t indexing it. Possible causes include duplication, canonicalization, quality/relevance signals, or other indexing decisions — not necessarily a single “content quality” problem
Indexed
Yes
Yes
Yes
Eligible to appear in search results

An Important Nuance Most Articles Skip

Google’s official Search Console documentation defines “URL is unknown to Google” as meaning Google hasn’t seen that URL before. However, third-party indexing research (notably from the Indexing Insight newsletter) has documented cases where URLs that were previously crawled and indexed later show this state. Google’s Gary Illyes addressed this directly in a public LinkedIn comment, explaining that Google’s systems can effectively “forget” a URL as the signals collected about it change over time — distinct from a page that’s genuinely new and simply hasn’t been crawled yet. Treat this as an advanced diagnostic possibility to check, not an assumption to apply to every URL in this state.

Why this matters for your fix

If you assume every affected URL is “new and just waiting in line,” but some of them were actually indexed before and got dropped, internal linking and sitemap fixes alone won’t solve it — you need a content-quality review for those specific URLs instead.

Why Does This Status Happen? (Root Causes)

This status occurs before Google has crawled the page, so the immediate issue relates to discovery and crawling rather than a confirmed page-level indexing decision — though the underlying causes can still involve site architecture, crawl demand, server behavior, and broader site quality signals. This falls under technical SEO broadly. Google doesn’t crawl every discovered URL immediately. Two forces control the timing:

  • Crawl capacity — the technical limit of how much your server can handle without slowing down or erroring out.
  • Crawl demand — how much Google actually wants to crawl your site, based on your site’s popularity, historical content quality, and update frequency.

(Google’s own large-site crawl budget documentation covers this in more technical depth.)

Diagram showing crawl capacity plus crawl demand equals crawl budget, the two forces behind a discovered but not indexed page
Does crawl budget even apply to your site?

Google says most sites don’t need to actively manage crawl budget — it becomes relevant mainly for very large sites or ones that change rapidly (some practitioners use rough thresholds around 1 million+ URLs, or 10,000+ pages that change frequently). – Small site: Don’t obsess over crawl budget. Check discovery, internal links, sitemap health, crawlability, and content quality first. – Large or fast-changing site: Investigate crawl capacity, crawl demand, URL duplication, faceted navigation, server logs, and crawl waste.

The 7 Most Common Causes

“Discovered – currently not indexed” shows up when either of these is constrained. Common specific causes, in rough order of frequency:

  1. Weak internal linking/orphan pages — the URL exists but almost nothing on your site links to it, so Google has no signal it’s a priority.
  2. Crawl budget drained by low-value URLs — faceted navigation, filter combinations, tracking parameters, and internal search result pages can generate thousands of near-duplicate URLs that eat Googlebot’s attention before it reaches your real content.
  3. Sitemap-only discovery — a sitemap helps Google discover URLs, but it doesn’t replace a strong internal linking structure; a URL that exists only in your sitemap with no internal links pointing to it is a common contributor to this status.
  4. Site-wide content quality signals — if a site contains large amounts of low-value, duplicate, or unhelpful content, Google may crawl it less frequently overall. That said, don’t assume the “Discovered” status on its own proves a content-quality problem — it has several other common causes too.
  5. Server performance problems — slow response times, intermittent 5xx errors, or timeouts during Googlebot’s visit cause it to back off and crawl less.
  6. Redirect chains and loops — every hop costs crawl budget; long chains can cause Googlebot to abandon the request before reaching the final page.
  7. New or recently launched sites — new sites and pages may take time to be discovered and crawled, particularly with limited internal linking and little established search presence. Google says new pages can take a few days to appear.

How Serious Is the Problem? (Triage First, Fix Second)

Before changing anything, figure out whether this is background noise or a real problem.

  • A handful of low-priority URLs (thin tag pages, filtered variations) sitting in this state is normal and often resolves on its own.
  • Important pages — product pages, core landing pages, cornerstone articles — stuck here is a real issue worth investigating immediately.
  • A rising count over time, or a pattern concentrated in one template/section, points to a systemic cause rather than random queue timing.
Checklist for triaging discovered–currently not indexed pages by severity — low priority, investigate now, or systemic cause

Quick Severity Checklist

  • Confirm the status is current — check the URL Inspection Tool directly, since the Pages report can lag behind real-time status.
  • Count how many affected URLs are actually important to your business.
  • Sample 10–20 affected URLs and look for a shared pattern (same template, same parameter, same recently launched section).
  • Check whether the count is growing week over week.

Discovered – Currently Not Indexed: Diagnostic Decision Tree

Flowchart for diagnosing why a page is discovered but currently not indexed, from URL Inspection check to requesting indexing

Read the decision tree as text

Is the URL still showing this status in URL Inspection (not just the report)?
 ├─ No → Already resolving. Monitor, no action needed.
 └─ Yes → Was this URL previously indexed or receiving Search traffic (check historical Search Console data, past audits, or server logs if available)?
      ├─ Yes, it was dropped → Treat as a CONTENT QUALITY issue, not a crawl issue.
      └─ No, genuinely new → Continue:
           ├─ Does it have internal links pointing to it? 
           │    └─ No → Fix internal linking first.
           ├─ Is it only in the sitemap? 
           │    └─ Yes → Add contextual internal links.
           ├─ Is the server returning 5xx errors or slow response times?
           │    └─ Yes → Fix server/hosting performance first.
           ├─ Are there thousands of similar parameter/filter URLs on the site?
           │    └─ Yes → Reduce crawl waste (robots.txt, canonical, consolidation).
           └─ All clear → Request indexing via URL Inspection Tool and monitor 2–4 weeks.

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

Work through these in order — don’t jump straight to “Request Indexing” without addressing the likely cause first, or you’ll be back here in two weeks with the same URLs.

1. Verify the Status Is Still Accurate

Paste the URL into URL Inspection and check its live status. Reports can be a few days behind reality.

2. Strengthen Internal Links

Add relevant, contextual internal links from pages Google already crawls frequently and that are topically related to the target — not just a footer or sitemap page. Fix orphan pages (URLs with zero internal links) as a priority.

3. Clean Up Your XML Sitemap

Your sitemap should contain only URLs that return a 200 status code, aren’t blocked by robots.txt, don’t carry a noindex tag, and are the canonical version of the page. A sitemap full of redirects or errors teaches Google to trust it less.

4. Reduce Crawl Waste

Identify and control low-value URL patterns — filtered/faceted navigation, sorting parameters, session IDs, and internal search result pages. Use robots.txt to block crawling of these paths.

Important: robots.txt ≠ noindex. robots.txt Controls crawling. noindex Controls indexing, but Google still needs to crawl a page at least once to see a noindex directive. Don’t use robots.txt as a substitute for noindex when your goal is to keep a URL out of Google’s index — a URL blocked from crawling can still potentially appear in Google’s index if Google discovers it elsewhere (for example, through an external link), because Google never gets to see the noindex tag. Use robots.txt for crawl-waste control and noindex for indexing control; they solve different problems.

5. Fix Redirect Chains

Update internal links to point directly to the final, canonical 200-status destination instead of routing through multiple redirect hops.

6. Check Server Health

In Search Console → Settings → Crawl Stats, review average response time and the breakdown of response codes. Rising response times and a growing share of 5xx errors both signal that Google is deliberately throttling its crawl rate on your site. Slow, unstable server responses usually show up in your Core Web Vitals too, so it’s worth checking both at the same time.

7. Audit Site-Wide Content Quality

Crawl demand isn’t only about one page — it’s shaped by your domain’s overall track record. If many pages across the site are low-value, duplicate, or unhelpful, Google may crawl parts of the site less frequently. Review site-wide content quality when the problem affects many important URLs; strengthening originality, depth, and demonstrated first-hand expertise across the site can help — a solid on-page SEO foundation across your site makes this fix stick.

8. Check for Hidden Blockers

Look specifically for: – X-Robots-Tag HTTP headers (server-set, invisible in page source — check via Live Test or browser dev tools) – Misconfigured canonical tags pointing elsewhere – JavaScript rendering issues, where content visible in a browser doesn’t appear in Google’s rendered HTML

9. Request Indexing (Last Step, Not First)

Once you’ve addressed the likely root cause, use URL Inspection → Request Indexing. This asks Google to crawl the URL — it does not guarantee that Google will crawl or index the page. For a batch of URLs after a sitewide fix, use Validate Fix in the Page Indexing report instead of submitting them one by one.

10. Monitor for 2–4 Weeks

Track the affected URL count weekly. A declining count means the fix is working. If a URL moves to “Crawled – currently not indexed” instead of disappearing entirely, that’s progress — the crawl stage has been reached, so the diagnosis should shift toward indexing, canonicalization, duplication, and page-level quality/relevance signals. If you’re checking dozens of URLs at once, a dedicated Google index checker tool saves time over inspecting one URL at a time — our Rapid Index Checker review covers one option worth trying.

How to Fix It on WordPress (Click-by-Click)

This section assumes you’re using Yoast SEO or Rank Math, the two best WordPress SEO plugins for this kind of indexing control — if you’re using something else, the same settings exist under different menu names.

1. Confirm your whole site isn't hidden from Google

Go to your WordPress dashboard → Settings → Reading. Scroll to “Search engine visibility.” Make sure the box labeled “Discourage search engines from indexing this site” is unchecked. If it’s checked, uncheck it and click Save Changes. (This setting, left on by accident after a site migration or redesign, can prevent your WordPress site from being indexed as intended — check it before diagnosing individual URLs.)

2. Check the specific page or post isn't excluded

  • If you use Yoast SEO: open the post/page in the editor, scroll to the Yoast box below the content, click the gear/cog icon (“Advanced” tab), and confirm the dropdown next to “Allow search engines to show this Post in search results?” is set to “Yes” (not “No”).
  • If you use Rank Math: open the post/page, find the Rank Math panel, go to the “Advanced” tab, and confirm that “Robots Meta” does not have “noindex” checked.

3. Confirm your sitemap is submitted

  • Find your sitemap URL: Yoast users go to yourdomain.com/ sitemap_index.xml Rank Math users go to yourdomain.com/ sitemap_index.xml as well (both plugins use this URL by default). If you aren’t using Yoast or Rank Math, WordPress core has generated a sitemap at yourdomain.com/ wp-sitemap.xml by default since WordPress 5.5.
  • In Google Search Console: click Sitemaps in the left menu, paste in sitemap_index.xml , and click Submit. If it’s already submitted, confirm the status says “Success,” not “Couldn’t fetch.”

4. Add an internal link manually

Open an older, established post that already gets traffic. While editing it, add one sentence that naturally links to your new page (highlight some relevant text, click the link icon, and paste the new page’s URL). This is free, takes two minutes, and is one of the simplest ways to strengthen discovery for a non-developer.

5. Watch for accidentally noindexed archives

Many sites unintentionally block category, tag, or author archive pages. In Yoast: Yoast SEO → Settings → Content Types, review the toggle for each content type. In Rank Math: Rank Math → Titles & Meta → Taxonomies, same idea. Review whether archive pages are intentionally indexable and provide enough unique search value — large numbers of low-value archive URLs can also contribute to unnecessary crawling.

Common WordPress-Specific Culprits

  • Orphan posts — older posts with no internal links from newer content are a frequent cause on blogs specifically.
  • A caching or security plugin misconfigured to block bots (check your plugin’s firewall/bot-blocking settings if you use one like Wordfence or Sucuri).
  • A staging-site robots.txt or “Discourage search engines” setting that was never turned off after launch.

What NOT to Do

  • Don’t repeatedly click “Request Indexing” on the same URL. Google explicitly says requesting a recrawl multiple times for the same URL won’t make it crawl faster.
  • Don’t resubmit your sitemap over and over hoping it forces a crawl — fix the underlying cause instead.
  • Don’t assume it’s a penalty. There’s no manual action tied to this status by definition.
  • Don’t rewrite content blindly before diagnosing whether the issue is discovery/crawl-related or a quality issue on a previously-indexed page (see the decision tree above).
  • Don’t try to force every URL on your site into the index. Filtered, parameterized, and low-value utility pages often don’t need to be indexed at all — see the next section.

Do You Actually Need Every URL Indexed?

Not every page deserves an index slot. Before spending time “fixing” a URL, ask whether it should exist in Google’s index at all.

  • Pages worth fixing: Core landing pages, product/service pages, cornerstone articles, category pages that drive real traffic.
  • Pages you can leave alone (or deliberately exclude): Filtered/ faceted variations, internal search result pages, thin tag archives, duplicate content variants, session-specific URLs.

Removing unnecessary URLs from your crawlable/internal-link structure and consolidating duplicate URL patterns can reduce unnecessary crawling and strengthen your domain’s overall quality signal. Use noindex when the goal is to prevent an otherwise-crawlable page from appearing in the index — note that Google still has to crawl a page to see its noindex tag, so noindex isn’t itself a crawl-budget shortcut.

How Long Does It Take to Resolve?

There’s no fixed Google-guaranteed timeframe — Google says crawling can take anywhere from several days to several weeks. As a practical estimate, isolated URLs with a clear fix (internal links added, indexing requested) often see changes within a few days to two weeks, while site-wide crawl budget or content-quality issues — tied to Google re-evaluating your domain’s overall crawl demand — can take several weeks to a few months. If nothing changes after four weeks of consistent effort, it’s worth a deeper technical audit — server logs, rendering checks, and a content quality review.

How to Prevent This in the Future

  • Publish new content with internal links already in place — don’t rely on the sitemap alone.
  • Keep sitemaps clean on an ongoing basis, not just when troubleshooting.
  • Monitor Crawl Stats periodically, not only when something breaks.
  • Avoid generating large numbers of low-value, duplicate, or unnecessary URLs at once.
  • Keep server response times fast and stable, especially during traffic spikes.

"Discovered – Currently Not Indexed" Fix Checklist

  • Verified current status via URL Inspection (not just the report)
  • Checked whether this URL was previously indexed and dropped
  • Added contextual internal links to the URL
  • Confirmed sitemap only contains clean, canonical, 200-status URLs
  • Reduced crawl waste from parameters/faceted navigation
  • Fixed redirect chains pointing to this URL
  • Reviewed Crawl Stats for server response issues
  • Checked for X-Robots-Tag headers and rendering issues
  • Checked whether the URL is canonical or an alternate/duplicate version
  • Confirmed the URL returns a stable 200 response
  • Audited site-wide content quality if the issue is widespread
  • Requested indexing (or used Validate Fix for a batch)
  • Set a 2–4 week reminder to recheck the count

Get a Free Indexing Audit

Please tell us which URLs are stuck and we’ll tell you why — no obligation. Our team will pull your Search Console data, check crawl stats and server response, and walk through exactly what’s blocking indexing on your site. You’ll get a clear, written explanation and a prioritized list of fixes, whether or not you decide to work with us.

Get My Free Audit

Frequently Asked Questions

What does "Discovered – currently not indexed" mean?

It means Google is aware a URL exists but hasn’t crawled it yet, so it can’t be evaluated or indexed. It’s a queue state, not an error or penalty by default.

How do I fix "Discovered – currently not indexed"?

Strengthen internal links to the page, clean up your XML sitemap, reduce crawl waste from low-value URL patterns, confirm your server responds reliably, and then request indexing through the URL Inspection Tool.

What's the difference between "Discovered" and "Crawled – currently not indexed"?

“Discovered” means Google hasn’t fetched the page yet — it’s a crawl-priority issue. “Crawled” means Google fetched it but isn’t currently indexing it; possible causes include duplication, canonicalization, quality/relevance signals, or other indexing decisions.

Is "Discovered – currently not indexed" the same as "URL is unknown to Google"?

No, though they can look similar. Google’s official definition says “URL is unknown to Google” means Google hasn’t seen the URL before. Third-party indexing research has documented cases where previously-crawled URLs later show this state — Google’s Gary Illyes has publicly discussed Google’s systems effectively “forgetting” a URL as its signals change. “Discovered” means Google already knows about the URL and is waiting to crawl it.

How long does it take to resolve?

There’s no fixed Google timeframe. As a rough practitioner estimate, isolated pages with a clear fix often resolve in a few days to two weeks; site-wide crawl budget or quality issues can take several weeks to a few months.

Should I keep clicking "Request Indexing"?

No. Request Indexing asks Google to crawl the URL — it doesn’t guarantee a crawl or indexing, and Google says repeated requests on the same URL don’t make it crawl faster.

Is this status a Google penalty?

No. It’s a normal part of Google’s crawl and index pipeline, not a manual action or quality penalty by itself.

Does internal linking really help?

Yes. Internal links help Google discover pages and understand the relationships between them, and Google recommends making important content easily findable through internal links.

Does this affect AI Overviews?

Yes. Google says a page must be indexed and eligible to appear in Search with a snippet to be eligible as a supporting link in AI Overviews or AI Mode. An unindexed page doesn’t meet that bar.

Why is my important page still stuck after fixing everything?

Check whether the page was previously indexed and later dropped — that’s a content-quality issue, not a crawl issue, and needs a different fix than a brand-new URL waiting in the discovery queue.

Key Takeaways

  • “Discovered – currently not indexed” means Google knows about a URL but hasn’t crawled it — it’s a queue state, not a penalty.
  • The two forces behind it are crawl capacity (server limits) and crawl demand (how much Google wants to crawl your site).
  • For important URLs, check internal linking, sitemap inclusion, crawlability, and server health before requesting indexing — not every affected URL needs fixing.
  • A URL that was previously indexed and later dropped can look similar to a fresh discovery issue — this is an advanced diagnostic possibility worth checking, not something to assume by default.
  • Google says pages must be indexed and eligible for Search to be eligible as supporting links in AI Overviews and AI Mode, so resolving this status is a prerequisite for AI-search visibility too.

Leave a Comment

Your email address will not be published. Required fields are marked *

Related Posts

Join Our Newsletter

Need Help? Chat with us