Traffic drop recovery
Search traffic fell and nobody can say why. I find the cause, fix what's fixable and tell you plainly which part of the drop isn't coming back — because some causes are recoverable in weeks and others aren't recoverable at all, and knowing which is yours is worth more than a plan built on hope.
100
+Completed projects
Websites, landing pages and SEO projects for businesses in different niches and markets.
15
Years of experience
Hands-on experience in SEO, website development and digital strategy.
17
+Industries covered
From local services and startups to real estate, e-commerce and B2B projects.
3
Working languages
English, Polish and Russian — with content and structure adapted to each market.
What traffic drop recovery involves
The date first, before any theory
Search Console shows when the decline started, to the day. That single fact eliminates most of the competing explanations immediately — a drop that began the day of a deployment is a different problem from one that began three weeks earlier.
Separating what fell from what didn't
Rarely does everything drop equally. Which pages, which queries, which countries, which device — the shape of the loss usually names the cause before anything technical is examined.
Checking the mechanical causes in order of likelihood
Redirects, indexation status, robots directives, canonical tags, structured data, page availability at crawl time. Boring, fast and where most answers are.
Establishing whether it was you or the world
If nothing on the site changed and the drop is broad, the cause is external. That distinction determines whether there's a fix or a strategy — and pretending an external change is a technical fault produces months of pointless work.
Fixing what's fixable, in priority order
Redirects and indexation first, because they're both fast and high-impact. Content and authority questions after, because they're neither.
A plain statement of what isn't coming back
Some drops are permanent. An algorithm update that reweighted your category, a competitor who genuinely improved, demand that moved elsewhere. You'll be told which part of the loss is in that category rather than billed for chasing it.
Why the date the traffic dropped is the whole diagnosis
Almost every conversation about a traffic drop starts with theories. The developer suspects the SEO work, whoever does the SEO suspects the last deployment, and someone mentions an algorithm update they read about. All of it is guessing, and all of it is unnecessary, because the answer is usually visible in ten minutes.
Search Console shows the day the decline started. Not the month — the day. And that single fact does most of the diagnostic work, because causes have signatures.
A drop that begins on the day of a deployment is a deployment problem. A drop that begins two to three weeks after a site launch is usually a crawl problem — the search engine took that long to notice the pages had changed. A drop that appears over several days across every page equally, with nothing having changed on the site, is external. A drop confined to one section is confined to whatever happened to that section.
Working from the date backwards is faster and more honest than working from theories forwards. It's also the reason this work can be quoted at all: without a date, the scope is anyone's guess.
What actually breaks, in order of how often
Redirects after a rebuild. By a wide margin the most common. New URLs, old ones returning nothing, and every accumulated signal pointing at addresses that no longer exist. Entirely fixable, usually within days, and the recovery follows once the pages are recrawled.
I've seen this cost a construction company most of its search traffic after a redesign that changed every URL without a redirect map. Two weeks to diagnose, about a month to recover — and the diagnosis was slower than the fix, which is typical.
Indexation quietly turning off. A noindex left on after staging, a robots directive blocking a section, a canonical tag pointing everything at one page. Fast to find, faster to fix, and invisible unless someone checks.
Migration losses. Platform, domain or hosting changes go wrong in specific ways: lost redirects, changed URL patterns, pages that render differently to a crawler than to a browser.
One case I worked on involved a site rebuilt with AI assistance where the language versions were wired to the wrong locales. Traffic fell within two days. Diagnosis and repair took two weeks — again, most of that was finding it.
Content and structure changes. Pages merged, text shortened, headings rewritten during a redesign. Slower to show up and slower to reverse than the technical causes.
External change. No site change, broad decline, competitors moving in the same period. This is where the work stops being repair and starts being strategy.
The part where a supplier should tell you no
Not every drop is recoverable, and the honest position is worth stating before anyone signs anything.
If an algorithm update reweighted what your category rewards, the traffic you had was earned under rules that no longer apply. Recovery there isn't repair; it's rebuilding under different conditions, and it takes as long as building did.
If a competitor genuinely improved — better content, better site, more authority — then nothing on your side is broken. You were passed. That's a strategy conversation, not a fix.
If demand moved, the queries that used to bring traffic bring less to everyone. Your position may be unchanged.
I'd rather establish which of these applies during a diagnosis that costs a few hundred euros than discover it after a year of retainer. And where the answer is "this part isn't coming back", you'll hear that phrase rather than a plan.
Why diagnosis is quoted separately from the fix
Because the fix can't be quoted until the cause is known, and any supplier who quotes both together before looking is pricing a guess.
Redirect repair after a rebuild is a known quantity — days of work, predictable outcome. Recovering from a content change is weeks. Rebuilding after an algorithmic reweighting is months and isn't guaranteed. Those are three different projects with three different prices, and which one you have is exactly what the diagnosis establishes.
The diagnosis is also useful on its own. Several clients have taken the report and had their existing developer implement it, which is a reasonable outcome and one I'd rather have than a padded engagement.
What recovery actually looks like when it works
Not a straight line. Fixed redirects are recrawled over days or weeks depending on the size of the site and how often it's crawled, and positions return unevenly — some pages recover in days, others take a month.
Expect the shape rather than a date: an initial partial return as the most-crawled pages are reprocessed, then a slower tail. Anyone offering a specific date for full recovery is describing something they don't control.
And full recovery isn't always the outcome even when the cause was technical. Signals accumulate over time, and an interruption long enough for competitors to take the positions can leave a permanent gap. That's a reason to act quickly rather than a reason not to act.
If the traffic was never really there to begin with, that's a different problem — local SEO is what addresses ongoing visibility rather than a one-off drop.
Not sure which situation is yours? A technical SEO audit looks at why a site has no traffic at all — this service is specifically for traffic that was there and then wasn't.
How traffic drop recovery runs
Diagnosis, quoted and delivered separately
The date, the shape of the loss, the mechanical checks, and a written statement of the cause and what's recoverable. This is a complete deliverable — several clients have implemented it themselves.
A scope and price for the fix, once the cause is known
Different causes are different projects. You get the figure after the diagnosis rather than before it, which is the only order in which the figure means anything.
The fix, in priority order
Redirects and indexation first because they're fast and high-impact; content and structure after.
Monitoring the return
Recovery is uneven and takes weeks. Positions and non-branded clicks tracked against the pre-drop baseline, so the question of whether it worked is answered rather than assumed.
