In this article
Google began rolling out a spam update on September 24, 2026. It applies globally and to all languages, and Google says the rollout may take up to two weeks. A drop observed during that window is a reason to investigate; it does not, by itself, establish that the update caused it. Check the Google Search Status Dashboard for the rollout state before making a final assessment.
Establish a usable baseline
Export Search Console clicks, impressions, click-through rate, and average position for your most important page groups. Record when those pages were edited, when the site was deployed, and whether there were outages. Compare equal-length periods with comparable weekdays. For seasonal stores, look at the same product families rather than relying on an all-site total.
Separate branded queries from nonbranded discovery, commercial pages from informational articles, and countries where the business actually sells. If clicks decline while impressions remain steady, investigate the search result and the offer. If both decline for one page group, examine its queries and indexing state. Neither pattern proves a particular algorithmic cause.
Rule out changes you can verify
Test affected URLs. Do they return 200? Are they still indexable, internally linked, and represented by the expected canonical URL? Did a theme release, redirect, inventory change, or content edit occur near the same time? Use URL Inspection and your deployment log before rewriting copy across the site. A measurable technical fault deserves correction even while a ranking update is still rolling out.
Put each finding in a short log: URL or page group, measured change, competing explanation, next check. That keeps an assumption from turning into a bulk edit. For example, a product category that disappeared behind a broken navigation link needs a navigation fix; changing its keyword density would not address the observed issue.
Review after the rollout
Recheck the same groups and query sets after Google reports the rollout complete. Look for persistent, material changes rather than a single day's volatility. Google’s traffic-drop debugging guide lists technical issues, demand shifts, and seasonality among the possible causes. If the evidence points to weak page content, improve the facts, usefulness, and purchasing information of the affected pages. Keep the dates of both the edit and the follow-up measurement.
Next check: rollout status, page-level impressions and clicks, indexing, and any operational change in the same period.
Build a diagnosis that survives coincidences
A global update and a traffic fall in the same week do not prove causation. Export the affected pages and queries, including their trend before September 24. Separate clicks, impressions, and average position: fewer clicks with stable impressions may also reflect a changed search layout or demand. Compare countries and page types. A decline limited to one product template suggests a different investigation from a decline across the entire site.
Check the site before rewriting
Inspect HTTP status, noindex rules, canonicals, sitemaps, and recent deployments. A configuration error can create an abrupt loss on the same day as an update. Also check manual actions and security issues in Search Console, without assuming a spam update will appear as a direct notification. If pages remain accessible and indexable, review their actual usefulness: do they answer distinct needs, or repeat almost the same copy across many URLs?
Example of a staged decision
In a hypothetical scenario, clicks to several store categories fall by 20% while sales remain stable. These invented figures illustrate a review process; they are not measured client results. It records the ongoing rollout, checks measurement, and isolates affected queries. It first improves one category with weak descriptions, filters, and shipping information, then waits for data after the rollout ends. Rewriting the whole catalog at once would obscure what helped. See Google's traffic drop diagnosis guide.
