Crawled – Currently Not Indexed

TL;DR — “Crawled – currently not indexed” in Google Search Console means Google did visit your page but decided not to add it to its index. There’s no noindex, robots block, or canonical elsewhere in the way — those get their own separate statuses in Search Console. What’s usually left is a content- or site-quality question worth investigating, not a bug. Google says there’s no need to resubmit the URL; re-crawling the same page won’t change its mind. To get the page in, you have to make it (and your site) more worth indexing.

What the status means

When you open the Page Indexing report in Google Search Console (it used to be called Index Coverage), Google buckets your URLs by why they are or aren’t indexed. “Crawled – currently not indexed” means one specific thing: Googlebot fetched the page, but it is not currently indexed. Evidence for this claim Google defines Crawled - currently not indexed as a page crawled by Google but not indexed, which may or may not be indexed later. Scope: Google Search Console Page Indexing status; it does not by itself prove a single root cause. Confidence: high · Verified: 2026-07-14 Google: Page indexing report

The status describes the outcome, not a single proven cause. Check URL Inspection before concluding whether quality, duplication, canonicalization, rendering, or another factor is responsible.

Why Google does this

Crawling a page doesn’t guarantee it gets indexed. Google doesn’t index everything it finds — it makes a judgment call about whether a page is worth keeping. Once you’ve ruled out a technical block, these are the most common reasons pages land in this bucket — check them as hypotheses against the specific page, not as a guaranteed single cause:

• Thin — not much unique content, or not much useful content.
• Duplicate or near-duplicate — too similar to other pages (yours or someone else’s).
• Low value or low priority — Google doesn’t think the page adds enough to be worth a slot in the index.

And here’s the part people miss: it’s often not about that one page. It’s frequently about the quality of your whole site. If the site overall looks low-quality, individual pages get caught in that judgment too.

Is it a problem?

Not always. Some pages are supposed to sit here — junk URLs from filters and tracking parameters, thin tag or archive pages, near-duplicate variations. You don’t want those indexed anyway. Most sites have a pile of pages in this bucket and that’s normal.

It’s only a problem when a page you actually want in search — a real article, a product, a service page — is stuck in it.

Don’t confuse it with “Discovered – currently not indexed”

These two look similar and people mix them up constantly. The difference is whether Google fetched the page at all:

• Crawled – currently not indexed = Google did fetch it, looked at the content, and decided not to index it.
• Discovered – currently not indexed = Google knows the URL exists but hasn’t crawled it yet.

So “Crawled” is a quality decision Google made after seeing the page, and “Discovered” is a scheduling decision before it ever fetched the page.

What actually fixes it

Re-submitting the URL doesn’t help — Google literally says there’s no need to resubmit. Evidence for this claim Google's status guidance says there is no need to resubmit a Crawled - currently not indexed URL for crawling. Scope: Resubmission guidance for this Search Console status. Confidence: high · Verified: 2026-07-14 Google: Page indexing report Hitting “Request indexing” over and over on a page you haven’t changed does nothing, because the page hasn’t changed, so Google’s decision won’t either. What moves the needle is making the page (and the site) genuinely better: stronger content, fewer thin/duplicate pages, better internal links.

Want the full diagnosis-and-fix version, the decision tree, and what Google has actually said about it? Switch to the Advanced tab.

TL;DR — “Crawled – currently not indexed” is a Google Search Console Page Indexing status meaning Google fetched the page and then chose not to index it. It’s an index-selection decision, not a technical block — there’s no noindex, robots disallow, canonical-elsewhere, or error in the way. The most common causes to check are quality, value, duplication, or thinness, and it’s frequently a site-wide quality read rather than a single-page problem. Google says the page may or may not be indexed later and there’s no need to resubmit — re-crawling an unchanged URL changes nothing. It’s distinct from “Discovered – currently not indexed,” which is a pre-crawl scheduling/crawl-budget situation. Some URLs belong in this bucket (filters, parameters, thin tags, near-dupes) and should be consolidated or removed, not forced in. To recover pages worth recovering: rule out noindex/robots/canonical/soft-404, then improve content and overall site quality and strengthen internal linking.

What the status actually is

This is a status in Google Search Console’s Page Indexing report (formerly the Index Coverage report). Google’s own definition is exact: “The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.” Evidence for this claim Google defines Crawled - currently not indexed as a page crawled by Google but not indexed, which may or may not be indexed later. Scope: Google Search Console Page Indexing status; it does not by itself prove a single root cause. Confidence: high · Verified: 2026-07-14 Google: Page indexing report

Read that line carefully, because every practical decision flows from it:

• “crawled by Google but not indexed” — the fetch succeeded. This is not a crawl error, a server problem, or a robots block. Google downloaded the page and then declined to index it.
• “may or may not be indexed in the future” — it can self-resolve, and it can also stay this way indefinitely. The status is not permanent and not a penalty.
• “no need to resubmit this URL for crawling” — and this is the one people fight hardest. Evidence for this claim Google's status guidance says there is no need to resubmit a Crawled - currently not indexed URL for crawling. Scope: Resubmission guidance for this Search Console status. Confidence: high · Verified: 2026-07-14 Google: Page indexing report Because the cause is a decision, not a fetch failure, re-crawling the same unchanged URL does nothing. Validate Fix and Request Indexing on a page you haven’t materially changed are wasted clicks.

So this is the most quality-driven of all the “not indexed” reasons. When a page is crawled but not indexed and there’s no noindex, no robots block, no canonical pointing elsewhere, and no error, what’s left is Google judging the page — and often the site — as not worth indexing.

Crawled vs. Discovered – currently not indexed

This is the distinction I see conflated more than any other, so it’s worth nailing down. The whole difference is whether Google fetched the page:

Google’s wording for the sibling makes the timing explicit: the Discovered page “was found by Google, but not crawled yet.” In practice Google often rescheduled the crawl because fetching it then was expected to overload the site. So “Crawled” reflects a post-crawl index-selection decision and “Discovered” reflects a pre-crawl scheduling decision. If you’re seeing a lot of Discovered, look at server performance, internal linking, and reducing low-value URLs — not at content quality on the individual page.

Is it a problem? When to chase it and when not to

The honest answer most posts skip: a chunk of pages sitting in this bucket is normal, and not all of them are worth chasing. Indexing isn’t guaranteed, and a healthy site routinely has pages Google looked at and reasonably passed on.

Pages that should stay out — leave these alone, or better, stop generating them:

• Faceted-navigation, filter, sort, and parameter URLs (?color=, ?sort=, session IDs) — near-infinite low-value variants.
• Thin tag, category, and archive pages that are mostly a list with no unique value.
• Near-duplicate pages — boilerplate variations, printer-friendly copies, thin syndication.

For these, the right move isn’t to force indexing — it’s to consolidate, improve, or remove them (canonicalize, redirect, noindex, or block the pattern at the source). Forcing low-value pages into the index works against you: it’s exactly the kind of bloat that drags down the site-wide quality read that put your good pages here in the first place.

Pages worth recovering — a real article, product, or service page you wanted indexed that’s stuck here. That’s a genuine problem, and the rest of this is about those.

One more practical note: GSC counts and samples lag and can be stale. Don’t panic over the raw number alone, and don’t assume a page is still in this bucket just because the report says so — spot-check with URL Inspection.

Why Google crawls but doesn’t index

Index selection is fundamentally about quality and value. The causes I see, roughly in order:

• Thin / low-quality content — the page doesn’t offer enough unique, useful substance to earn a slot.
• Duplicate or near-duplicate content — too similar to other pages, so Google sees no reason to index another copy.
• Lack of relevance / search demand — nothing is really being searched for that this page uniquely answers.
• Site-wide quality — and this is the big one. The judgment is often about the whole website, not just the page’s text.

That site-wide angle is the part people underestimate. Improving one page in isolation frequently won’t help if the site overall reads as low quality — the direction is to lift the whole site’s quality, structure, and depth, not to polish a single URL and resubmit it.

There are also technical and economic factors that look like this status but aren’t really the quality story: a stray noindex, a robots block, a canonical pointing elsewhere, soft-404s, low authority, slow load, and poor architecture or internal linking. Rule those out first (the decision tree below) — if the page is clean technically, you’re left with a quality/value/priority call.

How to diagnose it

Work the page through this order before you conclude “quality.” Each step rules out a non-quality cause:

1. noindex? — Check the rendered HTML and HTTP headers for a stray noindex. A page set to noindex shouldn’t sit here, but mixed signals and rendering issues produce surprises. Rule it out.
2. Robots block? — Is the URL disallowed in robots.txt? (A blocked URL is usually reported differently, but check anyway, especially for resources the page depends on.)
3. Canonical elsewhere? — Does the page canonicalize to a different URL? If so, Google is treating that URL as the real one — by design, not a bug.
4. Soft-404 / error / empty render? — Does the page render real, unique content for Googlebot, or does it come back thin/empty (common on JS-heavy pages where the content needs JavaScript to appear)?
5. None of the above? — Then it’s a quality / value / priority call. Now you fix content and site quality, not technical plumbing.

Use URL Inspection to check how the live page is crawled and rendered, and to confirm what Google actually sees.

Report vs. live inspection — why they can disagree. The Page Indexing report shows Google’s last-known state and can lag behind the page’s current condition; URL Inspection’s live test shows what’s happening right now. A discrepancy between the two isn’t automatically a red flag — it can just mean the report hasn’t caught up. But the live test doesn’t cover everything the report does: duplicate content and canonical conditions specifically aren’t evaluated by the live test, so a clean live-inspection result doesn’t rule those out. Compare dates and current page state before treating either view as the final word.

How to fix it

Once you’ve confirmed it’s a quality call on a page you genuinely want indexed:

1. Improve content and overall site quality. Make the page genuinely worth indexing — unique, valuable, in-depth, clearly better than what’s already ranking. Then zoom out: because this is often a site-wide read, improving the surrounding content and cutting the dead weight raises the whole site’s standing, which is what actually lifts pages out of this bucket.

2. Consolidate or remove low-value pages. Counterintuitively, deleting, noindex-ing, or canonicalizing thin and duplicate URLs can help your good pages get indexed, by improving the overall quality signal and not diluting the site with junk. Don’t try to index everything.

3. Strengthen internal linking and architecture. Pages that are well-linked from relevant, indexed pages send a stronger “this matters” signal than orphans buried deep in the site. Make sure the pages you want indexed are reachable and linked from places that count.

4. Technical clean-up. Remove stray noindex, fix robots blocks that shouldn’t be there, correct canonicals, and clear soft-404s/server errors — so nothing technical is contradicting your intent.

5. Then — and only then — request a re-crawl. After you’ve meaningfully changed the page, use URL Inspection to request indexing. Doing this on an unchanged page is the thing Google explicitly tells you not to bother with.

Will it resolve on its own, and how long?

There’s no fixed timeline. “May or may not be indexed in the future” is literal: pages do sometimes get indexed later with no direct action, especially as overall site quality and links improve — and pages also stay here indefinitely if nothing changes. The lever isn’t time or resubmission; it’s whether the page and site become index-worthy. If you’ve made real improvements, give Google time to re-crawl and re-evaluate rather than hammering Request Indexing.

Common myths

A few things this status is not:

• “Just hit Request Indexing / Validate Fix until it works.” Google says no need to resubmit; re-crawling an unchanged page doesn’t change the decision. Evidence for this claim Google's status guidance says there is no need to resubmit a Crawled - currently not indexed URL for crawling. Scope: Resubmission guidance for this Search Console status. Confidence: high · Verified: 2026-07-14 Google: Page indexing report
• “It’s a bug or a penalty.” It’s neither — it’s a routine index-selection outcome, and most sites have pages here.
• “It’s purely a single-page problem.” It’s frequently site-wide quality, not just that one page’s text.
• “More links straight at the page will force it in.” You can’t force indexing. Authority helps site-wide quality, but thin/duplicate value is the real lever.
• “Every URL in this bucket must be fixed and indexed.” Many should stay out; chasing all of them wastes effort and can dilute site quality.
• “Adding it to the sitemap fixes it.” Sitemaps aid discovery, not index-worthiness — and the page was already crawled, so discovery wasn’t the problem.

For the bigger picture, this status lives inside the broader story of how Google indexes what it crawls, and sits next to its siblings in the Page Indexing report. The fixes here overlap heavily with avoiding index bloat — most of the “don’t force it” advice is really bloat management.

AI summary

A condensed take on the Advanced version:

• What it is. A Google Search Console Page Indexing status: Google crawled (fetched) the page but chose not to index it. Google’s definition — “crawled by Google but not indexed… may or may not be indexed in the future; no need to resubmit.”
• It’s a decision, not an error. No noindex, robots block, canonical-elsewhere, or fetch failure is in the way. Google looked and passed.
• Most common causes to check: quality/value. Thin, duplicate/near-duplicate, low-value, or low-priority content — and often site-wide quality, not just that one page. Treat these as hypotheses to test against the specific page, not a single guaranteed cause.
• Resubmitting doesn’t work. Re-crawling an unchanged URL changes nothing; only changing the page/site changes the decision.
• Crawled ≠ Discovered. “Crawled” reflects a post-crawl index-selection decision; “Discovered – currently not indexed” is a pre-crawl scheduling/crawl-budget situation (Google hasn’t fetched it yet).
• Some pages belong here. Filters, parameters, thin tags, near-dupes — consolidate or remove them, don’t force-index. Forcing low-value pages in is bloat that hurts the site-wide quality read.
• Diagnose in order: noindex → robots → canonical → soft-404/empty render → if clean, it’s a quality/value/priority call. Use URL Inspection.
• Fix: improve content & overall site quality, consolidate/remove low-value pages, strengthen internal linking, clean up technical contradictions — then request a re-crawl, only after meaningful changes.
• Timeline: none fixed. It can self-resolve as quality/links improve, or persist indefinitely. The report can lag the page’s current state — compare dates against a live URL Inspection, and remember the live test doesn’t check duplicate/canonical conditions either, so don’t treat either view alone as final.

Official documentation

Primary-source documentation from the search engines.

Google

• Page Indexing report — the report this status lives in, with the verbatim definitions of “Crawled – currently not indexed” and the sibling “Discovered – currently not indexed.”
• Crawling and indexing — the hub for how Google decides what to crawl and index, and the controls (robots, canonicals, noindex) you rule out when diagnosing this status.
• In-Depth Guide to How Google Search Works — the crawl → index → serve pipeline, and Google’s point that “not all pages make it through each stage.”
• Block search indexing with noindex — for the pages you want kept out (so you can deliberately remove low-value URLs instead of forcing them in).

Bing / Microsoft

• Bing Webmaster Guidelines — Bing doesn’t use this exact label, but its guidance on unique, valuable content and avoiding thin/duplicate pages is the same conceptual lever. (Confirm the current URL in your browser.)

Quotes from the source

On-the-record statements about this status. The Google help-doc lines below are deep-linked to the passage on the source page.

Google Search Console Help — the definitions

• “The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.” — Google Search Console Help, Page Indexing report. Jump to quote
• The sibling status, for contrast: “The page was found by Google, but not crawled yet…” — same doc. Jump to quote

John Mueller, Google — it’s site-wide, and you can’t force it

In the English Google SEO office-hours (June 28, 2021), responding to a “crawled – currently not indexed” question, John Mueller’s framing was that you can’t force pages to be indexed, that it’s normal for Google not to index every page on every site, and that the issue tends to be site-wide rather than about one specific page — so the direction is to improve overall site structure and quality.

He’s made the same point about what “quality” means: that Google doesn’t just mean the text of an article but the quality of the overall website — layout and design included.

Crawled – currently not indexed: diagnose & fix checklist

Run this on any URL you actually want indexed that’s stuck in this bucket:

Decide whether to chase it

• Confirm this is a page you genuinely want indexed (not a filter/parameter/thin tag/near-duplicate that should stay out).
• If it should stay out: consolidate (canonical/301), noindex, or stop generating the URL pattern — and move on.

Rule out non-quality causes (in order)

• No stray noindex in the rendered HTML or HTTP header.
• Not disallowed in robots.txt (page and its critical resources).
• The canonical points to itself, not a different URL.
• The page returns a real 200 with unique content — no soft-404, no empty render (check the rendered HTML, especially on JS-heavy pages).
• Checked with URL Inspection how Google crawls and renders the live page.

If it’s clean — treat it as quality/value

• Page content is genuinely unique, valuable, and in-depth (not thin or near-duplicate).
• Overall site quality addressed — thin/duplicate pages consolidated or removed, not just this one page polished.
• Page is well linked internally from relevant, indexed pages (not orphaned).
• Only after meaningful changes: request a re-crawl via URL Inspection.

Don’t

• Don’t repeatedly resubmit/Validate Fix an unchanged page.
• Don’t try to force every URL in this bucket into the index.
• Don’t panic over the GSC count alone — it lags; spot-check live.

The mental models

1. Crawled = a decision, not a failure. Nothing technical is blocking the page. Google fetched it and chose not to index it. Before you “fix” anything, internalize that the lever is Google’s index-selection judgment, not your server or your robots file.

2. The crawl-stage map: Discovered → Crawled → Indexed. “Discovered – currently not indexed” is before the fetch (scheduling/crawl-budget). “Crawled – currently not indexed” is after the fetch (quality/value). Place the URL on this map first — it tells you whether to look at server/crawl economics (Discovered) or content/site quality (Crawled).

3. Site-wide, not single-page. Treat this as a verdict on the whole site as often as on the one page. Polishing a single URL and resubmitting rarely works; raising overall site quality and cutting dead weight is what moves pages out of the bucket.

4. Some pages are supposed to be here. Indexing isn’t a goal in itself. Filters, parameters, thin tags, and near-dupes belong unindexed. The question isn’t “how do I index this?” but “does this page deserve a slot in the index?” — and frequently the answer is no.

5. Change the page, not the submit button. Because the cause is a decision, the only thing that changes it is changing the inputs. Re-crawling identical bytes yields the identical decision. Improve, then re-crawl — in that order.

Crawled – currently not indexed cheat sheet

Crawled vs. Discovered — currently not indexed

Decision tree (page is in “Crawled – currently not indexed”)

Should I even chase this URL?

Fast facts

• Google’s line: “may or may not be indexed in the future; no need to resubmit.”
• Re-crawling an unchanged URL changes nothing.
• Often a site-wide quality read, not a single-page issue.
• GSC counts lag — spot-check with URL Inspection, don’t trust the number alone.

Should you try to index this URL?

Mistakes that keep pages out

• Requesting indexing again without changing anything. Google already fetched the page. Improve the reason to index it before asking for another crawl.
• Treating the status as a crawl-budget error. The fetch happened; the decision is downstream. Investigate content, duplication, and site quality.
• Trying to index every filter, tag, and archive URL. Some pages should remain excluded. Consolidate or remove low-value inventory instead.
• Making cosmetic word-count changes. More text is not automatically more value. Resolve intent overlap and add information users cannot get from the indexed alternative.
• Diagnosing only the affected URL. Large low-value sections can shape site-level quality signals. Review templates and inventory patterns too.

Prompt: compare an excluded page with indexed alternatives

Compare the excluded page with the supplied indexed pages for intent, unique information, evidence, and duplication. Identify what the excluded page adds that cannot be obtained from the alternatives. Recommend one of: keep and materially improve, merge and redirect, canonicalize, noindex, or remove. Explain the evidence for the choice. Do not recommend resubmission unless a meaningful change is made.

[PASTE PAGE TEXT, CANONICAL/NOINDEX/STATUS EVIDENCE, INTERNAL LINKS, AND COMPARISON PAGES]

Prompt: find sitewide low-value patterns

Group this Page Indexing export by template and URL pattern. For Crawled – currently not indexed URLs, distinguish intended exclusions from pages meant to rank. Rank patterns by affected valuable URLs, then list the sample checks needed before changing a template. Do not infer quality from word count alone.

[PASTE SANITIZED EXPORT WITH URL, TEMPLATE, STATUS, CANONICAL, SITEMAP, AND INTERNAL-LINK DATA]

Flag common indexability signals in saved HTML

Run this in the DevTools Console on the live page:

({canonical: document.querySelector('link[rel="canonical"]')?.href || null, robots: document.querySelector('meta[name="robots" i]')?.content || null, title: document.title, textLength: document.body.innerText.trim().length, internalLinks: [...document.links].filter(a => a.hostname === location.hostname).length});

The output catches obvious signals; it cannot tell you Google’s selected canonical or indexing decision.

Extract excluded URLs from a CSV for sampling

If the exported CSV has a status column, Python can create a review sample without changing the source file:

import csv

with open("pages.csv", newline="", encoding="utf-8-sig") as f:
    rows = [r for r in csv.DictReader(f) if r.get("status", "").strip() == "Crawled - currently not indexed"]

for row in rows[:100]:
    print(row.get("url", ""))

Adjust the exact status text and column names to match the export.

Tools for diagnosis

• Google Index Checker checks observable status, redirect, noindex, and canonical signals, then routes you to Search Console for Google’s actual state.
• Canonical Checker helps surface declared-canonical conflicts and duplicate consolidation issues.
• Google Search Console URL Inspection shows the live test, last crawl, user-declared canonical, and Google-selected canonical for a sample URL.
• Google Search Console Page Indexing exports help group the status by directory and template instead of treating URLs one by one.
• A crawler plus server logs checks internal-link discovery, rendered signals, and whether Googlebot returned after a meaningful change.

Metrics for excluded-page recovery

Intended indexation rate

Metric: indexed URLs divided by URLs that are genuinely intended to rank. What it tells you: whether valuable inventory is represented without rewarding index bloat. How to pull it: classify canonical sitemap URLs by intent, then join to Search Console index status. Benchmark / realistic range: establish a template-level baseline; the denominator must exclude URLs that should not be indexed. Cadence: monthly.

Valuable-URL exclusion count

Metric: intended search pages in Crawled – currently not indexed. What it tells you: the size and concentration of the actual problem. How to pull it: export Page Indexing data and group by template or directory. Benchmark / realistic range: trend down after meaningful template or content fixes; no universal zero target fits every changing site. Cadence: monthly and after large releases.

Recovery after meaningful change

Metric: affected valuable URLs that move to indexed after a substantive fix. What it tells you: whether the intervention addressed selection rather than merely causing another fetch. How to pull it: maintain a dated cohort and recheck status plus impressions. Benchmark / realistic range: compare cohorts by fix type; do not invent a fixed recovery deadline. Cadence: at normal recrawl/indexing intervals until the cohort stabilizes.

Test yourself: Crawled – currently not indexed

Resources worth your time

My related writing

• What “Crawled – Currently Not Indexed” Means In Google Search Console — my Ahrefs deep dive on this exact status: the definition, the full cause list, and the fix process.
• The Beginner’s Guide to Technical SEO — where indexing fits in the bigger picture.

Official

• Page Indexing report (Google) — the verbatim definitions and the report itself.
• Crawling and indexing (Google) — the controls you rule out when diagnosing this.

From others

• How to fix GSC “Crawled – Currently not indexed” error (Search Engine Land) — Anna Crowe’s walkthrough, with relayed Mueller and Illyes remarks on index selection and quality.
• Crawled - Currently Not Indexed Possibly A Sign Of A Google Quality Issue (Search Engine Roundtable) — Barry Schwartz’s coverage of Mueller’s June 2021 office-hours remarks that this status reflects a site-wide quality assessment.
• Is Quality Why Your Pages Are Crawled but not Indexed? (JumpFly) — relays Mueller’s quote that “quality” means the entire website — layout, design included — not just the text of articles.
• Crawled - Currently Not Indexed: Meaning and Fixes (SEOTesting) — practical walkthrough and common fix patterns from the SEO testing community.
• Crawled – Currently Not Indexed (Rank Math KB) — carries Mueller’s “you can’t force pages to be indexed … it’s more site-wide” quote from the June 28, 2021 office-hours, with context.
• r/TechSEO — the community for crawl/index debugging.

Crawled – currently not indexed

A Google Search Console Page Indexing status meaning Googlebot fetched the page but Google decided not to index it — usually a content- or site-quality signal, not a technical error.

Related: Discovered – currently not indexed, Indexing, Index Bloat

Crawled – currently not indexed

“Crawled – currently not indexed” is a status in Google Search Console’s Page Indexing report (the report that used to be called Index Coverage). It means Googlebot successfully fetched and crawled the page, but Google chose not to add it to its index — at least not yet. There’s no robots block, no noindex, no canonical pointing elsewhere stopping it; Google simply decided the page wasn’t worth indexing.

Google says the page may or may not be indexed in the future, and that there’s no need to resubmit the URL. Re-crawling an unchanged page doesn’t change the decision. The fix is to change the page or the site so Google’s index-selection judgment changes — usually that means content quality, duplication, or thinness, and often it reflects the quality of the whole site rather than that one page.

It’s easy to confuse with its sibling, “Discovered – currently not indexed.” The difference is whether Google fetched the page at all: “Crawled” means Google saw the content and passed on it (a post-crawl quality call), while “Discovered” means Google knows the URL exists but hasn’t crawled it yet (a pre-crawl scheduling or crawl-budget call). Some pages — filter and parameter URLs, thin tag and archive pages, near-duplicates — are supposed to sit in this bucket, and the right move is often to consolidate or remove them rather than force them in.

Related: Discovered – currently not indexed, Indexing, Index Bloat

Changelog