Ranking Drop Investigation
Traffic fell. Revenue followed.
The board wants an answer you don't have.
We find the root cause and hand your team the task list that fixes it.
Your agency sent findings. Root cause: unconfirmed. Recovery plan: none.
One session. Your drop, mapped against the evidence.
Engagement arc · large games portal
A core update cut traffic in half. Here's the plan that brought it back.
organic visits
referring domains
01. The problem
Your investigation confirmed there is a problem.
It didn't tell you how to fix it.
A report that names the cause isn't a plan. Naming a Google update as the culprit tells you what happened. It doesn't tell you which page to fix first, what to change on it, or what order any of that should happen in.
Most agencies hand you the diagnosis and call the job done. You leave the meeting knowing why you're bleeding traffic, with nothing in hand to stop it. Knowing the cause was never the hard part. Building the fix is.
02. The difference
A prioritised task list. Then we fix it.
A drop of this kind almost always has two sides. Something on the site changed, and something in the authority profile changed with it. Fixing one and leaving the other is why so many recoveries stall.
WLDM runs both teams in house. Our Tech SEO team takes the on-page, crawl and indexation work. Our Backlink team takes the authority side. Both work the same prioritised list, so you get the plan and the people who execute it.
Standard investigation
WLDM investigation
-
What you receive
Slide deck with findings
Prioritised task list, ready to action
-
Recommendation format
Themes and observations
Exact URL, fix steps, owner, effort, expected impact
-
Quality standard
Completeness of findings
Whether another team member can action every task without asking a single question
-
Who does the work
One specialism, and a referral for the rest
Tech SEO team and Backlink team, both in house, both on the same list
-
What happens next
Debrief meeting
Work starts on Monday, ours and yours
Before any investigation leaves our team, it has to pass one test. Hand it to a WLDM colleague who has never touched this account. Can they action every finding without asking a single follow-up question? If not, we are not done yet.
That test kills the usual agency failure modes on sight. A "theme" instead of an instruction. A named problem with no fix attached. A task with no URL, no owner and no sense of how urgent it actually is.
Every recommendation is a row in one prioritised table. No recommendation ships without all six fields.
Action plan
Illustrative rows. Structure and figures are from a real investigation, client details changed.
-
Restore the topical H1 on
/software-category/for-small-businessHow
Set the H1 back to the exact category term the page ranked for. It had been swapped for a generic H1. Single highest-leverage change on the site.
Impact
Primary recovery lever. Reconnects the topical cascade.
-
Fix hreflang on the 579 pages pointing to non-canonical URLs
How
Point hreflang at canonical URLs, add the missing self-reference and x-default. Exact URLs in the linked tab.
Impact
Stops wrong-region pages outranking the target.
-
Add keyword-rich internal links from the
/software-categoryhub to the child pageHow
Replace generic "learn more" anchors with the target term. 8 link sites listed in the linked tab.
Impact
Amplifies the H1 fix. Passes hub authority down.
-
Disavow 12 toxic domains (ranked list linked)
How
Upload the ranked disavow file to Search Console. Low confidence this caused the drop, so it goes last.
Impact
Hygiene. Unlikely to move rankings on its own.
- P1 CriticalRoot-cause fix or highest-leverage quick win.
- P2 HighStrong lever, movement expected in weeks.
- P3 MediumSupporting work that compounds the primary fix.
- P4 LowHygiene or low-confidence items.
Rows are ordered by impact divided by effort. Root causes always come before their downstream symptoms.
The most common failure in ranking investigations is a theme dressed up as a recommendation.
Theme
"Consolidate semantically similar pages"
Task
P1. Merge the 3 near-duplicate guide pages into one pillar, 301-redirect the other two, add ~300-word sections for the two sub-topics that carry their own search demand. Owner: Content. Effort: M. Impact: recover the head term that fell from position 1.5 to 20.
If a team member could not start work from that row tomorrow morning, it is not a task yet.
03. The process
Five steps. Every investigation.
No cause ruled out without evidence.
-
01
Verify
Before we investigate anything, we confirm the drop actually happened in your own click data. An estimated traffic tool is not evidence. Your Search Console data is.
-
02
Locate
We find where the loss actually sits: which pages, which query groups, which countries, which devices. Is it one template failing, or the whole site bleeding at once?
-
03
Timeline
We align the drop with algorithm updates, on-site changes and seasonal patterns. Two things happening in the same month are not automatically the same cause.
-
04
Diagnose
We work through every plausible cause, technical, content and authority, link profile, SERP shift, until we can name a root cause with a confidence rating attached to it.
-
05
Deliver
Every finding becomes a task. Named URL, exact fix, priority tier, effort, expected impact, owner. Nothing in the deliverable is a theme or a suggestion.
What looks like five steps to you is ten phases internally. Each one is ruled in or out with reasoning we write down, never waved off as unlikely and skipped. Every source below is named in the methodology section of the report, so every claim in it can be checked against something real.
Diagnostic sequence
10 phases · each ruled in or out
-
Scope and data integrity
Confirm the drop is real in actual clicks before investigating anything. Third-party estimated-traffic models have overstated a "drop" by more than 30 percentage points on real client accounts. We define a clean 14-day pre/post window and skip the change week to cut noise.
EvidenceSearch Console click data; analytics annotations
-
Timeline and trigger correlation
Overlay the drop date against algorithm updates, on-site changes (H1, title, template, migration) and seasonality, year on year. The drop date is the most powerful diagnostic clue available. An algorithm hit and an on-site change weeks apart are two causes, not one.
EvidenceDaily Search Console trend; historical traffic data; archived snapshots of the page
-
Segmentation
Localise the loss by URL, subfolder, query, country, device, and above all branded against non-branded. "Traffic is down 30%" is not a finding. A branded-search spike can mask a complete topical collapse inside the site-wide total.
EvidenceSearch Console clicks by page, query, country and device; page-level traffic data
-
Technical and indexability
Index status, canonicals, hreflang, robots and noindex, redirect chains, sitemap, schema, all at URL level. Summary counts hide the exact pages that broke. We do not work from summaries.
EvidenceCrawl and index data at URL level; live URL inspection; fresh crawl of the affected templates
-
Content and E-E-A-T
Topical authority, semantic duplication, thin or AI-indistinguishable content, author and entity signals, freshness. Most core update and Helpful Content losses sit here. Near-duplicate clusters and missing author credentials on YMYL pages are the most common levers.
EvidenceContent duplication and similarity analysis; page-level traffic history
-
Rankings, SERP and intent shift
Position changes on target queries, new SERP features (AI Overviews, answer boxes, carousels) that eat clicks without moving rank, and intent shifts where Google now rewards a different page type for the same query.
EvidenceSearch Console position data; live SERP checks on the affected queries
-
Backlinks and link quality
Lost and gained referring domains, toxic-link spikes, anchor-text ratios. We assess quality, not count. If we recommend a disavow, the domains are ranked by spam score. We never hand over an unranked dump.
EvidenceReferring domain and anchor history; spam scoring of the current link profile
-
Core Web Vitals
Field p75 LCP, INP and CLS as a confounder check, not a headline finding. Core Web Vitals rarely cause a sudden ranking cliff. The question is narrow: did they actually move inside the drop window?
EvidenceChrome UX Report field data; page-speed diagnostics
-
GEO and AI Overviews
A modern loss vector. A page can hold its rank and still lose the click because an AI Overview answers the query above it. We check AI-search visibility for the affected queries and whether the brand is cited in the answer.
EvidenceLive AI answer checks; brand citation monitoring across AI search
-
Synthesis and root cause
All evidence pulled into a confidence-rated root cause and classified: penalty (rare, confirmed in Search Console manual actions), algorithm, self-inflicted on-site change, tool artifact, or competitive SERP shift. We state our confidence and what evidence would change the conclusion.
EvidenceCross-phase evidence review
04. Proof
From 5.5 million visits to a 12.8 million peak.
After a core update cut traffic in half.
A large games portal was hit by a core algorithm update. Traffic fell roughly in half. WLDM diagnosed the root cause, built the recovery plan, and executed the authority engineering behind it.
Referring domains started climbing from month one. Traffic turned at month two. It peaked at 12.8M in January 2025 and still ran at 9.9M in June 2026, with no ongoing intervention needed to hold it.
Organic traffic from the post-update trough to the Jan 2025 peak. 5.5M to 12.8M.
Referring domains moved first. Traffic followed a month later. That lag is the proof.
Still holding. 9.9M visits, June 2026.
The site, a large puzzle and card games portal, was hit by a core algorithm update in mid-2023. Traffic declined from 7.2M in June 2023 to 4.4M by October 2023, a 39% fall. By March 2024 it had stabilised at 5.5M with 3,148 referring domains. WLDM engaged in March 2024.
| Month | Organic visits | Referring domains | Note |
|---|---|---|---|
| 2023-06 | 7.2M | 2,562 | Pre-drop peak |
| 2023-07 | 5.6M | 2,540 | Core update impact |
| 2023-09 | 4.9M | 2,643 | |
| 2023-10 | 4.4M | 2,657 | Trough |
| 2023-12 | 5.1M | 2,764 | |
| 2024-03 | 5.5M | 3,148 | WLDM engaged |
| 2024-04 | 5.6M | 3,341 | |
| 2024-05 | 8.3M | 3,463 | Traffic turns, +51% month on month |
| 2024-06 | 7.8M | 3,740 | |
| 2024-08 | 8.8M | 4,010 | |
| 2024-09 | 10.1M | 3,936 | |
| 2024-12 | 11.3M | 3,967 | |
| 2025-01 | 12.8M | 4,148 | Peak |
| 2025-02 | 12.8M | 4,267 | |
| 2025-06 | 12.5M | 4,871 | |
| 2026-06 | 9.9M | 7,874 | Recovery holding, 27 months on |
The lag between cause and effect is the whole proof here. Referring domains start climbing from month one (Mar to Apr, 3,148 to 3,341). Traffic does not turn until month two (Apr to May, +51%). That 4-8 week gap is the signature of real links being crawled, indexed and processed through Google's standard ranking pipeline: crawl latency of roughly four weeks, then a two to four week ranking cycle, then statistical signal accumulation. A link that moved traffic overnight would be a signal Google would discount. The delay is what makes this recovery trustworthy and repeatable.
The recovery has held. As of June 2026, 27 months after engagement, the site holds 9.9M visits and 7,874 referring domains. Authority compounded throughout. The site did not need continuous intervention to hold the recovery.
Source: WLDM engagement data, cross-checked against third-party historical traffic and referring-domain records. Client anonymised.
05. The offer
We will investigate the drop and deliver a task list your team can action this week.
Last month or six months ago, the cause is findable. Turning it into something your team can act on is what most investigations skip.
We run the full ten-phase diagnostic, cross-check it against your real performance data, and hand back a prioritised task list with exact URLs, exact fixes and a projected recovery timeline. We work directly with your team. Your board isn't waiting. Neither are we.
Free initial consultation. We'll tell you what we can find before you commit to anything.
A branded HTML report with nine required sections. Here is what sits in each one.
-
Executive summary
Two or three findings in plain English a non-technical board member can follow. A metric grid of the headline numbers (traffic, keyword and referring-domain deltas), a 0-100 weighted scorecard across seven categories, and Top-5 Critical Issues plus Top-5 Quick Wins.
-
Action plan
The prioritised task table, placed right after the executive summary, not buried at the end. Every row: exact URL, fix steps, priority tier (P1-P4), expected impact, effort (S/M/L) and owner (Dev, Content or SEO).
-
Evidence sections
One section per finding. Each carries a chart and a per-URL or per-keyword table with pre, post and delta figures. Every data point linked to its source.
-
Competitive SERP tables
SERP tables for the target queries: which domains rank, their estimated traffic, their domain authority, and whether you appear in the top 10.
-
Confounders
What was ruled out and why. Core Web Vitals, seasonality, tracking gaps, tool artifacts, all stated upfront, so nobody re-raises them as alternative explanations three weeks into the fix.
-
Site-audit scorecard
Health score and issue counts by category, each row linked to the per-URL sheet tab holding the full issue list.
-
Projected impact
A ranged recovery estimate tied to specific work. For example: "60-80% recovery over 6-12 weeks if P1 and P2 ship, assuming no further algorithm changes." Ranges. Never promises.
-
Methodology and data sources
Every data source, property, analysis window and crawl date. Every claim auditable.
-
Recovery projection arc
Expected score progression from current state, to critical fixes shipped, to the full plan executed over 90 days, with the traffic and ranking movement expected at each stage. Every projection is ranged, tied to which specific tasks ship, and qualified against algorithm stability. The same format is used for every investigation, so progress can be benchmarked quarter over quarter.
Every week without an answer is a week the gap compounds.
The drop already happened. What happens from here is either recovery or more bleeding.
Ranking Drop Investigation
Book a strategy session
One session. Your drop, mapped against the evidence.
Free initial consultation. We'll tell you what we can find before you commit to anything.