Google August 2026 Spam Update: Timeline, Targets and Recovery
Google confirmed the August 2026 spam update on 18 August, three weeks into volatility it never confirmed. Here is how to tell which one moved your rankings.
Google released the August 2026 spam update at 09:27 Pacific on 18 August 2026. It is the third spam update of the year, and the first one that can act on AI Overviews and AI Mode.
- What Google actually said: One line on the Search Status Dashboard: the update applies globally and to all languages, and the rollout may take a few days. No blog post, no new policies, no impact figures, no named targets.
- Nothing finished in mid-August: The last confirmed ranking change before this one was the June 2026 spam update, which ended on 26 June. Between 26 June and 18 August, Google's ranking incident log is empty. If you remember an update wrapping up around the 16th, what you are remembering is tracker movement Google never confirmed.
- So the calendar rules most sites out: Trackers moved on 1 to 3 August, again on 5 and 6, and again around 12 and 13. An update that started on the 18th cannot explain a fall that started on the 12th. Date the drop before you diagnose it.
- It is the slowest spam rollout of the year: March 2026 took 19 hours 30 minutes and June 2026 took 2 days 1 hour. The August update passed three days with no completion note on the dashboard at the time of writing.
- A spam update is not a small core update: Core updates re-evaluate quality. Spam updates enforce 16 named policies, and the enforcement is punitive. Fixing the violation starts a wait measured in months, and the ranking benefit of spammy links never comes back at all.
- The new part is where it reaches: On 15 May 2026 Google extended the same spam policies to AI Overviews and AI Mode. Search Console reports those surfaces as impressions with no clicks, no position and no queries, so a demotion there is visible as a shape rather than a number.
If the spam update hit you, the work is a policy audit, not a content refresh. If your drop predates the 18th, the work is a better diagnosis.
Telling a spam update apart from a core update, a Discover swing, a reporting artefact and your own last deploy is a dating exercise before it is a diagnosis. CrawlRaven joins Search Console, GA4 and a 200-point crawl into one ranked plan, from $49 at launch. Try CrawlRaven free: 1 site, no credit card →
Google has confirmed exactly one ranking change in the last eight weeks. It started at 09:27 Pacific on 18 August 2026, and for most sites reading recovery advice this week, it is not the thing that moved their rankings.
The August 2026 spam update is real, global and still rolling. It is also the fourth or fifth candidate explanation for a month of traffic losses that started before it existed. Those are two different stories, and the trade press has been publishing them as one.
Here is what this piece covers instead of another rollout recap:
- Everything Google actually confirmed, with timestamps, and the 53-day gap before it.
- Why the first day of your drop rules more candidates in and out than any tracker chart can.
- What a spam update can act on, including the two things that quietly changed in 2026.
- Why a demotion inside AI Overviews or AI Mode is now possible and still barely measurable.
- What recovery means here, and what it will not mean.
What Google confirmed, to the minute
On 18 August 2026 Google opened an incident on the Search Status Dashboard at 09:27 Pacific time and logged the release note a minute later, at 16:28 UTC. The entry says the update “applies globally and to all languages” and that the rollout may take a few days to complete.
That is the entire official record. Note what is missing:
- No blog post. Core updates usually get one on Search Central. This got a dashboard line and a short social post repeating it.
- No new policies. Google's spam policies page was last updated on 15 May 2026 and did not change for this rollout.
- No named targets. Nothing about which violations the refreshed systems are catching better than before.
- No impact figure. Google gave no percentage of queries affected, which it does sometimes give for core updates.
- No completion time. At the time of writing the entry still carries no duration, three days in.
That last point is worth sitting with. The March 2026 spam update completed in 19 hours and 30 minutes, the fastest on record. The June 2026 spam update took 2 days and 1 hour. August is already slower than both, and a rollout that is still open is a rollout whose effects are still landing.
| 2026 spam update | Released | Duration | New policies |
|---|---|---|---|
| March 2026 | 24 March, 12:18 PT | 19 hours 30 minutes | None |
| June 2026 | 24 June, 09:03 PT | 2 days 1 hour | None |
| August 2026 | 18 August, 09:27 PT | Still open at 3 days | None |
The empty window: 26 June to 18 August
Ask around and you will hear that an update “finished around the 16th”. It did not. Google's ranking incident log records nothing at all between 26 June, when the June spam update closed, and 18 August, when this one opened.
That is 53 days with nothing logged, in a stretch when rank trackers moved three separate times. The gap is where the confusion comes from, and it is also the single most useful fact in this story.
Two confirmed events in eight weeks
Everything Google logged between 24 June and 21 August 2026
Released 24 June at 09:03 Pacific and logged at 2 days 1 hour. The last ranking change Google confirmed before August.
Third-party rank trackers register a sharp burst of reshuffling. Google logs no ranking incident for any day in the window.
Volatility heats up again, mixed with publisher reports of Discover, indexing and analytics problems in the same week.
Trackers move once more. This is the window most people mean when they say an update finished in mid-August.
Announced on X by Robby Stein, VP of Product for Search. An opt-in model choice for AI Pro and Ultra subscribers in English, not a change to ranking systems.
Released 09:27 Pacific, 16:28 UTC. Applies globally and to all languages. Google says the rollout may take a few days.
At publication the dashboard entry carries no duration. Past three days, this is already the slowest of the three 2026 spam rollouts.
Update dates, times and durations from the Google Search Status Dashboard, checked 21 August 2026. Tracker movement as reported by the SEO trade press.
Two entries on that timeline carry Google's confirmation. The rest are things that happened to search results without Google saying anything, plus one model change that is not a ranking system at all.
Rank trackers sample a fixed set of keywords every day and report how much the results moved. A spike means the results changed. It does not say what changed, whether Google intended it, or whether your site was in the sample. Google confirms an update when it logs one on the Search Status Dashboard, and only then.
We covered those waves as they happened, in the diagnosis piece on the early-August volatility. The argument there was that four very different causes draw the same chart. Six weeks later, one confirmed update has arrived, and it does not retroactively explain any of them.
Date the drop before you diagnose it
The cheapest diagnostic in SEO is a calendar, and almost nobody runs it first. Open Search Console, set the comparison to daily, and find the first day clicks fell and stayed down. That single date rules more candidates in and out than any tracker chart will.
Start with the date, not the theory
What the first day of your drop rules in, and what it rules out
The June 2026 spam update, the May core update still settling, or a change you shipped yourself.
The August 2026 spam update. It did not exist for another seven weeks.
Your deploy log against the first day clicks moved, then Search Console page indexing for the same week.
One of the three unconfirmed volatility windows, a Google Discover swing, a reporting artefact, or your own release.
The August 2026 spam update. Google started it on 18 August, five days after the last of those waves.
Average position against clicks. If position held and clicks fell, this is a surface or reporting story, not a ranking one.
The spam update is now a live candidate, alongside everything else that happens in a normal week.
Nothing yet. A date that fits is the weakest evidence in the diagnosis, not the strongest.
Whether the losing pages share a policy risk. Spam updates hit patterns, not random samples of your site.
Content decay. Queries you used to win drifting down one at a time while the totals hide it.
Every update on this list. Decay has no start date because it has no event.
Page-level impressions over 16 months, not the site total over 28 days.
Three of the four windows are settled with data you already hold, and none of them needs anyone else's tracker.
The reason this works is that updates have start times and your problems have start times, and they either line up or they do not. A fall that began on 12 August cannot be caused by a system Google switched on at 09:27 on the 18th.
Every update cycle produces a wave of sites rewriting content that was never the problem. This one is worse than usual, because the confirmed update arrived three weeks late to a volatility story that had already been running, and slotted neatly into the empty explanation everyone was holding.
If you cannot name the first day your clicks fell, you are not ready to decide what to change. That is not pedantry. It is the difference between a policy audit, a content project, a rollback and doing nothing, which are four incompatible responses to what looks like one chart.
A spam update is not a small core update
These two get treated as different sizes of the same event. They are different events, and they call for different work.
- A core update re-evaluates. It reassesses how useful your pages are relative to everything else available, and Google is explicit that dropping in one is not a penalty.
- A spam update enforces. It refreshes the automated systems that detect violations of 16 named policies. The demotion is the point.
- The recovery clocks differ. Core update recovery typically waits for the next core update. Spam update recovery waits for Google's systems to observe compliance over months.
- Link spam is asymmetric. When spammy links stop counting, cleaning them up does not restore what they were worth. That benefit is gone for good.
- Neither one is a manual action. Both are algorithmic. A manual action follows human review and appears in Search Console under Manual Actions, where an algorithmic demotion never does.
We wrote up the same distinction when the March update set its speed record, in the March 2026 spam update analysis. The distinction has not aged; the enforcement surface has.
What this update can actually act on
Since no new policy shipped, the scope is the existing list. Google names 16 of them, and refreshing SpamBrain changes how reliably violations are caught rather than what counts as a violation.
16 policies, now across three surfaces
What the August 2026 spam update enforces, and where it reaches
Covered since the policies existed
Brought under the same policies on 15 May 2026
Brought under the same policies on 15 May 2026
Policy list from Google's spam policies for Google web search, last updated 15 May 2026. No new policy shipped with the August update.
Four of those 16 are where most legitimate businesses get caught by accident, usually through a decision someone made for a good reason:
- Site reputation abuse. Third-party content published on your domain mainly to borrow its ranking signals. Coupon sections, rented subfolders and syndicated “partner” content are the usual shapes.
- Scaled content abuse. Many pages generated primarily to rank rather than to help, and Google's wording names generative AI tools explicitly. Scale is not the violation; scale without added value is.
- Expired domain abuse. Buying a domain for its history and repurposing it for unrelated content. Common in migrations that were really acquisitions.
- Thin affiliation. Affiliate pages built on merchant descriptions with nothing original added. The most common accidental violation on ecommerce content sites.
The two things that changed in 2026
Between the June update and this one, the policy set moved twice. Both changes predate the rollout, and both are in scope for it.
- Back button hijacking, added 13 April 2026. Google named it explicitly under malicious practices: inhibiting a visitor's return to the previous page to keep them on your site. Enforcement started on 15 June 2026, so August is the first spam update to roll out with it fully live.
- Generative AI manipulation, added 15 May 2026. The spam policies page now states that spamming includes attempting to manipulate AI responses in Google Search. It was the first time AI manipulation was named directly in the policy.
If your site uses history manipulation, interstitials that trap the back gesture, or any pattern designed to make leaving harder, that is now a named violation rather than a dark pattern with no policy attached. A redirect checker will show you the hop chain a visitor actually experiences, which is where these patterns usually hide.
The first spam update that reaches AI answers
The 15 May change is the more consequential one, and it has been almost absent from this week's coverage. Extending the policies to AI Overviews and AI Mode means the same enforcement can now change which sources those surfaces are willing to cite.
For anyone who has spent 2026 building content specifically for AI citation, that is the sentence to read twice. The tactics that felt untouchable because they lived outside classic ranking are inside a named policy now, and a spam rollout is how the policy gets applied.
You can be demoted on a surface you can only half measure
Here is the problem with enforcement reaching AI answers. Search Console's generative AI report, launched on 3 June 2026, gives you impressions for AI Overviews and AI Mode, plus pages, countries, devices and dates. It does not give you clicks, position, CTR or query data.
So a demotion inside an AI surface shows up as impressions falling with nothing to compare them against. You cannot see the position you lost, because position is not reported. You cannot see which queries stopped citing you, because queries are not reported either.
- What you can still do: read the impressions trend by day and by page, and line the shape up against 18 August.
- What you can still do: watch referral traffic in analytics, since a citation that used to send people and stopped is measurable at your end.
- What you cannot do: separate an AI Mode loss from a classic ranking loss using position, because one of the two has no position to report.
- What nobody can do: tell you which model answered a given query, since Gemini 3.7 Flash became an opt-in choice for paid subscribers on 14 August and the help documentation does not say what runs by default.
Our breakdown of what the Search Console AI reports track and leave out goes through the reporting gap in detail. It was written as an analytics story. The May policy change turned it into an enforcement story.
How to tell whether it was you
Work in this order. Each step is cheap, and each one either eliminates the spam update or sharpens the case for it.
- Find the first bad day. Daily clicks in Search Console, 90-day window. Before 18 August, stop here and diagnose something else.
- Check whether position moved. If average position held and clicks fell, you are looking at a SERP layout or surface change, not a demotion.
- Look for a pattern in the losers. Export the losing pages and ask what they share. A spam update hits a category of pages, not a random sample.
- Test that pattern against the policy list. Syndicated sections, programmatic templates, affiliate pages, pages on a purchased domain, pages built from a link campaign. Name the policy or drop the theory.
- Confirm the loss in a second source. GA4 sessions from organic search should agree that fewer people arrived. If they disagree, you may have a reporting problem rather than a ranking one.
- Check Manual Actions anyway. It takes ten seconds. Algorithmic demotions never appear there, so a clean report tells you which kind of problem you have.
Steps one and two settle most cases. That is the whole argument for doing them before you read another recovery checklist.
What recovery means after a spam update
The word oversells it. There is no reconsideration request for an algorithmic demotion, no ticket to file, and no date to wait for the way a core update gives you one.
- Remove the violation, do not disguise it. Deleting a syndicated subfolder counts. Adding an author byline to it does not.
- Expect months, not weeks. Google's guidance is that its automated systems need to observe compliance over a period of months before anything changes.
- Accept the permanent loss on links. Rankings that came from spammy links do not return when the links go. Budget for the lower baseline rather than chasing the old number.
- Keep the site crawlable while you wait. Compliance has to be observed, which means the fixed pages have to be fetched, rendered and re-evaluated.
- Do not stack changes. If you rewrite the site while the rollout is still open, you will never know which change did what.
What to do this week
None of this depends on the rollout finishing, which is the point. Each step is worth doing whether the update touched you or not.
- Date every drop you are worried about. Write the first bad day next to each one. Half your open questions will resolve themselves.
- Run a policy audit, not a content audit. Walk the 16 policies against your own site and be honest about the four that catch legitimate businesses.
- Inventory your third-party content. Every subfolder or subdomain publishing someone else's content on your domain is a site reputation abuse question waiting to be asked.
- Check your exit paths. Back button hijacking has been an enforceable policy since 15 June. Verify what happens when a visitor tries to leave.
- Baseline your AI impressions now. Save the current generative AI report numbers, because the comparison you will want in October needs a before.
- Wait for the completion note before judging. Rankings keep moving while a rollout is open, and a day-three reading is not a result.
What not to do
- Do not assume it was the update. The dates rule it out for most sites, and a coincidence of timing is the weakest evidence in the whole diagnosis.
- Do not disavow reflexively. Cleaning up links you did not build has no upside here, and the ranking benefit of the ones you did build is already gone.
- Do not delete pages in a panic. Removing a section that was never in violation costs you the traffic it was earning and teaches you nothing.
- Do not rebuild on one tracker's chart. Trackers sample keywords that are not yours. They are a weather report, not a diagnosis of your site.
- Do not read silence as safety. The rollout is still open, and the AI surfaces where it now applies report impressions without clicks, position or queries.
Key Takeaways
- →What is confirmed: Google released the August 2026 spam update on 18 August 2026 at 09:27 Pacific, 16:28 UTC. It applies globally and to all languages, shipped with no new policies, and had no completion note on the dashboard three days in.
- →What is not confirmed: Nothing between 26 June and 18 August. Trackers moved on 1 to 3 August, 5 to 6 August and around 12 to 13 August, and Google logged no ranking incident for any of those days.
- →The date test: A drop that began before 18 August cannot have been caused by this update. Finding the first day clicks fell and stayed down eliminates more candidates than any third-party chart.
- →Spam is not core: Core updates re-evaluate quality and are not penalties. Spam updates enforce 16 named policies, recovery is measured in months, and the ranking benefit of spammy links never comes back.
- →The new enforcement surface: Google extended its spam policies to AI Overviews and AI Mode on 15 May 2026 and named back button hijacking on 13 April 2026, with enforcement from 15 June. August is the first spam update to roll out with both fully in scope.
- →The measurement gap: Search Console's generative AI report gives impressions for AI Overviews and AI Mode but no clicks, position, CTR or queries, so a demotion on those surfaces is visible as a shape rather than a number.
Sources used in this post
Update dates, release times and durations are read off Google's own incident log, checked on 21 August 2026. Policy wording and effective dates come from Google's documentation.
- Google Search Status Dashboard: ranking incident history
- Google: spam policies for Google web search
- Search Engine Land: Google releases August 2026 spam update
- Search Engine Journal: Google begins rolling out the August 2026 spam update
- PPC Land: Google's third spam update of 2026 hits every language and region
- Search Engine Journal: new Google spam policy targets back button hijacking
Related reading on CrawlRaven
- Your Rankings Moved on 1 August and Google Confirmed Nothing
- Google March 2026 Spam Update: The Fastest Rollout Ever
- Google May 2026 Core Update: Volatility Data and Recovery
- Search Console AI Performance Reports and the Clicks Problem
- The Technical SEO Audit Checklist
- LLM SEO: How to Get Cited by AI Answer Engines
Frequently asked questions
Did Google release an algorithm update in August 2026?
Yes, one. Google released the August 2026 spam update on 18 August 2026 at 09:27 Pacific time, logged on the Search Status Dashboard as an incident affecting ranking. It applies globally and to all languages. It is the third spam update of 2026, after the March and June rollouts, and Google published no blog post and no new spam policies alongside it.
Did a Google update finish rolling out on 16 August 2026?
No. Google's ranking incident log records nothing at all between 26 June 2026, when the June spam update completed, and 18 August 2026, when the August spam update began. Third-party rank trackers did move around 12 and 13 August, which is where the mid-August impression comes from, but Google never confirmed a ranking change in that window and the spam update had not started yet.
How long will the August 2026 spam update take to roll out?
Google said only that it may take a few days. The two earlier spam updates of 2026 give the useful comparison: March took 19 hours and 30 minutes, and June took 2 days and 1 hour. The August update passed the three-day mark with no completion note on the dashboard, which already makes it the slowest of the three. Rankings can keep moving until Google logs the end.
Is the August 2026 spam update a core update?
No, and the difference matters for what you do next. A core update re-evaluates how useful your content is against everything else available, and it is not a penalty. A spam update enforces Google's 16 named spam policies, which is punitive by design. A site can be hit by a spam update without ever receiving a manual action, because spam updates are algorithmic and manual actions come from human review.
What does the August 2026 spam update target?
Google named no specific targets, and shipped no new policies, so the honest answer is the existing list. That covers cloaking, doorway abuse, expired domain abuse, hacked content, hidden text, keyword stuffing, link spam, machine-generated traffic, malicious practices, misleading functionality, scaled content abuse, scraping, site reputation abuse, sneaky redirects, thin affiliation and user-generated spam. What changes between spam updates is how well Google's automated systems detect violations, not what counts as one.
Does the August 2026 spam update affect AI Overviews and AI Mode?
It can, and that is the genuinely new thing about it. On 15 May 2026 Google updated its spam policies page to state that spam includes attempting to manipulate generative AI responses in Google Search, extending the same policy set to AI Overviews and AI Mode. This is the first spam update to roll out with those surfaces formally in scope.
How do I know if the spam update hit my site?
Start with the date. If clicks fell before 18 August 2026, this update is not the cause, whatever else is. If the fall starts on or after the 18th, check whether the losing pages share a pattern rather than looking like a random sample: syndicated third-party sections, programmatically generated pages, thin affiliate templates, a domain you bought used, or a link profile you paid for. Spam updates hit patterns.
How do I recover from a Google spam update?
Remove the violation and wait, with a longer horizon than feels reasonable. Google's own guidance is that its automated systems need to observe compliance over a period of months, so there is no fast path and no reconsideration request to file unless you also have a manual action. One loss is permanent: the ranking benefit that came from spammy links does not return when the links are cleaned up.
15+ years of growing SaaS websites through SEO | Author, 200-Point Audit Checklist
Aditi has spent 15+ years helping SaaS companies scale organic traffic through technical SEO and content strategy. She is the author of the CrawlRaven 200-Point Audit checklist used by agencies and in-house teams to systematically improve search performance.