Free tool
Google algorithm update checker
Find out whether a Google core or spam update really changed your traffic. Drop your Search Console export and the checker lines up your daily clicks with every confirmed update since 2025, compares the weeks before each one with the weeks after its rollout, and tells you whether the change is bigger than your site's normal ups and downs. It runs in your browser; nothing is sent to RankEcho.
Drop your Search Console export here
The zip from Performance, then Export, then Download CSV, or just Dates.csv inside it.
See which pages and searches moved
This file only holds site totals. Connect Search Console to RankEcho and every chart marks each confirmed update, a traffic alert tells you the week a drop starts, and the reports show which pages lost or gained and which searches moved. The first 72 hours are free, with no card.
How to export the right file from Search Console
- Open Performance, then Search results, for your property.
- Set the date range to Last 16 months, so every update since mid-2025 has days on both sides.
- Choose Export (top right), then Download CSV. Search Console gives you a zip with one file per tab.
- Drop the zip above. The checker reads the Dates table and ignores the others.
Prefer Google Sheets? Choose Export, then Google Sheets, open the Dates tab, select all, copy and paste it into the box above.
How the checker decides whether an update hit you
A before-and-after number on its own misleads. Traffic moves every week, sites that are growing look like winners after every update, and holidays or a site change can fall in the same weeks. So the checker does three things for each update:
- Before: the 28 days that end the day before the rollout started (7 or 14 if you choose).
- After: the same number of days, starting the day after Google marked the rollout complete. While an update is still rolling out, it reads the days since it started and calls the result an early read.
- Your usual range: it slides the same pair of windows, the same distance apart, across every other stretch of your data and measures how much your traffic usually moves between them. An update counts as a hit or a lift only when the change is at least 10% and more than twice your usual movement. With too little history to measure that, a 20% change counts.
The verdict reads clicks when the two windows hold at least 50 clicks between them, and impressions when clicks are too few to say anything. Both are in the table, with the average position, so you can see whether you lost rankings (position worse) or demand (impressions down with position steady).
A worked example: lifebylogic.com
We ran the checker on lifebylogic.com, a site run by the same company as RankEcho, with its Search Console days from 2026-04-16 to 2026-11-05 and the default 28-day window. It is a young site that was growing fast, which is exactly when a plain before-and-after misleads: almost every update looks like a win. Measured against the site's own usual movement, the picture is:
- May 2026 core update: Impressions per day went from 43.6 to 307.2 (+605%); your usual movement over the same span would have given about 93.7. This is within your usual ups and downs.
- June 2026 spam update: Clicks per day went from 1.0 to 2.9 (+204%); your usual movement over the same span would have given about 2.1. This is within your usual ups and downs.
- August 2026 spam update: Clicks per day went from 3.8 to 9.4 (+150%); your usual movement over the same span would have given about 7.3. This is within your usual ups and downs.
- September 2026 spam update: Clicks per day went from 8.7 to 18.2 (+110%); your usual movement over the same span would have given about 18.6. This is within your usual ups and downs.
Press Try it with lifebylogic.com above to see the chart and the full table.
Confirmed Google updates since 2025
11 ranking updates from Google Search Status Dashboard, 6 of them core updates. The list refreshes every six hours.
| Update | Type | Started | Finished | Rollout |
|---|---|---|---|---|
| November 2026 core update | Core | 2026-11-10 | Rolling out | |
| September 2026 spam update | Spam | 2026-09-24 | 2026-10-08 | 15 days |
| August 2026 spam update | Spam | 2026-08-18 | 2026-08-21 | 4 days |
| June 2026 spam update | Spam | 2026-06-24 | 2026-06-26 | 3 days |
| May 2026 core update | Core | 2026-05-21 | 2026-06-02 | 13 days |
| March 2026 core update | Core | 2026-03-27 | 2026-04-08 | 13 days |
| March 2026 spam update | Spam | 2026-03-24 | 2026-03-25 | 2 days |
| December 2025 core update | Core | 2025-12-11 | 2025-12-29 | 19 days |
| August 2025 spam update | Spam | 2025-08-26 | 2025-09-22 | 28 days |
| June 2025 core update | Core | 2025-06-30 | 2025-07-17 | 18 days |
| March 2025 core update | Core | 2025-03-13 | 2025-03-27 | 15 days |
What to do if an update hit your traffic
- Check it was the update. Look at the "Also inside these windows" note and at your own changes in the same weeks: a redesign, a migration, removed pages or a tracking change can look just like an update.
- Find the pages. In Search Console use Compare with the before and after dates from the table and sort the Pages tab by clicks lost. Usually a few pages carry most of the drop.
- Read the queries on those pages. If position fell, others now answer the search better: compare the pages that replaced you with yours. If impressions fell with position steady, the demand moved, often into AI Overviews.
- Fix, then measure. Core updates reward the page that best answers the search. Improve the pages that lost, then check the change with the SEO change calculator rather than waiting for the next update. See content decay for pages that slide slowly instead.
To filter the Queries tab by brand, questions or folders while you dig, use the Search Console regex builder. The Google Search Console guide covers the rest of the Performance report.
Frequently asked questions
How do I know if a Google update affected my site?
Compare the weeks before the update started with the weeks after its rollout finished, and ask whether the change is bigger than your site's normal week-to-week movement. A 15% drop means little on a site that often swings 20%, and a lot on one that rarely moves 5%. This checker does both steps from your own Search Console numbers.
Which Search Console file do I need?
Dates.csv. In Search Console open Performance, then Search results, pick the last 16 months, and choose Export, then Download CSV. You get a zip of several tables; drop the whole zip or just Dates.csv. Google Sheets works too: copy the Dates tab and paste it.
Why compare the days after the rollout, not after the start?
Rankings move throughout a rollout, which can take two weeks or more. Reading from the day it ended shows where the update left you. While an update is still rolling out, the checker reads the days since it started and labels the result as an early read.
Does this tell me which pages lost traffic?
No. The Dates table holds site totals only. To find the pages, open Performance in Search Console, choose Compare, set the same before and after dates the checker shows, and sort the Pages tab by the change in clicks. RankEcho's Search Intelligence does this for every update automatically.
Is my Search Console data sent to RankEcho?
No. The file is read in your browser and the numbers are worked out there. Nothing you drop or paste is uploaded.
Where does the list of Google updates come from?
From Google Search Status Dashboard, which lists every confirmed ranking update with its start and end. RankEcho checks it every six hours, so a new update appears here soon after Google announces it.
Turn the diagnosis into a shipped change: use the RankEcho Resources library for Find, Fix, and Prove playbooks, checklists, and templates.
