Google September 2026 Spam Update: What Brands Should Check

Google's September 2026 spam update ran from September 24 to October 8, according to its completed status record. For a multi-location service brand, the next useful step is to identify which page groups changed, check technical and policy problems, and record what the evidence can explain before attributing a lost booking to the update.

Last verified: October 19, 2026.

I would start with one shared evidence sheet: the pages that changed, the search queries behind them, the changes your team deployed and the checks still outstanding. A regional operator should be able to see whether the problem belongs to a location template, a technical release, a fall in demand or a policy concern. The announcement by itself cannot decide that.

What Google has actually announced

The completed notice establishes the September 24 start, October 8 finish and global scope across all languages. It does not name a new spam policy, say that every AI-written page is affected or identify your business as penalized. Google's existing spam policies provide the standards for reviewing a page.

That distinction matters when a team has hundreds of location URLs. Rewriting them all in response to an update can introduce new errors and make the original change harder to diagnose. Save a copy of the current pages and the performance export first. Then work on the page groups where you can point to a specific problem.

Start with the traffic change, then check its cause

In Search Console, record when the drop began and whether it affects clicks, impressions or both. Keep the search type consistent. A decline in web results and a decline in image results can need different investigations. Filter by page and query, then compare the affected group with an appropriate earlier period and the same season where you have enough history.

Google's traffic-drop guidance includes technical issues, security problems, manual actions, algorithmic changes and changing search interest. Check the Manual Actions and Security Issues reports. Review indexing and inspect a representative affected URL. Also look at your own release dates: a redirect, canonical change, robots rule or broken template is evidence your team can verify.

A dashboard needs to keep those observations separate from an inference about the update. "Clicks fell after September 24" is an observation when the export shows it. "The spam update caused the fall" needs more support. An empty Manual Actions report also does not rule out an algorithmic change.

Review the location template your customers actually use

Sample affected pages across service lines and markets. Include a location that held steady so the team has a comparison. Read the rendered page on a phone, follow its booking link and check that the service and coverage claims match what the local operation offers.

Two policy areas deserve a close look. Google describes doorway abuse as intermediate pages created to rank for similar queries that add little value before sending customers onward. Its scaled content abuse policy concerns many pages produced mainly to manipulate rankings without helping users. Neither definition is a count of how many branches a company owns.

Use these questions to review a city-page sample:

• Does this page answer a distinct service need with accurate coverage, contact and booking information?
• Can the location team verify its hours, services, credentials and any photos or customer evidence used?
• Do repeated sections add useful information, or do pages mainly swap city names and lead to the same generic destination?
• Can a customer reach the right team from this page without another search?

Keep useful shared service explanations. Replace unsupported local claims with facts the business can substantiate. If several pages cannot serve different customer needs, consider consolidating them into the appropriate service or coverage page. Our city-page guide explains how to make that ownership decision without inventing local detail.

Google's generative AI guidance says AI can support research and structure. It also warns that generating many pages without adding value may violate scaled content abuse policy. Review the information the customer receives, including its accuracy and relevance. An AI tool label cannot settle that review, and a human byline cannot rescue unsupported content.

Give the audit an owner and a week of work

The sequence below is a suggested five-day operating plan. It is not a recovery forecast. Start on the next working day, name one SEO owner and have each regional operator validate the local facts used on their pages.

On the first day, preserve the performance exports and the rendered templates. On the second, identify the page groups and queries responsible for the change. On the third, inspect the affected templates, technical settings and policy concerns. Make verified fixes on the fourth day. On the fifth, read back the live pages, contact paths and indexing settings, then record the next performance checkpoint.

If a manual action exists, follow its stated review process. If a robots or canonical change explains an indexing problem, fix that specific issue. If the evidence is still inconclusive, keep monitoring the same page group. Those findings deserve different owners and next actions.

The evidence sheet should contain a small set of fields your team can maintain:

• URL or page group, observation date and the exact Search Console filter used.
• Suspected issue, supporting export or page evidence, and anything still unknown.
• Named owner, change made and the live readback result.
• Next check date and the measure that would show improvement.

Keep organic search, AI visibility and bookings distinct

Organic search clicks, AI recommendations and booked jobs measure different events. A search change does not establish a booking change. Check your analytics and lead records before assigning a revenue figure, and label missing attribution as unknown. Our AI traffic measurement guide covers the limits of referral and attribution data.

After a fix, verify the page and keep measuring

Google's spam-update guidance says affected sites may recover over a period of months as its systems learn that they comply with the policies. It does not promise a recovery date for your site. A successful build or crawl confirms that part of the work; it does not confirm restored visibility.

Read back the live URL after each approved change. Check the canonical, indexing settings, visible local facts and booking path. Keep the original export so the next checkpoint uses the same definition. That gives your team a defensible account of what changed and whether performance followed.

For a brand managing this across many branches, Cheers' multi-location local SEO approach connects location evidence, content ownership and ongoing measurement. The first deliverable for this update is concrete: a short list of verified page problems, an owner for each fix and a dated record of the questions your data has not answered.

Sources

• September 2026 spam update. Google Search Status Dashboard, September 24 to October 8, 2026; checked October 19.
• Spam policies. Google Search Central; checked October 19, 2026. Doorway and scaled content abuse definitions.
• Debugging search traffic drops. Google Search Central; checked October 19, 2026. Investigation steps and possible causes.
• Spam updates. Google Search Central; checked October 19, 2026. Reevaluation timing and limitations.

Dylan Allen-Arnegård is the CEO & Co-Founder of Cheers, the local search platform for multi-location service businesses.