The Google Update No One Confirmed

Google Algorithm Updates

The Google Update No One Confirmed

Large sites crashed on September 4, fully recovered on September 13, and Google never confirmed a thing. Volatility is spiking again this week, and the nine-day reversal is the best argument yet for touching nothing while it runs.

If your rankings fell off a cliff around September 4 and came completely back on September 13, you did not imagine it, and you did not fix it. Glenn Gabe, who tracks large-site impact with first-party analytics, posted on September 13 that “a number of the sites that fell off a cliff around 9/4 completely surged back yesterday. They dropped heavily in Search and some in Discover as well. The recovery is wild.” Barry Schwartz of Search Engine Roundtable verified the important part: these were not third-party visibility artifacts but “a real drop and then a real reversal in its first-party analytics and data.” Google confirmed nothing, on the way down or on the way back up.

Then the story restarted. On September 15, Schwartz reported a huge spike in chatter: UK results churning, spam on page one, keyword sets swapping to entirely different pages, one webmaster describing “that kind of change [that] happens only on big updates.” I checked Semrush Sensor myself this afternoon (September 16): US desktop, all categories, reads 4.1 out of 10, up from roughly half a point on September 13. Sensor calls 4.1 “normal range,” but three days ago it read half a point, and it has been climbing since.

None of this is comfortable for people paid to react to rankings, but the last nine days say the most valuable action during an unconfirmed volatility event is often no action at all, because Google sometimes undoes the event for you. Sites that rewrote content, disavowed links, or shipped “recovery” work between September 4 and September 12 spent that effort against a change Google rolled back on its own.

What the last month looked like

September’s whiplash makes more sense inside the run of events since mid-August. Google confirmed exactly one of them.

May 21 – Jun 2
ConfirmedMay 2026 core update rolls out and completes.
Jun 14 – Jun 26
ConfirmedJune 2026 spam update rolls out and completes.
Jul 18 – Aug 13
UnconfirmedA chain of unannounced volatility Schwartz documents day by day: July 18–19, July 24, August 1–3, August 5, August 13.
Aug 18 – Aug 21
ConfirmedAugust 2026 spam update completes in about 64 hours, the fastest in recent memory. Volatility continues afterward anyway.
Aug 31
ConfirmedRajan Patel, VP of Engineering for Google Search, publicly states the spam team remains well-resourced and keeps refreshing its detection systems.
Sep 1
MeasurementGoogle Analytics data goes missing for September 1, including zero-user readings; Search Console indexing-report problem acknowledged by John Mueller as fixed on September 9.
Sep 3 – Sep 4
UnconfirmedCluster of large sites “fell off a cliff” in Search and Discover. Aggregate trackers disagree on the size (below).
Sep 13
UnconfirmedThe September 4 impact fully reverses for many of the same sites, per Gabe and WebmasterWorld reports. No Google statement.
Sep 15 – Sep 16
Live nowFresh churn: UK SERPs, Discover, page-one spam, keyword sets swapping owners. Semrush Sensor climbs from ~0.5 to 4.1 in three days. Schwartz suspects “the start of a Google update” but expects no confirmation.
Timeline compiled from Search Engine Roundtable (Aug 26, Sep 14, Sep 15), Schwartz on Patel’s statement (Aug 31), Search Engine Watch (Sep 10), and the author’s own Semrush Sensor capture (Sep 16).

As of today, Google’s Search Status Dashboard shows no ranking incident for September 2026. Google’s confirmation protocol covers core updates and spam updates. Everything else, including whatever moved on September 4 and got reverted on September 13, happens in silence.

Why the volatility trackers disagreed about September 4

Three trackers covered the same week and gave different accounts of it.

Semrush Sensor

US desktop, all categories, as read Sep 10 by Search Engine Watch
0.6 / 10 on Sep 9, labeled “Low.” No September 4 spike visible on the public chart. Semrush recently recalibrated Sensor scores, which lowers displayed numbers and breaks comparisons with older readings.

DataForSEO Volatility Index

US desktop, all categories, Sep 4 and Sep 8 readings reported by Search Engine Watch
5.98 / 10 on Sep 4 and 5.82 / 10 on Sep 8: mid-range turbulence on the exact days Sensor read near zero. Schwartz’s own aggregate chart likewise showed Sep 4 as the most volatile day of that stretch.
Both readings via Search Engine Watch, Sep 10, 2026; aggregate chart observation via Search Engine Roundtable, Sep 14, 2026.

For a real, first-party-verified crash to stay invisible to one major tracker, the hit has to be narrow. The most plausible reading, and it is inference rather than a Google statement, is that the September 4 event hit a specific cluster of large sites, hard, in Search and Discover. Aggregate trackers sample tens of thousands of SERPs across categories, and a sharp hit to even a few hundred properties barely registers in that average, especially under a freshly recalibrated scoring scale. A real, damaging event can read as calm on an aggregate score.

For practitioners, that reframes the familiar advice. “Sensor is calm, you’re fine” was never sound, and September proved it in both directions. If your own analytics show a cliff and the trackers show nothing, believe your own analytics. An aggregate score can dilute a real, narrow hit until it looks like nothing.

86420 Aug 19Aug 25Aug 31Sep 6Sep 12Sep 16 Sep 4 cliff window:Sensor reads LOW (~0.9) Sep 13 revert Sep 15–16:4.1 and climbing Semrush Sensor, US desktop, all categories (approximate readings)
Approximate values read from the public Semrush Sensor 30-day chart, captured by the author on September 16, 2026. Semrush recently recalibrated Sensor scores, so the absolute numbers matter less than the trend: flat through the September 4 event, then a jump over the last three days. Shaded bands mark the September 4 crash window, the September 13 revert, and the current spike.

Google has rolled things back before

Gabe’s September 13 post carried one easy-to-miss clause: “And note, this has happened in the past.” It has, and the record goes back a decade. None of these reversions were announced.

WhenWhat happenedHow it was known
Nov 2015Large unexplained ranking shifts; Google responded that there was no update to announce.Schwartz, SER
Jun 2017Core-ranking shift that then “rolled back or kind of adjusted” within days.Schwartz, SER
Mar 2019Core update that functioned as a partial rollback; Sistrix data showed losers of prior updates regaining.Search Engine Journal
Jun 2020What looked like “a 10–20% rollback or adjustment of the May 5th core update,” unconfirmed by Google.Schwartz, SER
Aug 2020An unconfirmed update “rolled back after a few hours”; rankings reverted to their prior state.Schwartz, SER
Jun 2021Google itself warned that June core update changes “may see a reversal or shift” with the July update. A rare announced-in-advance reversion.Schwartz, SER
Dec 2023Weeks of extreme volatility after the reviews update; observers concluded Google “rolled back the November core update or at least part of it.”Schwartz, SER
Sep 2026Sites crash Sep 3–4 in Search and Discover, fully reverse Sep 13, verified in first-party analytics. No confirmation either direction.Gabe via Schwartz, SER
Documented reversions and reversals in Google rankings, 2015–2026. Only June 2021 involved Google flagging the reversion in advance.

Confirmed updates are announced on the status dashboard, roll out over days or weeks, and stick. Unconfirmed events behave like experiments: a fast hit to particular site types, then a quiet reversion within one to two weeks in a meaningful share of cases. September 4 to September 13 is nine days, almost exactly the window the August 2020 rollback needed in miniature and the November 2023 partial rollback needed at full scale.

The push-revert loop

Google has never published a postmortem of the September event. The loop below is inference, built on the company’s observable behavior and Patel’s August 31 statement that the spam team “keeps updating” its detection systems.

1. A spam or quality system change goes live without a dashboard entry. Google’s confirmation policy covers core and spam updates only; hundreds of smaller changes ship silently.
2. A cluster of sites loses Search and Discover visibility within hours (Sep 3–4). The hit is concentrated enough that broad trackers disagree on whether anything happened.
3. Google’s own quality metrics, and the community’s, register the damage. Gabe’s charts and WebmasterWorld threads are the public half of this step; Google measures the same thing internally.
4. The change is rolled back or retuned. Impacted sites surge to their prior levels on the same day (Sep 13). No announcement accompanies the revert, just as none accompanied the push.
5. The system relaunches later, adjusted. Some of this week’s September 15–16 churn may be exactly that.
An inferred ship-watch-revert loop, based on the September 2026 sequence and documented precedents above. Google has not confirmed this account of the September event.
Google can push a change and revert it within nine days at zero cost to itself. A site owner who reacts on day two pays real costs, in rewritten content, disavowed links, and client panic, to fix a problem that disappears on day nine by itself.

Triage for this week’s spike

Volatility is live right now: Sensor at 4.1 and rising, UK SERPs churning, Discover unstable, and Schwartz expecting no confirmation either way.

Check for a real loss. Look at first-party analytics (GA4, server logs), not just a rank tracker, for lost traffic or rankings since September 4.
No loss
Do nothing. Record your baseline now so a later move has a clean comparison point.
Yes, a real loss
Check for a confirmed update. Look at the Search Status Dashboard and Search Console for manual actions.
Confirmed update or manual action
Follow the confirmed-update playbook: wait for rollout completion, audit quality signals, fix what the update targets. Spam-update recoveries rarely arrive from Google alone.
Nothing confirmed
Rule out a measurement artifact. Check the current ones: GA missing Sep 1 data, the GSC indexing-report problem fixed Sep 9, Sensor’s recalibrated scores, and EU DMA SERP layout changes.
Do not rewrite content, disavow links, or delete pages in this window. The September 4 cohort proves the move can fully reverse on its own within about nine days.
Log the exact first-affected date, pages, queries, country, and device; screenshot the SERPs; wait 14 days; re-measure. If the loss survives two weeks of continued volatility, treat it as durable and start a real audit.
Triage for the September 15–16 volatility window. The 14-day wait is calibrated to the longest documented silent-revert window above (Sep 4–13, 2026; Nov–Dec 2023).

The reports behind the current spike are geographically lumpy: “UK results are absolutely crazy since Saturday night. A lot of spam on page 1,” one webmaster wrote in Schwartz’s September 15 thread, while US trackers barely moved at first. Regional churn during EU DMA SERP redesigns is a known confound this month. The same thread also contains a shop owner reporting that conversions dried up at “4 PM on the dot” while traffic held, which smells like tracking or attribution breakage rather than a ranking change, so the sensible move is to verify before acting.

Two classes of volatility

Google’s ranking system now changes fast enough that its own operators sometimes reverse course within days, and its communication policy has not changed to match. The status dashboard covers updates Google wants to own, and it will never cover the ones Google decides to take back.

Confirmed updates are durable, announced, and worth restructuring for. Unconfirmed volatility is real while it lasts, frequently self-corrects, and punishes overreaction. The sites that came back on September 13 did nothing for nine days, and that nothing was the correct strategy. If the current spike follows the same script, the sites that make no panicked changes through early October will be the ones still standing when the chart flattens.

“Do nothing” applies to unconfirmed volatility inside a two-week window. It does not apply to a confirmed spam update hit, a manual action, or a loss that persists after the window closes. Those get audited and fixed. The discipline is knowing which one you are in, and September gave the whole industry a live demonstration of how hard that call is to make in the first days of a drop.

Primary sources: Search Engine Roundtable, “Google Search Ranking Update Around September 4th That Reverted September 13th” (Sep 14, 2026); Search Engine Roundtable, “Google Search Ranking Volatility Heats Up This Morning” (Sep 15, 2026); Glenn Gabe’s September 12–13 posts on X and Bluesky; Search Engine Watch, “Could Google’s next core update arrive in September 2026?” (Sep 10, 2026); Semrush Sensor, captured by the author Sep 16, 2026; Search Engine Roundtable, “Volatility Continues Post August Spam Update” (Aug 26, 2026); Search Engine Roundtable on Rajan Patel’s statement (Aug 31, 2026).