How to brief your web team or agency on Google's September spam update

Answer first: The best way to handle Google's September 2026 spam update is to send your web team or agency a short written brief with four parts: the facts, the measurement rules, the checks to run, and the changes to hold. A clear brief keeps everyone calm, keeps the data clean, and stops anyone from rebuilding the site in the middle of a two-week rollout.

Most small business sites will see no effect at all. The brief still matters, because a vague request like "check if we got hit" invites guesswork.

Part one: give them the confirmed facts

Start the brief with what Google has actually said, so nobody works from rumor. These are the points to include:

• According to Google's Search Status Dashboard, the update started at 9:15 a.m. PDT on September 24, and it applies globally and to every language.
• The dashboard says the rollout may need as long as two weeks, which does not mean it will use the full window.
• Google has now confirmed four spam updates in 2026, with the earlier three arriving in March, June, and August.
• No further detail has come from Google about what this one targets, so any claim about a specific tactic is a guess.

Add one line about timing, since it explains why patience matters. For comparison, March finished in 19 hours and 30 minutes, the June update needed 2 days and 1 hour, and August ran for 2 days and 16 hours, each with a stated window of a few days.

John Mueller of Google said he expected this rollout to run longer than several earlier ones. He gave no technical reason for the longer window.

Part two: ask them to rule out ordinary breakage first

Have your team check the common failures before anyone blames the update. Google's guidance on traffic drops lists several separate causes: algorithmic updates, technical issues, seasonality, and spam-policy violations with manual actions.

Put these questions in the brief and ask for a yes or no on each:

• Did a hosting, theme, or plugin change cause a break around September 24?
• Is robots.txt or a stray noindex tag keeping crawlers out?
• Did an SSL certificate, a DNS record, or a redirect chain fail?
• Is September normally slow in our industry when we compare year over year?
• Is there a manual action listed in Search Console?

AppWT finds that most worried calls about a Google update trace back to an expired certificate, a caching plugin, or a seasonal dip that returns every year. Getting those answers first keeps the team from chasing the wrong cause.

Part three: set the measurement rules

Your numbers will be unreliable for a couple of weeks, and a dip on day three might reverse by day nine. Spell out how the team should measure so the results mean something:

1. Annotate September 24 in analytics and track organic traffic through roughly October 8.
2. Save a clean snapshot by exporting the 28 days of performance data that came before September 24 from Search Console.
3. Report by page and by query, sorted by clicks lost, instead of a sitewide chart that hides the signal.
4. Match search types in every comparison. On the same day the update started, Search Console divided the Web search type into two parts, text and multimodal. That is a reporting change, not an effect of the update.
5. Wait for the completion notice on Google's ranking release history page before drawing conclusions.

Part four: name what stays frozen

Tell your team plainly which work pauses until the rollout ends. Large redesigns, mass content rewrites, and URL changes should wait, because nobody could tell which change caused which result.

Clear problems still get fixed right away. Broken pages, indexing errors, and any content you already know relies on a tactic Google's spam policies describe are fair game during the window.

Part five: hand them a useful audit

The two weeks do not have to be idle. Ask your team to review the items that are always worth reviewing, update or no update:

• Thin or mass-produced pages, such as 200 city pages that change nothing but the town name.
• Links that were bought, swapped, or picked up from a directory network.
• Old guest posts and sponsored content, which should be labeled as such on your site and on the sites that host you.
• Abandoned subdomains, unused staging sites, old forums, and forgotten subfolders that someone could hijack and fill with junk.
• AI-generated filler made to keep a posting schedule full instead of helping a customer with a real question.

Questions to ask about past work

If an earlier vendor built or marketed your site, this is a good week to ask direct questions. Keep them factual and neutral:

• Were any location pages generated in bulk from a template?
• Were backlinks ever purchased or traded on our behalf?
• Was any content produced in volume to hit a publishing quota?

Those three shortcuts are the ones that tend to cause trouble, and an honest answer now is worth more than a surprise later.

Set expectations for what comes back

Make sure the team knows how spam demotions behave. Google's spam systems demote sites on their own, with no manual action and no message in Search Console, so a quiet inbox proves nothing either way.

Collateral damage can happen with any update, and legitimate sites also move around during these periods. A decline during the rollout is not proof that Google labeled your site as spam.

If the data does point to a hit, Google's guidance is to check Search Console, consider the timing, find where the meaningful changes are, and review those pages against its published spam policies. Recovery means fixing the real problem and then waiting for Google's systems to reassess the site, which can take until another update cycle.

Keep the brief in proportion

Spam updates go after large-scale manipulation. Picture a Michigan plumbing company with a twelve-page site, a genuine address, honest reviews, actual job photos, and pages that serve real customers. That business is not the target.

Spam updates improve Google's automated detection, so the filters get better at catching what already broke the rules. The rules themselves usually stay the same, which is why steady, honest work rarely needs an emergency response.

A short brief you can copy

• Start: 9:15 a.m. PDT, September 24, 2026, with up to two weeks to finish.
• Rule out technical causes, manual actions, and seasonality first.
• Snapshot the prior 28 days, compare matching search types, and report by page and query.
• Fix clear problems now, and hold redesigns, bulk rewrites, and URL changes.
• Audit thin pages, links, sponsored content, old subdomains, and filler.

Not sure what caused a drop in traffic? Contact AppWT with your questions, or book a call, and AppWT will look through your Search Console data with you and help you write the brief.