SEOGoogle
Google's August spam update and the policy on AI-answer manipulation
Google's August 2026 spam update ran from 18 to 21 August. The existing policy also covers manipulation of AI answers, but Google did not identify this update's specific targets.

Jump to a section
Google completed its August 2026 spam update on 21 August. Its spam policies already included manipulation of AI responses in Search. Those two facts belong together in an audit, but they do not prove that this rollout targeted a particular AI-search tactic.
What happened (added 19 September 2026): Google marked the rollout complete on 21 August 2026, a little under three days after it began, as Search Engine Roundtable reported. The comparison below still works; the window it measures now runs from 18 to 21 August.
The rollout and the policy
Google keeps a public list of things it treats as cheating. It calls this list its spam policies. Break them and your site can drop down the results, or disappear from Google altogether.
A spam update changes Google’s automated spam-detection systems. It is distinct from a manual action, which is recorded separately in Search Console.
This one began at 9:27 a.m. Pacific on 18 August, logged on Google’s Search Status Dashboard — the public page where Google records changes and outages in Search. Google published no blog post to go with it and named no new policy, as Search Engine Land and Search Engine Journal both noted.
It’s Google’s third spam update this year. March finished in roughly 19 and a half hours. June took two days and one hour. The August rollout finished on 21 August.
The May policy clarification
On 15 May, Google edited the first sentence of its spam policies page. The definition explicitly includes efforts to manipulate generative AI responses in Google Search, alongside manipulation of search rankings.
That final clause is the new part. Before, spam meant trying to get a page ranked where it didn’t belong. Now it also means trying to steer what the AI answer says about you — or about a competitor.
Search Engine Land reported the change at the time and read it as extending spam enforcement to a whole category of newer tactics: the ones aimed at getting named inside an AI Overview rather than at position three. Seeded forum threads. “Best tool for X” listicles written to be scraped by a model rather than read by a person. Pages published purely so that an answer engine repeats a particular sentence. We wrote about the seeding version of this earlier in the month.
Nothing about the August update tells us Google is enforcing that clause hard. Google hasn’t said. But the clause is live, this is the second enforcement pass since it went live, and it applies in every language.
Why it will be hard to tell what hit you
Google did not identify the specific tactics targeted by this update. The dashboard entry says “spam update” and that’s it.
A traffic decline during the rollout is not enough to identify its cause. Ranking spam and AI-answer spam are the same two words on the same status page.
It gets muddier. PPC Land points out that rank trackers picked up unexplained volatility on 1–3 August and again on 12–13 August, before any of this was confirmed. Movement in that window could have been early deployment, or something unrelated. There’s no way to separate them from the outside.
Recovery can also take time. Both Search Engine Journal and PPC Land land on the same figure from Google’s documentation: recovery from a spam action is measured in months, and isn’t guaranteed.
Investigating a change in performance
- Mark the date. In Search Console, compare 18 August onward against the two weeks before it, broken down by page and by query. The boundary is cleanest while the rollout is fresh.
- Ask two separate questions, not one. Did rankings move? Did citations move? A page can keep its position and still stop being quoted in the AI answer. Those are separate outcomes; investigate their causes rather than assuming they moved together.
- Audit anything you paid for. Placements, sponsored listicles, seeded threads, syndicated “reviews”. Review the intent and execution against the actual policy. Writing content that may be cited is not itself spam; deceptive or manipulative practices are the concern.
- Don’t panic-rewrite. Google’s standing advice on volatility hasn’t changed: fixing the fundamentals beats reacting to a three-day wobble.


