The Google algorithm update lands again: how to actually check if it hit you
Every client with a wobble in their rankings this week is asking the same question. The honest answer takes twenty minutes in Search Console, not a content rewrite.
What the Google algorithm update actually did on 18 August#
spam update Google has shipped in 2026, and this one arrived with a status-dashboard note instead of a blog post.
A fox does not sprint at every rustle in the hedgerow. It stops, reads the wind, and decides whether the sound is a threat or a thrush. That patient pause is exactly what most marketing teams skipped on 18 August 2026, the day a fresh Google algorithm update went out and every client with a wobbly ranking chart reached for the panic button at once.
Here is what actually happened, stated plainly. Google's own Google Search Status Dashboard logged the release starting at 9:27am US Pacific on 18 August 2026, describing it as applying "globally and to all languages," with the rollout expected to take a few days to complete. Within the hour, Google Search Central's own account on X confirmed the same news in one line: "Today we released the August 2026 spam update. We'll update our ranking release history page when the rollout is complete." That sentence, brief as it is, is the entire official record of this Google algorithm update. There was no keynote, no case study, no glossy explainer.
A spam update is not the same animal as a core update#
Marketers use "google algorithm update" as a catch-all, and that habit is the first thing worth unpicking, because a spam update and a core update police different territory. Google's ranking systems guide explains that its automated ranking systems weigh hundreds of billions of pages against "many factors and signals," and that spam-specific systems sit alongside, not inside, the broad relevance systems a core update retunes. A core update reshuffles what counts as helpful. A spam update enforces rules that were already written down, chiefly the conduct described in Google's own spam policies documentation, last revised 15 May 2026.
That distinction matters for anyone running a diagnosis this week, because the fix for each is nearly opposite. A core update calls for better content. A Google spam update calls for the removal of a specific, nameable practice: a cloaked page, a doorway, a scraped template stitched together at scale. Confuse the two and you will spend a fortnight rewriting paragraphs that were never the problem.
No blog post is itself a data point#
Every spam update since 2024 has shipped with some form of Google Search Central write-up. This one has not, at least not by the time of writing, and Google's own documentation changelog shows nothing dated 18 August, only entries running back through July.
Search Engine Journal covered the rollout the same day it began, noting that this is the third named spam update of 2026, after releases in March and June, and that Google "provided only a brief release note via the Search Status Dashboard but did not publish an accompanying blog post." We will say plainly what we do not know about this Google algorithm update: whether the silence means a narrower scope, a policy Google would rather not spell out in public, or simply a quieter news week at Mountain View. Anyone claiming certainty on that point is guessing, and the guess is not worth acting on.
What is worth acting on is the pattern underneath. March 2026's spam update finished in roughly nineteen and a half hours, the fastest confirmed rollout on record, and June's took a little over two days. This Google algorithm update, by contrast, is still marked as an active service disruption on the status dashboard days after it started, which is itself useful evidence: a slow, still-rolling update is a bad week to make any drastic content decision, because the page you rank check today may sit in a different bucket tomorrow.
The violation categories a Google spam update actually polices#
Read Google's spam policy the way a fox reads a boundary hedge: not as decoration, but as the line that decides which side of the field you are standing on. The canonical spam policies page names sixteen specific violation categories, and a Google spam update is Google's automated enforcement of exactly that list, nothing broader and nothing vaguer. Cloaking, doorway abuse, scaled content abuse, site reputation abuse, hidden text, link spam, thin affiliation and a dozen siblings each have a plain, checkable definition. If your site does none of the sixteen, this update, whatever else it changes, is not aimed at you.
Site reputation abuse keeps climbing the list, and it is the easiest to miss#
Site reputation abuse is the quiet villain of this list, because it does not require you to have done anything wrong on your own domain. It covers third-party content hosted on your site's authority purely to borrow that authority, a sponsored section, an outsourced coupon page, a syndicated feed with no editorial oversight.
We at folkfox have walked more than one otherwise-clean client through exactly this pattern: strong core content, a bolted-on partner section, and a ranking dip that looked like a core-update casualty until the audit found the real culprit sitting two folders deep. Read the spam policies documentation again with that lens, and the fix for that kind of Google algorithm update is usually a firewall between sections, not a fresh round of blog posts.
Why not every ranking dip is this Google algorithm update#
August has already delivered one round of confused diagnosis this year, and it happened on Discover, not classic search. Google ran a dedicated Discover core update through February 2026 aimed at clickbait and thin templated posts, and New/Or Media's coverage documents a second, separate wave of Discover volatility that began around 1 August, unconfirmed by Google as any named update at all.
One publisher watched Discover clicks fall from ten million a month to under one million, while others on the identical network grew over the same stretch. The lesson travels straight across to this Google spam update: uneven impact across a market is not proof of a cause, it is proof that several forces are moving the water at once, and only one of them has your name on it.
Rewrite first, ask questions never
Traffic dropped, so we rewrote the top ten pages, changed the meta descriptions, and hoped. Three weeks later nobody can say whether anything worked, because nothing was measured before the edit.
Pull the data, then decide
Traffic dropped, so we pulled Search Console impressions and position for the affected pages, checked the Manual Actions report, and matched the pattern against the named violation categories before touching a single sentence.
The second column is duller to describe and considerably cheaper to run, because it spends an afternoon instead of a quarter, and it tells you which pages, if any, are actually implicated before a single word gets rewritten.
Google launched a new spam update today. Historically I haven't paid too much attention to spam updates, but they are worth watching closely now. I've seen SpamBrain increasingly impacting good sites doing things they don't realise Google considers manipulation. If you see drops that aren't seasonal, it usually means the AI identified patterns consistent with manipulation.
That practitioner note is worth sitting with, because it names the real risk of this Google algorithm update precisely: SpamBrain does not only catch sites that meant to cheat, it catches sites that built a link pattern or a content pipeline without registering that Google would read it as manipulation. Good intent is not a defence a machine-learning classifier can see. The only defence is knowing, category by category, what the classifier is trained to flag, and checking your own site against that list honestly rather than defensively. That is the same discipline folkfox brings to every SEO and GEO engagement: evidence before edits, always in that order.
How to check whether the Google spam update actually hit you#
This is the part worth printing out. None of it requires guesswork, and none of it requires touching a page before you know whether that page did anything wrong.
Start with the Performance report in Search Console, and read impressions, clicks and average position together rather than any one of them alone. If impressions and position have held steady while clicks fell, you are looking at a click-through problem, an AI Overview or a competitor's new snippet, not a Google spam update. If position itself has fallen on pages that were stable for months, that is the pattern worth investigating further.
Next, open the Manual Actions report and check for anything logged against the site. This step alone resolves half of the false alarms folkfox sees: a manual action is issued by a human reviewer, is visible by name in that exact report, and is not the same mechanism as an automated spam update at all. No entry there means whatever moved your rankings, it was not a human reviewer acting on a complaint.
Google's own guide to debugging traffic drops lays out the fuller diagnostic sequence: separate algorithmic movement from technical breakage (crawl errors, a misplaced noindex tag) and from ordinary seasonality before assuming an update did anything at all. Sixteen months of Performance data, compared against the same weeks a year earlier, tells you in ten minutes whether a dip is a Google core update 2026 story or a story about last August looking exactly the same.
Read that shape the way you would read a fox's tracks after rain: the clean trail wanders but always returns to the same hedgerow, while the trail that strays into someone else's warren does not find its way back on its own. A dip that recovers within two weeks is volatility. A dip that keeps sliding after the update window closes is the pattern worth a proper audit, not a rewrite, and that is the entire diagnostic a Google algorithm update deserves.
What to actually do while the Google core update 2026 rollout finishes#
Google's own status page says this rollout "may take a few days to complete," and March's version of this same Google algorithm update took under a day while June's took just over two. Nobody, including Google, can currently tell you which of those this one resembles, so the sane move is to keep collecting evidence rather than keep making changes.
A ranking chart cannot tell you why it moved. Search Console, read properly, can.
Build a short watchlist instead of a rewrite plan: the pages that moved, the date each one moved, whether the movement matches the 18 August window or predates it, and whether the page in question touches any of the sixteen named categories even loosely. Most of a marketing team's twenty highest-value pages will clear that check in an afternoon, which frees the remaining hours for the pages that genuinely need attention rather than the ones panic pointed at first.
If a pattern does emerge, chase down specific, checkable evidence, not adjectives. "We think our backlink profile looks unnatural" is not a finding, it is a hunch; a dated list of the exact links, the anchor text and the acquisition method is a finding, and it is the only kind Google's own spam policies rewards with an actual fix. The same discipline is exactly what folkfox brings to content marketing work more broadly, whether the question is a Google spam update this week or an AI Overview eating clicks next month, covered at greater length in our piece on AI Overviews SEO and SEO vs GEO.
The fox that survives a hard winter is not the boldest one in the thicket, it is the one that reads the ground before it moves. Treat this Google spam update 2026 rollout the same way: watch the trail, gather the tracks, and only then decide whether to change course. Most sites reading this will finish the rollout exactly where they started, and that, quietly, is the best possible outcome.
Frequently asked questions#
What is the current status of the Google spam update?
Google logged the rollout as starting 9:27am US Pacific on 18 August 2026 on its Search Status Dashboard, describing it as an active service disruption applying globally, in all languages. As of writing it is still marked ongoing, with Google saying the rollout may take a few days to complete.
What is the August 2026 Google algorithm update?
This Google algorithm update is a spam update, the third Google has shipped in 2026, that re-runs its automated spam-detection systems, including SpamBrain, against the sixteen violation categories in Google's spam policies. It is narrower than a broad core update, which retunes general relevance rather than enforcing named rules. Google logged this one on its Search Status Dashboard at 9:27am US Pacific on 18 August 2026 rather than announcing it in a blog post, which is why it surfaced as a status-page entry rather than a headline. The practical difference matters for site owners: a spam update asks whether your pages break a specific published rule, such as scaled content abuse or site reputation abuse, while a core update asks whether they still deserve the visibility they already had. The recovery paths differ accordingly.
How do I know if a Google spam update hit my site?
Check Search Console's Performance report first: if impressions and position held steady while clicks fell, the update likely is not the cause. Then check the Manual Actions report for anything logged against your site, since a manual action and an algorithmic spam update are different mechanisms entirely. Compare the dates properly: the rollout began at 9:27am US Pacific on 18 August 2026, so a decline that started before that timestamp belongs to something else. Rollouts also take time to settle and the range is wide. March 2026's spam update finished in roughly nineteen and a half hours, the fastest on record, while June's took just over two days, so a reading taken mid-rollout can reverse itself. If the timing does line up, work through Google's sixteen named spam policy categories rather than rewriting content on instinct.
Is the August 2026 spam update the same as a core update?
No. A core update changes how Google judges general page quality and relevance across the whole index. A spam update enforces specific, named policy violations such as cloaking, doorway pages or scaled content abuse. The fixes for each are different, so the diagnosis has to come first.
How long does a Google core update 2026 rollout usually take?
It varies. March 2026's spam update finished in roughly nineteen and a half hours, the fastest on record, while June's took just over two days. The August 2026 rollout was still active on Google's status dashboard several days after it began, with no confirmed completion date yet.
What are the main Google spam policy violation categories?
Google's spam policies name sixteen categories, including cloaking, doorway abuse, scaled content abuse, site reputation abuse, hidden text, link spam, thin affiliation, scraping and sneaky redirects. Any content that falls outside all sixteen is not the kind of practice a spam update targets.
Read more on this topic#
SEO vs GEO: why your best pages miss AI citations entirely
A different failure mode entirely: pages that rank cleanly but never get quoted. Useful once this update's dust settles.
Read the pieceAi Overviews Seo: Five Proven Moves for the 43% Shift
The click-share problem sitting next to this one: what to do once impressions hold but clicks keep falling.
Read the pieceThe opt-out button that quietly removes you from the news
Another Google mechanism worth understanding before you touch it: what publishers actually give up by opting out.
Read the pieceSEO and GEO services
The diagnostic-first discipline this piece describes, built into an ongoing SEO and GEO engagement.
See the service
Ready to separate a real penalty from a bad week?
We turn Google algorithm update anxiety into an evidence-based diagnosis, then build the content and technical fixes that actually move the needle, not the ones panic pointed at first.