Update, 23 August 2026. Google confirmed the August 2026 spam update on 18 August, the day after this published, and it finished on 21 August. The gap described below ran from 26 June to 18 August. What this piece says about unconfirmed volatility still holds. The specific claim that nothing had been confirmed since June expired within a day of publication, which is a fair reminder that a dated observation is only true on its date. The original text is unchanged below.
Google’s Search Status Dashboard has been quiet since the June 2026 spam update finished on 26 June. No core update, no spam update, nothing in progress. That’s the longest gap of the year so far.
Meanwhile the volatility trackers and the timelines have not been quiet at all, with community reports of ranking movement through early and mid August. Every one of those reports describes an unconfirmed update.
What an unconfirmed update actually is
Google changes things constantly. It has said for years that it ships thousands of changes annually and announces only the broad ones. So a period with no announced update is not a period with no change, and volatility on a tracker is not evidence that a named update happened.
What the trackers measure is how much the results they sample moved. That tells you the weather. It cannot tell you the cause, and it certainly cannot tell you whether the cause was one update, several unrelated tweaks, or a shift in what people were searching for that week.
Why the gap is worth noticing anyway
Two or three core updates a year has been the pattern recently: March and May this year, with December before them. On that cadence the next core update is plausibly due between now and the autumn.
That is a pattern, not a schedule. Google has broken its own rhythms repeatedly, including dropping a core update 2 weeks before Christmas in 2025 after years of avoiding the holiday season. Anyone telling you the date of the next core update is guessing.
What to do about it
If your traffic moved in the last few weeks, the honest first step is to rule out the boring explanations before reaching for an unconfirmed update: seasonality, a tracking or tagging change, a deployment on your own site, a competitor’s move, or the SERP changing shape around stable rankings.
The diagnosis workflow on our update history works the same whether or not an update is confirmed. Match the dates, segment by page type, and check whether rankings fell or only clicks did.
And if it turns out an unnamed change did hit you, the response is identical to a named one, which is covered in core update recovery. There is no separate playbook for updates Google didn’t name.
Sources
Google’s Search Status Dashboard, checked today. Volatility reports are third-party and are described here as such.