# How to Explain a Ranking Drop: Narrowing Down the Cause Without Overpromising

> When your boss or client asks why rankings dropped, what do you say? Sort possible causes into confirmed, possible and ruled out, then report with data instead of guesses. A beginner's guide grounded in Google's documentation.

| Field | Value |
|-------|-------|
| Published | 2026-10-13 |
| Category | Beginner |
| Author | Aro Ogata |
| Tags | beginner, SEO basics, SEO, ranking drop, SEO reporting, Search Console, stakeholder communication |
| URL | https://linksurge.jp/blog/en/explaining-ranking-drops/ |

---


## Key Takeaways: Say "Here's What We Know," Not "Here's the Cause"

"So why did we drop?" When rankings or traffic fall, that's the first question from your boss or client. Early in my career, that one question left me sweating. What I eventually learned is that a good explanation isn't about guessing the cause right. It's about clearly separating what you know from what you don't. Here are the four points that matter.

1. **There's often more than one cause** — Google lists updates, technical issues, security, spam, seasonality and site moves as causes of traffic drops. Several can overlap, so don't lock onto one from the start
2. **Before explaining, pin down what, when, how much and where** — Compare periods in Search Console and break the drop down by page, query and device. That scope is the foundation of your explanation
3. **Sort each possible cause into confirmed, possible or ruled out** — For each of six candidates, write down what you checked and what you concluded. Simply showing what you've ruled out goes a long way toward calming people down
4. **Don't overstate. Pair your data with a date for the next check** — Instead of "X caused it," say "X is the most likely cause, here's the chart, and we'll recheck on this date." Google itself says changes come with no guarantee of recovery

Let's break down how to narrow the cause and how to communicate it.

---

## 1. Why Explaining a Ranking Drop Is Hard

Start by understanding why this is difficult. Once I understood it, I stopped feeling pressure to invent an answer.

### Rankings move by nature

Google's guide, "Debugging drops in Google Search traffic," says search results are fluid by nature. Rankings move for reasons outside your site: other sites update, searcher interest shifts and Google keeps refining its systems.

### Many causes, and they can overlap

The same guide lists the main causes: algorithmic updates, technical issues, security issues, spam issues, seasonality and changing interests, and site moves. A drop can also just look like one because of a data processing change or logging error.

With that many candidates, overlaps are common. "We happened to change our URLs during an algorithm update" is not unusual.

### You can only see so much from the outside

Google says core updates (broad changes to its systems a few times a year) aren't aimed at specific sites or pages. So no one sends you a note saying "this part of your site caused the drop." You have to infer from your own data.

Think of a weather forecaster. They don't say "it will definitely rain tomorrow." They say "70% chance of rain." Explaining a ranking drop works the same way: state your conclusion along with how confident you are.

> References:
> [Debugging Drops in Google Search Traffic - Google Search Central](https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops)
> [Google Search's Core Updates and Your Website - Google Search Central](https://developers.google.com/search/docs/appearance/core-updates)

---

## 2. Four Facts to Pin Down Before You Explain

Before talking about why, get clear on what happened. Skip this, and the conversation will go in circles.

### What dropped?

Rankings, impressions (how often you appeared in results), clicks or overall site visits? These are different numbers. Someone says "rankings dropped," and it turns out visits fell while rankings held. "[Rankings, Impressions, and Clicks Are Not the Same Thing](/blog/en/rankings-impressions-clicks-difference/)" explains the differences.

### Since when?

Find the date. The daily chart in Search Console's Performance report will show it. The latest data is preliminary and shown as a dotted line, so anchor on dates that have settled.

### By how much?

Google recommends using the Compare feature to put the last 3 months next to the previous 3 months or the same period last year. Size matters too: Google's suggested response to a small drop (position 2 to 4) differs from a large one (top 10 to position 29).

### Where?

Narrow the scope. The Performance report lets you break data down by query, page, country, device and search appearance, and switch between search types (web, image, video, news). Whether the whole site dropped evenly, only one group of pages, or only mobile changes which causes you suspect.

Put those four together and you get one line like this:

"Since late September, clicks to our product pages are down about 30% year over year. Other pages are roughly flat."

Get that far, and you're halfway there.

> References:
> [Debugging Drops in Google Search Traffic - Google Search Central](https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops)
> [Performance report (Search results) - Search Console Help](https://support.google.com/webmasters/answer/7576553?hl=en)

---

## 3. Sort Causes Into Confirmed, Possible and Ruled Out

With the facts in hand, check each candidate cause. Use the same six-step order from the previous article, "[Rankings Dropped? What to Check First](/blog/en/ranking-drop-first-checks/)."

The key is recording each result in one of three buckets:

- **Confirmed** — The data backs it up
- **Possible** — The timing or scope fits, but nothing proves it
- **Ruled out** — You checked, and it doesn't apply

### A sample triage table

| Candidate | What you checked | How to judge |
|:--|:--|:--|
| Tracking problems | Search Console's Data anomalies page; analytics vs. Search Console | Matching dates, or only one source dropped: "possible" |
| Technical issues | Page indexing report, URL Inspection, recent site changes | A sharp drop in indexed pages or a config mistake: "confirmed" |
| Manual actions and security | The two Search Console reports | Green check marks: "ruled out" |
| Google updates | Start and end dates on the Search Status Dashboard | Matching dates: "possible." Never "confirmed" on timing alone |
| Seasonality and demand | 16-month trend, same period last year, Google Trends | Same dip last year: close to "confirmed" |
| Competitors and results-page changes | Live results, daily rank history | Known rival and date of the swap: "possible" |

Why never mark an update "confirmed" on timing alone? Because Google publishes update dates, and matching dates make it very tempting to declare a cause. Coincidence in timing isn't proof.

Since I started building this table, I haven't been caught off guard by "Did you consider anything else?" in a meeting. A filled-in "ruled out" column is evidence that you did the work.

> References:
> [Data anomalies in Search Console - Search Console Help](https://support.google.com/webmasters/answer/6211453?hl=en)
> [Manual Actions report - Search Console Help](https://support.google.com/webmasters/answer/9044175?hl=en)
> [History for Ranking - Google Search Status Dashboard](https://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history)

---

## 4. A Reporting Template: Don't Overstate, Show the Data

Once you've narrowed things down, it's time to communicate. Here's a structure that works for any audience.

### Build the report from six parts

1. **Current assessment** (one sentence) — e.g., "Seasonality looks most likely, and we haven't found any site issues."
2. **What happened** — What, since when, how much and where
3. **What you checked** — The "confirmed" and "ruled out" rows
4. **What's still unknown** — The "possible" rows and why they're unresolved
5. **Next check date** — e.g., "We'll compare again on the 20th, a week after the update completes."
6. **What you will and won't do** — Immediate actions, and what you're deliberately leaving alone

Include parts 5 and 6, and nobody has to follow up with "So what's the plan?"

### Rephrasing overconfident statements

| Avoid | Say instead |
|:--|:--|
| "The Google update caused it." | "The drop overlaps with the update. We haven't found any other cause so far." |
| "We'll be back next month." | "We can't say when it will recover. We'll recheck on the 20th and report back." |
| "A competitor beat us." | "For these three queries, a newly ranking page has taken our spot." |
| "There's no problem." | "Within what we've checked, we found no technical issues or manual actions." |

Saying "we don't know" takes nerve. Early on, I felt like I had to name a cause or it would look like I wasn't doing my job. But an unsupported claim that turns out wrong destroys trust fast. Google's own core update guide says there's no guarantee that changes will produce noticeable results. If the experts won't promise it, you shouldn't either.

### Always show a chart with something to compare against

Don't show a single line. Put a comparison next to it.

- Last year's same period (shows seasonality at a glance)
- Pages that dropped vs. pages that didn't (shows scope)
- Update windows and site-change dates marked on the chart

For marking dates, use Search Console's custom annotations. Right-click the chart, choose a date and add a note of up to 120 characters. Everyone with access to the property can see them. You can also share a link to the Performance report that shows only the current view.

> References:
> [Google Search's Core Updates and Your Website - Google Search Central](https://developers.google.com/search/docs/appearance/core-updates)
> [Adding Context to Your Search Console Data With Custom Annotations - Google Search Central Blog](https://developers.google.com/search/blog/2025/11/custom-chart-annotations)
> [Performance report (Search results) - Search Console Help](https://support.google.com/webmasters/answer/7576553?hl=en)

---

## 5. Adjusting for Different Audiences

The structure stays the same, but what you emphasize should change by audience. When I build a report, I keep the data identical and just swap the opening sentence for each reader.

| Audience | What they want to know | What to emphasize |
|:--|:--|:--|
| Your boss or leadership | Business impact and next steps | Assessment, size of the impact, next check date |
| Other teams (dev, design) | Whether their work was involved | Dates of site changes vs. timing of the drop |
| Clients | Whether they can keep trusting you | What you checked, what you ruled out, how you'll proceed |

When you talk to the dev team, keep it from sounding like blame. Instead of "the redesign killed our rankings," ask a factual question: "Did the release on the 3rd change any URLs or redirects?" "[5 Website Redesign Mistakes That Wipe Out Search Traffic](/blog/en/site-renewal-seo-mistakes/)" covers the usual suspects.

With clients, it's tempting to promise "we'll get you back to where you were." But nobody can guarantee search rankings. "[Why Nobody Can Guarantee a #1 Ranking on Google](/blog/en/seo-ranking-guarantee-myth/)" explains why. Instead of promising a result, commit to what you'll monitor and when you'll decide.

---

## 6. Common Misconceptions and Mistakes

Here are four mistakes that come up when explaining drops. Honestly, I've made every one of them at least once.

### Mistake 1: Blaming the update just because the dates match

This is the most common. If a missing tracking tag or config error turns up later, your first explanation collapses, and your whole report loses credibility. Keep updates at "possible."

### Mistake 2: Showing only site-wide average position

Average position averages your position across searches where you appeared. It drops just because you started showing up, low down, for new queries. Show it alongside numbers for the specific pages or queries that fell. A rank tracker like [LinkSurge](https://linksurge.jp/) that charts each keyword separately makes it clear exactly what moved.

### Mistake 3: Cherry-picking the date range

If you choose a window where the drop looks small or the recovery looks big, someone will eventually open the 16-month chart and see a different story. Agree on the comparison period up front and stick with it.

### Mistake 4: Ending with "let's wait and see"

Waiting is often the right call. But without "until when" and "based on what," it sounds like you're doing nothing. Always add the next check date and the number you'll look at.

---

## 7. How to Check Your Own Site

The quality of your explanation depends on the records you already have. You can't go back and collect history after a drop.

- **Search Console's Performance report** — 16 months of trends and period comparisons. Log change dates with custom annotations
- **Google Search Status Dashboard** — Update start and end dates
- **Google Trends** — Whether search interest itself changed
- **Daily rank history** — When and how much each query moved

That last one backs up your explanation in a way Search Console's average position can't. [LinkSurge](https://linksurge.jp/)'s [rank tracker](https://linksurge.jp/features/ranking-dashboard/) charts daily positions for each keyword, so "which queries dropped, and since when" can go straight into your report.

---

{{linksurge-card}}

## Quick Check

### Q1: Your drop started during a Google core update. Can you tell your boss "the update caused it"?

Answer: Avoid saying that outright. Matching dates aren't proof, so present it as "possible" and include what you found when you checked other causes.

### Q2: When narrowing down causes, which three buckets do you sort results into?

Answer: Confirmed, possible and ruled out. Include the "ruled out" items in your report as evidence of what you checked.

### Q3: When you report "we'll wait and see," what must you include?

Answer: The date of your next check and the number you'll look at. Without them, it sounds like nothing is happening.

---

## Frequently Asked Questions

### How should I explain a ranking drop to my boss?

Pin down what dropped, since when, by how much and where. Then present each possible cause as confirmed, possible or ruled out. Add your current assessment, the next check date, and what you will and won't do, and you'll head off most follow-up questions.

### What should I say if I can't find the cause?

It's fine to say you don't know yet. Show which causes you've ruled out, which remain possible, and when you'll check what next. An unsupported claim damages trust if it turns out to be wrong.

### What if a client asks when rankings will come back?

Don't promise a date. Google says improvements can take a few days to several months to show, and there's no guarantee that changes will produce noticeable results. Commit instead to what you'll monitor and when you'll recheck.

### What kind of chart works best in a report?

Charts that include a comparison, such as the same period last year or a group of pages that didn't drop. Use Search Console's Compare feature to line up periods, and mark updates and site changes with custom annotations so the timing is obvious.

---

## Conclusion: The Goal Is Better Decisions, Not a Perfect Guess

When someone asks why rankings dropped, lay out the facts first, then show the causes in the order you checked them. Confirmed, possible, ruled out. With those three separated, people can make decisions even when no single cause is certain.

When you communicate, don't overstate. Pair every conclusion with a supporting chart and a date for the next check. It isn't flashy. Over time, though, it builds a reputation for reports people can rely on.

The previous article in this series is "[Rankings Dropped? What to Check First](/blog/en/ranking-drop-first-checks/)." Up next: "[Why Nobody Can Guarantee a #1 Ranking on Google](/blog/en/seo-ranking-guarantee-myth/)." For the full reading order, see the "[SEO, GEO and AIO Beginner Curriculum](/blog/en/seo-beginner-curriculum/)," and check the "[SEO Glossary for Beginners](/blog/en/seo-glossary-beginners/)" whenever a term trips you up.

LinkSurge's [rank tracker](https://linksurge.jp/seo-hub/ranking-dashboard) records daily rankings for each keyword, so you can show exactly when and where a drop began.