Why my website traffic dropped: was it Google or was it you.

What actually happened on 18 August.

Google publishes its updates on a public board, the Search Status Dashboard. This is not a forum rumour or somebody's reading of the tea leaves: it is the official source, with a start date and a duration.

Here is what it records:

• August 2026 spam update: started on 18 August and ran for 2 days and 16 hours, so it finished around the 20th.
• Before that, a spam update in June (24th to 26th) and a core update in May (21 May to 2 June).

Two distinctions almost nobody makes, and they change the reading. First: a spam update is not a core update. A core update reshuffles what Google considers useful for a query, and it moves perfectly honest sites. A spam update targets specific practices that breach the policies. If your site does nothing unusual and it falls during a spam update, the likeliest explanation is not a penalty: someone else went up, or the drop is unrelated.

Second: the dashboard does state the scope, and it pays to read it properly. For the August update, Google writes that it applies globally and to all languages. That describes where the change is deployed, not who loses traffic. Global does not mean every sector or every language moved the same way, and it certainly does not mean your drop came from that update.

The three causes everyone confuses.

When traffic falls, almost everyone jumps straight to the third one. And the first three weeks of work go into fixing what was never broken.

1. Google changed. An update, a change in result formatting, more room for generated answers. Not in your control.
2. The market changed. It is August. Your customers are at the beach. Seasonality explains a great many drops that get blamed on the algorithm.
3. You changed. A migration, a template swap, a noindex left in place, an expired certificate, a plugin that rewrote your URLs. This one is in your control, and it is the most common cause of sharp drops.

The good news is that all three leave a different fingerprint, and you can tell them apart in under an hour.

Four checks, in this order.

1. The exact day, not the week. In Search Console, Performance report, daily chart for the last three months. Find the specific day the line breaks. The shape of the curve is a useful hint, not a law. A technical drop usually falls vertically, overnight, because the cause switches on in an instant. But that is not a law either: a noindex applied across the whole site drops slowly, because Google has to recrawl page by page to find out. An algorithmic one tends to move across the days the rollout lasts, though Google itself warns that swinging sharply up or down early on and then reversing is common. So: the shape points you somewhere, it does not close the diagnosis.

2. Separate impressions from clicks. If impressions hold and clicks fall, you are still appearing but nobody is clicking: usually a change in how the result is displayed, not in position. If impressions fall, you genuinely lost visibility. Two different problems, two different fixes.

3. Cross query with page. Search Console lets you view both dimensions at once. That exposes two things you cannot see otherwise: three pages competing for the same query, and a page in one language answering queries in another.

4. Check whether everyone fell. If your three direct competitors also lost positions on the same day, it was the sector. If you were the only one, look at your site.

What not to do for the next fortnight.

The instinct after a drop is to do things. Almost all of them make the diagnosis harder.

• Do not rewrite half the site at once. Change twenty things together and, if traffic returns, you will not know which one did it, and you will be back here in six months.
• Do not deindex pages in the heat of the moment. I have seen entire sections pulled from the index over a drop that turned out to be seasonal.
• Do not buy links. Especially right after a spam update. That is precisely the behaviour it targets.
• Wait for the rollout to finish. While an update is deploying, positions swing. Google recommends waiting not just for it to finish but a full week afterwards, then comparing that week against one from before it started. Measuring earlier is measuring noise.

Impressions are not visits.

There is a trap I see constantly, and it is worth understanding before you draw any conclusion from any report.

Search Console counts an impression when your page appears in the results page the user actually loads. So an average position of 90 with real impressions does not mean many people see you: it means that on those particular queries someone went that deep, or there were few results. A site can rack up hundreds of monthly impressions at that depth and record zero clicks. That is not a clickthrough problem: at that distance there is no traffic to win.

This matters because it tells you where to act. At average position 90 there is no point tweaking the title or the meta description: nobody reads them. The problem is that Google does not consider that page a serious answer to that query, and that is a content and authority problem, not a cosmetic one.

When it is not Google's fault.

These are the causes I most often find behind a drop the client had blamed on the algorithm:

• A migration without 301 redirects, or with chained redirects.
• A noindex or a Disallow that travelled from staging to production.
• The certificate expiring over a weekend.
• A template change that ate the headings or left the site three times slower on mobile.
• The crawl file regenerated by a plugin and pointing at URLs that no longer exist.

None of these appear on Google's dashboard. All of them can be found in an afternoon.

Frequently asked questions.

How do I know if the August 2026 spam update hit me?

Look at the daily chart in Search Console and find the exact day the line breaks. The update started on 18 August and ran for two days and sixteen hours. If your drop starts before the 18th or after the 21st, it was not that update. And if your site breaches none of Google's policies, a spam update rarely penalises you: what usually happens is that someone else moved up.

How long does a site take to recover after a Google update?

If it was a core update and the issue is content quality, recovery usually arrives with the next update, and months can pass between them. If it was a technical problem on your side, recovery can take days once it is fixed and reindexed. That is exactly why telling the two apart matters before you start work.

What is the difference between a core update and a spam update?

A core update broadly revises what Google considers the best answer to a query, and it can move sites that have done nothing wrong. A spam update targets specific practices that breach the policies, such as buying links or publishing mass-generated content with no value. If you do none of that, a spam update is almost never your problem.

I have plenty of impressions and no clicks. What does that mean?

Check average position first. If it is above 30, you do not have a click problem: nobody is seeing you, because you appear on result pages almost no user reaches. Tweaking titles there changes nothing. If your position is between 1 and 10 and you have no clicks, then yes, look at the title, the description and what surrounds your result.