Google began rolling out its August 2026 spam update on the 18th and confirmed it finished on the 21st. The whole thing took two days and sixteen hours, applied globally, and covered every language. If your organic traffic changed shape in that window, this is the first thing to check, and if it changed outside that window then this update is almost certainly not your cause.
That second half matters more than people expect. Most traffic drops blamed on an algorithm update turn out to have started before the rollout or after it ended. The dates are the cheapest diagnostic you have.
A spam update is not a core update
These get treated as interchangeable and they are not. A core update changes how Google weighs quality across the whole web. Nearly every site sees some movement, and the sites that lose are usually not breaching any policy. They have simply been reassessed against everyone else.
A spam update is narrower. It improves how well Google detects violations of spam policies that already exist. The rules did not change in August, and Google announced no new policy types with this rollout. What improved was enforcement.
The practical difference is what a recovery looks like. After a core update, you improve the site and wait for the next reassessment, which is slow and frustrating and has no guaranteed date. After a spam update, if you were hit, something specific triggered detection. Find it, remove it, and the path back is clearer.
This is why the diagnosis has to come before the work. We have written before about what to do after a core update, and the approach genuinely differs. Applying core update advice to a spam update problem means spending months improving content quality while the actual trigger sits untouched.
Check the dates before you check anything else
Open Search Console, compare the four weeks either side of 18 August, and find where the line changes direction. You are looking for a step, not a slope.
A step change inside the 18 to 21 August window is consistent with this update. A gradual decline that began in July is not, whatever else was happening in August. A drop that started on the 25th is not either, and chasing this update will waste the time you should spend finding the real cause.
Seasonality catches people here. Traffic moves in late August for reasons unrelated to Google, and a business selling to European clients often sees August dip and September recover on its own. Compare against the same weeks last year before concluding anything.
Also separate impressions from clicks. If impressions held and clicks fell, you probably have a presentation problem rather than a ranking problem, and that is a different investigation entirely.
We ask for the exact date traffic moved before anything else, because the answer is often days away from the update and the investigation goes somewhere entirely different.
What spam updates actually target
Google's spam policies are published and stable. They cover scaled content abuse, site reputation abuse, expired domain abuse, cloaking, sneaky redirects, hidden text and doorway pages. This update sharpened detection against those existing rules rather than adding to them.
Two of these catch legitimate businesses more often than the rest, and neither feels like spam to the people doing it.
Scaled content abuse is producing many pages primarily to rank rather than to help anyone, and it does not require automation. A hundred near identical location pages written by a person still qualify, as does a programme publishing daily against a keyword list without anyone asking whether the pages say anything. The volume is not the problem. The absence of a reason for each page to exist is.
Site reputation abuse is hosting third party content on your domain to borrow your authority. Sponsored post sections, coupon subdirectories, and guest content published without meaningful oversight all fall here. Many businesses added these years ago as a small revenue line and forgot about them.
Notably, this update did not target link spam. If your backlink profile is your worry, that is a separate mechanism with separate updates, and the August dates tell you nothing about it.
The sites we are asked to look at after one of these are rarely the ones doing anything deliberately manipulative. They are sites that published a great deal of thin material because it was cheap, and the enforcement caught the pattern rather than the intent.
The AI content question, answered precisely
Every spam update produces the same speculation about AI written content. The position has not changed, and it is more specific than the discussion usually allows.
Google's policy targets scaled content abuse, which is defined by intent and value rather than by production method. Content generated to manipulate rankings violates the policy. Content that helps a reader does not, regardless of what wrote the first draft. There is no penalty attached to the tooling.
What changed is that thin content is cheaper to produce, so more exists and detection improved to match. If your programme generates volume against a keyword list with light review, the risk is real. Not because a machine wrote it, but because nobody could say why each page needed to exist, which we covered in how Google identifies thin content.
The test worth applying to every page is uncomfortable and useful. If this page did not rank at all, would anyone miss it. If the honest answer is no, you have found something.
If you were hit, work through this order
Start with the pages that lost, not with the site as a whole. Export the queries and URLs that dropped and look for a pattern. Spam update losses usually cluster, and the cluster tells you the trigger.
Then read the pages with the policy text open beside you. Not with a general sense of quality, but against the specific published rules. Most sites that recover do so by finding one identifiable thing and removing it, rather than by broadly improving everything.
Removal usually beats improvement for genuinely thin pages. A page with no reason to exist does not become valuable through editing, and leaving it while adding better content elsewhere keeps the signal on your site.
What recovery actually looks like
Fixes are not reflected immediately. Google has to recrawl the affected pages, which takes weeks on a large site. Removing content today and checking rankings on Friday tells you nothing.
Recovery is usually tied to subsequent updates rather than arriving continuously. You may fix the problem in September and see nothing until a later rollout reassesses the site. That is why the diagnosis has to be right before the work starts. Fixing the wrong thing and then waiting three months is an expensive way to learn nothing.
Keep a written record of what you changed and when. When movement does arrive, that record is the only way to know which change caused it, and without it you will repeat the guesswork next time.
The wider position this sits inside
Spam updates land against a search landscape that is shrinking as a traffic source regardless of enforcement. Search volume is falling, AI answers absorb a growing share of informational queries, and a ranking recovery in 2026 returns you to a smaller pool than the same position delivered two years ago.
That is not an argument for ignoring the update, but against treating recovered rankings as the finish line. The businesses handling this period well fix what they can control while building demand that does not depend on a results page. We set that out in proving SEO value when clicks fall.
If your traffic moved in August and you are not certain why, our website development team runs the diagnosis against the actual rollout dates before recommending anything, because the first job is establishing whether this update is even your problem.
Frequently Asked Questions
When exactly did the August 2026 spam update roll out?
It began on 18 August and Google confirmed completion on 21 August, taking two days and sixteen hours in total. It applied globally and to all languages. Ranking movement that began clearly outside that window has a different cause, which is the most useful thing these dates give you.
How do I tell a spam update from a core update?
Check the pattern and the date. Core updates move rankings broadly across a site and affect nearly everyone to some degree. Spam update losses cluster in specific pages or sections, because a specific policy violation triggered them. Google confirms both types on its Search Status Dashboard, so the classification is published rather than something you need to infer.
Was this update about AI generated content?
Not specifically. It sharpened detection of existing spam policies, including scaled content abuse, which is defined by intent rather than by how the text was produced. AI assisted content that serves a genuine purpose is not in scope. High volume content produced to rank, with no reason for each page to exist, is in scope whether a person or a machine wrote it.
Does this update target backlinks?
No. This rollout did not target link spam. If your concern is your backlink profile, the August dates are not evidence either way, and you should be looking at a different set of signals entirely.
How long does recovery take?
Longer than most people expect. Google has to recrawl the affected pages, which takes weeks on a large site, and spam update recovery is often tied to a later rollout rather than arriving gradually. Plan in months rather than weeks, and keep a dated log of changes so you can attribute movement when it comes.
Should I delete affected pages or rewrite them?
It depends on whether the page has a reason to exist. If a page was created to capture a keyword and offers nothing a reader would miss, removal is usually cleaner and faster than editing. If it addresses a real need but does it poorly, improve it. The question is not writing quality, it is whether the page should be on the site at all.
My traffic dropped but not during the rollout window. What now?
Then this update is not your cause, which is useful to establish early. Check seasonality against last year, deployments around the date, whether impressions or clicks moved, and whether AI Overviews began appearing for your main queries. Each produces a different pattern, and matching the pattern to the date is how you avoid fixing the wrong thing.
Talk to our team if your traffic moved in August and you want the diagnosis done against the dates rather than by guesswork.