Google’s August 2026 Spam Update: What It Hit, and the Change That Matters More

Google ran the August 2026 spam update from 18 to 21 August 2026, taking two days and sixteen hours to complete. Google described it as “a normal spam update” rolling out across all languages and locations. It was not a core update, and Google did not present it as a link spam or site reputation action. If your traffic changed inside that window, this is the most likely cause — but the change with wider consequences for most sites happened quietly in June.

Update panic is a bad advisor. Before rebuilding anything, it is worth separating what Google actually said from what the internet said about it.

What was the August 2026 spam update?

A routine enforcement pass against Google’s spam policies, run globally, between 18 and 21 August 2026.

The facts, from Google’s own Search Status Dashboard:

Google’s public framing was deliberately unremarkable: a normal spam update, with affected sites pointed back at the spam policies. Google did not disclose what share of queries were affected, and did not name link spam or site reputation abuse as targets — which matters, because those are separate, specifically-named actions when Google does run them.

The last core update was in May 2026. There has not been one since. If you are searching for a core update to explain an August movement, there isn’t one.

What sites actually saw

Here is where the honest answer gets less satisfying.

Third-party trackers registered real volatility across the rollout. Beyond that, the public record is anecdote: forum reports ranged from “traffic has been absolutely decimated” to relief that a previous false positive had finally been reversed. A recurring theme was niche specialist sites losing ground to larger, less specialised retailers.

Treat all of that as signal about variance, not as a diagnosis. Update discussion threads are self-selecting — people who lost traffic post, people who gained it mostly don’t. A pattern reported by twenty anonymous commenters is not a finding, and building a recovery plan on it is how sites end up rewriting pages that were never the problem.

The only dataset that tells you anything reliable about your site is your site.

How to tell whether it actually hit you

Four checks, in order. Most “we were hit by an update” cases fail at step one or two.

1. Line up the dates properly. The rollout ran 18–21 August. A decline that began on the 12th, or on the 24th, is not this update. Google Search Console’s date comparison is the right tool; platform-reported sessions with lagging attribution are not.

2. Confirm it is organic, and confirm it is Google. Filter to organic search, then to Google specifically. Paid changes, an email send, a referral spike dropping off, or a tracking change will all look like an algorithm hit in a blended traffic chart.

3. Segment before concluding. Split by page type, by query intent, and by device. A sitewide decline and a decline confined to one template are entirely different problems. If it is one section, you have a content or technical issue in that section, not an algorithmic penalty on the domain.

4. Separate impressions from clicks. Impressions holding while clicks fall is usually a SERP-layout story — you are being surfaced and answered above the fold — not a ranking loss. That distinction is the whole basis of how AI search changes what “ranking” means, and it gets misread as an update hit constantly.

What to do if it was you

Read the actual spam policies before touching anything. Spam updates enforce documented rules. If you cannot point at the specific policy you might be breaching, you do not yet have a diagnosis, and edits made without one usually make things worse.

The honest checklist of things that genuinely trip spam enforcement:

• Scaled content abuse — mass-produced pages, however they were made, that exist to rank rather than to help. Volume AI publishing is the current common cause.
• Expired domain abuse — buying an aged domain to inherit its authority for unrelated content.
• Site reputation abuse — third-party content published on your domain to borrow your rankings, typically coupon or casino sections bolted onto a real brand.
• Thin affiliate pages — templated content with no original evaluation.

And the things people do in a panic that rarely help: mass-deleting old posts, disavowing links reflexively, rewriting titles sitewide, or republishing everything with a fresh date. Each of those adds noise to the very signal you need in order to learn anything.

If nothing on that list applies to you, the most probable explanation is ordinary re-ranking — competitors moved, or the query mix shifted. Wait for the dust to settle before acting. Recovery from a genuine spam action typically requires the next update to run, which means the timeline is months, not days.

The June change that matters more

While everyone was watching August, Google switched off a feature many sites still have markup for.

Google removed the FAQ rich result on 15 June 2026, after flagging the deprecation in May. FAQPage structured data no longer produces expandable questions under your result in Google Search.

Two things follow, and they point in opposite directions:

• Stop counting on FAQ markup for a Google SERP feature. It will not render. If your reporting or your business case for adding FAQs rested on rich result real estate, that justification is gone.
• Do not strip the questions off your pages. The visible Q&A block is doing different work now. Self-contained question-and-answer passages are among the most extractable content on any page, and extractability is what determines whether an assistant quotes you — which is what actually decides whether you get cited.

The markup itself is still valid schema, still parsed by non-Google systems, and costs nothing to leave in place. It simply stopped being a Google rich result. We have kept it on this site for that reason, and the FAQ block below is there for readers and retrieval, not for a snippet that no longer exists.

What actually changed in Google search this year

For context, the 2026 record so far:

Read down that column and the pattern is clear enough. The spam updates are maintenance. The consequential moves were about where answers appear — and Google’s own guidance in May was blunt: write for people, use ordinary structure, and do not produce separate versions aimed at machines.

That is the same conclusion from the other direction. The durable work is not update-chasing. It is covering a subject properly and publishing things that cannot be synthesised from everyone else’s pages.

Frequently asked questions

Was there a Google update in August 2026?
Yes — the August 2026 spam update, which ran from 18 to 21 August 2026 and took two days and sixteen hours. It was a spam update rather than a core update, and it rolled out across all languages and locations.

What did the August 2026 spam update target?
Google described it only as a normal spam update enforcing its published spam policies. It was not presented as a link spam action or a site reputation abuse action, both of which Google names explicitly when it runs them.

When was the last Google core update?
May 2026. There has been no core update since, so an August ranking change cannot be attributed to one.

How long does it take to recover from a spam update?
If the cause is a genuine policy breach, recovery generally requires the fix to be in place and crawled, then the next relevant update to run — months rather than days. If the movement was ordinary re-ranking, positions often settle within a few weeks with no action.

Should I remove FAQ schema now that FAQ rich results are gone?
No. It no longer produces a Google rich result, but it remains valid structured data that other systems still read, and it costs nothing to keep. What matters more is keeping the questions and answers visible on the page, because self-contained Q&A passages are highly extractable by AI assistants.

ThynqAi builds SEO and organic growth programmes that are not rebuilt every time Google runs an update. If your traffic moved this month and you want a straight answer on why, ask us for an audit.