We’re kickstarting a brand new series here at SEW, where we will do our best to watch and report in search engines’ updates. As you are probably aware, not all of them are announced, only the bigger ones. However, a lot of webmasters, publishers and agencies report ongoing fluctuations and volatility.
Tracking potential Google algorithm updates [August 2026]
Various ranking trackers detected sharp movement, but publisher reports point to a messy combination of Search, Discover, indexing and analytics disruption.
For the record, Google has not confirmed an algorithm update in August 2026 but publishers and site owners are nevertheless reporting abrupt traffic losses, unstable rankings and unusual Discover behaviour.
The obvious conclusion might be that Google has quietly launched another major update. The evidence, however, is nowhere near that straightforward.
Search Engine Roundtable’s Barry Schwartz first reported heightened volatility between August 1 and August 3, citing spikes across several third-party tracking tools and growing discussion among search marketers.
Search Engine Watch subsequently reviewed 88 visible posts and comments across Reddit, Search Engine Roundtable and WebmasterWorld. The reports continued well beyond August 3 but they did not agree on when the disruption began, which Google product was affected or even whether traffic was rising or falling.
One publisher said keyword positions had improved while traffic declined by 14%. Another reported roughly 50% less traffic despite seeing no meaningful ranking changes.
Those accounts matter because they could point to changes in click-through rates, search features or measurement and not necessarily an algorithmic demotion.
Google Discover traffic falling
The timing was equally inconsistent. The clearest Reddit example showed an organic traffic decline beginning around July 22–24, more than a week before the supposed August update. A Brazilian publisher said Discover traffic had been falling since mid-July, while an Indonesian publisher reported slower indexing on August 5.
There were positive reports, too. One UK operator said results on August 6 appeared to be returning to their pre-July state.
The sharpest account came from WebmasterWorld.
A publisher said Google traffic across several sites dropped by at least 70% on August 5, with a shop, advertising campaigns and a news site all affected. Hours later, the same person reported that traffic had surged back, sales had jumped and fresh news articles were appearing again by the following morning.
Other participants could not reproduce the decline. One reported normal traffic but weaker sales. Another discovered that an apparent performance problem was caused by their own server.
That is not the consistent pattern normally needed to identify the impact of a broad ranking update.
There were also widespread complaints about GA4 real-time reporting on August 4. Google did not record an Analytics incident, although it did confirm a separate Google Ad Manager disruption lasting from 09:26 to 19:00 UTC that day. We’ve actually seen this happen across our properties, as well.
The advertising incident does not explain changes in organic rankings. It does show why traffic, revenue, analytics and search visibility should not be treated as interchangeable signals.
So, is Google rolling out an update?
Possibly, but there is not enough evidence to call this an August core update or claim that it targets a particular type of site.
Google’s Search Status Dashboard shows no ranking, indexing, crawling or serving incident between August 1 and August 6. Its latest confirmed ranking change remains the June 2026 spam update, which began on June 24 and completed on June 26.
The responsible conclusion is narrower: Google’s results became unusually volatile around August 1, while publishers experienced several overlapping disruptions through August 6. Those disruptions may not share a single cause.
Site owners should compare Search Console positions, impressions and clicks separately; isolate Discover and Google News traffic; verify GA4 data against another source; and rule out technical problems before making major changes.
Our comments’ section is open, so if you have anything else to add, let us know what you’ve observed so far.
