You open Search Console, check a page you care about, and get the status that annoys site owners more than any other: Crawled, currently not indexed. Google visited your page. Google read it. Google decided not to show it to anyone. Nothing is marked as broken, there is no error to fix, and the page just sits there.
Here is what the status actually means, and how I approach it on client sites.
The short answer
Crawled, currently not indexed means Google fetched your page, read it, and chose not to store it in the index, so it cannot appear in search results yet. It is not an error and it is not a penalty; it is a quality decision, and Google revisits that decision as the page and the site change. In my client ledgers the cause is almost always one of four things: thin content, near-duplicate pages, weak internal linking, or a site whose overall standing makes Google index selectively. Fix the cause, resubmit once, and the status usually moves. Resubmit without changing anything and it usually does not.
Indexing is a two-step decision
Crawling and indexing are separate things. Crawling means Google fetched the page. Indexing means Google decided the page is worth storing in its index, which is what makes it eligible to appear in results at all.
Crawled, currently not indexed means step one happened and step two did not. It is not a penalty and it is not a bug. It is Google saying: I saw this page, and I am choosing not to keep it right now. The word “currently” is genuine, because the decision gets revisited as your site changes. And if your status says Discovered instead of Crawled, Google has not even fetched the page yet, which is a different problem with different fixes.
Why does Google decline to index a page?
Across the client sites I have worked on, the same few patterns account for almost every case.
Thin content. The page does not say enough to be worth storing. Category pages with two products, location pages with three sentences, tag archives with no text at all. Google crawled it, found little, and moved on.
Near duplicates. The page is too similar to another page Google already has: product variants, city pages that swap only the city name, printer-friendly versions. Google keeps one and declines the rest.
Weak internal linking. Nothing on your own site points at the page, so nothing on your own site vouches for it. Google reads that exactly the way it sounds.
The site’s overall standing. Newer sites and sites with a history of thin pages get less stored, page for page, than established ones. On a site like this Google indexes selectively, and pages that would sail into the index on a stronger domain get held at the door.
What this looks like in real numbers
Most articles about this status are written from documentation. Here is what it looks like from inside the ledgers. Across the public case studies, thousands of URLs are tracked one by one, and on a typical backlog this status is the biggest bucket by far: not errors, not blocks, just pages Google fetched and declined. The longest single job on record here took 1,006 hand submissions across 118 days to walk a store catalogue from mostly ignored to mostly indexed.
Two patterns repeat on every job. Pages flip to indexed within days once the actual cause is fixed, sometimes the same day. And pages that get resubmitted without any change refuse to move for months, because nothing about Google’s question changed. Store catalogues are the worst offenders on both counts; if yours is on Shopify, the platform-specific version of this problem has its own guide.
What does not fix it?
Pressing Request Indexing over and over on an unchanged page. If the page did not clear the bar yesterday, submitting the same page today rarely changes the answer. Request Indexing is a doorbell, not a key.
The Validate Fix button gets the same honesty. Most articles tell you to hit it, so people hit it and wait. Validation asks Google to re-check the affected pages, and if the pages have not changed, the re-check returns the same verdict. Validation confirms a fix you already made. It is not a fix.
Indexing bots and automated submission tools do not fix it either. They violate Google’s guidelines, most of them stopped working after the Indexing API crackdowns, and the ones that limp on put your site at risk for a status that was never about submission in the first place.
What actually fixes it?
You change Google’s answer to the only question it is asking: is this page worth storing?
First, substance. The page needs to say something a competitor’s page does not. On e-commerce sites this often means real category descriptions and product detail instead of boilerplate. On local service sites it means location pages with genuinely local content, which is a discipline of its own. Substance also means matching what the searcher actually wanted: a page can be long and still get declined because it answers the wrong question for the query Google sees it as a candidate for.
Second, internal links. Link the page from pages that already rank, from navigation, from related content. Give Google a reason to believe you care about this page.
Third, deduplication. If two pages compete, merge them or set a canonical so Google knows which one to keep.
Then, and only then, resubmit by hand and track what happens. On client jobs I have watched a page flip from this status to indexed the same day the cause was fixed. I have also watched clean, well-linked pages take weeks while Google made up its mind. Both are normal, and the full timelines from tracked URLs are here. It is why every job I run ends with a per-URL ledger instead of a promise: every page marked indexed, pending, or fixed, with dates, so you can watch the decision change.
Where this fits in my work
Diagnosing which of these patterns applies is the first step of every indexing job I take. If the cause turns out to be thin content, the fix crosses into content work, and I will say so instead of resubmitting pages that will keep getting declined. The results of that approach are public: case studies tracked URL by URL, including catalogues that went from mostly ignored to mostly indexed.
If your Search Console is full of Crawled, currently not indexed, send me the site. I will tell you which pattern is doing it, free, usually within a day. No obligation.
Quick answers
What are the main causes of crawled, currently not indexed?
Four patterns cover almost every case in my client ledgers: thin content that does not say enough to be worth storing, near-duplicate pages competing with each other, weak internal linking that leaves the page unvouched for, and a site whose overall standing makes Google index selectively. Most stuck pages combine two of these.
What is the difference between crawled and discovered, currently not indexed?
Crawled means Google fetched the page and declined to store it, so the page itself is the problem. Discovered means Google knows the URL exists but has not fetched it yet, which points at crawl priority and internal links instead. The fixes are different, which is why the two statuses should never be treated as one.
Is crawled, currently not indexed a penalty?
No. It is a quality decision about individual pages, not a sanction against the site. Google fetched the page, judged it not worth storing, and moved on. Change what made it decline and the decision gets re-made.
Does Validate Fix solve crawled, currently not indexed?
No. Validate Fix only asks Google to look again; it changes nothing about the page. If the content that was declined is still the same, validation ends the same way. In practice fixing first means changing what made Google decline: rewrite the thin or templated content, strengthen the internal links pointing at the page, then request indexing once. Validation after a real change passes; validation after no change fails on schedule.
How many crawled, currently not indexed pages are normal?
On a large catalogue, some residue is normal, because Google rarely stores every variant and filter page. It becomes a problem when pages you need to rank sit in the status for weeks. Those are the ones worth fixing and resubmitting.