Google has not confirmed an August 2026 update. A lot of pages say otherwise.

If your traffic moved in the first half of August, you have probably already read that an "August 2026 core update" or an "August 2026 spam update" caused it.

Google's own log does not record one.

What the primary record says

Google publishes a ranking update history on its Search Status Dashboard. It is the authoritative list: every core update, spam update, and named ranking change, with start and end dates.

Checked on 2026-08-14, the most recent entry is the June 2026 spam update, 24–26 June 2026. There is nothing after it. No August entry of any kind.

Search Status Dashboard — ranking update history

That is the whole of the confirmed record. Anything dated August 2026 is coming from somewhere else.

What is actually happening

Something is moving. Search Engine Roundtable, which tracks ranking volatility daily using third-party trackers and webmaster chatter, reported spikes on 1–3 August, 5–6 August, and again on 12–13 August.

Volatility reports are evidence that rankings moved. They are not evidence of why. Google runs continuous, unnamed adjustments alongside the named updates, and third-party trackers cannot distinguish one from the other.

So the honest description is: rankings moved, and the cause is unattributed.

What is being claimed

Here is one example, and it is representative rather than unusual.

A guide published on 2026-08-11 lists this row in a table of Google spam updates:

August 2026 Spam Update | 08/01/2026 | 08/12/2026* | Thin-content and cloaking signals | Google Search Status Dashboard

Two things are worth noticing.

The official reference column names the Search Status Dashboard — the page above, which contains no such entry. The citation is checkable, and it does not check out.

The end date is 08/12/2026 on a page published 08/11/2026. The update is recorded as finishing the day after the article about it appeared.

The page, as checked on 2026-08-14

We are not claiming intent. A generated summary that blends real past updates with plausible-looking new rows produces exactly this artefact. The point is that the error is visible from the primary source in under a minute, and it is propagating anyway.

Why this costs publishers money

Two mistakes follow from a phantom update, and they point in opposite directions.

Rebuilding a site to counter something that was never announced. The row above attributes the phantom update to "thin-content and cloaking signals." A publisher who believes it may start pruning pages, rewriting titles, or de-indexing sections in response to a target that does not exist. Those changes carry real risk and take real weeks.

Dismissing the volatility because the update was fake. The traffic movement is separately reported and does not depend on the phantom update being real. If your numbers changed, they changed.

The gap between those two is where the useful work sits.

What to do instead

Check the dashboard first. Bookmark the ranking history page. It takes fifteen seconds and settles the question of whether a named update exists.
Measure your own movement before reading anyone's diagnosis. In Search Console, compare the last 14 days against the previous 14 by page and by query. Volatility that shows up everywhere in the industry but not in your property is not your problem.
Do not make structural changes during an unattributed swing. If you change five things during a period you cannot attribute, you will not learn which one mattered. Wait for the record, or change one thing and measure it.
Write down what you observed, with dates. When Google does confirm something, your own dated notes are the only way to connect it to your site.

What we do not know

We do not know what caused the volatility. We have not run a controlled test on our own properties, and we are not claiming one. It is entirely possible that Google later confirms an August 2026 update and backdates it in the history — that has happened before with rollouts announced after they began.

If that happens, the record will change and this page will be updated with the date it changed. The claim here is narrow and it is about today: as of 2026-08-14, no August 2026 update appears in Google's published history.

Check it yourself

All three were checked on 2026-08-14.