- The December 2024 core update ran December 12 to 18, 2024, completing in 6 days and 4 hours, only 7 days after the November 2024 core update finished on December 5.
- It was the middle event in three major updates inside about six weeks: November core, December core, then the December 2024 spam update (December 19 to 26).
- The defining problem was attribution: with rollouts stacked back to back, sites could not tell which system moved them.
- SISTRIX measured larger absolute visibility swings in December than November, so the short rollout was not a minor tremor.
- The durable 2026 lesson is diagnostic discipline: log the exact dashboard timestamps and segment traffic by the day each rollout started before you change anything.
A second core update in 30 days
The December 2024 core update is the cleanest real-world proof that you often cannot tell which Google system moved your rankings, because it sat in the middle of a three-update pileup inside roughly six weeks.
On December 12, 2024, Google began rolling out a core update barely a week after the marathon November 2024 core update had finally completed. The November rollout had run from November 11 to December 5, about 24 days. The December update started on December 12 and finished on December 18, taking just 6 days and 4 hours. Two core updates inside 30 days is unusual enough that Google pre-empted the obvious question in its own announcement.
What makes this update worth studying is not its size in isolation but its position. It was the second of three major updates: the November core update, this December core update, and then the December 2024 spam update that began on December 19, one single day after the December core finished. For anyone watching their analytics, the rollouts blurred into one continuous tremor with no clean gaps to anchor a diagnosis.
The announcement, and the question it pre-empted
There was no dedicated Search Central blog post for this update. The only first-party signals were a post from Google Search Central on X and the Search Status Dashboard incident, which is titled simply "December 2024 core update" with no descriptive body beyond start and end timestamps.
The Dec. 2024 core update is rolling out, and we expect it will complete in two weeks. If you're wondering why there's a core update this month after one last month, we have different core systems we're always improving.Google Search Central on X, December 12, 2024
The detail to notice is that Google felt compelled to answer "why again?" inside the announcement itself, pointing to its explanation that it runs different core systems it is always improving. Google guided to a two-week rollout. In practice the dashboard closed the incident at 11:00 PST on December 18, six days in. The gap between the guided window and the actual close is itself a reason to log the dashboard timestamps rather than the tweet.
For the discipline of reading these announcements precisely, our core update history tracks the exact dashboard windows for every confirmed rollout.
Who moved, by the numbers we have
SISTRIX published winners and losers with changes visible from December 15, across UK and US data. Every figure below is a SISTRIX Visibility Index delta, not a traffic measurement, so read it as a directional signal rather than a revenue number. The vertical pattern is more instructive than any single domain: health-information sites were hit, big owned platforms rose, and retail was genuinely mixed.
| Site or segment | Move | Why it matters |
|---|---|---|
| verywellhealth.com (-17.05%), webmd.com (-10.56%) | Loser | Health-information sites were hit, while Mayo Clinic and NHS rose modestly. |
| wikiart.org (-46.40%), mirror.co.uk (-39.15%) | Loser | The largest named single-domain drops in the SISTRIX set. |
| etsy.com (-8.67%), sainsburys.co.uk (-8.66%) | Mixed retail | Amazon UK, Etsy and eBay UK fell, yet the 453-domain retail set netted a gain. |
| wikipedia.org (+95.06), instagram.com (+32.55) | Winner | Large owned platforms gained, alongside Spotify, IMDb and YouTube. |
| u.co.uk (+242.61%), jamieoliver.com (+44.76%) | Winner | Top named percentage gainers in the SISTRIX winners list. |
Search Engine Journal also noted Pinterest and BBC improving, though Pinterest's movement is partly a September 2024 domain-consolidation effect rather than purely this update, which is exactly the kind of confound this whole episode is about. Notably, Glenn Gabe did not publish a dedicated December-core winners list; his case studies focused on the adjacent spam update and the reversal pattern, because that was where the clearer story sat.
Why a gain here could be a countdown
Here is the durable point. Glenn Gabe documented multiple sites that gained on the November and December core updates and then immediately reversed when the December spam update hit days later. A core-update gain stacked on top of a spam-update reversal is not a recovery. It is a countdown. Some sites that appeared to win the core updates were really just sites the spam systems had not caught yet, which Gabe summarized bluntly: spamming will work until it doesn't.
That reframes the entire winners-and-losers exercise. If you celebrated a December core update lift without separating core movement from spam movement, you may have been congratulating yourself for a position you were about to lose. The fix is not a content tactic. It is diagnostic discipline applied before you touch anything.
- Log the exact timestamps. Record the Search Status Dashboard start and end for each rollout, not the date you noticed the change. December core closed at 11:00 PST on December 18; the spam update opened December 19.
- Segment by rollout day. Cut your traffic into the windows each update occupied so you can see which one actually moved you, instead of attributing everything to the most recent headline.
- Separate quality from violation. Treat core or quality movement and spam or policy movement as different problems with different remedies. Conflating them sends you fixing the wrong thing.
- Distrust a clean win next to a spam update. A lift that arrives right before a spam rollout deserves more scrutiny than a quiet, stable position.
For the full version of this method, see our step-by-step diagnosis framework.
Where it sits in the sequence
This update only makes sense as part of a chain. It opened seven days after the November 2024 core update completed and closed one day before the December 2024 spam update began. Three major systems fired in roughly six weeks, which is why the period is a textbook case of counterbalancing updates running on overlapping schedules.
- Stacking: November core (Nov 11 to Dec 5), December core (Dec 12 to 18), December spam (Dec 19 to 26).
- Magnitude: SISTRIX measured larger absolute visibility swings in December than in November, so the short window did not mean a small impact.
- Confound: the one-day gap between the core finishing and the spam update starting made it nearly impossible to attribute movement cleanly.
- Successors: at least the March 2025, June 2025 and December 2025 core updates have since reshuffled the SERP, so any visibility shift specific to December 2024 has long been overwritten.
If your sense is that core and spam systems pulling in opposite directions sounds like the modern norm, that is the right read. See how the policy side evolved in our look at Google's spam updates in 2026.
The takeaway we carry forward
This update is purely retrospective now. It finished on December 18, 2024, about seventeen months before this writing, and the SERP has been reshuffled by several core updates since. We are not offering a recovery playbook for it. We are keeping the lesson.
The habit that the December 2024 pileup forced on us has only become more useful as Google ships core and spam updates closer together. Anchor every diagnosis to dashboard timestamps, separate quality movement from violation movement, and treat a win that lands right before a spam update as a position to defend, not a victory to bank. That is the whole takeaway, and it has aged well.