Discovered vs. Crawled – Currently Not Indexed: What Each Google Search Console Status Actually Means

If you've spent any time in the Page Indexing report, you've probably seen both of these sitting in the "Why pages aren't indexed" table: Discovered – currently not indexed and Crawled – currently not indexed. They sound almost identical, they're both colored the same shade of "not good," and Search Console gives you exactly one line of explanation for each. Naturally, most people assume they're the same problem with two names.

They're not. One is about Google not having gotten around to your page yet. The other is about Google visiting your page and deciding, at least for now, not to index it. Mixing them up leads to the wrong fix — and the wrong fix means the status just sits there for another crawl cycle while you wait.

Two Different Problems Wearing the Same Warning Label

Both statuses live under the same "Not indexed" umbrella in Search Console, and both mean the URL isn't in Google's index right now. That's where the similarity ends.

• Discovered – currently not indexed: Google knows the URL exists — usually from a sitemap, an internal link, or an external link — but has not crawled it yet. There's no content judgment happening here because Google hasn't looked at the page at all.
• Crawled – currently not indexed: Google has crawled the page. It fetched the HTML, rendered it, read it — and then chose not to add it to the index.

In other words, Discovered is a queue problem. Crawled is a judgment problem. Treating a judgment problem like a queue problem (e.g., just requesting indexing again and again) is the single most common reason people feel stuck on this status for weeks.

What "Discovered – Currently Not Indexed" Actually Means

This status is Google's crawl scheduler saying "I have this URL on my list, but I haven't prioritized it yet." Common causes:

• Crawl budget constraints — large or low-authority sites get crawled more slowly, so newly discovered URLs can sit in the queue for days or weeks.
• Weak internal linking — a page that's only reachable through a sitemap, with no internal links pointing to it, signals low importance to Google's crawler.
• Low overall site authority — new domains or domains with thin backlink profiles simply get smaller crawl allocations.
• Server response issues — if Googlebot has recently hit slow response times or errors on your site, it may deliberately throttle crawling.

The reassuring part: this status usually resolves on its own once Google's crawler gets to the URL. The frustrating part: "usually" can mean anywhere from a few days to over a month on sites Google doesn't crawl frequently.

What "Crawled – Currently Not Indexed" Actually Means

This one is more serious because it means Google already evaluated the page and decided it wasn't worth indexing — at least not yet. The most frequent underlying reasons:

• Thin or low-value content — pages that don't add enough unique substance beyond what's already indexed elsewhere on the web (or on your own site).
• Near-duplicate content — pages that overlap heavily with another URL on your domain, without a clear canonical signal.
• Quality threshold, site-wide — if a meaningful share of your site is thin or templated, Google can become more conservative about indexing new pages from that same domain, even good ones.
• Recently published, low-authority page — sometimes it's not a quality issue at all — it's a new page on a site that hasn't yet earned enough trust for Google to index every new URL by default.

If you're seeing this status on pages you're confident are genuinely useful, the fix is rarely "wait." It's usually "strengthen."

How to Fix Each One

For Discovered – currently not indexed:

1. Add or strengthen internal links from pages Google already crawls frequently (your homepage, top navigation, or high-traffic posts).
2. Confirm the URL is in your sitemap and that the sitemap is submitted in Search Console.
3. Check server logs or Search Console's Crawl Stats report for response-time or error spikes that might be throttling Googlebot.
4. Be patient before requesting indexing repeatedly — repeated manual requests on a page still sitting in the discovery queue rarely speed things up and can sometimes get rate-limited.

For Crawled – currently not indexed:

1. Read the page the way a stranger arriving from search would. Does it say something a dozen other pages don't already say?
2. Check for duplicate or near-duplicate content on your own site and consolidate or canonicalize where appropriate.
3. Add genuinely useful specifics — data, examples, screenshots, original analysis — rather than restating general knowledge.
4. Build a small number of relevant internal and external links pointing to the page to reinforce that it matters.
5. Only after making real content changes, request indexing again. Requesting indexing on an unchanged page that Google already evaluated and passed on will not change the outcome.

Why This Distinction Matters More Than It Looks

The cost of confusing these two statuses isn't just wasted time — it's misdiagnosis. If you keep requesting indexing on a page stuck in Crawled – currently not indexed, you're not addressing the actual reason Google skipped it, so nothing changes between requests. And if you rewrite content on a page that's simply stuck in Discovered – currently not indexed, you're solving a problem that was never about content quality in the first place.

The fastest way to know which situation you're actually in is to check the status directly in the Page Indexing report before deciding on a fix — the label tells you which playbook to use.

Keeping an Eye on This Without Living Inside Search Console

Both of these statuses can shift between crawls, and Search Console itself doesn't proactively tell you when a page moves from one bucket to another or finally gets indexed. Traffic Monitor pulls your Search Console data automatically and flags meaningful changes — including when pages move in or out of "not indexed" states — so you're not manually re-checking the Page Indexing report every few days to see if anything changed.

If you're dealing with a batch of pages stuck in either status, start by separating them into the two buckets above. It's a five-minute sort, and it's the difference between fixing the real problem and repeating a fix that was never going to work.