A bad weekend proves nothing
Google finished rolling out its September 2026 spam update on October 8, and the whole thing took two full weeks to complete. The early tremors peaked over the weekend of September 26 and 27, exactly when owners were watching their numbers fall and asking for an explanation before the working week had even started.
A weekend crash during an active spam rollout is a weather report, rather than a post mortem. The number your tracking tool recorded is real in that narrow sense, but it is not final, and no decision built on top of it is safe either.
Why early numbers mislead
Spam updates do not work like core updates. Google evaluates technical configurations, automation footprints and link profiles across several independent systems, and those systems do not refresh at the same moment. While they are still running, automated processes test adjustments and apply new filters across data centers around the world, so the jumps and drops you see are rolling tests rather than a verdict.
Weekend behavior widens the gap. Mobile traffic rises, business queries drop and local map results take up far more of the screen, so a chart can look catastrophic for reasons that have nothing to do with the update. Day five is not day 14, and treating a weekend rank report as a final verdict is how ordinary turbulence becomes an emergency.
Freeze the site first
The discipline that protects a site during an active window is a complete freeze: no changes to website code, no new URL redirects, no rewritten page titles, no bulk content adjustments, until the rollout is officially over and visibility settles. Pruning sections, rewriting hundreds of pages or disavowing backlinks on day five only adds noise to a noisy situation.
There is a practical reason beyond patience. If your developer alters core templates while Google is still updating its systems, nobody will be able to tell later whether a recovery was helped or harmed by those edits. The useful work in that window is recording: dated snapshots in Search Console, the exact date the update started, and how each type of page responds.
What changes in your week
The owner sets the date instead of reacting to one. Nothing technical or editorial gets approved while the Google Search Status Dashboard shows the update still running. When Google marks it complete, an agreed pause follows, 10 to 14 days for the index and the data centers to settle, before anyone calculates what the drop actually cost.
Only if traffic has not returned to normal after that pause does the structured review begin, and then it begins on real numbers. What you notice in the week is quieter: no emergency invoices for rewrites and redirects, no broken templates that worked fine before, and a marketing conversation that sounds like a plan instead of a bad weekend.