Quick Answer
If organic traffic changed during the September 2026 spam update, annotate the date and diagnose the loss before changing the site. Confirm tracking and Search Console data, check manual actions and indexing, segment the impact, compare it with recent releases and demand, then audit relevant spam-policy risks. Wait for the rollout and data to stabilise before making irreversible content or link decisions unless you find a clear technical or policy problem that already warrants correction.
What Google Confirmed
The Google Search Status Dashboard lists a September 2026 spam update beginning on 24 September. Google's spam updates improve automated systems that detect content and behaviour violating Search spam policies.
Google does not publish a list of affected sites or a single fix. That is why broad claims such as “the update targeted AI content” or “the update was about backlinks” should be treated cautiously unless they are tied to evidence from the affected site and official guidance.
A Matching Date Is Not a Diagnosis
Traffic can fall during an update for unrelated reasons:
- analytics or consent changes;
- seasonal demand;
- a website release;
- robots, canonical, noindex, or sitemap errors;
- server or rendering problems;
- lost rankings to a stronger competitor;
- changed search features and click behaviour;
- manual actions;
- policy enforcement;
- a small set of high-volume pages losing visibility.
The first job is to reduce the number of plausible explanations. This is why a search engine optimisation review should begin with first-party evidence and recent site changes, not a predetermined story about the update.
The Diagnosis Tree
| Question | Check | Likely next step |
|---|---|---|
| Did only GA4 traffic fall? | Compare Search Console clicks and impressions | Audit tracking, consent, channels, and landing-page tags |
| Did impressions fall across the site? | Segment by page type, query, country, and device | Check demand, ranking, indexing, and site-wide changes |
| Did one template fall? | Compare affected and unaffected URLs | Inspect template, internal links, duplication, and technical output |
| Did clicks fall but impressions hold? | Review CTR, search features, titles, and query intent | Improve snippet relevance and assess zero-click changes |
| Is there a manual action? | Search Console Manual actions report | Fix the stated violation and follow reconsideration guidance |
| Did conversions hold? | Compare qualified leads, revenue, and conversion rate | Avoid treating traffic alone as the business verdict |
This sequence protects the site from fixes aimed at the wrong problem. If traffic moved but enquiries or sales did not, connect the diagnosis with CRO and analytics before calling it a commercial loss.
The First 60 Minutes
1. Annotate 24 September in your reporting timeline. 2. Confirm Search Console and GA4 are collecting current data. 3. Check Manual actions, Security issues, Page indexing, and Crawl stats. 4. Compare the last complete period with an equivalent earlier period. 5. Export pages and queries with the largest absolute click and impression changes. 6. Check releases, migrations, redirects, template changes, and tracking changes from the same period. 7. Record whether calls, forms, sales, and qualified leads changed with traffic.
Do not begin by asking an SEO tool which pages to delete. Begin with first-party data and a change log.
A Practical Audit Note
Create a worksheet with URL, page type, query group, country, device, impressions before, impressions after, clicks before, clicks after, conversion outcome, index status, recent change, policy risk, first check, owner, and retest date.
Sort by absolute loss, not only percentage loss. A low-traffic page can show a dramatic percentage decline after losing only a handful of clicks, yet still be less urgent than a modest decline on a high-intent service page. Prioritise the business impact, not the most alarming percentage in the report.
Then compare an affected page with an unaffected page of the same template. This often reveals whether the issue is site-wide, template-specific, topic-specific, or related to search demand. Use the SEO audit checklist when the evidence points to a broader technical or template issue.
When a Content Audit Is Justified
Review content when the affected set shows patterns such as:
- pages created mainly to capture near-identical keyword variations;
- generic summaries with little original contribution;
- misleading titles or claims;
- copied or lightly rewritten material;
- doorway pages;
- expired or inaccurate information;
- pages that no longer satisfy the intent they target.
The answer may be to improve, merge, redirect, remove, or leave the page alone. Make that decision page by page or pattern by pattern, not as a panic rewrite across the whole blog. The guide to why SEO content fails gives a useful review lens for pages that are polished but still add little value.
When to Review Links
Audit links when there is evidence of a risky acquisition pattern, manual action, sudden unnatural growth, paid placement without appropriate qualification, or links created primarily to manipulate rankings.
Do not buy a “toxic backlink cleanup” solely because a third-party tool assigns a high risk score. Google has systems designed to ignore many spammy links. The Disavow tool is a specialised measure, not a routine response to every update.
Reporting to a Founder or Marketing Head
Keep the report proportional to the business. A small local company may need one page covering visibility, calls, enquiries, affected URLs, and the next action. A large multi-market site may need template, country, category, and conversion segmentation.
Depth depends on business model, industry, competition, site size, budget, scope, monthly activity, and expected return. The purpose of the report is to support the next decision, not to prove that the analyst opened every available dashboard.
Tips During an Active Search Update
- Freeze non-essential SEO releases so new changes do not muddy the diagnosis.
- Keep a dated log of technical, content, link, and tracking changes.
- Compare impressions and clicks separately; they point to different problems.
- Check high-intent and high-value pages before low-value traffic pages.
- Preserve evidence before rewriting titles, merging URLs, or changing redirects.
- Reassess after Google marks the rollout complete and a stable comparison period exists.
What to Keep an Eye On
Watch the Search Status Dashboard for completion. Continue monitoring Search Console impressions, clicks, position by query and page, indexing, manual actions, affected templates, conversions, lead quality, and whether losses persist after the rollout settles.
FAQs
How long should we wait before making changes?
Do not wait to fix a confirmed technical error, security issue, manual action, or clear policy violation. For unexplained ranking movement during the rollout, avoid irreversible changes until the rollout completes and the data stabilises.
Should we delete AI-assisted articles?
Not because AI assisted with them. Review whether the pages are accurate, original, useful, well maintained, and created for readers rather than scaled search manipulation.
Should we disavow suspicious links?
Not as a default update response. Use the tool only when there is a serious link-scheme issue or manual-action context and the decision is supported by evidence.
What if traffic fell but leads did not?
Investigate the traffic loss, but do not describe the business result as a total failure. The lost visits may be lower intent, while conversion rate or traffic quality improved.
Protect the Evidence Before You Change the Site
Search updates create pressure to act. Good diagnosis creates permission to act on the right thing. Preserve the before state, narrow the affected pattern, test each explanation, and make the smallest defensible change first.