Smaller core updates now roll continuously and without announcement. When the target moves silently and constantly, reactive optimisation stops being a strategy and becomes a superstition.
Lucy Aingworth
AI Visibility Consultant
Published 7 min read
The short answer
Google confirmed in 2026 that smaller core updates now roll continuously without announcement. That removes the stable target reactive optimisation depended on: when the system is being adjusted during your observation window, you cannot attribute an outcome to your change rather than to the adjustment. What remains worth investing in is whatever the mechanism is trying to approximate. Every version of every ranking system is attempting to identify who is genuinely credible, so independent validation is an investment in the objective rather than in a temporary implementation of it.
Key takeaways
Trackers registered another unconfirmed movement over the weekend of 18 and 19 July, with some of the previous week's changes partially reversing.
Continuous silent updating removes the feedback loop, because the system changes during the window in which you are measuring your own change.
Diagnoses made from a two-day window are guesses, and teams accumulate internal doctrine assembled from coincidence.
Earned Authority does not depreciate on a model update, because it is the evidence every system is built to detect rather than a preference of one.
Authority Debt is directly observable, does not fluctuate with the weather, and is the only backlog worth keeping.
Trackers and forums picked up another unconfirmed ranking movement over the weekend of 18 and 19 July, with a visible blip on the Saturday. Volatility was lower than the movement a week earlier, and several practitioners reported that some of those earlier changes had partially reversed themselves. Nobody announced anything, and nobody will, because Google confirmed earlier this month that smaller core updates now roll continuously without announcement.
The obvious reading of that is that updates have become more frequent. The more useful reading is that the update, as a discrete event you can respond to, has ceased to exist.
What does continuous updating remove?
Reactive optimisation depended on a feedback loop, and the loop depended on a stable target. You observed a position, changed something, waited, and observed again. If the position improved, the change worked. That inference was always shakier than the industry admitted, but it was not absurd, because between announced updates the system held still long enough for the comparison to mean something.
Continuous silent updating removes the stillness. When the system is being adjusted during the observation window, you cannot attribute an outcome to your change rather than to the adjustment. Worse, you cannot tell the difference between a real decline and a temporary movement that will reverse itself next week, which is precisely what practitioners watched happen this month. Every diagnosis made from a two-day window is now a guess wearing the costume of analysis.
You cannot reverse-engineer a system that is being rewritten while you read it.
Why does reactive optimisation become superstition?
There is a cycle worth recognising, because most teams are living inside it. A position moves. Someone notices and raises it. Changes are made under pressure. The position moves again, for unrelated reasons, and the changes are credited or blamed. Nothing was learned, effort was spent, and the team now holds a belief about what works that was produced by noise.
Repeat that quarterly for three years and you have a body of internal doctrine assembled entirely from coincidence. The beliefs feel earned, because they came from observation rather than from a blog post, and that is exactly what makes them hard to dislodge. The mechanism is the same one that produces superstition anywhere else: an unpredictable outcome, a ritual performed beforehand, and a mind that will not tolerate a missing explanation.
What survives an unreadable system?
If you cannot optimise for the mechanism, the only rational move is to invest in whatever the mechanism is trying to approximate. Every version of every ranking and answering system, past and future, is attempting to identify who is genuinely credible on a subject. The methods change constantly. The objective does not, because a system that stopped caring about credibility would simply be worse at its job.
That is why Earned Authority is the only asset in this field that does not depreciate on a model update. Independent validation is not a preference of a particular algorithm. It is the evidence every algorithm is built to detect, which means an investment in it is an investment in the objective rather than in a temporary implementation of it.
Earned Authority
Earned Authority is the independent validation of a business across the wider ecosystem, generated without prompting or payment. It is the one signal a business cannot manufacture alone, which is why systems weigh it heavily and why it survives changes to how those systems work.
The framework behind this argument
The named ideas from Become the Answer, set out in full.
If the reactive list is worthless, something has to replace it, and the honest replacement is a list of the places where your independent record is thinner than your claims. That is Authority Debt, and unlike a ranking position it is directly observable, does not fluctuate with the weather, and does not require you to know anything about how the system works this week.
Authority Debt
Authority Debt is the gap between how confidently a business describes itself and how little independent evidence exists to confirm it. It compounds quietly, it is unaffected by algorithm changes, and paying it down is the one form of progress you can measure without a dashboard.
Backlog item
Observable?
Affected by updates?
Position moved this week
Yes, but meaninglessly
Entirely
Claims with no independent confirmation
Yes, directly
No
Inconsistent naming across records
Yes, directly
No
Third-party coverage older than two years
Yes, directly
No
There is a particular pattern that this environment punishes hardest. A business that earned genuine recognition years ago, and has not maintained it since, looks stable right up until it does not. Volatility eventually catches a brand whose independent validation has quietly aged out, and because the decline arrives during a period of general noise it gets misread as an algorithmic penalty rather than what it is. That is Decaying Authority, and it is the pattern most likely to be misdiagnosed in a market that has learned to blame updates.
What should you do when the trackers light up?
Practically, the discipline is restraint. Hold reactive changes when trackers light up, because a weekend movement carries almost no information and acting on it introduces a variable you will misattribute later. Lengthen your observation window until it is long enough that continuous adjustment averages out, which in practice means months rather than weeks. And tell whoever asks about the movement, before they ask, that unannounced rolling updates are now the baseline condition rather than an event.
That last one is worth doing deliberately. Explaining volatility in advance converts an awkward conversation into a demonstration that you understand the system better than the people reacting to it. It is also true, which is the part that eventually matters most. The businesses that will hold their position through the next three years of silent rewriting are not the ones responding fastest to movement. They are the ones who spent that attention paying down Authority Debt while everyone else was refreshing a chart.
A note on the evidence in this article: the weekend movement described here is unconfirmed, detected by third-party trackers and forum reports rather than announced by Google. That is precisely the point being made, and it means the specific event should be treated as illustrative rather than established. What is established is Google's own statement that smaller core updates now roll continuously without announcement, and the consequences for attribution follow from that regardless of what happened on any particular Saturday.
Frequently asked questions
Do Google core updates still get announced?
Large core updates are still announced, but Google confirmed in 2026 that smaller core updates now roll continuously without announcement. That means most of the movement a site experiences will never be attached to a named event, and third-party trackers will register volatility that nobody confirms.
Should I react to a weekend ranking drop?
No. A two-day window carries almost no information when the system is being adjusted continuously. Movement over a weekend is frequently reversed the following week, and changes made in response will be credited or blamed for outcomes they had nothing to do with. Lengthen the observation window to months before drawing conclusions.
Why does reactive optimisation stop working?
Reactive optimisation depends on a feedback loop, and the loop depends on a stable target. You observe a position, change something, wait, and observe again. When the system is being adjusted during that observation window, the outcome cannot be attributed to the change rather than to the adjustment. The inference the method relies on is no longer available.
What should businesses invest in instead of chasing updates?
Whatever the mechanism is trying to approximate. Every ranking and answering system, past and future, is attempting to identify who is genuinely credible on a subject. The methods change constantly, the objective does not. Investing in independent validation is an investment in the objective rather than in a temporary implementation of it, which is why it does not depreciate on a model update.
What is Decaying Authority?
Decaying Authority describes a business that earned genuine recognition in the past and has not maintained it since. The position looks stable until it is not. Because the decline usually arrives during a period of general volatility, it tends to be misread as an algorithmic penalty rather than what it is, which makes it the most commonly misdiagnosed pattern in a market that has learned to blame updates.
How should I explain volatility to a client or a board?
Explain it before it happens rather than after. Tell them that unannounced rolling updates are now the baseline condition rather than an event, that short-window movement carries little information, and that you will not be making reactive changes on the basis of it. Pre-empting the conversation converts an awkward moment into a demonstration that you understand the system better than the people reacting to it.
Lucy Aingworth is an AI visibility strategist and brand authority consultant, and the author of Become the Answer. She helps founders and CMOs build the authority that AI search actually cites. More about Lucy
Where to start
Stop reacting. Start building something that holds.
The Recognition Diagnostic shows you where your independent record is thinner than your claims, which is the one backlog worth working through.