Keep publishing. The decision about publishing during a Google spam update comes down to what kind of page you’re about to put live, not the calendar. Our reading: a post or service page that answers a real customer question can go out on the normal schedule. Hold back batches of near-identical pages — a stack of city pages launched at once, or a block of unedited drafts — until each one can stand on its own. Leave pages that already perform alone, apart from a factual correction. Google released its September 2026 spam update on September 24 and says the rollout may take up to two weeks to complete.
Both mistakes cost time and money. Pause the whole calendar for the full allowance and you skip every publishing slot inside it. Launch a batch of thin, near-identical pages and you can put those pages under a spam policy Google spells out. And as a general rule, a batch that lands during the rollout can make a later ranking change hard to trace.
Should You Stop Publishing During a Google Spam Update?
No. Neither Google’s dashboard entry for this update nor Google’s page on spam updates asks site owners to stop publishing. So the question that matters isn’t whether to publish. It’s what kind of page you’re about to publish, and whether that page would hold up on any ordinary week.
A spam update is a change to how Google’s automated systems detect spam. Google’s Search Status Dashboard entry for the update puts the release at September 24, 9:15 a.m. Pacific. It applies globally and to all languages. The entry also says the rollout may take up to two weeks to complete.
That’s all the dashboard entry says about the release. It names no spam category and lists no end. Nothing in the entry says which pages the update affects, so don’t build a plan around a guess about the target.
The two-week allowance is also worth putting in context. Google’s Search Status Dashboard history for Ranking lists the durations of the earlier 2026 spam updates: 19 hours and 30 minutes for the March 2026 spam update, 2 days and 1 hour for the June 2026 spam update, and 2 days and 16 hours for the August 2026 spam update. Against those, two weeks is a much longer stretch, but the same history lists earlier spam updates that ran longer, such as 26 days and 15 hours for the August 2025 spam update, so past durations don’t predict this one. Our reading: a calendar paused for the whole allowance would skip every slot inside it. And if your calendar is already paused, neither the dashboard entry nor Google’s page on spam updates says it has to stay that way.
What the official pages do say is about the pages themselves. Google’s page on spam updates says sites that violate its spam policies may rank lower in results or not appear in results at all. With no stated target and that consequence in writing, our reading is that the safer course isn’t silence — it’s publishing only pages that help readers.
Keep Publishing Pages That Answer a Real Customer Question
Our reading: the test is narrow. Does the page answer a question a paying customer has asked you? A post that explains what your quote includes, or a service page updated with details that are true and specific to your work — that goes out on the normal calendar.
Spilt Media’s content and blog creation page says it builds quarterly content calendars, and a calendar is the plan this decision has to fit into. A rollout doesn’t erase the slots you already committed to.
There’s one limit on all of this, and it comes straight from Google. Google’s guide to debugging drops in Search traffic says “we recommend avoiding making radical changes if your page is already performing well.” Our reading: the pages that already earn their traffic are the ones to leave alone. If a page carries a wrong phone number or an out-of-date fact, correct it and keep the correction to a one-line entry in your change log. Resist the urge to rework a page that’s working.
Hold Back Batches of Near-Identical Pages
Google’s spam policies describe scaled content abuse as what happens when “many pages are generated for the primary purpose of manipulating search rankings and not helping users.” The same page says the practice is typically focused on creating large amounts of unoriginal content that provides little to no value to users, “no matter how it’s created,” and it lists “using generative AI tools or other similar tools to generate many pages without adding value for users” among its examples.
Under doorway abuse, Google’s spam policies list a related example worth reading closely: “having multiple domain names or pages targeted at specific regions or cities that funnel users to one page.”
Put those two side by side and a pattern shows up. Our reading: what to hold back is a batch of pages that differ from each other only by a swapped name — a set of city pages built from one layout, or a block of drafts pushed live without edits. Build those pages one at a time instead. Each one should carry information only that page needs, like the work you’ve done in that city or the person who handles it.
There’s a timing reason too, and we’d flag it as a general rule rather than anything Google states: a batch that lands during the rollout can make a later ranking change hard to trace. You won’t know what moved your numbers, your batch or the update.
If you’re working out how much city coverage your site needs, we wrote separately about whether you need a page for every city you serve.
What Should You Write Down Before You Publish Anything?
Write down the release time first: September 24, 9:15 a.m. Pacific. Then, for every page you publish or change from that point on, log the date, the URL and what changed. Add the page’s clicks and impressions from Search Console, Google’s free report on how a site appears in Search, taken before you touch it.
That log is our suggestion, not a Google requirement. It exists for one reason: when something moves, you want to be able to point at a change you made or at the update, instead of shrugging. A log with dates beats memory.
The dashboard entry lists the release and carries no completion note. So read your results after the dashboard shows the rollout is over, not partway through. We’re not going to guess at when that happens, and you shouldn’t have to either.
The Search Console checks themselves are in our post on the June 2026 spam update, so we won’t repeat them here.
When Is It Time for an Outside Review?
Our reading: bring in an outside reviewer when a large drop spread across your pages is on the charts after the dashboard shows the rollout is over, and your own review of those pages doesn’t explain it. That’s the trigger. It isn’t a dip on one URL, and it isn’t a wobble partway through a rollout.
Google’s guide to debugging drops in Search traffic adds a whole-site step. For a large drop in position, it says to “self-assess your whole website overall (not just individual pages) to make sure it’s helpful, reliable and people-first.” That’s a whole-site review, not a page-by-page patch.
Pace matters too. Google’s page on spam updates says making changes may help a site improve if its automated systems learn over a period of months that the site complies with its spam policies. Our reading: a repair gets judged over months, not days, which is another reason to keep the change log. Months after a fix, it’s the record of what you edited.
Spilt Media’s search engine optimization page says its process starts with an audit of a site’s technical health, content gaps and competitive position. Our reading: whole site first, individual pages second.
Frequently Asked Questions About Publishing During a Google Spam Update
Does the September 2026 spam update apply outside the United States?
Yes. Google’s Search Status Dashboard entry for the update says it applies globally and to all languages. That’s the whole of what the entry says about reach.
Will a post published during the rollout be treated differently?
Neither Google’s Search Status Dashboard entry for the update nor Google’s page on spam updates says a post’s publication date during a rollout changes how it’s treated. Google’s page on spam updates points to its spam policies instead. Our reading: publish as normal, and judge each page by whether it helps the person reading it. We won’t guess past what Google wrote.
Does AI-assisted writing break Google’s spam policies?
Google’s spam policies describe scaled content abuse as what happens when “many pages are generated for the primary purpose of manipulating search rankings and not helping users,” and they name “using generative AI tools or other similar tools to generate many pages without adding value for users” as one example. The same page says the practice is typically focused on creating large amounts of unoriginal content that provides little to no value to users, “no matter how it’s created.” Our reading of that wording: the concern named is many pages made to manipulate rankings without helping readers, not which tool produced them. We’ll leave it there, because that’s where Google’s text leaves it.
How long can recovery take if pages were affected?
Google’s page on spam updates says making changes may help a site improve if its automated systems learn over a period of months that the site complies with its spam policies. That’s the only timeframe that page gives, and it’s a may, not a promise. Our reading: don’t judge a repair in days.
Does every city page count as a doorway page?
Under doorway abuse, Google’s spam policies list “having multiple domain names or pages targeted at specific regions or cities that funnel users to one page” as an example. The example describes pages that funnel users to one page, not every page about a city. Our reading: what the example describes is the funnel and the sameness, so each page you keep should carry information only that page needs.
What if traffic rises during the rollout?
Google’s guide to debugging drops in Search traffic says “we recommend avoiding making radical changes if your page is already performing well.” Our reading: write the rise down, leave those pages alone, and compare the numbers after the dashboard shows the rollout is over.
Want a Second Opinion on Your Content Calendar?
If you’re holding a batch of pages and can’t decide whether to ship them, that’s a conversation worth having before you hit publish. Bring your calendar and your change log. Pick a time and book a consultation with Spilt Media.