Rank trackers logged their sharpest volatility of the September 2026 spam update over the weekend, with Saturday, Sept. 26 producing the biggest swings across more than a dozen monitoring tools. Barry Schwartz reported the pattern for Search Engine Roundtable on Sept. 28, five days into a rollout Google has said will take about two weeks. That timeline is the one our earlier coverage of the update’s launch described on Sept. 25, and if Google’s estimate holds, roughly nine days remain.
Schwartz’s post compiles readings from Semrush, AccuRanker’s Grump, Mangools’ SERPWatcher, Wincher, Zutrix Tension, Wireboard’s aggregate chart, Mozcast, Serpstat, DataForSEO’s SERP Volatility Index, AWR, CognitiveSEO, SimilarWeb, Sistrix and Algoroo. Movement began Friday, Sept. 25, intensified Saturday and tapered by Sunday, Sept. 27, according to Schwartz, who notes the update was announced Thursday, Sept. 24 at about 12 p.m. ET and that “the volatility may be calming today, a bit.”
Glenn Gabe described the weekend as more severe than the pattern he flagged on Friday. In a Sept. 28 post cited by Schwartz, Gabe wrote that he is “seeing big drops across a number of sites. And that’s across verticals and countries.” In a separate Sept. 25 post, he noted that Grokipedia, the AI-generated site he has tracked through prior surges and drops, had lost further ground during the mid-September volatility: “it’s very interesting to see it drop even more with the mid-September volatility.”
Trackers and third-party analysts are not Google. Semrush Sensor and the dozen tools Schwartz cites measure SERP churn; they do not confirm what the update targets or how much of the observed movement traces back to it rather than to unrelated noise. Gabe’s read is his own analysis, offered without a Google statement behind it. None of that makes the data unreliable, but it means a weekend spike is evidence of volatility, not proof of cause.
That distinction matters most for what a site owner should do with a Saturday ranking drop noticed five days into a fourteen-day rollout. The correct response is not to diagnose the spam update from a single tracker reading; it is to pull Search Console’s performance data for the same window and check server logs for crawl and indexing anomalies that predate Sept. 24. A drop that started before the announcement points to a different cause entirely, and a drop confined to one template or content type is more diagnostic than an aggregate volatility score.
Weekend spikes in spam-update volatility also carry a specific risk: they invite premature recovery work. A site that starts stripping content or disavowing links based on Saturday’s numbers, before the rollout finishes and before Google has said what the update targets, may be reacting to noise that reverses on its own once the two weeks close. Schwartz’s own update makes clear the targeting is still unclear: he writes that he expects the update to hit “lots of tactics,” not one specific pattern, which argues against narrowing remediation to a single theory this early.
Teams that saw ranking movement this weekend should log the affected URLs and query sets now, cross-reference them against Search Console impressions and clicks rather than tracker sensor scores, and hold any remediation decision until Google’s Search Status Dashboard marks the rollout complete. Acting on day five of fourteen risks fixing the wrong problem twice.
Barry Schwartz reported the weekend volatility for Search Engine Roundtable on September 28, 2026.
