Crawled – Currently Not Indexed

What "Crawled – currently not indexed" means in Google Search Console — Google fetched the page but chose not to index it, usually a content- or site-quality call. How it differs from "Discovered – currently not indexed," when to chase it, and how to fix it.

First published: Jun 23, 2026 · Last updated: Jul 17, 2026 · Advanced
demand #7 in Indexing#30 in How Search Works#153 in Technical SEO#207 on the site
1 evidence signal on this page

"Crawled – currently not indexed" is a Google Search Console Page Indexing status: Google fetched the page but chose not to index it. There's no robots block, noindex, or canonical stopping it — it's an index-selection decision, usually about content quality, duplication, or thinness, and often about the quality of the whole site rather than that one page. Google says the page may or may not be indexed later and there's no need to resubmit, so re-crawling an unchanged URL won't help. It's distinct from "Discovered – currently not indexed," which is pre-crawl (scheduling/crawl-budget). Some pages — filters, parameters, thin tag/archive pages — are supposed to stay in this bucket; consolidate or remove them rather than force them in. To recover pages worth recovering: rule out noindex/robots/canonical/soft-404, then improve content and overall site quality and strengthen internal linking.

TL;DR — “Crawled – currently not indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.” is a Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. Page IndexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. 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-crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. 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 linkingAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them..

What the status actually is

This is a status in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason. (formerly the Index Coverage reportThe Google Search Console report (renamed from \"Index Coverage\" in 2022) that shows which URLs Google has indexed, which it hasn't, and why. It splits your known URLs into Indexed and Not indexed, grouping the not-indexed ones by reason.). 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 crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor..” 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: 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: 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:

Crawled – currently not indexedA 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.Discovered – currently not indexedA Google Search Console Page Indexing status meaning Google knows the URL exists but hasn't crawled it yet — the Last Crawl date is empty. Often a crawl-capacity or crawl-demand (site-quality) signal.
Did Google fetch the page?Yes — it was crawledNo — Google knows the URL but hasn’t crawled it yet
When the decision happensAfter seeing the contentBefore ever fetching it
Typical root causeQuality / value / priority call on the contentCrawl scheduling / crawl-budget / server-load call
What to fixContent & overall site quality, duplication, thin pagesThin content is web content that provides little or no value to users. Google's spam policies name it 'thin content with little or no added value' — and it's about value per page, not word count.Site/server performance, internal linkingLinks between pages on the same site., crawl prioritization, cutting low-value URL bloat

Google’s wording for the sibling makes the timing explicit: the Discovered page “was foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. 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.

The Last Crawl field tells you which stage failed: Crawled is post-fetch selection; Discovered is pre-fetch scheduling. Source: Google Search Console Help

Google knows the URL. On the Discovered currently not indexed branch, Google has not fetched it, the Last Crawl field is empty, and diagnosis focuses on crawl priority or capacity. On the highlighted Crawled currently not indexed branch, Google fetched the page but did not index it, the Last Crawl field has a date, and diagnosis focuses on index selection, page value, duplication, rendering, and conflicting signals.

© Patrick Stox LLC · CC BY 4.0 ·

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-duplicateThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. 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, redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., 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 contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. — 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 renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. 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 GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer., 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 reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason. 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.

TIP Reconcile current page signals with the exported index state

Compare a sitemap inventory, a fresh crawl export, and a Search Console export without pretending a public fetch can see Google's private index state using my free Indexation Reconciler Free

  1. Export the affected URLs from Search Console and supply a current crawl plus the intended sitemap inventory.
  2. Separate URLs whose current technical signals changed from URLs that remain fetchable and indexable.
  3. Return to URL Inspection for Google’s actual crawl, render, and canonical evidence before assigning the cause.

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.
  • “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 sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. 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 bloatAn SEO term for when a search engine has indexed a lot of low-value, thin, or duplicate URLs that don't serve search demand. It's a quality and crawl-efficiency problem, not a penalty. — most of the “don’t force it” advice is really bloat management.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.