The August 2026 spam update finished after three days

Google’s August 2026 spam update is finished. The Search Status Dashboard records the rollout as starting 18 August at 09:27 and completing 21 August at 01:49, US Pacific time: two days and 16 hours, applied “globally and to all languages,” per Google’s own incident note. Short enough that the start and end of the decline should read as clean edges in a daily Search Console export.

Spam update or core update#

A core update re-scores the index against revised notions of relevance and quality. Nothing is flagged. A site can lose visibility having done nothing newly wrong, and the recovery path runs through the content itself.

A spam update enforces specific policies: scaled content abuse, site reputation abuse, expired-domain abuse, cloaking, link schemes. The fix is not “improve the content” but “stop doing the specific thing,” and stopping does not register until Google’s systems reprocess the site on a later run.

How to check your own data#

Mark the dashboard dates on your series first. A decline that begins two days before the rollout is not the rollout, whatever the calendar suggests.

Segment by page group, not site total. Spam enforcement is usually concentrated: one template, one directory, one content programme. A site-wide, even decline is a weak match for a spam action.

Rule out the boring explanations before the algorithmic one. A robots change, a noindex shipped by accident, a CDN rule, a migration, seasonality. In most drop investigations the cause is on this list, and the update was a coincidence that happened to be nearby.

Why we care#

If it is a spam action, the audit question is whether the content programme in question would have existed at all with search traffic taken out of the equation. Identify the practice, not the page, remove or rebuild it, then accept the clock runs on Google’s next spam-update schedule, not yours. There is no reconsideration request for algorithmic spam enforcement, and no way to accelerate it.