Google is rolling out its third spam update of the year. Here's what it means if you own a trade business

On August 18, 2026, Google's status dashboard logged a ranking incident and the release note landed a minute later: the August 2026 spam update, rolling out globally and in every language. Google's wording was the same one-liner it uses every time — "Released the August 2026 spam update, which applies globally and to all languages. The rollout may take a few days to complete."

That is the third spam update of 2026, after March and after June. The June one went out on June 24 and finished on June 26. No new policy was published alongside the August rollout and no blog post explained it, which means it is enforcement of rules that already exist rather than a new rule.

A spam update is not a core update

These get mixed up constantly and the difference decides whether you should do anything. A core update re-weighs what counts as a good answer, so a perfectly clean site can move up or down. A spam update enforces a published list of things you are not allowed to do. Nobody drops in a spam update by accident of quality — they drop because something on the site matches a policy.

Google's own guidance on recovery is blunt about the timeline: fix the violation and its automated systems may take months to notice. There is no button, no appeal for an algorithmic drop, and no agency that can shorten it.

The thing that actually hits contractors

It is almost always scaled content abuse. You paid someone $300 a month and they generated a page for every city within ninety miles — Roof Repair in Ashland, Roof Repair in Medford, Roof Repair in Central Point — each one the same 600 words with the city name swapped. That is the pattern the policy names. It worked in 2019. It has been a liability since 2024.

• Forty near-identical city pages for towns you have never driven to.
• A blog posting three times a week that nobody at the company wrote or read.
• Service pages describing work you do not do, because they came with the template.
• A page for every combination of service and city, which is how you end up with 400 URLs on an eight-truck operation.

What to do this week

Open Search Console, set the date range to the last 28 days, and look for a step change after August 18 rather than a wobble. Daily noise is normal. A cliff is not.

• No change: nothing to do. You are not in scope.
• A cliff: sort your pages by clicks, find the ones that used to bring traffic, and read them. You will usually know within two pages.
• Thin pages you cannot defend: delete them or merge them into one real page. Deleting pages that were never read costs nothing.

One more thing worth saying plainly, because it gets sold as a fix: nobody can promise you a recovery date, and anyone who does is guessing at the end of a process Google says runs for months.

Written by Nick Georgalos, who builds the sites. Corrections go to the same number everything else does.