What happened: Two things in the last two weeks of August that most SaaS teams will only notice in their September reports. Google’s August 2026 spam update rolled out from 18 to 21 August (2 days, 16 hours according to the Search Status Dashboard), and it was unusually disruptive. Separately, Google confirmed on 26 August that it is wrapping organic result links in a google.com/goto redirect, which is now at near-100 percent rollout and is affecting rank tracking tools.

This guide covers august 2026 spam update for SaaS teams: what it means, why it matters, and the practical steps to get it right.
Sources: Google Search Status Dashboard; Search Engine Land on SE Ranking’s data; Google’s goto confirmation.
The spam update in numbers
SE Ranking compared US rankings for the same 100,000 keywords across 20 industries on 17 and 22 August (before and after the update) against a quiet baseline of 26 and 31 July.
| Metric | Spam update window | Quiet baseline |
|---|---|---|
| Top 10 URLs that fell beyond position 100 | 16.71 percent | 9.2 percent |
| Relative increase | 82 percent, so a top 10 URL was about 1.8 times more likely to vanish from the top 100 | |
| Share of keywords with top 10 changes, by niche | 74.6 percent (real estate) to 85.6 percent (fashion and beauty); YMYL categories were the steadiest | |
Reports collected by Roger Montti point to at least part of the update targeting content generated to rank, with several practitioners describing sites that publish automatically through coding agents being filtered broadly rather than page by page. That matches John Mueller’s comment a week later that low-value programmatic content makes Google lose faith in a site.
What to check on a SaaS site
- Compare 17 August to 22 August in Search Console, by page group. If the blog held and a template section dropped, you have your answer. Our Search Console setup guide has the regex filters for page groups.
- Look for site-wide drops, not page drops. Spam updates that hit a domain’s trust show up as a uniform slide across unrelated pages. That pattern means a content-quality problem, not a keyword problem.
- Do not “fix” it by publishing more. The next spam update is the earliest recovery point. Remove or noindex the weak sections now so you are clean before it.
The google.com/goto redirect
Since late July, and confirmed by Google on 26 August, links in Google’s organic results point to google.com/goto with the destination encoded, and Google redirects the click. Google’s only comment was that it has “a long history of deploying technical measures against evolving forms of abuse”. Derek Perkins of Nozzle reported close to 100 percent deployment across residential IP providers by the end of August.
For users nothing changes. For anything that parses result pages, every link now needs a redirect to be followed to learn the real URL, and HEAD requests on the redirect are blocked, so resolving a five-page report can take 500 to 1,000 requests instead of five. The practical effects for a SaaS team:
- Rank tracker data may be late, missing or wrong for a few weeks while vendors adapt. If a keyword shows “not ranking” but Search Console shows impressions and clicks, trust Search Console.
- Some tools will raise prices or lower limits because their cost per SERP went up. If you are choosing a tool, our rank tracker comparison covers the current options.
- Referrer data is unaffected: GA4 still sees google as the source after the redirect.
We will add vendor status notes here as the major trackers confirm they have adapted.
Quick recap: August 2026 spam update
August 2026 spam update usually comes down to a short, repeatable checklist. Use this whenever august 2026 spam update comes up again:
- Diagnose august 2026 spam update by checking the relevant report first, not assumptions.
- Confirm the current setup is actually causing august 2026 spam update before you change anything.
- Re-check august 2026 spam update again after the fix ships, not before.
Treat august 2026 spam update as an ongoing signal rather than a one-time fix. For background on the platform rules behind this, see Google Search Central.
