All posts
Algorithm UpdatesGoogle Search ConsoleSEO Analysis

How to Track Google Algorithm Update Impact Using GSC Data

Published 6 July 2026·10 min read
Peter Claridge
Founder, KeywordHistory · Fractional CMO at Riverforge

When organic traffic drops sharply, the first question is always whether an algorithm update caused it. The second question — harder to answer — is whether the update actually affected your site specifically, or whether you're attributing normal volatility or an unrelated cause to the most prominent recent event.

Google ran four core updates in 2024: March (45 days, described by Google as the "largest in history"), August, November, and December — plus multiple spam updates. Search Engine Land's 2024 algorithm update review documents each one with dates and scope. Understanding whether your site was affected requires looking at the data before and after each update window, not just noting that a coincidence in timing exists.

The Core Method: Before and After Windows

The diagnostic approach recommended by Optimum7 and others:

  1. Note the exact start date of the algorithm update (Google announces these on their Search Status Dashboard)
  2. In GSC → Performance, set the date range to start 8 weeks before the update and end 8 weeks after
  3. Switch to weekly view to reduce daily noise
  4. Look at clicks, impressions, and average position for the target period
  5. Add a device filter (desktop and mobile separately) — algorithm impacts often affect mobile and desktop differently
  6. Add a country filter if you serve multiple markets — updates can roll out differently by region

The 14-Day Quick Check

For an initial assessment, compare the 14 days immediately before the update start date to the 14 days immediately after. Use the GSC compare function with custom date ranges. If clicks are materially lower (more than 10-15%) in the post-update period and the trend persists into weeks 3 and 4, the update is worth investigating. If week 1 shows a drop that normalizes by week 3, it was likely volatility during the rollout, not lasting impact.

2024 Major Update Reference

UpdateStart DateDurationScope
March 2024 CoreMarch 5, 202445 days"Largest in history" — targeted low-quality and AI content
August 2024 CoreAugust 15, 202419 daysBroad quality signals
November 2024 CoreNovember 11, 202424 daysRanking signals refresh
December 2024 CoreDecember 12, 20246 daysSmaller targeted update

When investigating a traffic drop that started in Q1 2024, the March update is the most likely candidate. The March 2024 Core Update ran from March 5 through April 19 — 45 days — making "before and after" comparisons particularly important because traffic during the rollout period was volatile rather than representing a stable new baseline.

What True Algorithm Impact Looks Like vs. Volatility

Signs of Real Algorithm Impact

  • Clicks drop by 15%+ in the first 2 weeks after an update and continue declining or hold at the lower level for 8+ weeks
  • Position changes are concentrated on specific page types or content categories (e.g., all your comparison pages drop while product pages hold)
  • Average position for multiple keywords moves simultaneously in the same direction
  • The drop is visible across all devices and countries, not just one segment

Signs of Normal Volatility

  • Traffic drops in week 1 post-update but recovers to within 5-10% of pre-update levels by week 3-4
  • Position changes are scattered across different keywords with no clear pattern
  • The drop is concentrated on one device or one country segment
  • Normal weekend/weekday fluctuations account for the magnitude of the change

The 2025 GSC Bug Complication for Algorithm Analysis

Any algorithm impact analysis involving dates between May 13, 2025 and April 27, 2026 is complicated by the fact that GSC impressions were systematically over-counted for that 50-week period. Clicks were not affected.

The specific consequence for algorithm impact analysis: if you're trying to assess whether a 2025 algorithm update affected your site, and you're using impressions or CTR as your metric, the comparison is unreliable. Use clicks only for any analysis containing data from this period. Position data (average position) is also unaffected by the impression bug and can be used as a secondary signal.

For algorithm update analysis specifically, historical data depth matters. If an update from August 2024 is still affecting your site in June 2026, you need data going back to early 2024 to establish the true baseline. GSC's 16-month window doesn't cover this range anymore. BigQuery export of historical GSC data — or Keyword History's annotations and historical tracking — is needed for this kind of multi-year impact assessment.

Distinguishing Algorithm Cause from Other Causes

The timing correlation between a traffic drop and an algorithm update is suggestive, not conclusive. Traffic drops in the same week as an algorithm update can be caused by:

  • The algorithm update itself (affecting your content quality signals)
  • A concurrent technical issue (slow server, broken canonical tags, crawl errors)
  • A competitor launching new content that displaces your rankings
  • Seasonal demand changes (if the update timing coincides with a seasonal trough)
  • SERP feature changes that absorb clicks without affecting rankings

To rule out technical causes: check GSC Coverage report for sudden increases in crawl errors, check Core Web Vitals for performance degradation, and check server logs for crawl frequency changes around the same date.

To isolate algorithm-specific impact: if your clicks dropped but your average positions held, the cause is more likely SERP feature changes (AI Overviews appearing) than algorithm-driven ranking loss. If both clicks and positions dropped together, ranking changes are the cause — and those are more likely to be algorithm-driven.

Recovering From Algorithm Impact

Google's stated position is that recovery from core updates happens via improving the overall quality of the affected content — not by waiting for the next update to reverse the impact. The practical approach:

  • Identify the specific pages that lost rankings (filter GSC queries for the update period, sort by position change, find pages that moved down 5+ positions)
  • Compare those pages against current ranking pages for the same queries — what do the ranking pages have that yours doesn't?
  • Improve the content quality, depth, and E-E-A-T signals on the affected pages
  • Wait for the next core update — recovery typically correlates with core update cycles, not individual recrawls

The March 2024 Core Update's aftermath demonstrated this: sites that had published content at scale using AI generation without quality control saw lasting drops, while sites with genuine editorial quality and original research recovered within one or two subsequent update cycles.

The most important habit for algorithm update analysis is establishing a clear data baseline before any update hits. A site with months of stable GSC data at the keyword level can immediately identify which pages were affected and by how much. A site without systematic historical tracking has to reconstruct the baseline from fragmented sources — which is slower and less precise.

Peter Claridge

Written by

Peter Claridge

Founder, KeywordHistory · Fractional CMO at Riverforge

Led organic growth at Unmetric, eG Innovations, and StreamAlive over 13+ years. Built KeywordHistory after rebuilding the same Google Data Studio dashboards one too many times.

Connect on LinkedIn

Keep your keyword history forever.

Every day you wait, Google deletes another day of your GSC data. KeywordHistory backs up to BigQuery automatically and surfaces the insights that matter.

Start free