The August 2026 Spam Update: What Google Published

Sites that moved in the second half of August have one confirmed event to work with, and it is smaller than most of the commentary around it. Google’s Search Status Dashboard records an August 2026 spam update beginning on 18 August 2026 with a duration of 2 days and 16 hours. That entry is the whole of what Google published. The Search Central blog’s August 2026 archive contains one post, and it is about the site reputation policy.

The dashboard entry is the announcement

This matters because the usual shape of a spam update includes a blog post explaining scope — which practices it targets, whether it is global, whether it applies to all languages. There is no such post this time. Anyone telling you what the August 2026 spam update was designed to catch is inferring it, and the inference may well be reasonable, but it should be labelled as one. The ranking history on the Google Search Status Dashboard is the primary record and it carries three fields: name, start date and duration.

Cite the end as start plus duration

The dashboard gives a start date but not a start time, and it notes that all times are US/Pacific. A duration of 2 days and 16 hours from 18 August therefore completes on 20 or 21 August depending on the hour it began. That is not pedantry when you are correlating a traffic change against a rollout window: a report built on the wrong boundary attributes a Friday movement to a Wednesday cause. Write it as “18 August 2026, 2 days 16 hours” and let the boundary stay honest.

A spam update is not a core update

The two are frequently discussed as interchangeable, and they are not. A core update is a broad change to the ranking systems described in Google’s ranking systems guide, which are about relevance and quality assessment across the whole index. A spam update improves the automated systems that enforce published policy. Google’s spam policies for Google web search describe the mechanism directly: policy-violating practices are detected both through automated systems and, as needed, human review that can result in a manual action, and sites that violate the policies may rank lower in results or not appear at all.

The page was last updated on 28 August 2026, ten days after the update began, though that revision was the site reputation change rather than anything about the update itself. It is worth reading the current version regardless, because the definition at the top has widened: spam now explicitly includes attempting to manipulate generative AI responses in Google Search, a clarification Google made on 15 May 2026. The policies apply to all web search results, including those from Google’s own properties.

Two spam updates in the second half of 2026

Set against the equivalent rollouts on the same dashboard, the 2026 spam updates have been unusually short:

• March 2026 spam update — 24 Mar 2026, 19 hours 30 minutes.
• June 2026 spam update — 24 Jun 2026, 2 days 1 hour.
• August 2026 spam update — 18 Aug 2026, 2 days 16 hours.
• August 2025 spam update, for comparison — 26 Aug 2025, 26 days 15 hours.

A short rollout is not a small one, but it does mean the window in which movement can honestly be attributed to the update is narrow. If your traffic changed on 27 August, the August spam update had finished roughly a week earlier, and something else is the more likely explanation. There has been no spam update since, and no core update since 21 May 2026.

What recovery after a spam update looks like

The route depends on which mechanism touched you, and the distinction is sharp. A manual action appears in the manual actions report in Search Console, and the path back is remediation followed by a reconsideration request. Algorithmic spam detection produces no notification and there is nothing to submit; the site is reassessed as its pages are recrawled and re-evaluated, and the only lever is compliance with the published policies.

Neither route is content refreshing. Rewriting an article does not address a policy violation in how it was produced, how links were acquired, or how third-party sections are hosted. Work the policy list instead: read the current spam policies in full, identify which named practice your pages could be read as matching, and fix that specific thing. The policies covering produced-at-scale content are set out in the scaled content abuse policy, the acquisition side in what link building still works, and the distinction between ordinary republication and a violation in what actually triggers a penalty. And do not wait for the next update window before acting: nothing in Google’s documentation ties algorithmic reassessment to the next named rollout.