Skip to content Published: 11 October 2026 | Updated: 11 October 2026
The September 2026 Google spam update finished on 8 October. If your South African website lost traffic, confirm what changed before deleting articles or blaming AI. Check affected queries, indexing, recent website changes and policy compliance. A drop during the rollout is a clue, not proof that your site was penalised.
A quiet enquiry inbox can make a search graph feel urgent. But changing twenty pages before checking the evidence can turn one problem into several. You also lose the baseline that would have helped you understand the original decline.
This guide gives business owners and WordPress teams nine checks for the September 2026 Google spam update. It separates facts from possible explanations, includes a practical diagnosis table and shows how to prioritise fixes without sacrificing pages that still work.
Google’s official update record lists a start on 24 September and completion on 8 October 2026. The update applied globally and to all languages. The announcement doesn’t identify individual affected websites or establish that every traffic decline during those dates came from spam detection.
The September 2026 Google spam update is separate from the August spam update. Keep the timelines separate when reviewing your own records.
Google also revised its guidance about generative AI content on 1 October. That documentation change isn’t, by itself, evidence of another algorithm rollout. This article is checked against Google’s primary sources as at 11 October 2026. Site-specific conclusions still require your own data.
Identify the failing stage before choosing a fix. A page can be accessible but not indexed, indexed but less visible, visible but less attractive to click or visited without generating enquiries. Those are different problems.
| Observed pattern | Possible explanation | Next useful check |
|---|---|---|
| Analytics visits fall, Search Console clicks stay similar | Tracking or consent behaviour changed | Test measurement on the live site |
| Specific queries lose visibility while pages remain indexed | Ranking, relevance or competition changed | Compare the same query and page groups |
| Important URLs become excluded or inaccessible | Technical indexing or access problem | Inspect URLs, directives and responses |
| Impressions stay similar but clicks decline | Different query mix, snippets or search layout | Inspect affected searches and devices |
| Traffic stays similar but enquiries decline | Intent mix or conversion failure | Test forms, calls and message delivery |
| Seasonal queries decline across the market | Demand changed | Compare comparable periods and trends |
Several explanations can coexist. A redesigned website might have a tracking error and a missing service page at the same time. For a broader measurement framework, see our guide to search and analytics measurement.
Take a backup and export the relevant reports. Keep a dated record of the affected URLs, titles, headings, internal links and important settings. Screenshot useful graphs for your own records, but retain the underlying data too.
Create a simple change log with the date, page, observation, proposed change and rollback method. Include deployments, cache changes, plugin updates and content releases. Your goal is to make the next decision easier, not produce a lengthy report nobody uses.
For the September 2026 Google spam update, record whether the decline started before, during or after the rollout. Then compare that timing with your own work. A match warrants investigation; it doesn’t settle the cause.
If you’re rebuilding, preserve successful URLs and relevant content while fixing proven weaknesses. Our AI website-builder SEO checklist covers common launch risks, while custom website planning should account for existing search performance.
Start with the URLs that lost valuable enquiries or search clicks. Separate branded searches from unbranded searches and compare the same country, device and search type. A single site-wide average can hide a problem in one service or conceal a change in the mix of searches.
Use equal-length, complete reporting periods with comparable weekdays. As at 11 October, only a few days have passed since completion. That’s too little post-rollout data for a confident long-term verdict. You can investigate access failures immediately while gathering a more useful performance window.
Google’s traffic-drop troubleshooting guide distinguishes technical, security, spam and demand-related causes. Use it to check alternatives rather than treating the update date as a diagnosis.
Record which queries declined, which destination pages changed and whether the loss is concentrated. For example, losing a branded query requires a different investigation from losing a broad comparison query. Keep stable, useful pages out of a mass rewrite.
Inspect representative affected URLs in Search Console. Compare the indexed information with the live page. Check that the intended page loads, shows its main content and points to the correct canonical URL.
For WordPress sites, inspect accidental production blocking, redirects, missing pages and staging URLs appearing in production links. A security challenge can also interfere with particular automated requests. Test the actual response before changing protection settings.
Keep staging protected from indexing while ensuring the live website has its intended production settings. Don’t remove staging safeguards because you’re investigating a public-site decline.
Work through a business website audit if several technical issues overlap. If the fixes need implementation, WordPress search optimisation should address the demonstrated failure rather than install more plugins by default.
Review Search Console’s Manual Actions and Security Issues reports. Record what each report actually says. An explicit notice gives you a concrete problem to address and a documented process to follow.
No manual action doesn’t prove that every page complies with Google’s policies or that an automated ranking change is impossible. Equally, a ranking decline alone doesn’t establish a manual penalty. Use the correct label when discussing the issue with your developer or SEO supplier.
Check unexpected pages, unfamiliar outbound links and changes your team didn’t make. If you find a compromise, secure the site and preserve relevant evidence. Content edits won’t solve an active security problem.
AI assistance isn’t a diagnosis of spam. The useful question is what the published page adds for its reader. Google’s generative AI content guidance warns that generating many pages without added value may violate its scaled content abuse policy. It also calls for accuracy checks across content and metadata.
Pick a sample of affected articles. Can a customer act on the information? Are business facts correct? Are sources traceable? Does the page offer a meaningful explanation, useful comparison or properly documented example beyond a generic summary?
Remove invented claims and unsupported testimonials immediately. Improve thin sections with relevant detail rather than padding them to a target word count. An author block should identify the responsible person without manufacturing credentials or experience.
The AI-content publishing checklist helps you review individual pages. A custom SEO assessment can then separate content work from technical repairs.
Review pages created for similar services or suburbs. A Bellville page and a Durbanville page should serve real customer needs, with accurate scope and relevant information. Swapping place names across otherwise identical pages doesn’t establish useful local coverage.
Google’s spam policies cover doorway abuse, keyword stuffing, link spam and other manipulative practices. Compare your implementation with the policy rather than assuming every location page is either safe or abusive.
Follow the internal links a reader would need next. Check whether they reach the correct service, explanation or enquiry page. Replace broken or irrelevant links and make anchor text describe the destination. Don’t add the same large related-links block to every article just to reach a numerical target.
For business facts shared across channels, use the website and Google Business Profile consistency checklist. Links and local references should help a visitor verify your business, not simulate relevance.
Ask your supplier for a readable account of links obtained, how placements were arranged and whether payment or exchange was involved. Review actual examples. A report showing hundreds of links doesn’t explain their purpose or quality.
Investigate clearly manipulative arrangements without assuming every unfamiliar link is harmful. Don’t pay for a bulk link-removal campaign or submit a disavow file simply because a tool labels links toxic. Establish the problem and the appropriate scope first.
Google’s spam-update guidance says policy-related improvements may take months to be recognised. It also explains that lost benefits from neutralised spam links can’t be regained by cleaning them up. The September announcement itself doesn’t identify this rollout as a dedicated link-spam update.
For procurement questions, our guide to assessing low-cost SEO services can help you ask for accountable work rather than a recovery guarantee.
If clicks fell but impressions stayed similar, inspect the searches involved. Are different competitors appearing? Has the result layout changed? Does your title still describe what the page offers? Are you comparing the same query group?
AI Overviews are one possible part of a changed search experience, not an explanation you can infer from falling clicks alone. Record the query, location, device and date when observing a result. Repeat observations because layouts and answers can vary.
Track organic positions, AI citations, referral visits and qualified enquiries separately. Being indexed doesn’t prove that an AI answer retrieves your article. A citation doesn’t establish a recommendation, and a recommendation doesn’t prove a sale.
Read the South African AI Overviews guide for context and the AI visibility measurement framework for distinct measures. Preserve this separation when reviewing the September 2026 Google spam update.
Test the commercial journey yourself. Submit a genuine test enquiry, check the confirmation and confirm receipt. Test the mobile call and messaging links too. A working button is only part of a working enquiry process.
Choose the smallest change that addresses a supported finding. Record its date and expected effect. An access fix should be checked for access; a title change should be checked against relevant click behaviour; a form fix should be checked for completed delivery.
Maintain stable comparison groups where practical. If you change titles, content, URLs, schema and navigation simultaneously, interpreting the outcome becomes much harder. Your search optimisation plan should connect each change to a measurable problem.
This is an illustrative scenario, not a client result. A Bellville repair business notices fewer reported visits during the update and prepares to delete ten AI-assisted articles.
The owner first compares the same branded and service queries. Search Console clicks appear broadly stable, but analytics sessions fell after a consent setting changed. A test enquiry also reveals that email notifications aren’t arriving.
In this scenario, deleting articles wouldn’t repair measurement or message delivery. The sensible order is to verify those two problems, fix them and then review search performance separately. The example doesn’t establish that a similar pattern has the same cause on your site.
That distinction is the practical value of investigating the September 2026 Google spam update carefully: your fix should match the observed failure.
For each action, keep five fields: evidence, proposed fix, owner, completion date and acceptance check. Add a rollback note where the change could affect successful pages. This keeps a diagnosis from becoming a vague list of SEO tasks.
The September 2026 Google spam update finished on 8 October 2026, according to Google’s official status record. It began on 24 September and applied globally across languages.
South African websites were within the global scope. That doesn’t mean every local website changed or that an individual decline was caused by the update. Check your own affected pages and reporting before drawing that conclusion.
Don’t delete them solely because AI assisted the writing. Check accuracy, originality, usefulness and policy compliance. Correct a demonstrated problem and preserve useful content. Decide whether to improve, consolidate or remove a page based on its purpose and evidence.
Yes. Automated systems and other changes in search can affect visibility without a manual action notice. An empty Manual Actions report doesn’t diagnose the cause of a decline.
There’s no guaranteed deadline. Google says automated systems may need months to recognise sustained policy compliance. Fixing a technical error is a separate process, with its own recrawling and validation needs.
Yes, depending on what changed. Inspect URLs, redirects, canonicals, indexing controls, main content and internal links. Keep staging blocking isolated from production. A redesign and a Google update happening together require separate investigations.
Only when they improve relevance and usefulness. Repetition and irrelevant links aren’t repairs for an unidentified problem. Use natural terms that describe the issue and link to resources that answer the reader’s next question.
You need observations of the affected searches alongside performance data. A click decline by itself doesn’t prove an AI Overview caused it. Distinguish search appearance, citation, referral traffic and enquiries.
Request a custom website and search visibility assessment. Share your website URL, the date you noticed the decline and the pages or services that matter most. The assessment should identify supported findings and an ordered scope before you invest in repairs.
Editorial method: This guide uses official Google sources checked on 11 October 2026. The diagnosis framework and Bellville scenario are editorial guidance, not findings from an audit of your website. Illustrations are AI-generated editorial artwork, not screenshots or client evidence.
David Gous writes about WordPress websites, search visibility and practical digital growth for South African businesses. This guide separates official Google information from editorial recommendations and an illustrative business scenario.