Google’s September 2026 spam update is officially complete, and the aftermath requires more than a glance at your rank tracker. The update started on Sept. 24 and finished on Oct. 8, according to the Google Search Status Dashboard — a run of about 13 days and 16 hours.
The update that refused to hurry
That’s close to the “up to two weeks” window Google initially set, but a clear outlier against the three previous spam updates in 2026, which each wrapped in under three days.
SEOmonitor added a caution: from Sept. 26, industry-wide rank trackers saw sudden changes that regular Google searchers did not. It points to automated search tools receiving incomplete or inaccurate data from Google, rather than actual ranking chaos.
What to do: treat the Sept. 24 to Oct. 8 stretch as your comparison window. Real spam update movements usually persist across consecutive days and show up in Search Console impressions and clicks, so check those before calling a late-September tracker dip an update effect.
Timing ranges to bookmark
Gary Illyes shared timing expectations at Search Central Live Deep Dive Europe in Barcelona on Oct. 2, per a recap by event speaker John Campbell of ROAST:
- Site move: typically 1 to 3 months; slowest 6 months to more than a year.
- Core update recovery: typically 3 to 6 months; slowest 6 months to a year.
The recap doesn’t disclose sample size, time period, or how “typical” is defined. Use these as reference points when clients feel stuck, not as contractual deadlines.
Search Console gets easier for multi-market teams
Google updated the Performance report filters, announcing on Oct. 6 that you can now combine Google Search traffic across multiple countries or devices. Teams that manage a group of markets can pull one combined Search figure instead of comparing two at a time. Compare still works side by side for two devices, countries, Search types or appearances.
Fake author profiles are now a named warning
Google’s people-first content guidance now calls out fabricated creator profiles: AI-generated headshots, made-up names and false credentials used to make content look human-written. Google describes any such deception as “a signal of a low-quality page.”
Audit your bylines and author pages for anything that creates a false impression of human expertise — that’s now a direct quality risk.
AI crawlers won’t ask for your sitemap
John Mueller explained on the Oct. 1 Search Off the Record podcast that AI training crawlers usually don’t provide a sitemap submission path. A default name like sitemap.xml or an RSS feed helps them find content; he has seen AI crawlers access those files in his own server logs.
If a valid sitemap shows “Couldn’t fetch,” Mueller points to host load and crawl demand — often driven by perceived quality — rather than the file itself.
This week’s checklist
Before you send that client report, verify what’s behind the label: check Search Console data for the spam window, audit author profiles, and make sure your sitemap is easy for non-Google crawlers to find.
Source: Search Engine Journal
