Google's August 2026 Spam Update: Dates and Our Correction

What we got wrong, precisely

The claim that failed was this one: as of 14 August 2026, Google had announced no core update that month. Both halves of it were checkable and both were true when published; the last row on the dashboard was dated 26 June and nothing had been added since. The error was not in the fact. It was in the confidence. Seven weeks of silence invites you to treat silence as a trend, and while the body hedged, the headline did not, and headlines are what most people read.

So, plainly: if your rankings moved between 18 and 21 August, there was an announced ranking update inside that window. The earlier version of this page would have talked you out of looking.

Every 2026 update, with dates

The dashboard records each announced ranking update with a start and an end. This year now has six rows, not the five we published:

That last row is the one this page was missing. Its incident entry is public and carries the timestamps, which is a level of detail almost no coverage bothers to quote.

One part of the original held up, and it is worth repeating rather than quietly deleting. The rumour circulating that week named 26 August specifically and attached a figure to it, something like 45% of sites shifting. The real update ran from the 18th to the 21st. That is five days before the date the rumour gave, and the 45% still appears in no primary source anywhere.

The explanation we guessed at is also still visible on the dashboard. There is a row dated 26 August on it, but the year is 2025: the August 2025 spam update, which began on 26 August and did not finish until 22 September. Right date, wrong year.

Which produces an odd but honest conclusion. An update happened and the rumour was wrong. Those two statements sit together fine, and anyone who has told you only one of them has told you half of it.

A spam update is not a core update

Here is the distinction that decides whether any of this applies to you, and it gets flattened constantly.

A core update reworks how usefulness is assessed across the board. It can demote a site that has done nothing wrong, simply because something else answered the query better. A spam update goes looking for specific patterns instead: bulk content generated to fill pages, purchased links, expired domains bought for their leftover authority, parasite pages hosted on a reputable domain.

The blast radius is narrower as a result. If none of those patterns describe your site, the odds that 18 August is your culprit are low, and two possibilities remain. Either a competitor doing those things was cleared out ahead of you, in which case you have risen rather than fallen, or your drop has nothing to do with this update and the overlapping dates have misled you.

If you dropped after 18 August

Now that a real date exists, the first job is establishing your own date, not explaining it.

Open the Performance report in Search Console, set it to 28 days, and read clicks and impressions separately. Impressions flat with clicks down is not a ranking problem; it is a title, description and competition problem on a results page you still appear on. Both falling together means the position genuinely moved. why Search Console and a rank tracker disagree covers why those two numbers rarely match.

Then line your date up against that two and a half day window. A decline that began on 16 August predates the update no matter how convenient the story is. And a two or three place slide lasting a few days is very likely nothing at all: how much ranking movement is normal puts a number on that boundary.

With no historical positions to compare against, five ways to check your Google ranking is the fastest route to a baseline. When you are ready to work through causes in order, a checklist for diagnosing a ranking drop runs in the sequence that actually pays: indexing, then your own changes, then technical, then competitors.

Do not skim past the second one. A redirect, a theme swap, a new caching plugin, a noindex left behind after testing. An update on the calendar is exactly the excuse that stops people checking, and that is where the expensive weeks go.

Where this argument stops working

One line from the original survived intact and means more now than it did then: no announced update is not the same statement as nothing changed.

The dashboard logs what Google chooses to announce, while ranking systems are adjusted continuously and quietly in between. That caveat was the only part of the earlier version that needed no repair, and without it this page would simply have been wrong rather than incomplete.

The reverse deserves saying too, and almost nobody says it. An announced update on the calendar does not prove it caused your drop. One date overlapping another is a coincidence, not a diagnosis, and plenty else has happened on your site since 18 August.

If you have worked through all of this and are still stuck, tracing a ranking drop with our SEO team is the work we actually do, and it opens with the same two checks above rather than a six month retainer.

Sources

• Google Search Status Dashboard for the dated list of announced updates
• the August 2026 spam update incident page with exact start and end times
• Google Search Central Blog for official announcements

All three were re-checked on 5 September 2026, the day this page was corrected. If you are reading later, open the dashboard yourself, which is the thing we were slow to do.