Google’s December 2025 Core Update Is Rolling Out

If your rankings or traffic started moving this week, the December 2025 core update is the most likely reason. Google released it on 11 December 2025 at 9:25 a.m. Pacific Time. It says the rollout may take up to three weeks to finish. It is still rolling out, so what you see today is not the final picture.

In this guide, I explain what a core update is, what Google has actually said about this one, and what to do (and avoid) while it rolls out. I also show how to set up Search Console so you can judge the impact properly once it ends. And I cover the problem most people will face this month: holiday seasonality.

What Google Has Confirmed About the December 2025 Core Update

Google announced the update on its Search Status Dashboard with a short entry. It said the December 2025 core update has been released, and the rollout may take up to three weeks to complete.

In its social posts, Google called it a regular update to better show relevant, satisfying content to searchers from all types of sites. Google didn’t publish any new advice for this update. It didn’t name any site types, industries or ranking signals being targeted.

Here are the confirmed facts in one place:

• Start: 11 December 2025, 9:25 a.m. PST.
• Expected length: up to three weeks, which would take it towards the end of the year.
• Type: a broad core update, not a spam update, link update or reviews update.
• Scope: Google’s systems overall, across all types of sites. No specific niche was named.
• Place in the year: the third announced core update of 2025, after the March core update and the June 2025 core update.

Anything beyond these points is guesswork at this stage. That includes lists of “winners and losers” and claims about which factor changed. Early movement during a rollout often reverses or shifts again before the update finishes.

How It Compares With Earlier Core Updates

The Search Status Dashboard records how long each recent core update took. That history is the best guide to what “up to three weeks” may mean in real life.

The lesson from that table is simple. Rollout lengths vary a lot. So I plan around Google’s completion notice on the dashboard, not around a guessed end date. I walked through the post-rollout checks for an earlier update in what to check after the March 2025 core update.

What a Google Core Update Actually Is

A core update is a broad change to Google’s ranking systems. Google makes them several times a year. Each one aims to improve how well the results match what searchers want.

The key word is “broad”. A core update doesn’t target a specific site, page or tactic. It changes how Google’s systems judge content as a whole. So pages can move up or down even when nothing changed on the site itself.

How a Core Update Differs From a Spam Update or a Penalty

This difference matters, because the fix is completely different.

• Core update: a reassessment of relevance and quality across the web. A drop doesn’t mean you broke a rule. It usually means Google now judges other pages to serve those queries better.
• Spam update: improvements to systems that find content or links that break Google’s spam policies.
• Manual action: a human reviewer at Google has found a policy violation. It shows in the Manual actions report in Search Console, with a reason and a reconsideration process.

If you see a drop this month, check the Manual actions and Security issues reports first. That’s always my first step. If both are clear, a manual penalty is not the cause, and there is nothing to “request reconsideration” for.

Why Rankings Can Move With No Changes on Your Site

Think of a core update as Google re-sorting a long shelf of books on a topic. Your book hasn’t changed. But the shelf has been rearranged, and some books that were lower down may now sit above yours.

Google’s own documentation makes the same point: search results are not fixed. The web keeps changing, user expectations change, and the systems change. So positions shift over time, even for well-run sites.

Smaller, Unannounced Core Updates

Just before this rollout, Google updated its core updates documentation. It now makes clear that Google also makes smaller core updates that it doesn’t announce, because most people won’t notice them.

The practical point is good news. If you improve your content, you don’t always have to wait months for the next big named update to see a benefit. These smaller updates can pick up improvements too, although Google gives no guarantee or timeline.

What to Do While the December 2025 Core Update Is Rolling Out

The honest answer for most sites is: watch, record and wait. Google’s advice is to let the update finish before you analyse its effect, because rankings can keep shifting until the rollout is complete.

Do

• Record the dates. Note 11 December 2025 as the start, and watch the Search Status Dashboard for the completion notice.
• Mark the date in your reports. Add a note in Search Console and in your analytics tool. Then anyone looking at the data later knows why the line moved.
• Save a clean “before” baseline. Export the Performance data for the weeks before 11 December while it’s easy to find.
• Keep publishing as normal. Planned content, product updates and seasonal pages should go ahead as usual.
• Fix real technical problems. If a page is broken, returning errors or blocked from crawling, fix it. That’s maintenance, not a reaction to the update.
• Tell stakeholders early. Tell clients or managers now that numbers may swing for a few weeks, and that analysis will come after completion. In my experience, this one message saves a lot of panic later.

Do Not

• Don’t rewrite or delete pages based on daily movement. A page that drops on day three may recover by day ten.
• Don’t make “quick fix” changes. Google warns against things like removing parts of a page because you heard they are bad for SEO. Changes should make the site better for people.
• Don’t change many things at once. If you rewrite titles, change navigation and remove content in the same week, you’ll never know what helped or hurt.
• Don’t treat third-party volatility trackers as verdicts. They show that results are moving, not why your pages moved.
• Don’t file a reconsideration request. That process is only for manual actions, and a core update is not one.

How to Monitor the Update in Search Console

Search Console is the only tool that shows your real clicks and impressions from Google. If you are new to it, my Search Console guide for beginners walks through the Performance report in more detail.

Set Up Your Before-And-After Comparison

Google recommends waiting at least a full week after a core update finishes. Then compare the week after completion with the week before the rollout started. For this update, the “before” week is the seven days ending 10 December 2025. The “after” week depends on when Google confirms completion.

During the rollout, you can still watch the trend without drawing conclusions:

1. Open the Performance report and choose the “Search results” report.
2. Set the date range to the last three months so you can see your normal pattern before 11 December.
3. Turn on clicks, impressions and average position together.
4. Use the “last 24 hours” view if you want a near real-time look. But treat it as a quick pulse check, not proof.
5. Check the Pages and Queries tabs to see which URLs and search terms are moving most.

Search Console now also supports custom annotations on the Performance chart. They are a neat way to mark the update’s start date. I covered how they work in my article on Search Console’s branded queries filter and custom annotations.

Split the Data Before You Judge It

A single sitewide line hides most of the story. Break the data down so you can see where any change really is.

• Search type: check Web, Image, Video and News separately. A drop in one doesn’t mean a drop in all.
• Branded and non-branded queries: branded searches (searches for your business name) usually show demand for your business, not rankings. Filter them out to see your organic visibility more clearly.
• Page groups: compare sections such as blog, category pages and product pages. Core updates often hit some content types more than others on the same site.
• Country and device: a change in one market or only on mobile points to a different cause than a sitewide shift.

Read the Size of Any Change Correctly

Google draws a clear line between small and large moves. A page slipping from position 2 to position 4 is not a reason for big action. A large, lasting drop across many important queries is what needs a deeper review.

Also be careful with impressions. Google stopped supporting the num=100 results parameter in September. That changed the impressions and average position numbers many sites see. If you compare December 2025 with December 2024, that shift will distort the picture. My article on why Search Console impressions fell after the num=100 change explains why clicks are the more reliable metric for long comparisons.

The Holiday Seasonality Problem

A December core update lands in the middle of the most seasonal weeks of the year. That makes it very easy to blame the update for changes the calendar really caused. The December 2024 core update landed in the same busy weeks last year.

Here are two examples:

• A gift retailer may see clicks fall sharply after the last shipping dates, whether or not the update hit it. Searchers simply stop looking for products they can’t get in time.
• A B2B software company may see traffic dip in the last two weeks of December because offices close. That dip happens every year.

The reverse is also true. A site selling party supplies or travel deals may see traffic rise and think it “won” the update, when demand has just peaked.

How to Separate Seasonality From the Update

1. Look at last December. Search Console keeps 16 months of data. So you can view December 2024 and see what your normal holiday curve looks like.
2. Watch average position, not just clicks. If clicks fall but positions for your main queries hold steady, demand changed, not rankings.
3. Check click-through rate. Stable positions with falling impressions usually means fewer people are searching.
4. Compare with paid search data if you run ads. If paid impressions fell by a similar share, the drop is likely demand, not organic visibility.
5. Use Google Trends for your main terms. It shows if interest in a topic changes at this time of year.

One more warning. Google’s suggested week-after-completion comparison will fall over the holidays or into early January. For many sites, that week won’t be typical. I think it’s fairer to wait until normal January demand returns, then compare like with like. For example, match days of the week and similar points in the month.

If You See a Large Drop After Completion

None of this applies until Google confirms the rollout is finished and you have a clean week of data. But it helps to know the plan in advance, so you aren’t making it up under pressure.

Google’s advice for sites with a big, lasting drop centres on an honest review of content quality:

• Review the pages that lost the most traffic. Search the queries they used to rank for and look at what now ranks above them. Ask if those pages really answer the searcher better.
• Use Google’s self-assessment questions on helpful, reliable, people-first content. They cover originality, expertise, depth and whether content was made mainly to attract search clicks.
• Get an outside view. Google suggests asking trusted people who aren’t connected to your site to judge it fairly.
• Improve first, then restructure, and delete only as a last resort. Rewriting thin pages and making content easier to navigate comes first. Removing content is for pages that can’t be saved.

Looking at the sites that now rank above you is useful in itself. My step-by-step SEO competitor analysis shows how to compare pages fairly, instead of copying surface features.

How Long Recovery Can Take

Google is clear that some changes can show within days. But its systems may need several months to confirm that a site keeps producing helpful content. Sometimes the improvement only shows at a later core update, announced or not.

That’s why reacting during a rollout is risky. Google will judge changes you rush through in December over months. So they need to be real improvements, not guesses about what the update rewarded.

Common Mistakes During a Core Update

• Reading too much into the first few days. Early movement is often temporary.
• Comparing the wrong periods. Comparing a holiday week with a normal November week will make any drop look bigger.
• Blaming one factor. Core updates are broad. If you feel sure that one thing, such as word count or a page element, caused a drop, slow down. This is the mistake I see most often.
• Ignoring other causes. Site migrations, broken templates, robots.txt changes and lost redirects can all happen at the same time as an update. Rule them out before you blame Google.
• Chasing tracker headlines. Industry-wide volatility charts don’t tell you what happened to your pages.

Conclusion

The December 2025 core update started on 11 December and is still rolling out, with Google estimating up to three weeks. Until Google confirms completion, the best move is to record your baseline, mark your reports, keep normal work going and avoid reactive changes.

When the rollout ends, wait a full week, then compare carefully, with one eye on holiday seasonality. Here’s what I’d do today: open the Performance report, export the four weeks before 11 December, and add a note marking the start date. Then the comparison is ready when you need it.