Problem
Your organic traffic dropped. Here is what usually causes it.
What you would say
“Our organic traffic dropped and nobody can tell me why.”
- Urgency
- Usually urgent — it is costing money now
- First useful answer
- Usually within the first week we can tell you the date the drop started and whether it looks technical, content-related, measurement-related or external.
- Investigation steps
- 9 steps, in a fixed order
Business impact
What this usually costs
- Lost pipeline from the pages that used to convert
- Paid budget spent covering an organic gap that could be fixed
- Months of content investment producing nothing while the cause persists
- Internal credibility, when nobody can explain the chart to the board
Our approach
What we would investigate
Establish a clean baseline
Pull the full available Search Console history and GA4, so seasonality and year-over-year comparison are possible before anything is concluded.
Find the exact date
Day-level analysis per template and per query group. Different sections often have different dates, and that pattern alone eliminates whole categories of cause.
Check indexing and coverage
Did pages leave the index, or did they stay indexed and lose position? These are completely different problems with completely different fixes.
Compare technical state before and after
Canonicals, robots, status codes, redirects, rendering and internal links around the date. Most drops that are called algorithmic turn out to be a release.
Compare content changes
Pages edited, consolidated, pruned or moved. Removing pages with real demand is a common self-inflicted cause.
Check whether the drop is real
Cross-check GSC against GA4 and the CRM. A consent or tracking change can produce a drop in reported traffic while actual traffic is unchanged.
Compare competitors and result layout
Did someone take those queries, or did the result page itself change shape so the same position now earns fewer clicks?
Check links to affected URLs
Lost backlinks or internal links to the specific pages that dropped — measured on the affected cohort, not site-wide.
Line up external events
Known search updates, seasonality, market events and your own campaign history against the isolated date.
Differential diagnosis
Likely causes, and what proves each one
| # | Possible cause | Evidence that confirms or eliminates it |
|---|---|---|
| 01 | A release or migration changed URLs, canonicals, redirects or rendering | Crawl diff against the date, redirect chain analysis, rendered DOM comparison |
| 02 | Accidental noindex, robots or status-code change on a template | Coverage report movement by category, crawl of the affected template |
| 03 | Content consolidation or pruning that removed pages with demand | Removed-URL list against their historical clicks and queries |
| 04 | A measurement or consent change — reported traffic fell, real traffic did not | GSC versus GA4 versus CRM comparison across the date |
| 05 | Internal linking changes from a navigation redesign | Link graph comparison, link depth change for affected URLs |
| 06 | Competitor movement or a change in result layout on your key queries | Position versus click-through change, competitor visibility comparison |
| 07 | A search quality update interacting with an existing weakness | Date alignment plus the pattern of which page types were affected |
The no-guessing rule
If the data does not support a conclusion, we write “we do not have enough evidence to confirm this” and tell you what we would need. A guess never becomes a recommendation.Outcome
What you end up with
- A dated explanation of what happened, with the evidence behind it
- Causes separated into confirmed and unconfirmed — no guesses presented as findings
- A recovery plan ordered by impact and reversibility
- An honest view of what is unlikely to come back
- Monitoring on the affected URL cohort so recovery is measurable
No surprises
What happens if you get in touch
You send us your website and what is happening
One form, six fields. No call required to get started.
We review the situation
We look at your site and the public data before we reply, so the first conversation is useful.
We confirm whether we can help
If we are not the right fit, we say so — and where we can, we point you somewhere better.
We explain what we would investigate
Specifically: where we would look first and why, based on what we already saw.
You decide whether to move forward
No pressure and no follow-up sequence. You have the information; the decision is yours.
Questions
Questions about traffic drop
Evidence and further reading
- Worked example
Twelve thousand product pages that could not rank for their own model names
A canonical rule added during a duplicate-content cleanup pointed every product URL at its parent category. The catalogue was invisible for its highest-intent queries and nobody had connected the two facts.
- Worked example
A migration redirect map that covered 96% of URLs and 41% of the revenue
The redirect map was built from a CMS export, so it covered almost every URL by count. Scored by traffic, conversions and backlinks, it missed most of what the old site actually earned.
- Insight · Technical SEO
The first 48 hours of an organic traffic drop
A drop always has a date. Finding the date, at day-level resolution, per template, eliminates more possible causes than any other single step — and most teams skip it.
Services that fix this, and problems that travel with it
- ServiceSEO RecoveryFind out exactly when and why organic performance dropped — then recover what can be recovered.
- ServiceTechnical SEO & Search GrowthMake sure search systems can crawl, render, index and understand the pages that carry your revenue.
- ServiceGrowth DiagnosticFind the highest-value problems stopping growth, with the evidence behind each one.
- ProblemA website migration is comingMigration losses are avoidable, but only with work that happens before launch — not after.
- ProblemAnalytics cannot be trustedWhen the numbers are wrong, every decision made on them is a guess with a chart attached.