Did the Google Core Update Hit You? Here's How to Actually Find Out

You notice a traffic dip. You Google “Google algorithm update.” Sure enough - there’s been a core update in the last two weeks. So that’s it, right? You’ve been hit.

Maybe. But probably not in the way you think.

Most traffic changes around a core update fall into one of two camps:

Camp 1: The site owner panics, assumes they’ve been penalised, starts making frantic content changes - when in reality, the dip was during rollout volatility, seasonal, or caused by something completely unrelated to the update.

Camp 2: The site owner notices the dip, shrugs, assumes it’ll pass - and misses a genuine quality signal that, left unaddressed, will cost them rankings for months.

This post is a practical diagnostic guide. It won’t tell you why Google changed its algorithm (nobody outside Google fully knows), but it will help you work out whether the update actually affected your site specifically - and if so, where the signal is strongest.

What a Core Update Actually Is (and Isn’t)

Before diagnosing anything, it helps to know what you’re looking for.

A Google core update is a broad recalibration of how Google evaluates content quality across the web. Core updates are not penalties - they don’t single out specific sites for violations. They’re more like Google recalibrating its quality scale, which means previously undervalued pages can rise, and previously overvalued pages can fall. Neither is a “punishment.”

Key facts worth knowing:

They take weeks to fully roll out. Google’s core updates in 2024-2026 have ranged from 6 days (December 2024) to 45 days (March 2024). During rollout, rankings will oscillate as different systems update and reinforce each other. Your traffic can dip and recover multiple times before the dust settles.
Google also makes unannounced smaller updates constantly. The officially confirmed core updates represent only the larger, broader changes. Volatility between announced updates is often caused by incremental, unannounced changes.
Not every update affects every site. In fact, Google says most sites don’t need to worry about core updates and may not even notice one has happened.

Recent confirmed core updates (for reference):

March 2026: Started Mar 27 (rolling out now)
December 2025: Dec 11-29
June 2025: Jun 30-Jul 17
March 2025: Mar 13-27
December 2024: Dec 12-18

The authoritative source for confirmed dates is the Google Search Status Dashboard, which logs start and end dates for all announced updates.

Step Zero: Don’t Analyse Until the Update Has Finished

This is the step most people skip, and it leads to a lot of unnecessary panic.

Google’s own guidance is clear: wait at least a full week after a core update finishes rolling out before drawing conclusions from your Search Console data. During rollout, rankings fluctuate as Google’s systems update progressively. Analysing your performance on day 3 of a 3-week rollout will tell you almost nothing meaningful.

Once the rollout is complete, compare the week immediately after the update completed against the week immediately before the update started. That gives you a clean before/after picture that isolates the update’s actual impact from the noise of the rollout itself.

First, Rule Out the Non-Update Explanations

Before you conclude an algorithm update is responsible, eliminate the more common alternatives. Many of these can be confirmed or ruled out in minutes.

Is it a tracking problem?

A broken GA4 tag can look exactly like a traffic collapse. The quick check: compare your GSC clicks against GA4 organic sessions. If GSC clicks are holding steady but GA4 shows a drop, your GA4 tracking is the problem - not Google’s algorithm.

If you’re seeing discrepancies between the two tools, that’s often normal - we explain why in our post on why GA4 and Search Console show different numbers.

Is it a technical SEO issue?

A sudden, overnight cliff-drop in traffic - especially to your whole site at once - is rarely an algorithm hit. Algorithm impacts are gradual, rolling in over days or weeks. Sudden, catastrophic drops are almost always technical: a misconfigured robots.txt, accidental noindex tags pushed in a deploy, a server going down, or a botched site migration.

Check in GSC: Security & Manual Actions > Manual Actions. If Google has issued a manual penalty (which is different from an algorithmic devaluation), it will be listed there, and you’ll have received an email notification.

Is it seasonality?

Many industries have significant seasonal patterns that look alarming without context. Compare your traffic to the same period last year, not just the previous month. A 20% drop in January for a garden supplies site isn’t a Google hit - it’s January.

Is it AI Overviews displacing your clicks?

This is a newer issue affecting many informational queries. You’ll see the pattern in GSC: impressions holding steady or growing, but clicks and CTR falling. Google is still showing your content in results, but an AI Overview above your listing is absorbing the clicks. This is a separate phenomenon from a core update hit and requires a different response.

The Diagnostic Checklist

If you’ve ruled out the above, here’s how to check whether the update specifically affected your site, using GSC.

Check 1: Did impressions drop, or just clicks?

Open the GSC Performance report and look at the Clicks vs Impressions trend together.

Impressions dropped: Google is now showing your pages less in results - your rankings fell. This is the clearest signal of update impact.
Impressions stable, clicks dropped: Your pages are still appearing in search results, but something changed about how they appear (perhaps a featured snippet was lost, an AI Overview appeared, or your listing’s CTR changed). This isn’t necessarily a ranking hit.

Check 2: Is it site-wide or page/topic-specific?

In the Performance report, switch to the Pages tab and sort by traffic change. Is the drop distributed fairly evenly across your whole site, or is it concentrated on specific pages or topics?

Site-wide: More consistent with a broad algorithmic reassessment or a technical issue.
Concentrated on specific topic areas: Likely a quality signal on that content type specifically. Core updates often hit particular content categories harder (health, finance, reviews, news - so-called “YMYL” topics - tend to see the most volatility).

Check 3: Did average position change?

If average position fell significantly for your most important queries, that’s a clear ranking signal. A position drop from 4 to 29 is meaningful and worth investigating. A position drop from 2 to 4 isn’t drastic enough to warrant emergency action.

Check 4: Segment by device and country

Some core updates have had outsized effects on mobile users or specific regions. If your desktop traffic is stable but mobile dropped sharply, that’s a more specific signal worth noting - it can point to Core Web Vitals issues being weighted more heavily, or a page experience problem that only manifests on mobile.

Check 5: Cross-reference with GA4

Confirm the drop exists in GA4 organic sessions as well. Filter GA4 to Google organic only (source = google, medium = organic). If the drop is confirmed in both GSC and GA4, you have real evidence of a genuine traffic change. If GA4 is healthy while GSC shows a drop, focus on your tracking setup first.

You Were Affected. Now What?

If your diagnosis confirms a genuine update hit, the important thing to understand is this: core updates are not something you fix with quick technical patches. Google’s guidance is explicit - avoid “quick fix” changes like removing page elements because you heard they were bad for SEO.

Core updates represent a reassessment of content quality. The sites that recover fastest are the ones that identify which pages are underperforming relative to user expectations, and make meaningful improvements - better depth, clearer authorship, more original insight, stronger alignment with what searchers actually want.

Things worth reviewing on affected pages:

Does this page genuinely answer the search query better than the pages now ranking above it?
Is there clear evidence of expertise and authorship?
Is the content primarily written for the searcher, or does it feel like it was written to rank?

One useful data point: look at which queries lost the most clicks in GSC, then manually check what’s now ranking above you for those queries. That will tell you more about what Google’s updated quality signal is rewarding than any generalised guidance can.

The Easier Way to Run This Diagnosis

Doing this analysis properly involves jumping between GSC’s Performance report, GA4’s Traffic Acquisition report, filtering by date, device, and query, and mentally overlaying it against update dates you’ve had to look up separately. Most people either don’t do it at all, or do it once and never build a repeatable workflow.

With AI Data Stream, you can query your GSC and GA4 data together in plain language. Questions like “Did my organic clicks drop in the week after the December 2025 core update finished, and which pages were most affected?” or “Compare my GSC clicks and GA4 organic sessions for the 30 days around the June 2025 update” return direct answers without requiring you to build a custom dashboard or stitch together CSV exports.

It’s particularly useful for the “before and after” comparison Google recommends - specifying an update’s exact start and end dates and comparing the right windows is fiddly to do manually, and easy to get wrong.

The Bottom Line

The fact that your traffic changed around the same time as a core update does not mean the update caused it. The pattern matters more than the timing. A sudden overnight cliff-drop is almost certainly technical. A gradual, rolling decline across a 2-3 week rollout window, concentrated on specific content types, with impressions falling rather than just CTR - that’s a genuine update signal.

The good news is that most sites affected by a core update aren’t penalised - they’ve just been re-evaluated against a higher quality bar. That’s recoverable. The worst outcome is misdiagnosing the cause, making the wrong changes, and not noticing the real problem until the next update cycle.

Want to diagnose your next update impact in minutes? Try AI Data Stream free →