Crawled – Currently Not Indexed: What It Means

"Crawled – currently not indexed" means Googlebot fetched your page, read it, and decided not to store it in the index. It is a quality and priority judgement, not a technical error. Nothing is blocking the page — Google simply didn't think the URL was worth keeping, at least for now.

That last clause matters. "Currently" is doing real work in the label: the status is reversible, often without you touching the page, and a page can move into the index weeks after you stopped watching. It is also the status that generates the most wasted effort, because the instinct is to look for a bug that isn't there.

How it differs from the other exclusions

The Page indexing report in Search Console uses similar-sounding labels for very different situations. Getting the diagnosis right starts here.

Status	What happened	Where the fix lives
Crawled – currently not indexed	Fetched and read; not stored	Content and internal signals
Discovered – currently not indexed	Known about; never fetched yet	Crawl capacity, server speed, priority
Excluded by 'noindex' tag	Fetched; you told it not to index	Remove the directive
Indexed, though blocked by robots.txt	Never fetched; indexed from links	The disallow rule
Alternate page with proper canonical tag	Fetched; consolidated into another URL	Nothing, usually — this is correct behaviour
Duplicate, Google chose different canonical	Fetched; judged a copy of another URL	Differentiate or consolidate deliberately

The two that get confused are the first two. Discovered means Google hasn't spent a request on the URL yet — typically a capacity or priority decision, common on large sites and slow servers. Crawled means it spent the request and passed. A page sitting in Discovered may need nothing more than patience or a faster server; a page sitting in Crawled has been evaluated and found wanting.

The last two rows are worth a glance before you start rewriting anything. If the page is really a near-copy of something else on your site, Google may be putting it in the Crawled bucket for the same underlying reason it puts other pages in the duplicate buckets, and the fix is consolidation rather than expansion.

Six reasons Google declines to store a crawled page

In rough order of how often each one is the real cause:

The page adds nothing the index doesn't already have. Not necessarily thin — it can be 2,000 words — but if every claim on it appears on twenty other pages, there's no reason to store a twenty-first copy. This is the dominant cause, and it's uncomfortable to accept because the page usually looks fine.
It's a near-duplicate of your own content. Templated pages that vary by one variable, tag archives listing the same posts, product variants with identical copy. Google keeps one and quietly drops the rest. Does duplicate content hurt SEO covers what actually happens in that case.
Nothing on your site points to it. A URL that exists only in the sitemap carries no internal signal of importance. Google will crawl it and treat it accordingly — see what is an orphan page in SEO.
The site is new or low-trust. On a young domain, Google indexes conservatively and expands as the site proves itself. Pages that were skipped in month one often index in month four with no changes at all.
The URL is functionally low-value. Pagination beyond page two, filter and sort parameters, internal search results, thin tag pages. These should be excluded, and the status is the system working correctly.
Site-level quality is dragging the page down. Indexing decisions aren't made purely per URL. A site with hundreds of near-identical pages gets less benefit of the doubt on the next one, which is the mechanism behind Google's warnings about scaled content.

Working out which one applies

Four checks, cheapest first:

Read the page cold. Ask what a reader gets here that they can't get from the top three results for the same query. If you can't answer in a sentence, cause 1 is your answer and no amount of technical work will fix it.
Search a distinctive sentence from the page in quotes. If similar text appears on your own site elsewhere, you're in cause 2. If it appears on other sites, you may have a syndication or scraping problem that made your version look like the copy.
Count internal links to the URL. A site crawl, or Search Console's Links report, will tell you. Zero or one means cause 3, and it's the fastest of all of these to fix.
Look at the shape of the list. If the affected URLs are overwhelmingly parameters, pagination and tag pages, that's cause 5 and you should be pruning rather than fixing. If the list is mostly real articles on a site under a year old, cause 4 is likely and patience plus links is the plan.

The fixes that actually move a page

Merge rather than expand. Two mediocre pages on overlapping topics usually index better as one strong page with a 301 from the loser. This also removes a keyword cannibalization problem you probably had anyway.
Add something only you can provide. Original data, a real example with numbers, a first-hand account, a screenshot of something you actually ran. This is the E-E-A-T argument in its most practical form — see what is E-E-A-T in SEO.
Link to it from your strongest relevant pages. Not the footer, not a sitemap listing — in-content links with descriptive anchors from pages that already get crawled often. This is the single highest-yield action for most affected URLs, and what are internal links in SEO covers how to place them.
Get one genuine external link. A page other sites reference is a page Google has a reason to store. It also gives the crawler a second discovery path.
Prune what shouldn't exist. Noindex the pagination, tag pages and parameter URLs. Removing 400 pages Google was never going to index makes the report readable and concentrates crawling on the pages that matter.

Then request indexing once, and leave it. Repeated submissions do nothing — the queue position doesn't improve with pressure.

What doesn't work

Three things that consume time and change nothing: resubmitting the same unchanged URL weekly; pinging or resubmitting your sitemap (Google re-reads it on its own schedule regardless); and paid "instant indexing" services, which typically send links through low-quality networks and can create a backlink profile problem you didn't have before. Google's Search Essentials is clear that indexing is not guaranteed for any URL, and no third party has a lever on it.

How long to give it

After a substantive change, expect a recrawl within days to a few weeks, and a further wait before the index decision updates. Two to eight weeks is a reasonable window before you conclude a fix didn't work. On a new site, some pages index after several months with no intervention, so read a large Crawled bucket on a young domain as a signal about the domain's standing rather than about each individual page.

That standing is largely earned off-site. A domain nothing links to has little to persuade Google that its pages deserve storage — which is why external links are as much an indexing lever as a ranking one. Backlinkster is a 1-for-1 exchange where site owners in related niches trade in-content links and every placement is verified live by code; free accounts get five verified swaps a month, and the plans are here. Can you rank without backlinks covers where that does and doesn't matter.

Frequently asked questions

What does "Crawled – currently not indexed" mean in Search Console? Google requested the page, received it, and chose not to add it to the index. It is a quality and priority decision rather than a technical block — nothing is preventing indexing, and the URL can be indexed later without any change on your side.

Is "Crawled – currently not indexed" a penalty? No. It's a routine exclusion, not a manual action or algorithmic penalty. Every site of reasonable size has URLs in this state, and many of them are pages that should never be indexed anyway.

What's the difference between "Crawled" and "Discovered – currently not indexed"? Discovered means Google knows the URL exists but hasn't fetched it, usually a crawl-priority or server-capacity issue. Crawled means it fetched the page and declined to store it, which points at content, duplication or internal linking instead.

How do I fix "Crawled – currently not indexed"? Make the page genuinely distinct from what's already indexed, add in-content internal links from strong related pages, earn at least one external link, and request indexing once. If the URL is a tag page, parameter or pagination URL, noindex it instead — the exclusion was correct.

How long does it take to get indexed after fixing the page? Usually days to a few weeks for the recrawl, then more time for the index decision to update. Allow two to eight weeks before deciding a change didn't work. New domains can take considerably longer.

Will requesting indexing repeatedly help? No. One request per URL after a real change is enough. Resubmitting an unchanged page doesn't improve its chances and can't override the underlying judgement.

The bottom line

This status is Google telling you it has read the page and isn't convinced. Resist the urge to hunt for a configuration bug — check the page against what already ranks, check whether anything on your site links to it, and check whether the URL should exist at all. Most affected URLs fall into one of two groups: pages that need to be genuinely better, and pages that should be pruned. Very few need a technical fix.