An unannounced update shook rankings around September 3rd. Ten days later, a good portion of it reversed. Google has confirmed nothing. Here is what actually happened, and why the businesses that panicked are now in the worst position of anyone.
If your organic traffic dropped in the first week of September and you have been trying to figure out what you did wrong, you probably did not do anything wrong. Something moved in Google's rankings around September 3rd and 4th. It was never announced, it was never explained, and for a meaningful number of sites it appears to have partially undone itself ten days later.
That sequence is unusual enough to be worth walking through carefully, because the lesson it teaches is the most expensive one in SEO, and almost every business owner learns it the hard way at least once.
Marie Haynes reported evidence of a significant, unannounced change in rankings, dating the start to roughly September 2nd.
Glenn Gabe tracked a number of large sites taking real impact across this window. Aggregate volatility trackers showed September 4th as notably more turbulent than surrounding days. Google said nothing.
Gabe posted publicly about the unconfirmed update, noting he had deliberately held off a full day first, waiting for the data to accumulate before saying anything. That restraint turned out to matter.
Gabe reported that for a number of the sites hit on September 4th, the impact was completely reversed. Publishers began reporting that Google Discover traffic was returning. Whatever changed appears to have been rolled back or re-tuned.
Google's Search Status Dashboard still lists the August 2026 spam update as the most recent confirmed ranking update. There is no named September update to look up, no start date, and no end date.
Here is why the reversal matters so much. Picture two businesses that saw identical traffic drops on September 4th. One reacted immediately. One did not. Tap between them.
Read the first one again, because the ending is the part people miss. The business that panicked did not just waste a week. It permanently lost the ability to know what works, because it can no longer separate the effect of Google's change from the effect of its own. Every future decision now rests on a conclusion that happens to be false.
Changes made during a rollout do not just risk hurting you. They destroy your ability to learn anything from what happens next.
When Google confirms an update, you get something valuable: dates. A confirmed core update has an announced start and a declared completion, which means you can compare a stable period before it against a stable period after it and isolate what actually changed. That is the entire basis of a credible diagnosis.
An unconfirmed update gives you none of that. You do not know when it started, whether it finished, or whether it might reverse, as this one apparently did for many sites. You are measuring against a moving target. Any edits you make in that window get permanently mixed into the result, and there is no way to untangle them later. We wrote about the normal, healthy version of ranking movement in why your rankings fluctuate, and most of what people panic about lives there.
Most traffic drops that get blamed on Google are not Google. Work through the cheaper explanations first, because several of them are fixable in an afternoon and none of them require touching your content. Tap each one.
If you work down that list and genuinely rule out the first five, then you are probably looking at an algorithmic shift, and only then does it make sense to think about content and quality. That order matters, because the expensive response is the last one on the list and most people start there.
Here is the process we follow on client accounts, and it is deliberately unexciting. The goal in the early days is not to fix anything. It is to preserve your ability to diagnose.
If the drop is still there after that, with a clear pattern and no simpler explanation, then you have something real to work on, and the baseline you protected is what makes the fix measurable. That investigation is exactly what a proper SEO audit is for.
There is a reason agencies do not love this advice. Telling a worried client to do nothing for three weeks feels like not earning your money, and there is real commercial pressure to look busy instead. Plenty of the frantic activity that follows a traffic drop exists to reassure the client rather than to fix the problem.
But the honest version is that patience is the skill. Google's systems change continuously, most of those changes are never named, some of them reverse, and the sites that come out of genuine algorithmic hits fastest are almost always the ones that gathered evidence before acting. Restraint is the work, even when it looks like the absence of work.
The long view helps too. Every business that got hurt and stayed hurt was usually vulnerable for a reason that predates any single update, which is the same conclusion we reached looking at the August spam update. Build something that deserves to rank and these weeks become news you read rather than emergencies you survive.
Something happened, but Google has not confirmed it. Independent trackers including Glenn Gabe and Marie Haynes reported a significant unannounced shift in rankings around September 2nd through 4th, 2026. On September 13th, Gabe reported that for a number of affected sites the impact had reversed. Google's Search Status Dashboard still lists the August 2026 spam update as the most recent confirmed ranking update, so this remains unconfirmed.
It is a noticeable shift in search rankings that industry trackers observe but Google never announces. Google updates its systems continuously and only names a small fraction of those changes. Unconfirmed updates matter because you cannot look up a start and end date, which means you cannot cleanly separate the effect of the update from the effect of any changes you make to your own site.
Not immediately. Document everything first, then wait to see whether the drop holds. Changes made during an unfinished or reversing rollout make it impossible to tell later whether a recovery came from your work or from Google. Rule out the simpler explanations first: tracking problems, seasonality, a technical issue on your site, or a manual action in Search Console. Only after a drop persists and has a clear cause should you start changing pages.
For a drop with no confirmed cause, give it at least two to three weeks of observation unless you find a specific technical problem. Rollouts take time, reversals happen, and Search Console data lags by a few days. The businesses that recover fastest from real algorithmic hits are usually the ones that gathered evidence before acting, because they kept a clean baseline to measure against.
Send us what you are seeing and we will tell you honestly whether it looks like an algorithm, a tracking problem, or nothing at all. We will not sell you a recovery package for a dip that is going to correct itself. Tell us about your site below, or get a quote and see what we have done for others in our success stories.