Your Google Rankings Dropped in August. Is This the Update? Here Is What the Data Actually Shows.

Google has not confirmed an algorithm update in August 2026. But ranking trackers lit up starting August 1, publisher reports of traffic losses and volatile Discover behaviour have been consistent, and the disruption ran well into August 6. Here is how to figure out what is actually happening to your specific site and what to do about it.

If you woke up in the first week of August and your Search Console showed an impression or traffic drop you could not explain, you are not alone. Multiple ranking tracking tools, including Semrush Sensor, Mozcast, Ahrefs, and SERPmetrics, all flagged elevated volatility starting around August 1, 2026. The signal continued heating up through August 5 and 6, according to Barry Schwartz at Search Engine Roundtable, who has been tracking publisher reports closely.

The challenge is that Google has not confirmed any named update. The most recent confirmed update was the June 2026 spam update. What is happening in August looks different: the volatility pattern is broader and less uniform than a typical named update, and publisher reports are inconsistent in ways that suggest multiple overlapping changes rather than a single targeted update.

What Is Happening in Google Right Now?

Ranking tracker volatility and publisher traffic reports in early August point to something real happening in Google’s systems. The question is what kind of “real” it is. There are three possibilities that fit the observed data.

The first is a broad quality system update affecting how Google evaluates content across large categories of sites. This is the classic “core update” pattern, though Google has not labeled it that way.

The second is a system-specific change to Google Discover, which has its own ranking logic and can move independently of Search rankings. Several publishers reporting traffic drops in early August have traced them to Discover rather than web Search, which would make this a Discover-specific signal change rather than a broad algorithm update.

The third is a cluster of smaller, unlabeled updates that coincidentally hit within a similar timeframe. Google makes hundreds of algorithm updates per year, most unannounced. A period that looks like one big volatile event from outside can sometimes be multiple separate system changes landing close together.

The data from early August suggests all three may be in play for different subsets of sites, which is why publisher reports look so inconsistent. One site’s SERP volatility is not necessarily the same event as another site’s Discover collapse, even if both happened the same week.

Is This an Algorithm Update?

Probably. But not necessarily the kind with a name or a single clear cause. Google’s John Mueller and others on the Search Relations team have consistently framed core updates as broad re-evaluations of how Google’s quality systems assess content, rather than targeted changes to specific signals. The absence of a named update does not mean nothing changed.

What distinguishes this August period from typical background noise is the breadth of the tracking signal. Semrush Sensor hit levels above 8 (their threshold for “high volatility”) for multiple consecutive days starting August 1. That does not happen from background noise alone.

Whether Google eventually labels this update and what it calls it matters less for your immediate strategy than understanding what is happening to your specific site.

What the Tracking Data Shows

Third-party tracking tools measure average SERP changes across large samples of queries. They are useful for confirming that something is happening in Google broadly, but they cannot tell you why your specific site was affected or whether the movement affecting your site is the same movement affecting another site at the same time.

One analysis from an SEO practitioner tracking a portfolio of content sites noted that impressions fell 44% over two weeks in early August while clicks dropped only 11%. That discrepancy is significant. A 44% impression drop with only an 11% click drop suggests the site is ranking for fewer queries in positions that generate impressions but holding its click volume reasonably well for the queries where it does appear. That pattern points toward a ranking contraction rather than a traffic quality decline or a Discover issue.

Compare that to sites reporting flat Search impressions but collapsed Discover traffic. Those sites have a different problem entirely and a different data pattern in Search Console. Conflating the two just because both happened in August leads to the wrong diagnosis and wrong response.

How to Diagnose Your Traffic Drop

Start in Search Console, not GA4

Google Analytics 4 is a second-order measurement tool for organic traffic because it depends on session data that can be affected by consent mode, cookie acceptance, and attribution modelling. Search Console is the direct signal from Google about impressions, clicks, and position. When something changes in organic, Search Console is the more reliable starting point.

Segment by traffic source

In Search Console, separate Search, Discover, and News traffic. These are completely different surfaces and can move independently. If Discover is down but Search is flat, your response is different from if Search is down but Discover is flat. Running the two together obscures which surface is actually causing the overall drop.

Segment by page category

Is the drop happening across your entire site, or concentrated in specific page types? Filter your Search Console data by page URL to see whether the drop is evenly distributed or spiked in a specific section. If it is concentrated in one section, that is a much more specific signal about what changed.

Segment by query type

Filter by query to see which keyword groups are moving. Did you lose impressions for branded queries, informational queries, transactional queries, or navigational queries? Each pattern implies something different. Broad informational query losses during a period of volatility are more consistent with a content quality signal. Transactional query losses that track closely with core update timing suggest commercial quality signals are involved.

Check for technical issues first

Before concluding this is an algorithm signal, rule out the obvious. Check your Core Web Vitals for recent regressions. Check your crawl coverage report for any new 404s or noindex tags that should not be there. Check your sitemap for errors. A technical issue that emerged around the same time as industry-wide volatility can look like an algorithm impact in the data but is actually a separate, fixable problem.

What to Do Right Now

The most important instruction from every credible SEO analyst covering this period is the same: do not make major changes based on one to two weeks of volatile data. Google’s own guidance on core update recovery has consistently said that the right response is to improve overall quality over time, not to make reactive edits to specific pages immediately after a traffic drop.

What you can and should do right now is build the diagnostic picture described above so that when the volatility settles, you understand what actually changed and can make informed decisions. Use a two-week window before committing to any content strategy changes. If the recovery does happen on its own, as sometimes occurs after unconfirmed updates settle, you will have avoided making unnecessary changes that could introduce new problems.

For sites that have been managing WordPress SEO or on-page SEO actively, the priority during a volatility period is protecting what is working, not experimenting. Hold any planned content consolidation, URL changes, or navigation restructuring until the data settles.

Common Mistakes to Avoid

Rewriting pages that would have recovered on their own

Volatility periods produce a lot of false negatives. Pages that look like they lost ranking permanently during the first two weeks sometimes recover fully without any intervention once the update settles. If you rewrite them based on early volatile data, you may be changing pages that were about to recover, introducing a new editing signal that extends the instability rather than resolving it.

Building links aggressively to “recover” rankings

A sudden spike in link acquisition after a ranking drop is the kind of signal that spam quality systems are built to detect. If the cause of the drop was a spam quality signal, building links aggressively in response is more likely to compound the problem than resolve it.

Blaming everything on a single cause

The August 2026 volatility appears to involve multiple overlapping changes. Assuming your traffic drop is caused by one specific thing without doing the diagnostic work to confirm it leads to fixes for the wrong problem.

Pausing SEO investment entirely while waiting for clarity

Some agencies respond to ranking volatility by pausing all SEO activity until the dust settles. This is overcorrecting. Technical health monitoring, content production for genuinely useful pages, and earned link development are all activities that should continue through volatility periods. What should pause is major structural changes and reactive page-level rewrites based on incomplete data.

What This Means Going Forward

The August 2026 volatility is a reminder of something that has been true for years: organic search traffic is not a stable channel. It can move significantly without warning, without a named update, and without a clear cause visible from outside Google’s systems.

The practical response is not to panic and not to ignore it. It is to maintain strong measurement hygiene so you can tell the difference between an algorithmic signal and a measurement artefact, and to build the kind of editorial quality and technical infrastructure that recovers well from algorithm events rather than needing specific post-event intervention.

At Incisive Growth, the approach we take for SEO clients during periods of volatility is to build a diagnostic snapshot immediately, establish a two-week monitoring window before any strategic response, and separate the data by surface, page type, and query group before drawing any conclusions. That process prevents reactive changes that cause more harm than good, and it produces a cleaner picture of what actually needs to change once the volatility settles.

Frequently Asked Questions