An unconfirmed September update hit big sites, then fully reversed

A number of large sites lost significant Search and Discover traffic starting around September 3 into September 4, 2026, according to independent tracking by analyst Glenn Gabe. Nine days later, on September 13, the impact on a number of those same sites reversed completely and traffic surged back. Google confirmed nothing about either move, so what follows is what outside monitoring found, not what Google has said.

What did Glenn Gabe actually track#

Gabe, who monitors ranking volatility across a large set of sites, reported a number of large sites seeing a big impact starting around September 3 into September 4, 2026. Evidence he reviewed pointed to an underlying change dated around September 2, a day or two ahead of when the drop became visible in traffic. Some of the affected sites lost ground in both Google Search and Google Discover at the same time, which is notable on its own: Search and Discover run on different surfaces and do not always move together.

What happened on September 13#

On September 13, 2026, the impact on a number of the affected sites reversed completely, with traffic surging back. That is the detail that separates this event from an ordinary update: a full reversal, on a specific date, days after the drop, rather than a slow partial recovery spread over weeks the way a core update rollout typically resolves.

Why Google’s silence matters here#

Google did not confirm the drop when it happened, and it did not confirm the reversal either. That leaves the cause of both moves unknown. It could have been an unannounced ranking change that Google rolled back, a bug that was fixed, or something else entirely. Nothing here should be read as more certain than the tracking data allows: this is an unconfirmed event, described in hedged terms because that is what the evidence supports.

What to do with this if your traffic moved#

Check whether any drop in Search or Discover traffic on your own properties lines up with the window described here, roughly September 3 into September 4, 2026, and whether it recovered around September 13. A match does not prove cause, since Google never confirmed the update existed, but it narrows the search for an explanation before you look elsewhere. A move that does not fit this window is more likely a separate issue on the site itself.