Back in 2021, a local solicitors' firm in Manchester came to Seahawk after their blog had been sitting dead in Search Console for four months. Forty-three posts. Zero indexed. Every single one showing "Crawled, currently not indexed." Their previous agency had shrugged and told them Google was "just being slow." I pulled up the site in an afternoon and had a root cause within ninety minutes. Thin content, duplicate meta descriptions across practice area pages bleeding into the blog crawl budget, and a misconfigured Yoast sitemap pointing at noindexed category archives.
That phrase, "Crawled, currently not indexed," is one of the most maddening statuses Google Search Console can show you. It means Google found the page. It spent resources downloading it. And then it looked at what was there and said: not worth it. Understanding why Google makes that call, and fixing it systematically, is something I've had to get very good at across 12,000+ sites.
---
What "Crawled Currently Not Indexed" Actually Means
There's a common misconception that this status means Google hasn't got round to indexing yet. That's not what it means. Google has crawled the URL. It has made a deliberate choice not to include it in the index. That's a different problem entirely, and it requires a different response.
The two broad causes are quality signals and technical signals. Quality signals: Google doesn't think the page adds enough value to serve users. Technical signals: something in your setup is confusing Googlebot or contradicting your intent. Both are fixable. Neither fixes itself.
Worth reading Google's own documentation on how Google Search works if you want to understand the pipeline from crawl to index. It's dry but useful.
---
Step One: Pull the Full Picture in Search Console
Don't guess. Open Google Search Console and go to Pages (formerly Coverage). Filter to "Crawled, currently not indexed." Export the list. You want the full URL set, not just a sample.
I then cross-reference that list against a Screaming Frog crawl of the same site. Every time. Screaming Frog will tell you the page's word count (via the custom extraction or the built-in readability metrics), whether it's in the XML sitemap, its canonical tag status, its meta robots directive, internal link count to the page, and response code. That combination tells you most of what you need.
What I'm Looking For First
- Pages with fewer than 300 words of body copy
- Pages with identical or near-identical meta descriptions to other indexed pages
- Pages not included in the XML sitemap
- Pages receiving zero internal links
- Orphaned pagination URLs or thin archive pages getting crawled
In the Manchester solicitors case, the blog posts averaged 180 words. That was the core issue. Everything else was secondary.
---
The Quality Problem: Google Thinks Your Page Isn't Good Enough
This is uncomfortable to hear but it's the most common cause I see. Google's quality threshold has moved considerably since 2022. Pages that would have quietly sat in the index three years ago are now being actively excluded.
Thin Content
If a page has less than 400-500 words and doesn't have strong E-E-A-T signals (author bio, citations, original insight), Google will often crawl it and park it. I've seen this particularly with:
- WooCommerce product pages with manufacturer copy pasted verbatim
- Real estate listing pages with two-line property descriptions
- Location pages built from a template with only the city name swapped
- Old FAQ pages that answer one question in a paragraph
The fix is not just adding words. Adding filler makes it worse. The fix is adding useful specific information that a human would actually want to read. For the solicitors, I rewrote their blog posts to include real case outcomes (anonymised), specific UK legislation references, and worked examples. Word counts went from 180 to 900. Eight weeks later, thirty-one of the forty-three posts were indexed.
Duplicate and Near-Duplicate Content
Screaming Frog's duplicate content report is your friend here. But also run the URLs through Copyscape or Siteliner if you're worried about cross-site duplication. I've had clients in the e-commerce space where their supplier was providing the same product description to forty other retailers. Google indexes one and ignores the rest. That's not a bug, it's working as intended.
Internal near-duplication is sneakier. If you've got a site with service pages for "Plumber in Leeds," "Plumber in Sheffield," "Plumber in Bradford," and they're 95% identical apart from the city name, Google is going to pick one and suppress the rest. I've seen this pattern cause entire faceted search systems to fall into "Crawled, currently not indexed" hell.
---
The Technical Problem: Something in Your Setup Is Sending Mixed Signals
Sometimes the content is genuinely good and Google is still refusing to index. This is where you dig into technical signals.
Canonical Tag Confusion
This is the number one technical culprit I find. A page is canonicalised to itself (correct), but somewhere upstream, a category page or a paginated URL has a canonical pointing at the page you want indexed. Google sometimes interprets this as a signal that the canonical source is a duplicate. I've seen WordPress themes do this automatically in ways that are genuinely hard to spot without a crawl.
Check: does every page in your "Crawled, currently not indexed" list have a self-referencing canonical? Does anything else on the site have a canonical pointing at these URLs unexpectedly?
XML Sitemap Issues
Your sitemap should only list URLs you actively want indexed. That sounds obvious. In practice, Yoast, Rank Math, and most other SEO plugins will cheerfully include noindexed pages, paginated URLs, and tag archives in your sitemap if you're not careful. Google sees a URL in your sitemap, crawls it, finds a noindex or thin content, and that's a wasted crawl credit, plus a trust signal that you don't really know what you're doing with your site.
I audit sitemaps with a simple process:
- Download the sitemap XML
- Import every URL into a spreadsheet
- Run each URL through Screaming Frog (or use the bulk export)
- Flag any URL that is noindexed, redirects, or returns a non-200 status
- Remove those URLs from the sitemap
This alone has cleared "Crawled, currently not indexed" statuses for three clients in the last year. Without touching the content at all.
Internal Linking Gaps
PageRank (yes, still relevant, yes, even in 2024) flows through internal links. A page with zero internal links pointing to it is effectively invisible to Googlebot in terms of authority. Google may crawl it via the sitemap and then decide it's not important enough to index because nothing on the site is pointing to it.
Orphaned pages are common. I use Screaming Frog's "Orphan URLs" report (under Site Structure) to find them. Add three to five relevant internal links to every page that's sitting in the "not indexed" bucket and you'll often see movement within four to six weeks.
---
Crawl Budget: When It's Genuinely a Capacity Problem
For smaller sites (under 1,000 pages), crawl budget is almost never the real issue. I know people throw this explanation around a lot. But for large e-commerce sites (we had a fashion retailer at Seahawk with 80,000 SKUs), it genuinely matters.
If Googlebot is spending its visits crawling your infinite faceted navigation, your session ID parameters, or your internal search results pages, it's not getting to the product pages that actually matter. The Google documentation on crawl budget is one of the few pieces of official SEO guidance I'd actually recommend reading start to finish.
Fix: block URL parameters that generate near-duplicate pages via the URL Parameters tool (if you're still using the old Search Console) or via robots.txt for Googlebot, and make sure your internal search pages are noindexed. This frees up crawl capacity for the pages that matter.
---
Requesting Indexing: When to Use It and When Not To
The "Request Indexing" button in Search Console is useful for high-priority individual URLs after you've made changes. It is not a substitute for fixing the underlying cause. I see freelancers hitting that button compulsively on pages they haven't touched. It does nothing on its own.
My rule: fix first, request second. After you've made substantive changes to content, canonical tags, or internal linking, submit the URL via the URL Inspection tool. Give it two to four weeks. If it's still not indexed after that, the underlying problem isn't fixed yet.
One more thing: the request indexing quota is limited. Don't burn it on pages that still have thin content or broken canonical setups. You're just asking Google to confirm its own decision.
---
How Long Does It Take to Clear?
Honestly, it varies more than most SEO guides admit. I've seen pages flip from "Crawled, currently not indexed" to indexed within five days of a content update. I've seen others take twelve weeks. The factors that seem to matter most:
- How much authority the domain has overall (older, linked-to domains see faster reconsideration)
- Whether the fix was content-related (slower) or technical (faster)
- How often Googlebot visits the site (check the Crawl Stats report in Search Console)
Set a tracking spreadsheet. Note the date you made changes. Check back in Search Console every two weeks. Don't panic if nothing moves in week one.
---
FAQ
Why does Google crawl a page but then not index it?
Crawling and indexing are separate steps in Google's pipeline. Crawling just means Googlebot downloaded the page. Indexing means Google decided it's worth showing in search results. The gap happens when Google's quality assessment determines the page doesn't add enough value, duplicates existing content in the index, or contains conflicting signals like a noindex tag somewhere in the chain.
Does submitting a URL in Search Console guarantee indexing?
No. It puts the URL in a priority queue for review but Google still makes its own quality decision. If the page has thin content or technical issues, submitting it just speeds up Google confirming it won't index it.
Can a page be indexed after being stuck in this status for a long time?
Yes, absolutely. I've cleared URLs that had been sitting in "Crawled, currently not indexed" for over a year, once the content was properly improved. Google re-evaluates. It's not a permanent blacklist. That said, if a page has been in that status for more than six months, it's worth asking honestly whether it deserves to be indexed at all.
Is this status the same as "Discovered, currently not indexed"?
No, and the distinction matters. "Discovered, currently not indexed" means Google knows the URL exists but hasn't crawled it yet. It's often a crawl budget or internal link problem. "Crawled, currently not indexed" means it's already been evaluated and set aside. Both need attention but the fixes are slightly different.
---
There's no single magic fix for "Crawled, currently not indexed." In my experience, it's almost always a content quality issue or a technical signal problem, and usually a combination of both. Start with the data, fix what you find, and give it time. Google's not trying to punish you. It just needs a reason to care about the page. Give it one.