How do you tell which update hit you when several rolled out?
- Published November 6, 2026
- Linked from 3 answers
- In a cluster of 77
Match the day your traffic changed to the start and end dates Google publishes for each update, then check whether the pages that moved fit what that kind of update assesses. The dates come from the Search Status Dashboard, where every announced ranking update appears with the day it began and how long it ran; the Ranking history there is the record to compare against. The attribution you reach is your inference: Google confirms when an update ran, not which update moved your pages.
Step 1: line up the dates
Google’s core updates page gives a method for this: wait until the update has finished, then “After a week, try comparing this week with a week before the core update started rolling out”. Do the same for each update in question. A drop that starts inside one rollout window and before another begins points at the first. For scale, the dashboard lists the May 2026 core update as starting on May 21, 2026 and running 11 days and 21 hours, so a drop that began in early May needs another explanation.
Step 2: check which pages moved
| Update type | What it is aimed at | What a hit looks like |
|---|---|---|
| Core update | A broad reassessment of content across the web, not aimed at specific sites | Pages across the site move, up as well as down, with no single technical cause |
| Spam update | Improvements to Google's automated spam detection | Pages that use the practices in Google's spam policies lose ground |
| Link spam update | Unnatural links | Pages that relied on such links lose the value those links passed |
If the pages that fell are the ones with thin or unoriginal content, a core reassessment fits; if they are the pages that depended on bought or exchanged links, a link spam update fits better. These are patterns to weigh, not proof: the same pages can fall for different reasons, and a date match only tells you which update to suspect first. Ruling out a technical cause comes before either; the method is in telling an update from a technical break.
When the dates overlap or nothing matches
When two rollouts overlap, the date alone cannot separate them, and the page pattern carries the decision. When no listed update matches, keep two other explanations open: Google also makes smaller core updates it does not announce, and demand for your queries may have shifted. In either case the response is the same as for a core update, described in what a core update re-evaluates: compare the affected pages with what now ranks above them. Name the update only when both the dates and the page pattern point to it.
Add a comment