Tag: Google Spam Update 2026

On September 24, 2026, Google began rolling out its September 2026 spam update. Spam updates usually finish in a couple of days, so most site owners are used to a short burst of volatility followed by a clear before and after. This one is different. Google says the rollout may take up to two weeks, which means that for a full fortnight, every ranking change you see is a reading from a moving target.

That changes how you should respond. This piece covers what Google has confirmed, what it has not said, what early volatility data does and does not show, and a practical plan for the days between now and the end of the rollout. It is written for anyone responsible for search engine optimization at their company, whether you run a small site or manage a large content library.

What is confirmed

The core facts come from Google’s Search Status Dashboard and are consistent across Search Engine Land, Search Engine Journal and Search Engine Roundtable.

The update began on September 24, 2026, at 9:15 a.m. Pacific time. It applies globally and to all languages. Google’s dashboard says the rollout may take “up to two weeks to complete”, which puts the latest possible finish around October 8. It is the fourth spam update of 2026, following releases in March, June and August.

The rollout window is what stands out. The dashboard lists the earlier 2026 spam updates at 19 hours and 30 minutes for March, 2 days and 1 hour for June, and 2 days and 16 hours for August. Two weeks is several times longer than any of them. One point of precision matters here: two weeks is the announced maximum, not a measured duration. The update could finish sooner, and until Google marks it complete, nobody outside Google knows how long it will really take.

What Google has not said

Google has not said what this update targets. According to PPC Land, Search Central described it only as a normal spam update, with no new policy, no named category and no figures on how many queries are affected. That gap matters, because much of the commentary this week has filled it with confident claims about which sites are being hit and why. Treat those claims as hypotheses. The only firm statement from Google is that sites which see a change should review its spam policies. Anything more specific is inference from other people’s data.

What early data shows, and what it does not

Search Engine Roundtable reported that a long list of volatility trackers showed significant movement across the first weekend, September 25 to 27. The tools it named include Semrush Sensor, AccuRanker, Mozcast, Sistrix, Algoroo and several others. When that many independent trackers move at once, it is a reasonable signal that something real is happening in the results.

Glenn Gabe, a well-known analyst of Google updates, reported big drops across a number of sites in multiple verticals and countries. He described AI-generated content sites and programmatic content farms as among those losing rankings. That is one experienced observer’s read of the sites he tracks, and it fits how Google’s spam policies treat scaled content, but it is not confirmed by Google and it is not a full picture of who is affected.

There are three reasons to be careful with early data.

First, volatility is not damaging. Trackers measure how much results moved, not who won or lost. A large reading can come from a few sites moving a long way.

Second, the update is not finished, so the pattern on day five may look different by day ten.

Third, you are reading a mix of signals. Seasonal demand, your own recent changes, other Google systems and ordinary news cycles all move traffic at the same time. Attributing a dip to the spam update before it ends is a guess.

What to do while it rolls out

The most useful thing to do during a long rollout is resist the urge to react. Here is a working plan.

Record a baseline. Before anything else, capture your current position. Export Search Console performance data for the last 90 days by page and by query, along with clicks, impressions, average position and the countries you care about. Note recent changes such as redesigns, migrations, new content batches and link campaigns.

Annotate the timeline. Mark September 24 in your analytics and reporting tools, and add a note when Google marks the rollout complete.

Compare like with like. Weekday traffic and weekend traffic behave differently for many sites. Compare the days since September 24 with the same weekdays in earlier weeks.

Segment before you conclude. A sitewide traffic drop is rarely uniform. Split the data by page type, by folder, by template and by query group. If the loss is concentrated in one section, such as a batch of AI-assisted pages or a subdirectory of third-party content, that tells you far more than a total.

Do not make sweeping changes. Deleting hundreds of pages, rewriting templates or disavowing links mid-rollout makes it impossible to tell what caused what. If you suspect a policy problem, plan the fix and stage it.

Fix what is clearly broken. If you find hacked content, injected links, broken redirects or a security issue, fix it immediately.

Hold your publishing rhythm. Search Engine Land’s coverage advises sites that are not affected to keep doing what they were doing.

Audit against Google’s spam policies now

Whether or not you see a drop, this is a good week to check yourself against the policies Google points to. Google’s documentation names categories including cloaking, doorway abuse, expired domain abuse, hacked content, hidden text and links, keyword stuffing, link spam, scaled content abuse, scraping, site reputation abuse, sneaky redirects, thin affiliation and user-generated spam.

Three of these tend to matter most for modern content teams.

Scaled content abuse is about producing large volumes of low-value pages in order to manipulate rankings, whether the pages are written by people, generated by AI tools or scrapped. The test is value per page, not the tool used. A large batch of near-duplicate location pages or templated question pages with thin answers is the pattern to look for.

Site reputation abuse covers publishing third-party content on an established site mainly to borrow its ranking strength. Sponsored sections or partner content hubs on an established site are examples.

Link spam covers buying, exchanging or generating links mainly to manipulate rankings. If you have inherited a backlink profile from a past agency, this is the moment to review it critically, not defensively.

If you find something that fits, note what it is, how many pages it affects and what you would do about it. You need not act during the rollout, but be ready to.

What recovery looks like

If you are affected, it helps to set expectations early. Google’s spam update documentation says that fixing problems may help a site improve if its automated systems learn “over a period of months” that the site complies with its policies. It also warns that for link spam, changes may not bring an improvement, because ranking benefits from those links cannot be regained.

So recovery is not a matter of days, and it is not guaranteed. The right frame is a remediation plan measured in months, not a quick reaction to a bad week.

Spam updates also occasionally catch sites that were not breaking the rules. Search Engine Land notes that this should not typically happen but sometimes does. If you believe you were caught unfairly, audit yourself carefully, document your evidence and keep monitoring.

Why this matters beyond classic rankings

Most teams now think about visibility in more places than the ten blue links. Generative engine optimization and answer engine optimization are about being cited and recommended in AI answers, which draw on the wider web and on search results. No one has published data showing how this specific spam update affects citations in AI Overviews, ChatGPT or Perplexity, and it would be a mistake to claim otherwise.

What can be said is narrower and more practical. Pages that lose organic visibility in Google lose a route to being seen and cited, and the qualities that spam policies punish, such as thin, repetitive, mass-produced content, are also poor candidates for being quoted in an AI answer. Strong search engine optimization, generative engine optimization and answer engine optimization all tend to rest on the same base: original, useful pages that answer a real question well. If you are building visibility for AI search, the spam policies are a sensible floor.

If you track AI citations, set that baseline now too, and compare again after Google says the update is complete.

Where this leaves you

The confirmed facts are these. Google started the September 2026 spam update on September 24, it is global, and it may take up to two weeks. It is the fourth spam update this year and the longest announced window. Google has not said what it targets. Early volatility is real, and some analysts report losses among AI-generated and programmatic sites, but that is observation, not confirmation.

The practical response for any search engine optimization team is patience with discipline. Take a baseline, mark the dates, segment your data, audit your own site against the spam policies, fix genuine defects and hold back on big changes until the rollout ends. A two-week update rewards teams that measure carefully, not teams that react fastest.

Frequently Asked Questions

1. When did Google’s September 2026 spam update start, and when will it finish?
Answer: It began on September 24, 2026, at 9:15 a.m. Pacific time. Google says the rollout may take up to two weeks, so the latest expected finish is around October 8. It could end sooner.

2. Why is this spam update considered the longest of 2026?
Answer: Because the announced window of up to two weeks is far longer than the earlier 2026 spam updates, which the dashboard lists at 19 hours and 30 minutes, 2 days and 1 hour, and 2 days and 16 hours. Two weeks is a maximum, not a confirmed actual duration.

3. What does the September 2026 spam update target?
Answer: Google has not said. It applies worldwide to all languages. Some analysts report ranking losses among AI-generated content sites and programmatic content farms, but that is their observation, not a statement from Google.

4. Should I change my site while the update is rolling out?
Answer: Not in a sweeping way. Record a baseline, annotate the dates, and segment your data. Fix clear defects such as hacked content or broken redirects immediately, but avoid large deletions, rewrites or disavows until the rollout is complete.

5. How long does it take to recover from a spam update?
Answer: Google says recovery can take months, because its automated systems must learn over time that a site follows its spam policies. For link spam, ranking benefits from those links may not return at all, even after cleanup.

6. Does the spam update affect visibility in AI answers?
Answer: No data has been published on that yet. Pages that lose Google visibility lose one route to being cited, and low-value mass-produced content is a poor candidate for citation anyway. Measure AI citations before and after the rollout and compare, and do not draw conclusions from one week.

7. How can I check whether my site is at risk?
Answer: Audit against Google’s spam policies, especially scaled content abuse, site reputation abuse and link spam. Then compare your Search Console data by page type and query group against a 90-day baseline.

If you want to know where your brand appears, and where it is missing, across Google and AI answer engines, that is exactly what we look at in a free AI Visibility Audit.

Two separate things happened to Google Search in August 2026, and most of the coverage online is treating them as one event. Between 1 and 6 August, several third-party trackers reported ranking volatility with no confirmation from Google. Then on 18 August, Google rolled out a confirmed Google spam update, its third of the year. If your traffic moved in the first week of the month, that was not this update. If it moved after the 18th, it probably was.

Here is the confirmed timeline, what the update actually targets, and what to check on your own site before you assume the worst.

What actually happened, with dates

1 to 6 August. Search Engine Roundtable and several rank tracking tools reported noticeable fluctuation across search results. Sites saw movement in both directions, some up, some down, with no clear pattern by industry or region. Google’s own Search Status Dashboard showed no confirmed incident during this window. This matters because a lot of site owners who saw a dip in the first week have been blaming a spam update that had not happened yet, when the actual cause was more likely a routine ranking fluctuation, a competitor’s content going live, or something unrelated to Google entirely.

18 August, 9:27 AM Pacific. Google confirmed the launch of the August 2026 update on its Search Status Dashboard. This is the third spam update of the year, following updates in March and June. Each of the three followed a similar pattern, no advance warning, a short dashboard note, and a rollout lasting a few days.

21 August. Google confirmed the rollout was complete, roughly two days and sixteen hours after it started. That is a normal duration for a spam update. Google’s own core updates, which are broader and touch relevance and quality signals across the entire index, tend to run one to two weeks. Spam updates, which target specific manipulative practices rather than reassessing the whole web, tend to run shorter, usually under three days.

Google did not publish a dedicated blog post for this one and did not add any new spam policy categories. The release note on the dashboard was short: the update is live, it is global, it applies to all languages, and it may take a few days to fully roll out. Google Search Central posted near identical language on X and LinkedIn shortly after the dashboard update appeared, which is standard practice for a spam update as opposed to a core update, which usually gets more detailed communication.

What it actually targets

Google has not published a tactic-by-tactic target list for this update, which is normal practice. Google rarely names specific tactics for spam updates, since doing so would hand a roadmap to the people trying to game the system. What we do know, based on the existing spam policies and reporting from Search Engine Roundtable, is this.

The policies that generally apply during a spam update:

Scaled content abuse. Large volumes of pages produced mainly to rank, offering little value to an actual reader, regardless of who or what produced them. This includes location pages that only swap a city name, product pages that only swap a colour or size with no other differentiation, and any page that exists primarily to catch a keyword variant rather than serve a specific reader need.

Cloaking. Showing search engines different content than what a visitor actually sees. This is one of the oldest spam tactics on the list and remains a manual action risk, not just an algorithmic one.

Doorway pages. Near duplicate pages targeting slightly different keyword or location variants, all funnelling to the same destination or offer. A business with fifty pages for fifty nearby towns, each one nearly identical apart from the town name, is a textbook example.

Expired domain abuse. Buying an aged domain with existing authority and backlink history, then repurposing it for unrelated content to borrow that authority. This has become more common as domain marketplaces have made aged domains easier to buy at scale.

Keyword stuffing, hidden text, and sneaky redirects. The long standing basics that have been spam policy violations for over a decade and remain so.

One detail worth knowing if you are trying to diagnose a drop on your own site: Search Engine Roundtable reports that this particular rollout does not appear to specifically target link spam or site reputation abuse. Those policies still apply generally and can still trigger a manual action independently, they just do not seem to be the primary focus of this specific algorithmic update. If your drop looks like it is tied to a sudden loss of backlinks or a third-party content partnership, that is more likely a separate issue than this update.

The part most coverage is skipping

Here is the detail that actually matters if you are thinking about AI content or AI search visibility, and it is why we are covering this on our own blog rather than just linking out to someone else’s summary of the dashboard note.

On 15 May 2026, Google quietly rewrote the opening line of its search spam policies. The updated definition now explicitly includes attempting to manipulate generative AI responses in Search, alongside the long standing language about manipulating traditional rankings. In plain terms, the same spam rules that have always applied to blue links now apply to AI Overviews and AI Mode as well, in the same document, under the same policy framework.

This does not mean the August update specifically targeted AI generated content as a category. Google has been clear, repeatedly, across multiple public statements, that using AI to write is not itself a violation. The actual bar is whether a page adds value for a reader. A page written entirely by a person that exists only to catch a keyword variant fails the same test as a page written entirely by AI for the same reason. Neither authorship method gets a pass, and neither gets singled out either.

What has changed is the scope of what counts as manipulation. If your content strategy has been leaning on producing a high volume of thin pages specifically to get pulled into an AI Overview or cited by ChatGPT, that now falls under the same scaled content abuse policy as producing thin pages purely to rank in traditional blue link results. The target was never AI as a technology. The target has always been volume without value, and that definition has simply been extended to explicitly cover the newer surface where people are now trying to get seen.

Practically, this means a business that has been publishing dozens of near identical FAQ pages purely to try to win a featured snippet or an AI citation is now exposed to the exact same risk as a business that was doing the same thing purely for traditional rankings five years ago. The venue changed. The underlying rule did not.

How to check if this actually affected you

Before assuming a spam update hit your site, check four things in Search Console.

Performance report, filtered to the last 30 days. Look specifically at the period after 18 August. A drop that starts cleanly on or after that date lines up with this update. A drop in the first week of August lines up with the earlier, unconfirmed volatility instead, which may have been unrelated to Google entirely.

Compare clicks against impressions. If impressions held steady but clicks fell, that points toward something outside a spam update, most likely an AI Overview appearing above your result and absorbing the click. If both impressions and clicks dropped together, that is more consistent with an actual ranking change from this update.

Check page level data, not just the site total. Spam updates typically hit specific sections of a site rather than the whole domain uniformly. If the drop is concentrated in one content type, for example a large batch of near identical location or product pages, that is a strong signal worth investigating against the scaled content policy specifically, rather than assuming your whole site has a problem.

Look at the Manual Actions report separately. A search console ranking drop tied to an algorithmic spam update will not show anything here. If you do see an entry in Manual Actions, that is a different and more serious situation, handled by a human reviewer rather than the automated update, and it requires a reconsideration request rather than just a content fix.

A ranking drop on its own is not proof of a manual action or an algorithmic penalty. It can also be entirely normal fluctuation as Google’s systems reassess the wider web following an update, with rankings settling back over the following days as the rollout completes.

What to actually do

If the timing and the pattern point to this update, the fix is the same one Google has been giving for every spam update this year, worded slightly differently each time but consistent in substance. Review whether the affected pages would still be worth publishing if you could not link them from your sitemap and had no other way to drive traffic to them. If the honest answer is no, either rewrite them with genuine, specific value that a competitor’s page does not already offer, or remove them and redirect if there is equity worth preserving.

Google has also said that recovery is not immediate even after a fix is made. Automated systems need time to recrawl and reassess a site, and that process can take weeks rather than days. Do not make a second round of drastic changes a few days after the first if nothing has moved yet, give it the time Google itself says it needs.

Frequently asked questions

1. Did the August 2026 update specifically target AI generated content?
Answer: No. Google has not said this update targets AI content as a category. The relevant policy, scaled content abuse, applies to any high volume, low value content regardless of whether it was written by a person, an AI tool, or a mix of both.

2. My website traffic drop happened in the first week of August. Was that this update?
Answer: Almost certainly not. This update launched on 18 August. Volatility reported between 1 and 6 August was not confirmed by Google on its own Search Status Dashboard, and is more likely attributable to another cause entirely, possibly unrelated to Google at all.

3. How long does a Google spam update take to complete?
Answer: This one took roughly two days and sixteen hours, from 18 to 21 August. Spam updates in 2026 have generally completed faster than core updates, typically under three days from start to finish.

4. Does a ranking drop after this update mean I received a manual penalty?
Answer: Not necessarily. Spam updates are algorithmic, not manual actions. A drop can reflect Google’s systems reassessing your content against existing policy automatically, which is different from a manual action applied by a human reviewer and logged in the Manual Actions report.

5. Is this the same as an AI Overviews policy change?
Answer: Not exactly, but they are connected. Google’s May 2026 policy rewrite extended its spam definition to explicitly cover attempts to manipulate generative AI responses, which means content built purely to be cited in an AI Overview is now held to the same value standard as content built purely to rank in traditional results.

6. Should I stop using AI to write content because of this update?
Answer: No, and Google has said as much directly. The policy has never been about the tool used to produce content. It has always been about whether the resulting page adds genuine value at the volume it is being produced. AI assisted content that is researched, fact checked, and adds something a reader cannot get elsewhere is treated the same as any other well made page.

If you are not sure whether your drop is this update, a stale Search Console habit, or something in your AI visibility specifically, that is exactly what we look at in a free AI Visibility Audit. We check what is actually happening across search and AI platforms rather than guessing from a traffic graph.