Separate search-update shock from real churn before cutting organic

When organic traffic drops during a Google update, the fastest way to make a bad decision is to cut the channel before the rollout finishes. The drop may be a search-update shock, or it may be churn that was already there. During the August 2026 spam update, one tracking estimate found that about 16.7% of URLs previously in the top 10 fell past position 100, compared with a normal churn rate near 9%.

Treat the first days as a measurement window

The September 2026 spam update began on September 24, 2026, at 9:15 a.m. Pacific Time. It was Google's fourth spam-specific ranking release in 2026, after March, June, and August. The September 2026 spam update was described as reaching every region and language, with the rollout finishing within two weeks. If Google used the full allowance, the rollout would extend to about October 8, 2026.

The same drop can look like a penalty to a group of pages, a loss of link value, or ordinary churn. The clean read comes from a baseline you saved before the update, not from a same-day reaction. If organic search carries a meaningful share of acquisition, the question is channel risk, not a single page. You need to know whether the loss is update-driven or churn that was already there before you touch other channels.

The cost of waiting is uncertainty. The cost of cutting early is a permanent loss of a channel that may have been fine. A search-update shock can hit your best pages, your worst pages, or a set of pages that never deserved the traffic. The protocol keeps those cases separate. The wait is the hard part, because the dashboard is already moving.

Build the baseline before the two-week rollout finishes

The protocol below follows the rollout window. Each step is small, but together they create a before-and-after record. The early steps build the baseline, the middle steps create the control, and the final steps force the comparison.

• Export query-level traffic for the current reporting period and save it with a date stamp.
• Export page-level traffic for the same period and keep the file separate.
• Record the share of new sessions that came from organic search.
• Record the share of new sessions that came from every other acquisition channel.
• Note which pages and queries carry the largest share of organic acquisition.
• Mark the update start date and the expected rollout end date in your calendar.
• Save a screenshot or export of the relevant update status page.
• During the rollout, log any major content, link, or technical changes that could move traffic.
• After the rollout finishes, check rank tracking and export the same query- and page-level data for the same period.
• Compare the post-rollout loss to your normal churn rate before deciding to cut, hold, or shift the lever.

The baseline files are the control. Without them, every post-update number is untestable. With them, the comparison has a before and after. The acquisition mix matters because a drop in organic can be offset by paid, email, or direct, and that changes the decision. If the loss is concentrated in a small set of pages, treat it as a content or link issue, not a channel issue. If it is broad, treat it as channel risk. The rollout window makes that comparison cleaner.

Decide after the rollout, not during it

The August 2026 spam update began on August 18, 2026, and ended on August 21, 2026. Even after such a short update, temporary drops can recover. Around September 4, 2026, a group of large sites tracked by Glenn Gabe lost visibility in Search and Discover, and most recovered by September 13, 2026. If your post-rollout loss is close to normal churn, hold the organic lever and keep the baseline. If it is far above normal churn, cut or shift the lever and move the budget to channels you can control.