Discovered vs. Crawled — Currently Not Indexed: What Each GSC Status Actually Means

What's the difference between "Discovered – currently not indexed" and "Crawled – currently not indexed"? One means Google hasn't visited your page yet. The other means Google visited, read the whole thing, and decided not to index it. Founders mix them up constantly, and the two problems have almost nothing in common.

That difference changes everything about what you do next.

Mix them up and you'll waste hours fixing a crawl problem you don't have. Or worse, you'll sit around waiting patiently for a page Google already rejected.

This guide breaks down what triggers each status, how to tell them apart in under two minutes, and what actually moves a stuck page forward. No guessing. No "just wait and see."

You'll walk away knowing which lever to pull for your situation, because the fix for one status does nothing for the other.

• Discovered – currently not indexed means Googlebot knows the URL exists but hasn't crawled it yet, usually a crawl budget or priority issue.
• Crawled – currently not indexed means Googlebot already read the page and chose not to index it, usually a quality or duplication issue.
• Check status fast with URL Inspection in GSC, or filter the full Coverage report by status for a site-wide view.
• Internal links are the single biggest lever for moving a page from Discovered to Crawled.
• A page stuck at Crawled needs content changes, not more links or a resubmitted sitemap.
• Small sites (under a few thousand pages) rarely have real crawl budget problems; the issue is usually link structure.
• Re-inspecting a fixed page in GSC and requesting indexing can speed up reconsideration, but it doesn't guarantee a different outcome.

Open the Coverage report in Search Console and you'll see a graveyard of statuses. Most are self-explanatory. These two aren't, and they get lumped together constantly because both display the same frustrating outcome: the page isn't in Google's index.

But the mechanics behind them couldn't be more different.

'Discovered – Currently Not Indexed' Explained

Discovered – currently not indexed means Google knows a URL exists (through your sitemap, an internal link, or an external backlink) but hasn't crawled it yet. Think of it as a name on a waiting list. Google has the address. It just hasn't knocked on the door.

This is purely a queuing problem. Nothing about the content has been evaluated, because nothing has been read yet. The page could be brilliant or garbage. Google literally doesn't know.

'Crawled – Currently Not Indexed' Explained

Crawled – currently not indexed means Googlebot visited the page, rendered it, read the content, and then decided not to add it to the index. This is a judgment call, not a queue position.

And that judgment usually comes down to quality, duplication, or thinness. Google looked at what's on the page and decided it wasn't worth showing to searchers. That's a harder problem than a crawl delay, and it takes real editorial work, not patience.

Here's where founders lose time. Treat a Crawled issue like a Discovered issue and you'll spend a week building internal links to a page Google already read and rejected. Links won't fix a rejection. They'll just get Google to reread the same weak content, faster (great, more disappointment on a schedule).

Discovered Means Google Hasn't Visited Yet

If a page sits in Discovered for weeks, the fix is about visibility and priority, not content quality. Google's crawler has a finite budget for your site, and it prioritizes URLs based on signals like internal linking depth, sitemap presence, and how important your domain appears overall.

A brand-new blog with thin internal linking will see pages sit in Discovered far longer than an established site with a clear link structure. This ties closely into why some sites struggle with indexing altogether. If you're seeing this on a new domain, the deeper issue might be why Google won't index your new site even when everything looks fine, which covers the trust and authority signals that affect crawl priority from day one.

Crawled Means Google Visited and Passed

If a page shows Crawled – currently not indexed, stop thinking about crawl budget entirely. Google already spent the resources to visit and render this page. The problem now lives in the content itself.

Common causes include:

• Thin content that doesn't add anything beyond what's already indexed elsewhere
• Near-duplicate pages, like faceted URLs or near-identical product variants
• Low-value programmatic pages generated at scale without unique substance
• Content mismatched from search intent, where the page technically loads fine but doesn't answer anything anyone's searching for

This is also where founders leaning on AI-generated content run into trouble. Not because Google penalizes AI writing outright, but because thin, templated output often reads as low-value at scale. Worth understanding the nuance here: does Google penalize AI content, and what does the evidence actually show.

You don't need to guess. Search Console tells you directly, and checking takes less time than reading this paragraph.

Reading the Coverage Report by Status

Open the Pages report (formerly called Coverage) in GSC, scroll to the "Why pages aren't indexed" table, and look for the two statuses by name. Click on either one and you'll get the full list of affected URLs, along with when Google last checked each one.

This view works best when you're auditing an entire site or a content category, say, checking whether a whole blog subsection got stuck after a migration.

Using URL Inspection for a Single-Page Check

For a one-off check, paste the specific URL into the URL Inspection tool at the top of GSC. It'll tell you the exact status, the last crawl date if one exists, and whether the page is eligible for indexing at all.

This is the faster path when you're troubleshooting a handful of pages instead of running a full audit. It also shows the exact date Googlebot last crawled the URL, which tells you immediately whether you're dealing with a queue delay or a content rejection.

This is a pure crawl-prioritization problem, and it responds to structural fixes, not content edits.

Crawl Budget and Site Size

Crawl budget refers to the number of URLs Googlebot is willing and able to crawl on a given site within a given timeframe. Google's own documentation on crawl budget notes that this mostly matters for large sites (Google Search Central, Google Search Central Documentation, 2024). So if you're running a site with a few hundred or even a few thousand pages, budget exhaustion is rarely the real bottleneck.

Sites with millions of URLs (think large ecommerce catalogs or aggregator platforms) genuinely run into budget constraints where Google can't crawl everything fast enough. If that's not your situation, don't chase crawl budget as the fix. Look at your link structure instead.

Internal Links as the Main Lever at This Stage

Internal links are, by a wide margin, the strongest signal you control for getting a Discovered page crawled sooner. A page buried five clicks deep from your homepage, with zero other pages linking to it, sends a clear signal to Google: this isn't important.

Fix that by:

1. Linking to the stuck page from a high-traffic, frequently-crawled page like your homepage or a popular blog post
2. Adding the page to a relevant hub or category page with strong existing link equity
3. Making sure the page is in your XML sitemap and that the sitemap is submitted in GSC

For a deeper breakdown of which of these levers actually moves the needle fastest, the sitemap vs. internal links comparison is worth reading before you spend a weekend rebuilding your sitemap when a single link from your homepage would've done the job.

This is where the real work happens, and there's no shortcut around it.

A page crawled but rejected needs a content overhaul, not another ping to Google. Start by asking honestly: does this page say anything that isn't already said better elsewhere on the internet, including your own site? If the answer's no, that's your fix right there.

Practical steps that actually move Crawled pages into the index:

• Expand thin sections with genuine detail, examples, or data that competing pages don't have
• Consolidate near-duplicates into one strong page instead of three weak ones, using redirects to merge signals
• Rewrite for a clear search intent rather than a keyword, matching what someone actually wants when they type that query
• Remove or noindex low-value pages that were never going to earn a spot anyway, cleaning up your crawl footprint overall

Once the content is genuinely improved, use URL Inspection and request indexing manually. That's not a fix by itself, it just tells Google to look again sooner rather than waiting for the next natural crawl cycle.

For a full walkthrough of this exact scenario, including how to diagnose which specific quality issue is holding a page back, the founder's playbook for fixing Crawled – currently not indexed covers the diagnostic checklist step by step.