John Mueller told a practitioner on LinkedIn this week that Google does not begin rolling out a ranking update days before it tells the public. The answer closes a gap that has shaped how search teams read Search Console volatility charts for years. It also confirms, from inside Google, a conclusion this publication reached independently after tracking unexplained ranking movement ahead of the Google August 2026 spam update.
The question came from a practitioner who asked, over LinkedIn, why Search Console appeared to show rollout activity three to five days before Google made anything public. Mueller answered directly: “We don’t roll them out beforehand. We try to get the announcement as close as possible to the actual ‘button-pushing’ (which is sometimes challenging due to time-zones).”
That reply carries two separate claims, and search teams should keep them apart. The first is procedural: Google times its public announcement to the actual start of a rollout, not to some point after the update is already live and reshaping rankings. The second is specific to this cycle. Per Search Engine Roundtable’s Barry Schwartz, Google has told him the ranking movement seen before an official announcement is routinely unconnected to the update that follows, and that held true again for the August spam update.
Schwartz added institutional memory to Mueller’s answer. Google promised years ago to pre-announce updates and never delivered on that promise, because timing an announcement to a rollout that far in advance is not operationally realistic. Schwartz also flagged a complicating detail worth holding onto: small core updates roll out without any public notice on a routine basis, and on at least one occasion Google missed announcing a major update in real time, disclosing it only after the fact. Neither exception undercuts Mueller’s core point. An unannounced small core update is still a real update, just an unnamed one; a few days of pre-rollout drift ahead of a named update is a different phenomenon entirely.
This publication argued earlier this week that the spam update’s delayed announcement made it a poor candidate to explain the volatility search teams had already been tracking. Mueller’s answer reaches the same conclusion from the opposite direction, not by pointing at the calendar, but by describing how Google’s announcement process actually works. Two independent routes arriving at one answer is stronger evidence than either alone, and it is rare to get both the outside timeline and the inside mechanism confirming the same negative.
What this does not do is name a cause. Ruling out the spam update removes the explanation practitioners reached for first, since it was the most visible update on the calendar during that stretch. It does not identify what actually produced the earlier movement. Mueller offered no alternative explanation, and nothing in Google’s public documentation currently supplies one either. Search teams tracking that window are left holding a real signal with no attributed source, which is a less comfortable place than having a wrong answer.
For any team still tying ranking swings from earlier this summer to the August spam update, stop making that connection. Pull the Search Console data for the specific dates in question, cross-check it against site-level changes made in that window (content publishes, technical fixes, and link changes), and treat the underlying cause as unresolved until Google or an independent tracking tool names it. Attributing unexplained volatility to the nearest named update is now a documented mistake, not a reasonable guess.
Barry Schwartz reported this for Search Engine Roundtable on August 19, 2026.
