Google's routine August spam update pushed 16.71% of top-10 URLs past position 100

"Top 10 to beyond position 100, same keyword" is a specific transition, and it pays to read it as the measurement it is ^[5]. It is a keyword-level position comparison from an independent tracker, not a traffic figure ^[23]. A URL counts as moved if a query it held in the top ten now returns it past 100. That can happen to a page whose commercial query never budged, and the source is careful to say the data does not identify which site types were affected or prove the update caused every loss ^[9].

Two conditions have to hold before you treat the share as your own exposure. Your query mix has to resemble whatever set was tracked, because head terms and long-tail variants do not churn at the same rate. Then the movement inside the window has to be the release rather than a competitor, a shift in intent, an indexing fault, or another Google system running at the same time ^[11].

The part I would build against is the timestamp pair. Subtract the two dashboard entries and the rollout ran 64 hours and 22 minutes ^[16]. That has two measurement consequences. An "after" window pinned to the announcement date contains nearly three days of partially deployed state, so a single before/after cut blends the transition into the result. And the times are precise enough to annotate a daily rank series to the hour, which is a cleaner event boundary than most third-party systems hand you. The dashboard logs the release down to the minute, but it says nothing about whom the release landed on ^[8].

Now the arithmetic that makes the headline number mean something. The gap between the August share and the July comparison is 7.51 percentage points ^[17], which is roughly one extra top-10 URL in thirteen falling out of sight ^[18]. The multiple is 1.82, which is where the "roughly 82% higher" in the reporting comes from ^[20][7]. The figure I would actually keep on the wall is the quieter one: in a normal month, about one top-10 ranking in eleven still drops past 100 ^[19]. Without that denominator, every dip during a confirmed rollout reads as a penalty, and spam updates enforce policy that already existed rather than signalling that ordinary volatility has stopped ^[22].

Diagnosis then needs a control group. The source's method is to compare affected pages, queries and landing-page groups against unaffected ones, looking at templates, page purpose, internal linking and indexing status ^[12]. You can only assemble that comparison if per-URL, per-keyword history was already being recorded before the window opened. The alternative is reactive work the source warns against, such as mass keyword changes or hurried removals without evidence ^[13], and there is no site-by-site remedy on offer for this release ^[21].

Which is the argument for treating the channel as instrumented rather than assumed. A dependency that ships enforcement on its own schedule, publishes timestamps and no changelog, and offers no per-site diagnosis, is one you monitor per key and hold a churn baseline for. The source's last recommendation, reducing dependence on a single traffic channel and building direct audience relationships ^[14], is capacity planning under that reading, not an editorial preference.