What Google won’t confirm, it can reverse

It began on Friday the 7th and ran through the weekend: a shake in the search results large enough that, by Sunday, the SEO community was reporting what looked like a major update. The movement was real and measurable, not a rumour — rank-tracking tools logged sharp spikes in volatility, and analyses that compared how many top-three keywords a site held on the 7th against the 9th found large numbers of sites posting significant gains or significant losses. The impact spread across very different niches with no clean pattern to who won and who lost, which is part of what made it feel like an algorithm event rather than anything site-specific. Then the episode did something updates usually do not: it reversed. By the 13th, Google had largely undone it. The sites that had dropped or surged over the weekend were back roughly where they had started, and charts that laid Search Console data alongside third-party tools told the same story — a fall around the 7th, a recovery by the 12th and 13th. Whatever Google pushed, it appears to have rolled back within days. When the community pressed for an explanation, Google’s Search Liaison offered only that it does updates all the time and pointed to its standard guidance — word for word the response it had given for an unconfirmed update the previous November. It did not call this a core update; it did not name it. The honest summary is therefore both narrow and striking: a real movement in the rankings, never confirmed as a core update, reversed almost as fast as it appeared. Real, unconfirmed, undone — that combination is what makes the weekend worth a note.

The most useful thing this episode teaches is how much weight to put on whether Google confirms a change. Since early 2019, Google has deliberately made a practice of confirming — and frequently pre-announcing — its major core updates through its Search Liaison channel. That practice exists for a reason: to let site owners separate a deliberate, lasting change in how ranking works from the constant, low-level tinkering that goes on every single day. A core update is significant and intended to stick, so Google flags it; the flag is a promise of permanence. Once you understand that, the absence of a flag becomes just as informative as its presence. When a large movement happens and Google will not confirm or name it — when the most it will say is we do updates all the time — that refusal is itself a signal. It tells you the change is not in the category Google stands behind as a deliberate, lasting adjustment. It may have been an experiment run live on real results; it may have been a cluster of smaller changes colliding in ways no one intended; it may even have been something that briefly broke and then got fixed. All of those are the kinds of thing that get rolled back, and the February weekend is the textbook case — a big, genuine shake-up that Google would only wave at, followed by a near-total reversal. So the discipline is to read confirmation as a permanence signal in both directions. A confirmed core update is telling you the new order is meant to last, and you can plan around it. An unconfirmed shake-up is telling you no such thing, and you should hold your plans loosely until it proves otherwise. Reading that signal correctly, instead of treating every large movement as equally permanent, is what keeps measurement honest.

It helps to place this episode against the two failure modes it is most easily confused with, because it is neither, and the difference dictates the response. The first is ordinary noise: the small, near-random, day-to-day movement in positions that carries no meaning and deserves no reaction. The February shake was far too large and too coordinated to be noise — it was not a position or two of jitter, it was sites swinging across the top of page one in unison. The second is a data glitch: the case where your reporting moves but your site does not, where a dashboard wobbles while your real rankings and traffic hold steady, and the cure is to verify against the live results rather than react to the chart. February was not that either — independent tools and the live results agreed that genuine shifts had occurred, so the movement was real, not an artifact of measurement. That leaves a third category, the one this weekend belongs to: a real change that turns out to be temporary. The rankings truly moved, and then they truly moved back. You cannot wave it away as noise, you cannot explain it away as a reporting problem, and yet treating it as a permanent update would also have been a mistake, because it did not last. The distinguishing mark of this third category is the missing confirmation — a real move that Google will not stand behind is a real move that may not stay. Learning to sort a shake-up into the right bucket — noise to ignore, a glitch to verify, or a real-but-unconfirmed move that may reverse — is what tells you whether to shrug, to check, or to wait. That sorting is the measurement discipline the AC Group has worked by for {years} years.

The right move is to hold steady and let permanence declare itself before you commit to anything. The damaging response to an unconfirmed shake-up is to treat it as a final verdict and start rebuilding — restructuring the site, rewriting pages, reworking the strategy to chase the new picture — because if the change unwinds, as February’s did, you will have spent real effort and taken on real risk adapting to a state of the world that no longer exists, and the hasty changes themselves can leave lasting damage even after the fluctuation clears. This is, almost word for word, Google’s own standing advice for unconfirmed volatility: do not make sudden, drastic changes in response to a perceived update, because if it was not a real, lasting update, those changes can hurt you in the long run. So build a sequence and follow it. First, establish that the movement is real rather than noise or a reporting glitch — check the live results and independent tools, the way you would for any suspected drop. Then, and this is the part the panic skips, wait: monitor daily and give it a few days to show whether it holds or reverses. If it reverses, your calm cost you nothing. If it holds and Google later confirms a deliberate update, you now get to respond to a known, permanent change with a clear head instead of a scramble. And underneath all of it, keep doing the durable work — genuinely useful content, earned authority, clean technical health — because that is what survives every update, confirmed or not, reversed or kept. Knowing when to act and when to wait, judged by whether a change is confirmed and whether it lasts, is the measurement discipline the AC Group has worked by for {years} years.