December 2020 Core Update: The Update That Taught SEOs to Wait for the Rollout

The update that reversed itself

The single most useful thing the December 2020 core update taught us is that a core update is not locked in on the day it starts moving.

For years the standard reaction to a core update was to check rankings the morning after Google confirmed the rollout and start drawing conclusions. December 2020 broke that habit, hard. Glenn Gabe documented sites that surged within the first 24 hours, then watched that gain unwind through a second wave of movement, with some finishing the rollout below where they started. A Day-1 win turned into a net loss by the time Google called it complete on December 16.

That pattern is now ordinary. Every large multi-wave rollout since - March 2024, the August and November 2024 cycle, the 2025 updates - has rewarded the same discipline: wait for completion before declaring anything. December 2020 is where that discipline was first forced on the industry at scale.

It was also the biggest update of the year. Landing about seven months after the May 2020 core update - the longest gap Google had ever left between core updates - it released a large backlog of changes at once. Multiple data providers measured it as larger than May 2020, which had itself been considered enormous.

What Google said, and how it actually rolled out

Google announced the update on December 3, 2020, through Danny Sullivan's @searchliaison account. There was no dedicated blog post for this specific update - the Search Status Dashboard incident log did not exist until mid-2021 - so the announcement lived on Twitter and pointed back to Google's evergreen guidance on core updates.

Later today, we are releasing a broad core algorithm update, as we do several times per year. It is called the December 2020 Core Update. Our guidance about such updates remains as we've covered before.Google - @searchliaison, Dec 3, 2020

A follow-up the same day confirmed the rollout was live and would "typically take about one to two weeks to fully roll out." Completion came on December 16, 2020.

The rollout itself was unusually fast and visibly multi-wave:

• Movement appeared within 24 hours, on December 4-5.
• A distinct second tremor wave hit around December 9-10.
• Some sites that initially gained reversed completely and dropped below their pre-update baseline by the end.

It was the first major core update to run during peak holiday shopping season, which drew criticism. Google rebutted it by noting Black Friday and Cyber Monday had already passed before the rollout began.

Who it hit: online-only retail and dictionaries lost

The data for this update is reasonably rich, with several named analysts publishing datasets. SISTRIX surfaced the most structurally interesting pattern: 7 of the 10 biggest absolute losers were online-only retailers, while multichannel retailers gained ground. Dictionaries and encyclopedias - Lexico, Wiktionary, Dictionary.com - were hit hard, losing to richer, more authoritative sources. Most social platforms rose, with Pinterest the lone exception. Amazon fell sharply.

Lily Ray and Amsive analyzed 1,067 sites via SISTRIX (December 1 versus December 14) and found that big platforms which had swelled during the 2020 pandemic news cycle - Pinterest, Amazon, New York Times, CNN, Overstock - gave ground, while E-A-T-focused health sites such as Verywell Health, Prevention.com, and Dr. Axe recovered. Across their dataset, 29 of 38 categories were net winners. Searchmetrics flagged E-A-T-sensitive verticals: music, health, finance, news, and ecommerce.

Why it still matters in 2026

Two lessons from December 2020 outlasted the update itself.

1. Wait for the rollout to finish. The reversals proved that intra-rollout rankings are provisional. A Day-1 surge is not a win and a Day-1 drop is not a loss. Acting on either - rolling back content, panic-editing pages, declaring victory to a client - is acting on noise. This became standard advice for every multi-wave core update since.
2. Do not build on commodity content. The structural signal SISTRIX surfaced - online-only retailers losing to multichannel ones, dictionaries losing to richer authoritative sources - is the same "thin aggregator and commodity content loses to genuine entity authority" pattern Google's later helpful-content and E-E-A-T pushes formalized.

The second lesson is the one that compounds. If a bigger, more-trusted entity can replicate your content, December 2020 showed you are exposed. A dictionary definition, a generic product feed, a lyrics dump - these are commodities, and core updates have repeatedly handed commodity queries to the most authoritative holder. The work that survives is the work tied to a real entity, real expertise, or a real-world presence that cannot be copy-pasted. That thesis runs straight through to what qualifies as helpful content now.

How we apply it to the accounts we audit

December 2020 is purely retrospective now - it is more than five years old and there is no live recovery intent tied to it specifically. But the operating rules it produced are still exactly what we apply when a new core update lands on one of the accounts we audit.

• Hold the analysis: we do not write the post-mortem until Google confirms the rollout is complete. Mid-rollout snapshots get logged, not acted on.
• Two-date comparison: like Amsive's December 1 versus December 14 read, we baseline before the start and re-measure after completion, never against a mid-rollout day.
• Audit the commodity exposure: where a page's value can be replicated by a larger, more-trusted entity, we flag it as structurally at risk regardless of current ranking.
• Treat any one tool as directional: visibility-index winners-and-losers lists disagree because they sample different keywords. We corroborate before drawing a conclusion.

For the full version of the first rule, see our step-by-step core update diagnosis framework, and for the chronological sibling that followed, the June 2021 core update.