Google’s September 2026 spam update has no completion announcement in the official Search Status Dashboard consulted October 4. The notice records its start on September 24 at 09:15 PDT, equivalent to 18:15 CEST, and says it applies globally and across all languages. Google estimated that the rollout could take up to two weeks.
The retrieved incident page contains the release notice without a subsequent completion entry. The estimated duration is not a guaranteed finishing date. There are no additional details on that page identifying specific targets or confirming a separate second phase.
Keep the observation separate from the diagnosis
For a site owner, a ranking movement during this period is worth investigating, but its timing alone does not establish its cause. Our recommendation is to describe the observed change precisely before assigning an explanation: which pages lost visibility, for which queries, in which countries and on which devices?
A broad sitewide movement and a change limited to a few search terms require different investigations. Compare like-for-like periods and record other events that could affect the result, including releases, content changes and measurement changes. A useful report preserves those possibilities rather than declaring a final outcome from one day’s movement.
“Provisional” should refer to the causal conclusion, not to whether a real problem deserves attention. If a page is inaccessible or important information is incorrect, address the confirmed issue. Waiting for a rollout notice is not a reason to leave an independently demonstrated defect unresolved.
What Google’s spam-update guidance actually says
Google’s general spam-update documentation advises affected sites to review its spam policies. It explains that violations can reduce visibility or remove a site from results, and that improvements may require automated systems to observe compliance over months. It separately notes that benefits removed by a link-spam update may not be recoverable. That general explanation does not establish that this September update is specifically a link-spam update.
An editorial audit should therefore begin with evidence about the site’s practices. Identify content or behaviour that conflicts with a relevant policy and document the correction. Avoid removing useful pages simply because their rankings moved, or assuming that adding a reviewer name will resolve an unspecified problem.
Track search surfaces separately
For NetContentSEO readers monitoring AI visibility, our recommendation is to keep traditional rankings, AI answer appearances, citations and referral traffic in separate reporting groups. A simultaneous movement across those groups can motivate investigation, but it does not prove the spam update caused every change.
The official incident concerns ranking. The notice does not provide a specific account of Discover losses, translated Reddit pages or changes in AI citation selection. Any such observations need their own evidence and attribution. Community reports can help locate a pattern to inspect, while the dashboard remains the primary source for rollout status.
Prepare a useful review after completion
Maintain a dated record of the rollout and the site’s observations. Once Google announces completion, compare the subsequent pattern with the baseline and the changes made during the period. Preserve uncertainty where the available data cannot distinguish competing explanations.
The immediate operational priority is to collect clear evidence and correct confirmed issues. A completion notice will establish the announced rollout boundary; it will not, by itself, explain every site’s performance or guarantee that rankings stop changing afterward.