Google’s HCU Is Inside the Core Algorithm Now: What Actually Changed
In March 2024, Google folded the helpful content classifier into its core ranking system. Most recovery advice still treats the Helpful Content Update as a separate event you can wait out. It stopped being one more than two years ago — and that single change rewrites the timing, the diagnosis, and what “waiting” even means.
What does it mean that HCU is “baked into core”? Google’s helpful content classifier stopped being a standalone, announced update in March 2024 and became one signal inside the continuously-running core ranking system. Three practical consequences: (1) there is no “next HCU refresh” to wait for — assessment is continuous; (2) visible re-rating now tends to arrive with broad core updates instead of a dedicated helpful-content update; and (3) the effect is still site-level, so a body of unhelpful pages can suppress your good ones. The merge did not make recovery impossible. It changed the timing and the diagnosis, not the mechanism.
There has been no update named “helpful content update” since 14 September 2023. In the years since, Google has shipped 17 ranking updates — nine core updates, seven spam updates and one Discover update. Not one of them carried the helpful content name.
This page is kept current. Every date below comes from Google’s own Search Status Dashboard, which is the only authoritative record of when an update ran.
Is the helpful content update still a thing?
No — not as a named, separate event. Google shipped exactly three of them, and then stopped:
That is the entire list. If you are searching for the next one to arrive so your site can be re-rated, you are waiting for something Google stopped making nearly three years ago.
What replaced it is not a mystery either. Announcing the March 2024 core update on 5 March 2024, Google wrote that it “marks an evolution in how we identify the helpfulness of content”, and then the sentence that matters most:
“We have enhanced our core ranking systems to show more helpful results using a variety of innovative signals and approaches. There’s no longer one signal or system used to do this.” — Google Search Central, 5 March 2024
Read that precisely, because most write-ups get it wrong. Google did not say the classifier was moved intact into core. It said there is no longer one system doing this job. The single switch became many signals, distributed through core ranking. That is why nothing gets “turned back on” for you, and why there is no toggle to flip.
What does “baked into core” actually mean?
Before March 2024, the Helpful Content Update behaved like a discrete event. Google ran it, announced it, and you could point at a date on a chart. The guidance that followed was simple to the point of being comforting: improve the content, then wait for the next run of the classifier to re-assess your site.
That model no longer exists. Google announced with the March 2024 core update that the helpful content system had been integrated into its core ranking systems, and it retired the standalone “Helpful Content Update” label. The public documentation was rewritten around creating helpful, reliable, people-first content rather than around a named update you could be hit by.
Mechanically, the important word is continuous. The assessment is not a job that runs on a schedule you can wait for. It is part of how pages are evaluated on an ongoing basis. What is not continuous is the visible outcome — large re-ratings still tend to surface when Google ships a broad core update, which is why sites often sit flat for months and then move in a single week.
Why is “wait for the next HCU” now wrong advice?
This is the practical failure I see most often, and it costs people months.
A site gets hit. The team does real work — prunes thin pages, rewrites weak ones, adds genuine expertise. Then they stop, and they wait for an announcement that is never going to come, because there is no longer a dated helpful-content event to target. Six months later nothing has been published, nothing further has been improved, and the assumption is that recovery failed.
There is nothing to time your comeback to. You cannot ship the work the week before an HCU refresh, because there is no HCU refresh. The only sensible posture is to make the site genuinely better and keep it that way, then read the leading indicators rather than waiting for a headline.
How long does HCU recovery take now?
Recovery got slower to confirm, not necessarily slower to earn.
Because meaningful re-rating tends to land with broad core updates, and Google ships those every few months, the gap between finishing the work and seeing the result is now measured against Google’s core update calendar rather than a helpful-content one. In practice that means 2–6 months is a normal wait, and some sites need two or three core updates to be fully re-assessed.
The work itself has not changed much. If you want the actual sequence — diagnose, cut, rebuild, monitor — that is laid out step by step in our Helpful Content Update recovery playbook, and the broader mechanics of core updates are covered in recovering from a Google core update. This article is about what the merge changed, not how to do the work.
The site-level effect did not go away
This is the part people most want to be untrue. The helpful content assessment has always behaved as a site-wide signal rather than a page-by-page one, and folding it into core did not change that.
The consequence is uncomfortable but useful: your strongest pages can be held down by the proportion of weak ones around them. That is why recovery work that only polishes the best content usually fails, and why removing or consolidating the long tail of mediocre pages often moves things when rewriting the top ten does not. You are changing a ratio, not fixing individual articles.
The spam policies you also inherited in March 2024
The merge did not arrive alone. Alongside the same core update, Google introduced explicit policies for scaled content abuse, site reputation abuse and expired domain abuse.
This matters for diagnosis. A site that lost traffic in or after March 2024 is not automatically an HCU case. It may be caught by one of those policies instead, and the remedies are different — a site publishing mass-generated content and a site hosting third-party “parasite” pages need almost nothing in common to fix. Recovery is now a question about the whole quality framework, not one classifier.
How can you tell whether re-evaluation is going your way?
Since there is no announcement to wait for, you have to read the instruments. In rough order of what moves first:
- Impressions before clicks. Google testing you again shows up as impressions returning at poor positions long before those positions become useful traffic.
- Position distribution, not average position. Average position is a blunt number. Look at how many queries sit in positions 11–20 versus 21–50 — movement between those bands is the earliest honest signal.
- Which pages come back first. Recovery is usually uneven. The pages that return earliest tell you what Google now considers your legitimate territory, which is useful information about where to invest next.
- Crawl behaviour. Pages being fetched again after months of neglect is a signal in its own right, visible in Search Console’s page indexing reports.
Be honest with yourself reading these. A move from 30 clicks a day to 70 is a real signal and is also not a recovery if the site used to do 10,000. Both things can be true, and conflating them is how people talk themselves out of finishing the work.
What we still don’t know
Plenty, and anyone claiming otherwise is guessing with confidence.
The May 2024 Google API documentation leak surfaced attribute names — siteAuthority, siteFocusScore, hostAge, a contentEffort score — that map suggestively onto what the classifier appears to measure. Their existence is now public record. How they are weighted, or whether they are used the way their names imply, is not. Treat the leak as evidence that these things are measurable quantities, not as a recipe to optimise against.
We also do not know how much of a site needs to change before re-assessment tips, and there is no reconsideration request for an algorithmic re-rating. There is no button, no queue, and no one to appeal to. That is genuinely different from a manual action, and it is the single most important thing to understand before you start.
Will there ever be another helpful content update?
On the evidence, no — and the question is worth retiring, because it shapes how people wait.
Google's stated position is that helpfulness is now assessed by many signals inside core ranking rather than one system. A system that no longer exists as a discrete component cannot be updated as a discrete component. Seventeen ranking updates have shipped since September 2023 without the name reappearing, which is about as clear as behavioural evidence gets.
The practical translation, if you are sitting on a drop:
- The event you are waiting for is the next core update, not the next HCU. In 2026 that meant two opportunities all year — 27 March and 21 May.
- “HCU recovery” and “core update recovery” now describe the same work. Anyone selling them as different products is selling you the 2023 version of this problem.
- A drop during a spam update is a different problem entirely. Those enforce written policies — scaled content abuse, site reputation abuse, expired domain abuse — and no amount of quality work fixes a policy violation.
The one thing that would change this answer is Google announcing a new named system. If that happens, this page gets updated the same week — that is what the status date at the top is for.
Frequently asked questions
Is the Helpful Content Update gone?
The standalone update is gone; the assessment is not. Google integrated the helpful content system into its core ranking systems with the March 2024 core update and retired the separate “Helpful Content Update” name. The evaluation continues as part of core ranking — what disappeared was the discrete, announced event, not the scrutiny.
Will there be another HCU update to wait for?
No. There is no separate helpful-content refresh scheduled or coming, which is exactly why “finish the work and wait for the next HCU” is now bad advice. Significant re-ratings tend to become visible during broad core updates instead, and those arrive every few months without being tied to helpful content specifically.
Can a site still recover now that HCU is part of core?
Yes. Being folded into core made recovery harder to time, not impossible to achieve. The requirement is unchanged: demonstrate that the site is genuinely more helpful than Google judged it to be, then survive re-evaluation. Full recovery is common but never guaranteed, and some sites recover only partially.
How long does re-evaluation take now?
Typically 2–6 months from the completion of real remediation work, and some sites need two or three core updates before they are fully re-assessed. The variable is not how fast you work — it is when Google next re-evaluates the site at scale, which you do not control.
Does it apply to my whole site or just the bad pages?
The whole site. The helpful content assessment behaves as a site-level signal, so a substantial body of unhelpful, thin or search-engine-first pages can suppress rankings for your genuinely good content too. This is why pruning and consolidating the weak long tail usually matters more than perfecting your best few articles.
Not sure whether it’s HCU, a spam policy, or something else entirely?
Send your Search Console access and I’ll tell you which one you’re dealing with — and whether it’s recoverable — before you spend a rupee or a dollar on fixing the wrong thing.
Get a free written diagnosis →Not in India? We work with clients across the US, Canada, the UK, Australia and Singapore — same playbook, delivered async, billed in USD from $1,500. See what recovery costs in USD →
SEO & Growth Specialist with 8+ years of experience and 100+ campaigns delivered across India, USA and Canada. Founder of SEORevive, based in Guwahati. Specialises in Google penalty and algorithm recovery, technical SEO and organic growth.