Confirmed Google Update

The Google Spam Update of August 2026

According to the Search Engine Journal, the August 2026 spam update ran from 18/08/2026 to 21/08/2026, Pacific time, and was the third spam update of the year after March and June. According to the Search Engine Land coverage of its launch, Google stated it applies globally and to all languages. According to SE Ranking, reported by Search Engine Land, top-10 exits past position 100 rose sharply in the comparison window — but that study does not identify which techniques caused any individual site's drop.

The Update in Numbers

18/08/2026
Start of the rollout, at 9:27am Pacific time, according to the Search Engine Journal
2d16h
Total duration of the rollout, according to the Search Engine Journal
16,71%
Of top-10 URLs fell past position 100 in the comparison window, according to SE Ranking
Global
Scope stated by Google: all regions and languages, according to Search Engine Land

What changed in the August 2026 spam update?

Direct Answer

Google ran a broad spam update between 18/08/2026 and 21/08/2026, and a study by SE Ranking, reported by Search Engine Land, found a sharp rise in sites falling out of the top 100 in that window — but the study does not say which specific practices caused those drops.

This gap matters more than it sounds. It is tempting to read a drop that coincides with the update as proof of a specific mistake — too many AI-generated articles, a bought link, a page per city — and rewrite that one thing. Without evidence tying your own drop to a named cause, that rewrite is a guess with a cost, not a correction with a target. The honest first move is checking whether your account shows any manual action at all, which the update itself does not create.

When it started, when it ended, and how it compares to the others

According to the Search Engine Journal, the rollout began on 18/08/2026 at 9:27am Pacific time and finished on 21/08/2026 at 1:49am Pacific time, a duration of two days and sixteen hours. The same source counts it as the third spam update of 2026, after ones in March and June — a pace of roughly one every two months so far this year.

According to the Search Engine Land coverage of the launch, Google described the update as applying globally and to all languages — it was not framed as targeting a specific country, sector or content format.

A real effect, without a named cause

What SE Ranking measured
16.71% of top-10 URLs fell past position 100
Comparing 100,000 keywords across 20 sectors, US organic results, between rankings on 17/08 and 22/08, against a 9.2% baseline in a window with no confirmed update — an 82% increase in exits from the top 100, according to SE Ranking.
What SE Ranking did not measure
Which techniques caused each drop
The study reports the size of the movement, not the reason behind any single site's fall. Attributing your own drop to a specific practice — content volume, links, page structure — needs your own evidence, not this study.

For Roberto Wydra, founder of RudekWydra, the practical consequence is to resist the single-cause story. "A study with a percentage this size tells you the update was real and broad. It does not tell you why your specific site moved, and treating it as if it did leads to fixing something that was never the problem", he says.

Check the report before you rewrite anything

The order matters. Confirm whether there is a manual action, then look at your own practices against the policies Google names, and only then decide what, if anything, to change.

The Order to Follow

1. Manual Actions report
Empty means no named action against you.
2. Audit against the four abuses
Scaled content, doorway, links, site reputation — see the hub map.
3. Decide, then act
Only after a specific match, correct it and follow the recovery timing page.

FAQ

What changed in the August 2026 spam update? +
According to the Search Engine Journal, Google rolled out a spam update from 18/08/2026 to 21/08/2026, the third of the year. According to SE Ranking, top-10 exits past position 100 rose sharply in that window, but the study does not identify the techniques behind any individual site's drop.
How long did the update take to finish rolling out? +
According to the Search Engine Journal, two days and sixteen hours, from 9:27am Pacific time on 18/08/2026 to 1:49am Pacific time on 21/08/2026.
Was this the first spam update of 2026? +
No. According to the Search Engine Journal, it was the third of the year, after updates in March and June.
Did the update target a specific country or language? +
No. According to the Search Engine Land coverage of the launch, Google stated it applies globally and to all languages, with no country or sector named as the target.
How many sites actually lost ranking? +
According to SE Ranking, reported by Search Engine Land, in a sample of 100,000 keywords across 20 US sectors, 16.71% of top-10 URLs fell past position 100 in the comparison window, against a 9.2% baseline before the update — an 82% increase.
Does the SE Ranking study say which mistakes caused the drops? +
No. According to SE Ranking, the study measured the size of the movement across sectors, not the specific technique behind any individual site's drop. Attributing a cause to your own case needs your own evidence.
My traffic fell right after the update. Was I penalized? +
Not necessarily. A broad update recalculates relevance without naming a manual action. Check the Manual Actions report in Search Console first: an entry there means a specific practice was flagged; an empty report points to the broad update as the more likely cause.
What should I do first after a drop that coincides with this update? +
Check the Manual Actions report before changing anything. Only after confirming there is no named action should you review your own site against the four abuses Google Search Central defines, and act on a specific match rather than a guess.

Find out if the update explains your specific drop

The diagnosis reads your Manual Actions report and your site structure before recommending any content or link change.

See Where to StartEvidence first, correction afterwards