Crawled, currently not indexed: a verdict, not an error

What “crawled but not indexed” actually means

Open Google Search Console, look at the Pages report, and find the row that says “Crawled, currently not indexed.” Most teams read that as a bug. They check the robots file, the canonical tags, the sitemap, and the internal links, and when all of that looks fine they get confused.

It is not a bug. It is a verdict. Google spent the crawl budget, evaluated the page against everything already ranking for that query, and decided it did not earn a slot. The page is not broken. It is just not worth showing, which makes the response a question of SEO strategy rather than technical repair. If your pages are missing from search entirely rather than sitting in this specific status, start with the broader diagnosis of why your website is not showing up on Google, then come back here for the quality-verdict case.

Crawling and indexing are not the same step. Crawling is Google fetching the page; indexing is Google deciding to store it and show it. Crawling happens first, so “crawled, currently not indexed” means the fetch happened and the decision went against you. Its sibling status, “discovered, currently not indexed,” means Google knows the URL exists but has not crawled it yet, usually a crawl-budget or priority issue that the robots.txt cleanup below also helps.

That reframing matters. But before you rewrite anything, separate the pages that are a real verdict from the ones that are just noise.

Not every flag in Google Search Console is a problem

Look at which URLs are actually in the report before you treat it as a crisis. A lot of the time, “crawled, currently not indexed” is noise you never wanted indexed in the first place: URLs with UTM and tracking parameters tacked on the end, old pages, staging pages, and backend or system pages. Google surfacing a URL in Search Console is not automatically a bad thing. Half the list is often stuff that should never be in the index anyway.

The fix for that half is not content. It is your robots.txt. Mass-block the parameter URLs, the staging paths, and the backend directories so Google stops crawling them. That does two things. It clears the noise out of the report so you can see the pages that actually matter, and it protects your crawl budget. With fewer junk URLs to crawl, Google spends its limited crawl on the pages you care about, so when you ship a real change it gets recrawled and reindexed faster. You can only request so many URLs a day, so every wasted crawl is a real cost.

What is left after the cleanup is the part worth your attention: real, public-facing pages that Google crawled, evaluated, and still chose not to index. That is the verdict.

Why it is happening now: Information Gain

Information Gain is the signal doing the judging. It was filed as a patent in 2018, granted in June 2024, and re-weighted hard in the March 2026 core update, the one where roughly 80% of top-three results shifted and close to one in four top-ten pages fell out of the top hundred. It scores how much genuinely new knowledge your page adds relative to the set of documents the searcher has already seen. Repeat what is already out there and you score low. Add original analysis, proprietary data, or a net-new framing and you score high.

So the pattern is consistent: ranking losses, a rise in “crawled but not indexed,” and traffic decline on listicle content all point to the same root cause. Google raised the quality bar, and pages that mostly synthesize what already ranks get filtered before they ever compete.

You see it most clearly right after a core update. On one B2B SaaS account I run, “crawled, currently not indexed” jumped from 268 to 332 URLs during the March 2026 core update, after holding steady for months. The update did not break anything. It re-weighted Information Gain, and a batch of thin pages stopped clearing the bar.

The blog playbook that won in 2024 and 2025, which was to cover the topic, target the keyword, and publish a long ten-item list, is the exact format being demoted. Length and keyword coverage are not differentiators anymore. They are table stakes.

How to tell a verdict from a real technical problem

Before you accept the quality verdict, rule out a real technical cause, the same basics a full SEO audit checks first, so do not skip them. Sometimes the “crawled, currently not indexed” reason is not content at all: check for a stray noindex tag, a canonical pointing somewhere else, 5xx server errors, a robots block, and true duplicate content. WordPress is worth a careful look here, because a mis-set SEO-plugin option, tag and category archives, or paginated pages will show up as “crawled, currently not indexed” WordPress URLs that are configuration, not content, so audit your Yoast or Rank Math indexing settings before rewriting anything. Check that the page is not orphaned: a page with no internal links pointing to it gives Google little reason to prioritize it, so add links from related pages. If a cluster of pages drops out at once right after a template change, suspect the template.

But if the page is technically clean and still sits in “crawled, currently not indexed,” stop debugging and start reading the page like Google did. Ask the honest question: what does this page say that the top five results do not already say better? If the answer is nothing, you have your verdict.

What you see	Likely cause	The fix
Tracking-param, staging, or backend URLs	Noise you never wanted indexed	Block in robots.txt
Orphaned page, stray noindex, bad canonical, 5xx	A real technical problem	Fix the tag, link, or server
A cluster drops out after a template change	Suspect the template	Roll back or fix the template
Page is technically clean, still not indexed	A verdict: low Information Gain	Add a point of view and proprietary data

The fix: perspective and proprietary data

Two things separate a page that gets indexed from one that does not.

The first is a defensible argument instead of a neutral overview. Every page should take a position you can summarize in a sentence. “5 best [category] platforms” is being demoted across the board. “Why most [category] platforms fail in [segment], and what to do about it” still performs, because a reader, and a model, can tell you what it argues and why.

The second is original or proprietary data on the page. Stats borrowed from Gallup, SHRM, or McKinsey are commodity data. They appear on every competing page, so they add no gain. The data points that get cited by Google and by LLMs are first-party: customer outcomes, internal benchmarks, original survey data, named results. If a page cannot anchor on at least one proprietary number or first-hand example, it should not ship in its current form.

This is not only a blog problem. The same logic runs through product and feature pages. On a legal SaaS account I run, a batch of platform pages sat in “crawled, currently not indexed” for weeks. The pages were technically clean. The real issue was the headers: on the legal CRM hub, the target keyword was not in the H1 or the H2 at all. The H1 was a benefit statement. We made “Legal CRM” the H1, moved the benefit statement down to the H2, and pulled a real customer number into the section it supported. Across the platform set, 65 pages recovered indexation within five weeks. The pages that came back were the ones we gave the keyword, an argument, and a number. You can see the fuller version of that rebuild in the legal SaaS case study.

Test before you scale

The principles above are well established post-March, but the size of the lift depends on your competitive landscape and your current indexation patterns. So do not rewrite the entire library at once. Pick a small set, including a couple of pages currently flagged “crawled but not indexed,” rewrite those, and hold the rest as a control.

Track each test page for four to six weeks: does the index status resolve, do the target rankings move, does organic traffic and on-page engagement improve, and does the page start getting picked up in AI answers. If the test set beats the control, roll it out. If results are mixed, adjust before scaling. If they regress, revert and reassess. That is the same discipline I use to isolate any single change, and it is how you avoid betting the whole site on a theory. (For a clean example of changing one variable and measuring it, see the schema single-variable test.)

FAQ

Is “crawled, currently not indexed” a penalty?

No. It is not a manual action or a penalty. It is Google choosing not to index a page it judged low-value for the query. There is nothing to appeal, only the page to improve.

Is this normal for a new site?

Yes. New sites routinely have pages sit in “crawled, currently not indexed” while Google decides whether they are worth showing. Give it time, make sure each page earns its place, and do not panic over the count alone.

How long does it take to get indexed after a rewrite?

Plan for four to six weeks to read a result, longer on large sites where recrawling takes time. Request indexing for the updated URL, but do not expect an instant flip.

Will adding more words fix it?

No. Length is not the lever. A longer version of the same commodity content scores the same on Information Gain. Add a point of view and a proprietary data point instead.

Should I worry about every “crawled but not indexed” URL?

No. A lot of them are noise you never wanted indexed: tracking-parameter URLs, old pages, staging pages, and backend pages. Block those in robots.txt, which also frees crawl budget, and focus on the real, public-facing pages that are left.

Does this apply to product and feature pages too?

Yes. Feature pages that pair a keyword-only header with thin, repetitive copy are exposed to the same quality reset. Give each section a clear intent and differentiated content beneath it.

What is the difference between crawling and indexing?

Crawling is Google fetching the page; indexing is Google deciding to store it and show it in results. Crawling happens first, so “crawled, currently not indexed” means the fetch happened and Google then chose not to index the page. They are separate steps, which is why a page can be crawled and still never appear in search.

How do you fix “crawled, currently not indexed”?

You fix “crawled, currently not indexed” by improving the page, not by changing a setting, because it is a quality verdict rather than a technical error. Add genuine Information Gain: a point of view, first-party data, or specifics a competing page does not have, so the page earns a place in the index instead of repeating what Google already has ten times over. Then resubmit the URL through the Inspect tool and request indexing. Do not just add words or rebuild the sitemap; a longer version of the same commodity content gets the same verdict.

What is the difference between “discovered, currently not indexed” and “crawled, currently not indexed”?

“Discovered, currently not indexed” means Google knows the URL exists but has not crawled it yet, often a crawl-budget or priority signal. “Crawled, currently not indexed” means Google did fetch the page and then chose not to index it, which is a quality judgment. Discovered is “we have not looked yet”; crawled-not-indexed is “we looked and passed.” The fix for discovered is usually about crawlability and internal links; the fix for crawled-not-indexed is about making the page worth indexing.

How do I force Google to reindex a page?

You cannot truly force it, but you can prompt it: open the URL in Search Console’s URL Inspection tool and click Request Indexing after you have meaningfully improved the page. That queues a recrawl, but indexing still depends on Google judging the page worth showing, so a resubmission without real changes lands right back in “crawled, currently not indexed.” Plan for four to six weeks to read the result, longer on large sites.

Why does my “Validate Fix” keep failing in Search Console?

A crawled currently not indexed validation failed status usually means the same thing every time: validation only passes when Google actually indexes the pages, and clicking Validate Fix does not change Google’s judgment of them. If the pages are still thin, duplicative, or commodity, the validation fails no matter how many times you resubmit. Fix the underlying reason, add real perspective and first-party value, or accept that low-value pages should be consolidated or pruned, and the validation passes on its own. A failed validation is feedback about the page, not a bug to retry around.