Skip to content
VERQEN — home

Service 03 · Service

SEO recovery: we find what changed, and when.

A drop always has a date. Once you know the date, the list of possible causes gets short: a release, a migration, a template change, an indexing shift, a competitor move, or a search update. We work backwards from the data instead of guessing.
Investigate my traffic dropSee how we work
Timeline
Investigation 1–3 weeks; recovery depends on the cause
Starting from
From $2,500 for the investigation
Shape
Investigation first, then a scoped recovery project
Deliverables
7 items

The problem

Performance fell and the explanations you have been given do not fit the data.

“It was an algorithm update” is the most common answer and often the wrong one. Site releases, tag changes, CDN rules, template edits and consent changes produce drops that look identical in a traffic chart. The only way to tell them apart is to isolate the date and compare what changed around it.

You probably recognise some of these

  • Organic clicks fell and have not come back.
  • Rankings held but clicks dropped — or the reverse.
  • A specific template or section lost traffic while the rest held.
  • Impressions fell before clicks did.
  • GA4 shows a drop that Search Console does not, or the other way round.

Who needs this

Is this for you?

  • Companies with a measurable, sustained organic decline
  • Sites that lost traffic after a redesign, migration or platform change
  • Teams told to “wait it out” with no diagnosis
  • Businesses where the drop is now affecting pipeline or revenue
  • Companies that recovered partially and do not know why the rest has not returned

Why it happens

What usually causes it

  1. A migration or release that changed URLs, canonicals, redirects or rendering.
  2. Accidental noindex, robots or status-code changes on a template.
  3. Content consolidation or pruning that removed pages with real demand.
  4. Tracking or consent changes that altered what gets reported, not what happened.
  5. Internal linking changes from a navigation redesign.
  6. Competitor movement or genuine search-result-layout change on your key queries.
  7. A search quality update interacting with pre-existing weaknesses.

Scope, in detail

What exactly we check

Not a category list — the actual checks. If something is not on here and you need it, say so and we will tell you whether it fits the scope.

Baseline and timing

  • Establish a clean pre-drop baseline
  • Isolate the exact date the change began
  • Separate seasonality from a real decline
  • Check whether the drop is reporting or reality
  • Cross-check GSC against GA4 and CRM

Page and query comparison

  • Which URLs lost, and how much each was worth
  • Which queries lost impressions versus clicks
  • Position change versus click-through change
  • Template-level and section-level patterns
  • Brand versus non-brand split

Cause investigation

  • Release and deploy history around the date
  • Technical diffs: canonicals, robots, status codes, rendering
  • Content changes and removals
  • Internal link changes
  • Backlink loss on affected URLs
  • Indexing and coverage movement
  • Competitor and SERP-layout comparison

Deliverables

What you actually receive

Every important issue arrives in the same format: problem, evidence, why it matters, root cause, solution, exact actions, owner, priority and measurement.
Investigate my traffic drop
  • A dated timeline of what changed, and what the data shows around each change
  • A ranked list of probable causes with the confidence level for each
  • Explicit separation of confirmed causes from unconfirmed hypotheses
  • A recovery plan sequenced by impact and reversibility
  • The exact changes needed, written for implementation
  • A monitoring plan with the specific metrics that should move, and by when
  • An honest assessment of what is unlikely to come back

Process

How the work runs

Each step has an exit condition. We do not move on because time passed.

  1. Establish the baseline

    Pull at least 16 months of Search Console and analytics data so seasonality and year-over-year comparisons are possible.

    • 16+ months GSC
    • GA4 history
    • Seasonality check

  2. Find the date

    Isolate when the change actually began, at day-level resolution, per template and per query group. Different sections often have different dates — that alone tells you a lot.

    • Day-level analysis
    • Per-template
    • Per-query-group

  3. Compare what changed

    Affected pages against unaffected ones, queries against queries, competitors against you, and the technical state of the site before and after the date.

    • Page diff
    • Query diff
    • Technical diff
    • Competitor diff

  4. Confirm or discard causes

    Each hypothesis gets tested against evidence. What we cannot confirm is labelled as unconfirmed — we do not convert a guess into a recommendation.

    • Evidence test
    • Confidence labelling

  5. Recover

    Fix in order of impact and reversibility, one change group at a time, so we can attribute the result rather than shipping twenty changes at once.

    • Ordered fixes
    • Attributable releases

  6. Monitor

    Watch coverage, impressions, clicks and conversions on the specific affected URLs, and report what actually moved.

    • Affected-URL cohort
    • Weekly reads
    • Impact report

What we need from you

Access and data

We ask for read access only, and only for what the question needs.
  • Google Search Console — the full available history, all properties
  • GA4 with historical data intact
  • A release, deploy or change log around the suspected period
  • Any redirect maps or migration documentation
  • Server logs, where available
  • Backlink data, where available
  • CRM or revenue data to size the real business impact

Measurement

What results can be measured

Agreed before the work starts, so nobody argues about the definition afterwards.
  • Recovery of non-brand clicks and impressions on the affected URL cohort
  • Indexation recovery in the affected coverage categories
  • Position recovery on the specific queries that lost
  • Conversions and revenue from the affected pages
  • Time from fix release to first measurable movement

Afterwards

What happens when the project ends

You get a documented cause, so it does not happen again for the same reason. The sensible next step is release-time checks — a pre-deploy SEO checklist and monitoring — because the cheapest recovery is the one you never need.
How scoping and pricing works

Why trust us

How we keep ourselves honest

  • We will tell you when a drop was caused by something the previous agency or an internal release did, and we will show the evidence rather than assert it.
  • We will also tell you when it was a genuine search update and the honest answer is a different strategy, not a fix.
  • Confidence levels are stated. You will know which conclusions are proven and which are probable.

Honest limitations

What this service will not do

Stated up front, because finding out later is worse for both of us.
Not every drop is recoverable. If demand for your queries genuinely fell, or the result layout changed permanently, no fix restores the old number — and we will say that.
If historical data was deleted or the property was recreated, some questions cannot be answered at all.
We cannot attribute a recovery reliably if twenty unrelated changes ship in the same week. Sequencing matters, and we will ask for it.

Quick answers

SEO Recovery in nine questions

The same facts, stated plainly. Useful if you are skimming, and useful to any system trying to understand what we actually offer.
What is this service?
Find out exactly when and why organic performance dropped — then recover what can be recovered.
Who is it for?
Companies with a measurable, sustained organic decline; Sites that lost traffic after a redesign, migration or platform change; Teams told to “wait it out” with no diagnosis; Businesses where the drop is now affecting pipeline or revenue; Companies that recovered partially and do not know why the rest has not returned.
What problem does it solve?
Performance fell and the explanations you have been given do not fit the data.
What do you check?
3 areas covering baseline and timing, page and query comparison, cause investigation.
What do you deliver?
A dated timeline of what changed, and what the data shows around each change; A ranked list of probable causes with the confidence level for each; Explicit separation of confirmed causes from unconfirmed hypotheses; A recovery plan sequenced by impact and reversibility; The exact changes needed, written for implementation; A monitoring plan with the specific metrics that should move, and by when; An honest assessment of what is unlikely to come back.
How long does it take?
Investigation 1–3 weeks; recovery depends on the cause
How much does it cost?
From $2,500 for the investigation. Investigation first, then a scoped recovery project.
What access is needed?
GSC and GA4 history, release log, redirect documentation
What happens after?
You get a documented cause, so it does not happen again for the same reason. The sensible next step is release-time checks — a pre-deploy SEO checklist and monitoring — because the cheapest recovery is the one you never need.

Questions

Questions about seo recovery

Something else? hello@verqen.com

Evidence and further reading

Worked investigations and working notes on this subject.

Related services, problems and industries

The problems this service usually solves, and where we see them most often.