Google rolls out the August 2026 spam update: not links, not site reputation abuse

Google logged the August 2026 spam update on its Search Status Dashboard ranking history on 18 August 2026, and announced it publicly at roughly 12:30pm ET the same day. Google's wording is that the update "applies globally and to all languages" and that "the rollout may take a few days to complete." The detail that matters most for diagnosis is what Google ruled out: this update does not target link spam, and it does not target the site reputation abuse policy. Both of those are handled by separate systems.

The entry sits on the ranking history page of the Google Search Status Dashboard, which is where Google timestamps the start and the completion of every named ranking event. At the time of reporting that entry carried no completion duration, so the rollout was still in progress.

What Google confirmed about the August 2026 spam update

Google confirmed on 18 August 2026 that the August 2026 spam update targets sites violating its Search spam policies, that it applies globally and to all languages, and that the rollout may take a few days to complete. That is the entire official scope statement. Google did not name a vertical, did not name a technique as the main trigger, and did not describe the ranking systems involved beyond the two exclusions it published.

It is the third spam update Google has shipped in 2026. The March 2026 spam update started on 24 March and finished in 19 hours 30 minutes. The June 2026 spam update started on 24 June and took 2 days 1 hour. Neither is a reliable predictor of how long the August one runs, but both point at the same pattern: spam updates complete far faster than core updates. The most recent core update, the May 2026 core update, started on 21 May and took 11 days 21 hours.

What the August 2026 spam update does not target

Google stated on 18 August 2026 that the August 2026 spam update does not target link spam and does not target the site reputation abuse policy. That exclusion is worth more to a site owner than any of the inclusions, because it deletes two of the hypotheses people reach for first when traffic falls.

If a site lost visibility from 18 August and the working theory is a bought or spammy backlink profile, that theory does not fit this update. Link spam is handled by a separate system on its own schedule, and Google said so explicitly while announcing this one. The same applies to third-party content published on a strong host domain to borrow its rankings, which is what the site reputation abuse policy covers. Google confirmed that policy is enforced by a different system and is not what shipped on 18 August.

Analysis, not Google's statement: exclusions are more actionable than inclusions because they let you throw hypotheses away cheaply. If the only real risk exposure on a site is its link profile, and the site moved on 18 August, the likelier explanations are ordinary volatility, a technical change made on your own side, or a competitor moving. Commissioning a link audit in that scenario spends the budget on the wrong problem and buys a month of delay.

The 2026 update timeline, with the durations Google recorded

Google's ranking history page records a start date and a completion duration for every named event, which makes the 2026 updates directly comparable. These are the figures as they appear on the dashboard.

The last row is deliberately blank on duration. Google's dashboard had not logged a completion when this was reported, and the announcement only said the rollout "may take a few days to complete." Anyone reading their own movement in the first 48 hours is reading a partial rollout, not a result.

What Google's Search spam policies actually cover

Google's Search spam policies documentation is the reference point for the August 2026 spam update, because Google's announcement pointed at the policies as a whole rather than at any single technique. Those policies cover scaled content abuse, cloaking, doorway pages, expired domain abuse, hacked content, sneaky redirects, and machine-generated text produced mainly to rank rather than to help a reader.

Read against the two published exclusions, the practical shape of this update is everything in the spam policies except links and except site reputation abuse. That still leaves a wide surface. Analysis: the two categories most likely to catch a legitimate site by accident are scaled content abuse and machine-generated text, because the line between publishing many useful pages and publishing many pages for search engines is drawn on purpose and quality, not on volume. A site that shipped several hundred thin AI-assisted pages last quarter shares surface patterns with the sites the policy describes, whatever the intent behind it was.

Doorway pages are the second common accident. City-by-city or service-by-service page sets built from one template with the location name swapped in are a standard local SEO tactic and also a textbook doorway pattern. What separates them is whether each page carries information that only applies to that place: an address, a price that differs, stock that differs, a person who works there. If the only unique string on the page is the place name, the page is doing what the policy describes.

How to tell a spam update hit from a core update hit

Analysis rather than Google's guidance: a spam update and a core update leave different fingerprints, and the August 2026 spam update should be read with that in mind. A spam update tends to move a site sharply and specifically, often a whole property or one defined section of it, and the movement lands inside a short rollout window. A core update tends to reshuffle relative quality across a topic over a longer period, moves individual pages more than whole domains, and runs long enough that a drop can arrive on day eight. The May 2026 core update's 11 days 21 hours is exactly that kind of window.

The second distinguishing signal is how recovery behaves. Google's guidance for spam policy violations is to fix the violation and wait for the system to refresh, which Google says can take many months. Core update recovery is tied to ongoing quality signals and to subsequent core updates, not to a spam refresh. Two different clocks, and guessing the wrong one costs a quarter.

How to check the dashboard date against your own analytics

Google publishes start and completion timestamps on the Search Status Dashboard so that site owners can align them against their own data, and the August 2026 spam update entry gives 18 August 2026 as the start. The check is mechanical rather than clever.

• Pull daily Search Console clicks and impressions for 30 days either side of 18 August 2026 and find the exact inflection date.
• If the decline starts before 18 August, this update is not the cause, whatever else is true about the site.
• Segment by directory and by page type. A drop confined to one section points at what that section has in common, not at the domain.
• Segment by country. Google said the update is global and all-languages, so a drop in one market only is a hint that something else is running.
• If impressions fell while average position held, the movement may be search demand or SERP layout rather than ranking.

Do this before changing anything on the site. A rollout that Google says may take a few days is not a stable measurement window, and rewriting pages in the middle of it destroys your own baseline for telling whether the rewrite worked.

Why recovery runs on a refresh, not on a redeploy

Google's recovery guidance for the August 2026 spam update is unchanged from previous spam updates: review the Search spam policies, fix the violations, and wait for a periodic refresh of the system. Google says that refresh can take many months. It did not give a date, a range, or a way to request one.

Analysis: this is why spam update recovery feels unresponsive compared with a technical fix. The change does not take effect when it goes live, it takes effect when the system next re-evaluates the site. The sequence that follows from that is to make the cleanup complete rather than incremental, to record the date each change shipped so the eventual recovery can be attributed to something, and to stop expecting weekly feedback from work that is scored on a slower cycle. The absence of recovery in September is not evidence that the diagnosis was wrong.

What Google did not say

Google would not disclose what percentage of queries the August 2026 spam update affected, so that number does not exist in any official form. Google also did not publish a completion time while the rollout was running, did not identify affected countries or industries beyond confirming that the update is global and covers all languages, and did not describe which systems inside Search were changed. Any percentage circulating alongside this update is a third-party estimate, not Google's figure.

What this means for Thai marketers

Google said the August 2026 spam update applies to all languages, which puts Thai-language sites in scope on exactly the same terms as English ones. Thai sites in verticals where spam is dense, including gambling-adjacent affiliate content, cheap-SEO doorway networks and scraped Thai-language content clusters, sit directly inside that scope.

The risk for most Thai brands is inherited rather than intentional. A company that bought a low-cost content package, or a retainer sold on guaranteed rankings, may be carrying scaled content or doorway patterns nobody signed off page by page. Because Google excluded link spam from this update, the audit that answers the question here is a content audit, not a backlink audit: how many pages went live in the last two quarters, who produced them, whether each answers something a real reader asked, and whether the number of templates is smaller than the number of genuinely distinct topics.

If a Thai site dropped from 18 August, "low season" is a hypothesis and not a finding. The dashboard date gives you a way to test it against your own daily data, and a structured SEO audit settles it faster than a month of arguing about seasonality.

FAQ about the August 2026 spam update

Is the August 2026 spam update live in Thailand?

Yes. Google said the August 2026 spam update "applies globally and to all languages", which covers Thailand and Thai-language content. Google did not publish country-level detail, so there is no official statement about Thai search results specifically, only the global scope.

Does this update penalise my backlinks?

No. Google explicitly said the August 2026 spam update does not target link spam, which is handled by a separate system. If your rankings moved from 18 August 2026, the backlink profile is the wrong first place to look, and so is anything covered by the site reputation abuse policy.

How many queries were affected?

Google would not disclose it. There is no official percentage attached to the August 2026 spam update, and any figure being shared is a third-party estimate rather than a number Google published.

Do I have to do anything if my traffic is stable?

No. Google's guidance applies to sites violating its Search spam policies, and a site that did not move has nothing to action. The one task worth ten minutes is annotating 18 August 2026 in your reporting so that future month-on-month comparisons carry the date with them.

How long does recovery take after a spam update?

Google says it can take many months, because recovery depends on a periodic refresh of the system rather than on the day you publish the fix. Google did not give a date for the next refresh and there is no process for requesting one, so any specific timeline you are quoted is invented.

If your rankings moved from 18 August and you want the drop diagnosed against the dashboard timeline rather than guessed at, the SEO team at Relevant Audience can take the daily data apart with you and tell you honestly whether this update fits.