Crawled, Currently Not Indexed: What It Means and How to Fix It

“Crawled – currently not indexed” means Googlebot fetched the page, read it, and decided against adding it to the index — it’s a quality and relevance judgment, not a technical error. The fix almost never involves changing a meta tag; it involves changing the page itself: consolidating thin content, sharpening search intent, fixing broken structured data, or removing pages that duplicate a stronger one already ranking. Search Console’s Page Indexing report groups this under “Not indexed,” alongside “Discovered – currently not indexed,” but the two statuses point at different problems and need different fixes.

Sites see this status pile up most often after a content push: fifty near-identical location pages, a blog category that republishes the same product description with a different headline, or a set of thin FAQ pages built for a schema markup test. None of them are broken. Google just doesn’t think they’re worth a slot.

What does “Crawled – currently not indexed” actually mean?

In the Page Indexing report inside Google Search Console, every URL Google knows about lands in one of two buckets: indexed, or not indexed. Within “not indexed,” Google separates URLs it hasn’t crawled yet from URLs it has crawled and rejected. “Crawled – currently not indexed” is the second group — the page loaded fine, Googlebot read the full content, and the indexing decision came back negative.

This matters because it rules out the usual technical suspects. The page isn’t blocked by robots.txt (that would show as “blocked by robots.txt”). It doesn’t have a noindex tag (that would show as “excluded by noindex tag”). It returned a normal 200 status. Google simply looked at the content and the surrounding signals and concluded the page doesn’t add enough value to justify a place in the index right now.

How is this different from “Discovered – currently not indexed”?

These two statuses get confused constantly because they sit next to each other in the same report, but they describe opposite problems.

A page moving from “Discovered” to “Crawled – currently not indexed” is actually a sign of progress in one sense — Google looked at it — and a warning sign in another, because the content itself is now the thing being judged, not the crawl schedule.

What actually causes this status?

Across audits on sites of varying sizes, the same handful of causes account for nearly every case. None of them are exotic.

• Thin or low-effort content. Pages built to satisfy an internal template — a location page with one paragraph swapped for a city name, a tag archive with three posts — rarely clear Google’s bar.
• Duplicate or near-duplicate content. Product variants, syndicated articles, and near-identical service pages compete with each other, and Google indexes one and drops the rest.
• Unclear or absent search intent. A page that doesn’t clearly answer one query, or that mixes several unrelated topics, gives Google no strong reason to rank it over a more focused competitor.
• Structured data errors. Malformed or contradictory schema markup can confuse Google about what the page is actually for, adding friction to the indexing decision.
• Weak internal and external signals. A page with no internal links pointing to it and no external mentions gives Google little evidence that it’s worth surfacing.

The pattern across all five is the same: none of them are fixed by a plugin setting. They require either improving the page or removing it.

How do you fix a page stuck in this status?

The sequence below is the one that consistently moves pages out of “Crawled – currently not indexed” without wasting a recrawl request on an unchanged page.

Five steps to fix Crawled – currently not indexed

• Audit the affected URL cluster — Start here. Pull the full list from Search Console, group by template or topic.
• Decide: keep, merge, or remove — Triage. Thin near-duplicates get merged; templated filler gets removed.
• Fix the content and structured data — Core fix. Add real depth, fix schema errors, sharpen the target query.
• Strengthen internal links — Signal boost. Link to the page from a relevant, already-indexed page.
• Request indexing on changed pages only — Last step. Reserve the quota for pages that actually changed.

Consolidation is usually the highest-leverage move on step two. If ten pages are all “Crawled – currently not indexed” and they cover the same core topic with minor variations, merging them into one comprehensive page — and 301-redirecting the rest — often fixes all ten at once, because the surviving page now carries the combined relevance signal instead of splitting it.

Should you request indexing for every affected page?

No. Requesting indexing in Search Console has a daily quota, and firing it at a page that hasn’t actually changed since Google’s last crawl produces the same verdict, just later. Reserve the request for pages where you’ve made a real content or structured data change. For everything else, fix the content first and let Google’s normal recrawl schedule pick it up, or improve internal linking so the page gets recrawled sooner as a side effect of higher priority in the crawl queue.

For sites where this status affects a large batch of URLs at once — after a CMS migration, a bulk import, or a template change — it’s worth reading through how orphan pages get found and fixed, since orphaned pages with no internal links are disproportionately likely to end up crawled but not indexed. Pairing that audit with a clean sitemap index file structure makes it easier to track which URLs Google is choosing to skip once the content fixes go live.

When should you remove the page instead of fixing it?

Not every page stuck in this status is worth saving. If a page exists purely to satisfy an internal template, has no search demand behind its target query, and duplicates content that already ranks elsewhere on the site, removing it is usually faster and cleaner than trying to improve it into indexability. The right removal method depends on the situation — a look at the difference between 404, 410, a redirect, and noindex is worth reading before deciding, since picking the wrong one can leave the URL cycling back through the same “crawled, not indexed” status for months.

This decision — fix, merge, or remove — is the same triage exercise covered in the broader technical SEO guide, and it’s usually the single biggest lever for shrinking a bloated “not indexed” count in Search Console.

Frequently asked questions

What does “Crawled – currently not indexed” actually mean?

It means Googlebot successfully fetched the page but decided, after evaluating it, not to add it to the search index. This is different from a crawl error or a blocked page: Google saw the content and judged it not worth indexing right now, usually on quality, uniqueness, or intent grounds.

How is this different from “Discovered – currently not indexed”?

“Discovered” means Google knows the URL exists but has not crawled it yet, often due to crawl budget or scheduling. “Crawled – currently not indexed” is a step further: the page was fetched and read, and Google made an active decision to leave it out of the index.

How long does it take for a page to move out of this status?

There is no fixed timeline. Google re-evaluates pages on its own recrawl schedule, which can range from days to several weeks depending on the site’s crawl frequency. Requesting indexing in Search Console can prompt an earlier recrawl, but it does not guarantee indexing if the underlying quality issue is still unresolved.

Does requesting indexing in Search Console fix the problem?

It only forces a recrawl, not indexing. If the page’s content or signals haven’t changed since the last crawl, Google will likely return the same verdict. Fix the underlying cause first, then request indexing so Google evaluates the improved version.

Can thin or duplicate content cause this status even without technical errors?

Yes. This is the most common cause. A page can have a valid canonical, no noindex tag, and a clean crawl, and still land here purely because Google judged the content too thin, too similar to another indexed page, or too generic relative to the query it targets.

Sources

• Page Indexing Report — Search Console Help
• Googlebot Crawling Overview — Google Search Central
• Technical SEO: The Complete Working Guide