Why did organic traffic drop if rankings look the same?

Average position can hold steady while clicks fall. Common reasons are fewer searches for the query (check impressions in Search Console), a new search feature such as an AI Overview or a map pack pushing results lower on the page, or a title and description that now earn fewer clicks. Compare impressions and CTR, not only position.

How recent is Search Console data when I'm diagnosing a drop?

Performance data usually runs about two days behind, so the last day or two in the chart can look lower than it will end up. Avoid reporting a drop based only on the most recent days, and use the 24 hours view when you need the freshest numbers available.

Should I send the client screenshots from Search Console?

One chart with the date range marked is helpful. Several screenshots of reports the client has never opened tend to create more questions. If the client has their own Search Console access, give them the report name and the filter you used so they can see the same view.

How long does recovery take after fixing a noindex or robots.txt mistake?

There is no fixed timeline. Google has to recrawl the affected URLs, which can take days for important pages and longer for deep ones. Requesting indexing in the URL Inspection tool for key pages and resubmitting the sitemap can help, but set expectations in weeks rather than days.

What if the client made the change themselves?

Treat it the same way as a developer change: describe what changed, when, and what the fix is. Many CMS settings, like visibility toggles or SEO plugin options, are easy to switch without realising the effect, so explaining how the setting works is more useful than pointing out who clicked it.

← Back to the blog

How to Explain an SEO Traffic Drop to a Client

To explain an SEO traffic drop to a client, first work out which kind of drop it is: broken tracking, a Google update, a change on the site, seasonality, or a manual action. Then tell the client early, in plain words, with what you know, what you don't, and when they'll hear from you next.

The order matters because the checks take different amounts of time and some of them rule out the others. Twenty minutes of triage before you write anything usually saves a second, awkward email correcting the first one.

Triage for an SEO traffic drop, in the order worth doing it

1. Is traffic down, or is measurement down?

Open GA4 and Search Console side by side for the same date range. Search Console clicks come from Google's own logs and don't depend on anything installed on the site. GA4 organic sessions depend on the tag firing and, in many regions, on the visitor accepting cookies.

If Search Console clicks are flat and GA4 organic sessions fell off a cliff on a specific day, the problem is almost certainly tracking. Check whether the GA4 tag is still on the page (view source, or use Tag Assistant), whether GTM was republished, and whether the cookie banner or consent setup changed around that date. Our guide on how to check GA4 is installed walks through the checks.

If both lines dropped together, the drop is real. Keep going.

2. Did Google release an update?

The Google Search Status Dashboard lists ranking updates such as core updates and spam updates with their start and end dates. Core updates often take a couple of weeks to roll out, so compare the shape of the decline with the rollout window rather than a single day.

A match in dates is a lead, not a diagnosis. Sites change during update windows too, which is why the next step still matters.

3. Did something change on the site?

This is where most sudden drops live, and it's the one clients least expect. Check, roughly in this order:

a noindex in the meta robots tag or the X-Robots-Tag header on important templates
new Disallow rules in robots.txt (Search Console has a robots.txt report under Settings)
canonicals that now point to another URL, the homepage, or a staging domain
redirects added during a redesign or URL change, especially chains and redirects to irrelevant pages
URLs missing from the sitemap, or the sitemap returning an error in the Sitemaps report

In Search Console, the Pages report (under Indexing) shows reasons like "Excluded by 'noindex' tag" and "Blocked by robots.txt", with a chart of when the counts changed. The URL Inspection tool confirms what Google saw on a single URL and when it last crawled it. If you need a deeper walk through those reasons, see how to fix index coverage errors in Search Console.

Ask the client or their developer a direct question too: was anything deployed, migrated or updated in the two weeks before the drop? Plugin and theme updates count.

4. Is it seasonal?

In the Performance report, use the date filter's Compare tab and pick a year over year comparison, for example the last 3 months against the same period last year. Search Console keeps 16 months of data, so this works for any site that has been verified for more than a year. A retailer losing traffic in January, or a school supplier in October, may simply be looking at last year's pattern again. Google Trends helps when the site's own history is too short.

5. Is there a manual action?

Rare, but quick to rule out. Open Security & Manual Actions, then Manual actions. If the report says "No issues detected", you can say so with confidence. While you're there, check the Security issues report as well.

How to tell the client about the drop

Send the first message the day you confirm the drop is real, even if the triage isn't finished. A client who finds the drop in their own dashboard and then learns you saw it a week earlier will remember the week more than the cause.

Keep the first message short. State the size of the drop in clicks from Search Console (not a percentage alone), the date it started, what you've already ruled out, and the date of your next update.

When the cause is a change their developer made, describe the change and its date, not the person. "On 3 March, a release added a noindex tag to the product pages" gives the client the facts and gives the developer a clear fix. Include the affected URLs so nobody has to reproduce your work. Blame tends to slow the fix down, because the first reply becomes a defence.

When you don't know the cause yet, say that plainly and list what you've checked. "We don't know yet" backed by five ruled out causes reads as competence. A confident guess that turns out wrong costs more trust than the drop did.

Here's a template you can adapt:

Subject: Organic traffic drop on [site], what we know so far

Hi [name],

We've spotted a drop in organic search traffic on [site] starting around [date]. Clicks from Google went from about [X] per week to [Y], based on Search Console.

What we've checked so far:

Tracking is working (Search Console and Google Analytics show the same drop)

[No manual action in Search Console / A Google update ran from [date] to [date]]

[Result of the site change checks, e.g. "On [date], a noindex tag was added to [section]; affected URLs attached"]

What we're doing next: [action]. If the cause is a site change, we'd like [developer/team] to [specific fix] by [date].

We'll send the next update on [date], or sooner if we find the cause.

[Your name]

Delete the lines that don't apply rather than leaving vague placeholders in.

Preventing the "you tell me first" conversation

Look back at the triage list. Steps 2, 4 and 5 are things nobody can prevent. Steps 1 and 3 are changes on the site, and they have a date. The traffic drop shows up weeks later, but the noindex, the robots.txt edit or the missing GA4 tag existed on day one.

So the fix is to watch the causes rather than the symptom. You can do it by hand with a weekly checklist for a few sites. Past that, it helps to have something compare each site against yesterday and tell you what changed. Our guides on catching a noindex in production and robots.txt change alerts cover the two most damaging cases.

Deltio does this once a day. It reads each site's sitemap and pages, compares them with the previous check, and sends a Slack and email alert for that site when it finds a new noindex, a robots.txt change, a moved canonical, a changed title, meta description or H1, URLs leaving the sitemap, a missing GA4, GTM or Meta Pixel tag, or a changed cookie consent setup. It also covers uptime, SSL and domain expiry, and maintenance pages left live. Each site keeps a change history, which is useful in step 3: you can see what changed on which date instead of asking the developer to remember.

It won't tell you about rankings, traffic or Google updates; Deltio doesn't track those, so Search Console stays your source for the drop itself.

If you'd like the change history in place before the next drop, there's a 14 day free trial.

Frequently asked questions

Why did organic traffic drop if rankings look the same?: Average position can hold steady while clicks fall. Common reasons are fewer searches for the query (check impressions in Search Console), a new search feature such as an AI Overview or a map pack pushing results lower on the page, or a title and description that now earn fewer clicks. Compare impressions and CTR, not only position.
How recent is Search Console data when I'm diagnosing a drop?: Performance data usually runs about two days behind, so the last day or two in the chart can look lower than it will end up. Avoid reporting a drop based only on the most recent days, and use the 24 hours view when you need the freshest numbers available.
Should I send the client screenshots from Search Console?: One chart with the date range marked is helpful. Several screenshots of reports the client has never opened tend to create more questions. If the client has their own Search Console access, give them the report name and the filter you used so they can see the same view.
How long does recovery take after fixing a noindex or robots.txt mistake?: There is no fixed timeline. Google has to recrawl the affected URLs, which can take days for important pages and longer for deep ones. Requesting indexing in the URL Inspection tool for key pages and resubmitting the sitemap can help, but set expectations in weeks rather than days.
What if the client made the change themselves?: Treat it the same way as a developer change: describe what changed, when, and what the fix is. Many CMS settings, like visibility toggles or SEO plugin options, are easy to switch without realising the effect, so explaining how the setting works is more useful than pointing out who clicked it.