Discovered vs. Crawled Not Indexed in Google Search Console: What’s the Difference and How to Fix Each

When you log into Google Search Console (GSC) to check your site’s coverage, it can be very frustrating to find your URLs shoved into the “Not Indexed” bucket. But pay close attention to the specific reason GSC provides.

Two of the most common – and easily confused – statuses are “Discovered – currently not indexed” and “Crawled – currently not indexed.”

While they might sound like minor variations of the same problem, they point to two completely different stages in Google’s processing pipeline. Treating a “Discovered” issue with a “Crawled” fix is one of the most common technical SEO missteps site owners make.

Here is the exact difference between the two statuses and how to troubleshoot each one efficiently.

The Core Distinction: Queue vs. Quality

Before diving into solutions, it helps to understand how Google processes a web page:

1. Discovery: Google finds out a URL exists.
2. Crawling: Googlebot fetches the page’s HTML, rendering the code and assets.
3. Indexing: Google analyzes the content and decides if it deserves a place in its search database.

[ Discovery ] ──> [ Crawling ] ──> [ Indexing ]
      │                │                │
      ▼                ▼                ▼
"Discovered –    "Crawled –        "Page is
Not Indexed"     Not Indexed"      Indexed"
(Stuck in Queue) (Failed Quality)  (Success!)

• Discovered – currently not indexed: A scheduling and queue issue. Google knows the page exists, but it hasn’t actually spent the resources to fetch or read the page yet.
• Crawled – currently not indexed: An evaluation and quality issue. Googlebot visited the URL, downloaded the page, read your content, and explicitly decided not to put it in the index.

Understanding where your page got stuck determines your exact path forward.

Part 1: “Discovered – Currently Not Indexed” (The Queue Problem)

What It Means

When a URL displays this status, Googlebot detected the link – usually through an XML sitemap, an internal link, or an external backlink – and added it to its crawling queue. However, Googlebot has not actually visited the page yet. There is no record of the HTML or page content in Google’s crawl log for that specific visit.

Why It Happens

Google allocates server bandwidth and crawl resources based on site demand and authority. If a page stays in “Discovered,” Google is putting off crawling it due to one of the following factors:

• Weak Internal Linking: The URL is isolated or buried four or five clicks deep in your site architecture.
• Low Overall Domain Authority: New sites or sites with limited backlink profiles have lower crawl priority.
• Crawl Queue Congestion: Publishing a massive batch of new pages all at once can temporarily overwhelm Google’s crawl schedule for your domain.
• Sitemap Noise: Flooding your XML sitemap with low-value, redirected, or utility pages slows down how fast Google gets to your main content.

How to Fix “Discovered” Statuses

1. Build Direct Internal Links: Don’t rely solely on automated sitemaps. Add direct links to the stuck page from your homepage, high-traffic blog posts, or main category navigation.
2. Clean Up Your XML Sitemap: Audit your sitemap file. Remove non-canonical URLs, 301 redirects, 404 errors, and utility pages. Keep only primary 200 OK pages in your sitemap feed.
3. Pace Content Publishing: If you are migrating content or launching a massive directory, publish in structured phases rather than dropping thousands of unlinked URLs onto your server at once.
4. Build External Authority: Earning quality backlinks to your domain naturally raises your site’s overall crawl budget and priority in Google’s queue.

Related: How to Leverage Broken Link Building to Get High-Quality Backlinks for Your Website

Part 2: “Crawled – Currently Not Indexed” (The Quality & Technical Problem)

What It Means

This status is often harder to digest. Googlebot visited the server, fetched the HTML, processed the CSS/JS, and rendered the content. But after reading the page, Google chose not to index it.

Editing your sitemap or adding a couple of internal links won’t resolve this issue because Google has already seen the page and deemed it insufficient for its index.

Why It Happens

Google aims to keep redundant or low-value pages out of its index to preserve search result quality. Common triggers include:

• Thin or Low-Value Content: The page lacks original information, depth, or standalone utility.
• Duplicate or Similar Content: The page overlaps significantly with other content already indexed on your site or across the web.
• Crawl Traps & Dynamic Parameters: URLs generated by search filters, sorting options, or tracking parameters (e.g., ?sort=price&color=blue).
• Canonical Conflicts: Google decided another URL on your site is a better primary representative for the content and selected it as the canonical page.

How to Fix “Crawled” Statuses

1. Upgrade Content Value: Evaluate the page objectively. Expand thin articles with unique insights, original screenshots, actionable examples, or clearer formatting to make the page worth indexing.
2. Consolidate Duplicate Pages: If you have multiple pages targeting virtually the same topic, consolidate them into a single comprehensive guide and set up 301 redirects from the legacy URLs.
3. Filter Out Parameter Traps: Block dynamic query strings or session parameters using your .htaccess file, server configuration rules, or robots.txt disallows. If you find thousands of dynamic parameter URLs or search result pages inflating your “Crawled – currently not indexed” report, check out our guide on How to Fix Crawl Budget Waste and Crawled – Currently Not Indexed in Google Search Console for step-by-step rules to block these traps.
4. Prune Dead-Weight Pages: If a page serves a functional purpose for users (like a print view or account page) but holds no organic search value, set it to noindex or keep it out of search engine scope altogether.

Side-by-Side Reference Breakdown

Feature / Aspect	Discovered – Currently Not Indexed	Crawled – Currently Not Indexed
Has Googlebot read the HTML?	No. It is sitting in the crawl queue.	Yes. Google fetched and rendered the page.
Primary Underlying Issue	Link discovery, queue priority, or authority.	Content value, duplication, or canonical conflicts.
First Place to Audit	Internal link depth & XML sitemap health.	On-page content quality & URL parameter setup.
Primary Action Required	Improve discovery paths & strengthen authority.	Expand content depth or consolidate duplicate URLs.

The Takeaway

Before making changes to resolve indexation issues in Google Search Console, always verify the exact status listed in the Pages report.

Rewriting content on a page marked Discovered won’t change anything until Googlebot actually visits the URL. Conversely, pointing more internal links to a page marked Crawled won’t force Google to index it if the content itself doesn’t offer unique value.

By diagnosing the exact stage where your URL stalled, you can apply the right fix the first time and keep your search visibility on track.

Related: Does Faster Website Speed Increase Googlebot Crawl Frequency?

How to make sure Google crawls all your webpages for indexing?

Already indexed, but want to better your page ranking? Read: Why Great Content Gets Stuck on Page 8 (And How to Fix It)

---

Frequently Asked Questions (FAQ)

1. Does “Discovered – currently not indexed” mean my site has a manual penalty?

No. This status is purely an operational queue and crawl-priority issue, not an algorithmic or manual penalty. It simply means Google has not prioritized fetching the URL yet.

2. Can a URL move from “Discovered” directly to “Crawled – currently not indexed”?

Yes. In fact, this is a common transition. When Googlebot finally gets around to fetching a “Discovered” URL, it evaluates the content. If it finds thin or duplicate content, the URL will move into “Crawled – currently not indexed.” If the content is solid, it moves straight to “Indexed.”

3. Should I use the “Request Indexing” tool in GSC for every affected URL?

Use it selectively. The URL Inspection tool’s “Request Indexing” button pushes a page into a priority re-crawl queue, but Google throttles how many manual requests you can make daily. Request indexing only after you’ve fixed the root cause (e.g., added internal links or expanded thin content) on high-value pages. Clicking it repeatedly without making on-page improvements will not force indexing.

4. How long should I wait before worrying about a brand-new page showing “Discovered”?

It is completely normal for a newly published page to sit in “Discovered – currently not indexed” for 24 to 72 hours – and sometimes up to a week for newer or lower-authority sites. You only need to intervene if the status persists past a few weeks on important, high-quality content.

---

Looking for a website builder that will help you maximize your SEO?

👉 What makes a website builder the best for SEO

Learn more about UltimateWB! We also offer web design packages if you would like your website designed and built for you.

Got a techy/website question? Whether it’s about UltimateWB or another website builder, web hosting, or other aspects of websites, just send in your question in the “Ask David!” form. We will email you when the answer is posted on the UltimateWB “Ask David!” section.