The September 2026 spam update: how I would audit a site before changing it
Google confirmed a global spam update and new image-led reporting in Search Console. A practical audit separates ranking signals, reporting and site changes.
Google’s status dashboard dates the global update to September 24 and says rollout may take two weeks. Search Central separately announced multimodal reporting. No ranking outcome is claimed for this portfolio.

First, mark the timeline
Google says the spam update started on September 24, applies globally and to all languages, and may take up to two weeks to roll out. That timeline is a starting point for investigation, not proof that a particular site was affected. [1]
On the same day, Google announced a Search Console filter for searches begun with an image. It covers Lens, Circle to Search, image uploads and Chrome’s “Search this image” action. This is a reporting change; it should not be read as an explanation for a ranking change. [3]
Then inspect pages, not just a site-wide graph
My audit sequence for a static site or portfolio:
- Record the deployment and content dates so a site edit is not mistaken for an algorithm effect.
- Compare Search Console clicks and impressions by page over a window before and after September 24.
- Check indexing, canonical URLs, language alternates and sitemap entries for pages that moved.
- Review the affected pages against published spam policies and their actual usefulness to a visitor.
- Keep the new multimodal filter as a separate baseline if the property receives image-led traffic.
A build that produces valid pages can still have thin or repetitive copy. Conversely, a useful article can disappear from the comparison because a canonical, redirect or indexing rule changed. I would check both before rewriting content.
What I would change
I would fix an identifiable defect: a broken canonical, a page that repeats another without added value, or an outdated answer. I would not batch-edit titles during an unfinished rollout just to create activity. Google’s spam update guide points site owners back to the published policies. [2]
The longer Meuveryone guide explains the business-site checks and the limits of the new report in English and Spanish. [4] [5]

