"Crawled – Currently Not Indexed" in Google Search Console: Why It Happens & How to Fix It

Few statuses in Google Search Console cause as much confusion as "Crawled – currently not indexed." You open the Page indexing report, expecting to find a broken canonical tag or a stray noindex, and instead you find a list of perfectly accessible URLs that Google has visited and then quietly declined to add to its index. There's no error to fix, no redirect to undo, no robots rule to delete. The page works. Google just doesn't want it.

That's exactly why this status is so frustrating, and so often misdiagnosed. Unlike most indexing problems, "Crawled – currently not indexed" is rarely a technical fault. It is, in the overwhelming majority of cases, a judgment call. Google's systems crawled the URL, evaluated it, and decided it didn't earn a place in the index right now. That "right now" matters too: the status is not permanent, and pages can move out of it. But they usually only do so when something about the page, or the site around it, changes.

This guide is a focused deep-dive on what the status actually means, the real underlying causes (most of which trace back to content value rather than crawl mechanics), how to diagnose which cause applies to your URLs, and a concrete fix playbook. We'll also draw a sharp distinction between this status and its close cousin, "Discovered – currently not indexed," because the two get conflated constantly and the fixes are completely different.

What "Crawled – Currently Not Indexed" Actually Means

The wording is precise, and each part tells you something. Crawled means Googlebot successfully fetched the URL. The server responded, the page rendered, and Google has the content. Currently means the decision is provisional rather than final. Not indexed means that, despite having the content, Google chose not to store it in a way that makes it eligible to appear in search results.

In other words, this is the stage after crawling. Google has already spent the crawl budget. It has seen the page. The bottleneck is not access, it is selection. Google indexes a subset of the pages it crawls, and selection is driven heavily by perceived quality, uniqueness, and usefulness relative to everything else already in the index.

This is the single most important mental model to hold: "Crawled – currently not indexed" is almost always a value signal, not a crawl signal. The page cleared the technical bar (it was reachable and renderable) but did not clear the quality bar. That reframes the entire troubleshooting process. You are not hunting for a misconfiguration. You are asking a harder question: why doesn't Google think this page deserves to be in the index?

It's worth saying plainly what this status does not usually mean. It does not mean your site is penalized. It does not mean there's a manual action. It does not mean Googlebot was blocked (if it were, you'd see a different status). And it does not guarantee the page will never be indexed; pages routinely transition into the index later, especially after improvements or as the site earns more authority.

Crawled vs. Discovered – Currently Not Indexed

These two statuses sit next to each other in the report and sound nearly identical, but they describe opposite problems.

Discovered – currently not indexed means Google knows the URL exists (it found the link, usually via your sitemap or internal links) but has not crawled it yet. The page hasn't been fetched. This is fundamentally a crawl-budget and scheduling signal. Google is deciding whether the URL is worth the resources to crawl at all, and large or low-authority sites with many thin URLs often see big clusters here. The fixes revolve around crawl efficiency, site authority, internal linking, and signalling that the URLs are worth fetching. We cover that case in depth in our guide to Discovered – currently not indexed.

Crawled – currently not indexed means Google has already taken the next step. It fetched the page, evaluated the content, and then declined to index it. Because the content has been seen, crawl budget is no longer the issue. The issue is what Google found. This is a quality and value signal.

| | Discovered – currently not indexed | Crawled – currently not indexed | |---|---|---| | Did Google fetch the page? | No | Yes | | Primary signal | Crawl budget / scheduling | Content quality / value | | Typical trigger | Too many low-priority URLs, weak authority | Thin, duplicate, or low-value content | | Main fix lever | Internal linking, sitemaps, site authority | Improve, consolidate, or prune content |

If you take one thing from this contrast: when a URL is Discovered, you're trying to convince Google the page is worth crawling. When it's Crawled, you've already won that argument and lost the next one — you now need to convince Google the page is worth keeping.

The Real Causes

Because the status is a value judgment, the causes cluster around content quality and how a page fits into the wider landscape of what's already indexed. Here are the ones that actually account for most cases.

Thin or low-value content

The most common cause. The page exists, but it doesn't offer enough substance, depth, or original insight to justify a slot in the index. This isn't strictly about word count — a short page can be valuable and a long page can be empty. It's about whether the page meaningfully helps someone with the query it targets. Boilerplate, auto-generated summaries, and pages that restate common knowledge without adding anything tend to land here.

Duplicate or near-duplicate content

When several pages cover essentially the same thing, Google may index one and leave the rest as "Crawled – currently not indexed." Note that this is distinct from the "Duplicate without user-selected canonical" and "Alternate page with proper canonical tag" statuses, which involve explicit canonical relationships. Here, the pages aren't formally canonicalized to each other — Google has simply decided they're redundant and only one is worth keeping. Faceted navigation, near-identical location or service pages, and lightly reworded variants are classic offenders.

Doorway and programmatic pages at scale

Programmatically generated pages — thousands of "[service] in [city]" permutations, tag archives, thin filter combinations — frequently get crawled and then dropped. Google has become very good at recognizing when a large set of URLs is produced from a template with little unique value per page. If most of the content is identical except for a swapped-in keyword, expect this status.

Content that doesn't add value versus what already ranks

Even genuinely well-written content can stall here if it's redundant with what's already indexed and ranking for the topic. If your article says the same things as the ten pages already on page one, Google has little incentive to add an eleventh near-copy. The bar isn't "is this good?" — it's "does this add something the index doesn't already have?"

Weak E-E-A-T and site-level quality signals

Indexing decisions aren't made purely page by page. A new or low-authority site, or one with a large proportion of weak pages, can find that even decent individual pages struggle to get indexed because the site hasn't established enough trust. Experience, expertise, authoritativeness, and trustworthiness operate at the site level as well as the page level.

Weak internal linking and orphaning

A page buried deep in the architecture, linked from nowhere meaningful, sends a quiet signal that even the site's owner doesn't consider it important. Internal links are how you communicate priority. Pages with little or no internal support are easier for Google to deprioritize.

Genuinely new pages still being evaluated

Sometimes the status is just temporary. A freshly published page can sit in "Crawled – currently not indexed" briefly while Google decides. If a page is days old, has no obvious quality issues, and is otherwise sound, the right move is often patience plus a few supporting signals rather than a rewrite.

How to Diagnose Which Cause Applies

Don't guess. The same status hides several different problems, and the fixes diverge sharply, so spend time identifying the actual pattern before you change anything.

Start with the URL Inspection tool. For a representative affected URL, run it through URL inspection and view the crawled page. Confirm Google rendered the content you expect (not an empty shell from a JavaScript rendering failure, which can make a page look thin to Google even when it looks full to you). Check the canonical Google selected versus the one you declared.

Look for patterns across the affected list. Export the URLs from the Page indexing report and look at them as a group. Are they all from one section, one template, one CMS content type? A cluster from /tag/ or a faceted filter parameter points to duplication or programmatic thinness. A scattering across your best content points to something more site-wide, like authority or rendering.

Compare affected pages to your indexed ones. Take an indexed page and an unindexed one on a similar topic and read them side by side. Be honest about whether the unindexed page is genuinely thinner, more derivative, or more redundant. This comparison usually reveals the cause faster than any tool.

Search for what already ranks. Run the target query and see what's on page one. If your page is a weaker version of results that already exist, you've found your problem: redundancy, not technicality.

Check internal links and crawl depth. Identify how many internal links point to the affected URLs and how deep they sit. Orphaned or near-orphaned pages need structural help. Our broader walkthrough of index coverage errors can help you place this status in the context of everything else the report is telling you.

The Fix Playbook

Once you know the cause, the response follows. The table maps causes to fixes; the sections expand on the most important moves.

| Cause | Primary fix | |---|---| | Thin / low-value content | Add genuine depth, originality, and usefulness; raise the page above the index baseline | | Duplicate / near-duplicate | Consolidate into one strong page; redirect or canonicalize the rest | | Doorway / programmatic pages | Add unique value per page or remove the thin set entirely | | Redundant vs. what ranks | Differentiate with a unique angle, data, or depth — or merge into a stronger asset | | Weak E-E-A-T / site quality | Strengthen authorship, trust signals, and overall site quality; prune weak pages | | Weak internal links / orphaning | Link from relevant, authoritative pages; reduce crawl depth | | Newly published, still evaluated | Add internal links and supporting signals, then allow time |

Improve depth and uniqueness

For thin or redundant pages, the only durable fix is to make the page genuinely better than what's already in the index. That means original information, firsthand experience, useful specifics, and a clear reason for the page to exist. Ask what this page offers that the ranking results don't, and build the answer into the content. If you can't articulate that reason, the page may not need to exist at all — which leads to the next move.

Consolidate duplicates

When multiple pages compete for the same intent, pick the strongest, fold the useful parts of the others into it, and 301-redirect or canonicalize the rest to your chosen URL. One strong, comprehensive page almost always outperforms several thin ones, and consolidation removes the redundancy that triggered the status in the first place.

Prune or noindex low-value pages

Not every page deserves to be indexed, and that's fine. For tag archives, thin filter pages, or programmatic permutations that will never carry standalone value, the right answer is often deliberate removal: noindex them, consolidate them, or remove them entirely. This also has a site-level benefit — reducing the proportion of weak pages can improve how Google perceives overall site quality, which helps your good pages. Counterintuitively, the fix for many "not indexed" pages is to stop trying to index them.

Strengthen internal links and topical authority

Give your important unindexed pages meaningful internal links from relevant, well-established pages. Build out topic clusters so related content reinforces each other and signals genuine depth on a subject. This both raises perceived importance and helps Google understand where the page fits. If you're working on a storefront and your product URLs are stuck here, our guide to Shopify product pages not indexed covers the e-commerce-specific patterns. For the bigger picture of turning Search Console data into ongoing improvements, see how to use Google Search Console to improve SEO and our framework for a Search Console SEO audit.

Request indexing — but only after you've fixed something

Using "Request Indexing" in URL Inspection is reasonable after you've materially improved a page, because it nudges Google to re-crawl and re-evaluate. It is not a fix on its own. Repeatedly requesting indexing for an unchanged thin page won't change Google's decision, and it isn't the lever that moves pages out of this status. Improve first, then request.

A realistic note on expectations

Be honest with yourself and your stakeholders: there is no button that forces indexing, and not every page should be indexed. Some pages will stay in this status because Google's assessment of their value is, frankly, correct. The goal isn't to game indexing — it's to produce pages worth indexing. When you do that, the status tends to resolve on its own as Google re-crawls.

If you want help turning your actual Search Console data into prioritized, depth-focused content briefs — so you're improving the pages most likely to earn indexing — Search Console Tools is free and connects securely with Google OAuth.

Frequently Asked Questions

Is "Crawled – currently not indexed" an error I need to fix?

No, it's a status rather than an error, and Google won't flag it as something blocking your site. It means Google fetched the page but chose not to index it, usually for quality or value reasons. You only need to act if these are pages you genuinely want indexed and they offer real, unique value.

How long does it take to get out of "Crawled – currently not indexed"?

There's no fixed timeline. For genuinely new pages, it can resolve within days to weeks as Google finishes evaluating. For pages with real quality or duplication issues, it won't resolve until you make meaningful changes and Google re-crawls, which can take weeks after the fix.

Will requesting indexing fix it?

Requesting indexing only prompts a re-crawl; it doesn't override Google's quality assessment. If you request indexing on an unchanged thin page, Google will likely make the same decision again. Improve the page first, then use Request Indexing to speed up re-evaluation.

What's the difference between this and "Discovered – currently not indexed"?

"Discovered" means Google knows the URL exists but hasn't crawled it yet, which is a crawl-budget and scheduling signal. "Crawled" means Google has already fetched and evaluated the page and chosen not to index it, which is a content-quality signal. The fixes differ: Discovered needs better crawl prioritization and internal linking, while Crawled needs better, more unique content.

Can thin content really cause this even if the page works fine?

Yes, and it's the most common cause. A page can be technically perfect — fast, accessible, error-free — and still be passed over because it doesn't add enough value beyond what's already indexed. Google selects which crawled pages to index based largely on usefulness and uniqueness, not just whether the page loads.

Should I just noindex pages stuck in this status?

Often, yes. If a page will never offer standalone value — like thin tag archives or near-duplicate filter pages — deliberately noindexing, consolidating, or removing it is the right call. Reducing the share of low-value pages can also improve how Google perceives your site overall, which helps your pages that do deserve to rank.