Article · Client communication
When rankings drop: how to investigate it and explain it to your client
A fixed sequence turns a stressful traffic drop into a short, factual email instead of a guess. Here is the order we work in, with templates to adapt.
Before you investigate: send a short holding reply
When a client spots a drop before you do, reply the same working day: confirm you have seen it, say what you will check, and give a time for the full answer. Do not name a cause yet: every early guess is one you may have to take back.
Subject: Re: [CLIENT'S SUBJECT LINE]
Hi [FIRST NAME], thanks for flagging this. I'm looking into it today. I'll start with Google's own reports for your site, then check whether anything changed on the site or in Google Search around those dates.
You'll have a written summary from me by [DAY AND TIME]: what we know, what we don't know yet, and what happens next.
[YOUR NAME]
The diagnostic sequence
Google's Search Central guide to debugging traffic drops lists the usual causes: ranking updates, technical problems, security problems, spam problems (including manual actions), seasonality and shifting interest, and site moves. The sequence below works through them, quick and urgent checks first. You need access to the client's Search Console property; if you don't have it, see our Search Console reporting setup.
-
Confirm the drop is in the data, not just in one search
Clients often notice a drop by searching for themselves. Google's Performance report help says results vary with location, device, time and history, so one manual search proves little. Open the Performance report and note the dates. Two things can distort the chart: the newest data is preliminary (a dotted line) and can still change, and Google's Data anomalies page lists, by report and date, known logging errors and other events that affect the data, including some real changes in Search. If an entry covers your dates, say so first.
-
Rule out the urgent problems: Manual actions and Security issues
If either report lists something, the plan changes. A manual action means a human reviewer at Google found pages that break its spam policies; affected pages can rank lower or be left out of results. The Security issues report covers hacked content, malware or unwanted software, and social engineering; affected pages can carry a warning in search results or in the browser. A green check mark in a report means nothing is listed there.
-
Read the shape of the drop
Look at clicks and impressions together. Per Google's guide, if both fell, keep working through this list; if impressions held but clicks fell, the cause may be the page title and snippet, or more attractive results from other sites. Use the Search type filter to see whether the loss is in web, image, video or news results.
-
Check for seasonality and changing demand
Set the date filter to Last 16 months and look for the same dip a year earlier. Then compare the last three months with the same period a year before. Look up the top queries that lost clicks in Google Trends: if interest fell across the web, the drop may reflect lower demand rather than lost ground.
-
Find where the loss sits
With a date comparison applied, the tables gain a difference column. In the Pages tab, sort by Clicks Difference, then check the Queries, Countries and Devices tabs. Is the loss site-wide, in one section or template, or on one important page?
-
Check technical causes
For a site-wide drop, open the Page indexing report. Some pages are not indexed on purpose (duplicates, redirects), so look for a sharp fall in indexed pages or a jump in reasons such as noindex, robots.txt blocking or server (5xx) errors, and check the Crawl stats report for matching spikes. For a handful of pages, use the URL Inspection tool. Then ask the client: did anything change on the site around those dates, such as a redesign, new URLs or a hosting change? When URLs change, Google says rankings can fluctuate while it recrawls and reindexes the site, and on a medium-sized site it can take a few weeks just for Google to notice the move; larger sites can take longer. For a redesign or site move, see the website redesign SEO checklist.
-
Match the dates against Google's ranking updates
Last, open the Google Search Status Dashboard. Its Ranking history lists updates with a start date and a duration. It covers widespread issues and updates, not problems on a single site, so an empty dashboard doesn't clear your site, and a listed update doesn't prove it caused your drop.
From finding to explanation
This table ties each explanation to what Google's documentation supports. If your finding is not in it, say you don't know yet, plus what you will watch and when.
| What you found | What Google's documentation says | What to tell the client |
|---|---|---|
| A Data anomalies entry covers the dates | Most entries are logging errors that affect the data only; some record a real change in Search, such as a result type that stopped appearing | Google has noted [a logging error / a change in Search] for those dates; here is what it means for your numbers and what happened to leads from search |
| A manual action is listed | Fix every affected page, then send a reconsideration request; most reviews take several days or weeks | What the action covers, what we'll fix, and when we'll request a review. No date for a return |
| A security issue is listed | Fix every issue on every affected page, then use Request Review; reviews can take days or weeks | What was found, who must act (host, developer, us), and the next update date |
| Impressions steady, clicks down | Titles and snippets may be less appealing, or other sites show richer results | Visibility held; fewer people chose the listing. We'll test titles and descriptions on the affected pages |
| Same dip last year, or lower interest in Trends | Seasonality and changing interest reduce traffic for some queries | Demand fell, and here is the same period last year for comparison |
| Indexing or crawl errors jumped | Technical problems can stop Google crawling, indexing or showing pages | What broke, what we fixed, and that we've asked Google to validate the fix, which typically takes up to about two weeks |
| Dates match a listed core update, small position drop | Small drops are normal and can reverse; avoid big changes to pages that perform well | We'll monitor it and make no large changes |
| Dates match a listed core update, large lasting drop | Assess the site against Google's helpful-content questions; changes can take days to months to show | We'll reassess the affected pages; the timeline is not in our control |
If the dates line up with a core update
Google describes core updates as broad changes it makes several times a year, not aimed at specific sites. Its advice, in short:
- Confirm the update has finished rolling out. The dashboard shows the dates.
- Wait at least one full week after it finishes, then compare that week with the week before the rollout began.
- A small position drop calls for no drastic action. For a large, lasting drop, review the site against Google's self-assessment questions on helpful, people-first content, ideally with people who don't work on the site.
- Skip quick fixes based on rumors. Real improvements can take days to months to show, and Google says changes may have no noticeable effect.
If the matching entry is a spam update, Google's advice is different: review the site against its spam policies. Any improvement can take months, and after a link spam update, changes may not help.
When we checked on 29 October 2026, the dashboard's latest core update was the May 2026 core update, and its latest entry was the September 2026 spam update. Check the list each time.
The full client email
Send this when you promised, even if part of the answer is unknown. Replace the brackets and delete any line you can't back with a report.
Subject: Search traffic since [START DATE]: what we found and next steps
Hi [FIRST NAME],
What we saw. Clicks from Google Search to [SITE] went from [NUMBER] in [PERIOD A] to [NUMBER] in [PERIOD B]. Impressions [fell by a similar amount / held steady] over the same period.
What we checked. Google's Manual actions and Security issues reports ([both clear / ISSUE FOUND]), the Page indexing report, the same period last year, search interest for your main terms, and Google's list of ranking updates.
What we found. [ONE OR TWO SENTENCES, EACH TIED TO A REPORT: FOR EXAMPLE, WHICH PAGES LOST THE CLICKS AND WHAT THE REPORT SHOWS]
What we don't know yet. [OPEN QUESTION, OR DELETE THIS LINE]
Leads and sales. [WHAT HAPPENED TO LEADS, CALLS OR SALES FROM SEARCH OVER THE SAME PERIOD, IF YOU TRACK THEM]
What we're doing. [ACTION 1] and [ACTION 2]. We'll review the numbers again on [DATE] and write to you then.
What we need from you. [ACCESS, APPROVAL OR INFORMATION, OR: Nothing for now.]
[YOUR NAME]
For a drop at month end, see the bad-month version of our monthly report email template. For the leads line, see the Organic Search row in GA4.
What not to say
Two rules cover nearly everything: describe what happened rather than who caused it, and promise actions and update dates, never results.
| Avoid | Say instead |
|---|---|
| Google penalized us (when the Manual actions report is clear) | Google's Manual actions report shows no action against the site |
| It's the algorithm update | The drop started during a Google ranking update. That makes it a likely factor, not a confirmed cause |
| Your developer broke the site | A change on [DATE] added a noindex tag to [PAGES]. It's fixed, and we've asked Google to recheck them |
| It'll be back in two weeks | Google says changes can take days to months to show. We'll report again on [DATE] |
| Don't worry, this is normal (before you have checked) | Small movements are common. Here is what I checked to confirm this is one |
| We need to rewrite the whole site (after a small drop) | We're leaving pages that still perform well as they are |
| Rankings don't really matter | Here is what happened to leads from search over the same period |
If you also track rankings daily
Search Console reports average position for searches people actually made (see Do it free first). A daily rank tracker keeps a day-by-day record for a fixed keyword list, which helps you date a movement against the dashboard. Before quoting a tracker to a client, check that its location and device match the client's market.
As listed on 28 October 2026, Semrush's Position Tracking help page says a campaign's original location and device type can't be changed once it is set up, and its SEO plan lists 500 keywords tracked daily across five monitored websites. Part A of our walkthrough shows a tracking and report setup.
Make the next drop less of a surprise
- Agree at the start how you'll handle drops, and get Search Console access on day one: see the client onboarding checklist.
- Report on a few agreed measures tied to the business, so a ranking dip is read in context: see SEO KPIs for clients and the five questions.
- Track a keyword set you can explain: see how many keywords to track.
- Show year-over-year context every month, so seasonal dips are expected. The report outline has a place for it.
- Subscribe to the Search Status Dashboard's RSS feed to hear about ranking updates before your clients do.
- Keep a dated change log for each client site (releases, redesigns, migrations, hosting changes).
Sources
- Causes of traffic drops, Performance report checks, 16-month view, comparisons, Clicks Difference, Google Trends, Page indexing, Crawl stats, URL Inspection and site moves: Google Search Central, Debugging drops in Google Search traffic
- Core updates, rollout dates, the one-week wait, quick fixes and recovery time: Google Search Central, Google Search's core updates and your website
- Self-assessment questions: Google Search Central, Creating helpful, reliable, people-first content
- Search Status Dashboard: status.search.google.com; ranking history: Ranking incident history
- What the dashboard covers, and its RSS feed: Google Search Central, Google Search Status Dashboard FAQ
- Manual actions: Search Console Help, Manual actions report
- Security issues: Search Console Help, Security issues report
- Page indexing and fix validation: Search Console Help, Page indexing report
- Performance report metrics, preliminary data and personalized results: Search Console Help, Performance report (Search results)
- Comparing date ranges and the Difference column: Search Console Help, Advanced filtering and comparison
- Logging errors and other events that affect report data: Search Console Help, Data anomalies in Search Console
- Spam updates: Google Search Central, Google Search spam updates
- Semrush Position Tracking location and device: Semrush KB 548, Configuring Position Tracking
- Semrush SEO plan limits: semrush.com/pricing/seo-ai-search