Google's Search Status Dashboard now records exactly one ranking event for the period: the August 2026 spam update, which started on August 18, 2026 and ran for 2 days and 16 hours, wrapping up around August 20. It is the only ranking incident logged there across July, August and September 2026.

First, a Correction to Our Own Previous Article

In our August 26 piece, "Rankings Shook August 1 to 3 and Google Confirmed Nothing", we wrote that the most recent officially confirmed ranking change was still the June 2026 spam update (June 24 to June 26). That sentence was already out of date when it published — the August spam update had begun on August 18 and finished around August 20. The main conclusion of that article still holds (the third-party volatility on August 1 to 3 has no matching official event), but the "most recent confirmed change" line needed fixing, and we have corrected the original.

The distinction matters for diagnosis: if your traffic dropped in early August, there is still no official event that matches it; if it dropped in the second half of August, the spam update is a plausible fit. When the dates don't line up, don't blame the update.

A Spam Update Is Not a Core Update, and Recovery Works Differently

Google has confirmed only two broad core updates so far in 2026: March (March 27 to April 8) and May (May 21 to June 2). A spam update is a different animal:

  • A core update re-evaluates what counts as helpful content. Sites affected by one usually haven't done anything specific wrong; recovery comes from sustained content improvement and being re-assessed at the next core update.
  • A spam update targets specific behaviour that violates the spam policies — fabricated content, parasite hosting, expired-domain abuse, mass low-quality generation. If one of these hits you, removing the behaviour gives you a chance of recovering at a later update. There is no guarantee and no instant effect.

Conflating the two usually sends people in the wrong direction: a specific policy problem gets answered with three months of vague "site-wide content optimisation".

Why "2 Days 16 Hours" Is Actionable

That is a short rollout. Core updates routinely take two weeks or more. A tight window concentrates the volatility, which gives you two practical rules:

  • Don't draw any conclusion from August 18 to 21 data. Day-over-day comparisons inside a rollout are distorted, and rankings bouncing around during those days is expected behaviour, not signal.
  • Compare stable periods on either side: take a block after August 22 against a block before August 10 and skip the middle entirely. Use the same length for both (14 days each, say) and avoid mixing different weekday/weekend compositions.

A Four-Step Check, in This Order

  • Confirm the change is real. In Google Search Console's performance report, compare total impressions, total clicks and average position across the windows above. Impressions down while position holds is usually demand, not ranking.
  • Localise it. Break it down by query and by page separately. A drop concentrated in one page type or one query cluster looks algorithmic; an even site-wide decline looks more like seasonality or demand.
  • Rule out self-inflicted damage. Did you change templates, switch CDN, touch robots.txt, adjust canonicals or migrate servers in the same window? Self-inflicted issues that coincide with an update are extremely hard to separate later, so eliminate them first.
  • Only then change content — one class of change at a time, with an observation period after each.

One more fact that gets overlooked: as of early September, Google has not confirmed any September core or spam update. If your rank trackers light up this month, the first move is still to check the official dashboard rather than trust a third-party volatility index.

Get the Infrastructure Side Clean First

Diagnosing an algorithm update assumes your site isn't handicapped technically. High TTFB, cross-continent origin fetches, certificate or redirect problems — any of these will turn an already subtle ranking change into something you simply cannot attribute. Server location affects SEO mainly through the indirect TTFB path, and if you also run crawlers or rank trackers yourself, how to choose a VPS for SEO tools breaks the resource profile down by tool type. SharkCloud runs independent instances in Japan, Singapore, Hong Kong and the US, so you can put the site on the side of the ocean your audience is on — control the controllable variables before arguing about the algorithm.