SEO Consultancy for Site Migrations

Migrate without the traffic cliff. Most of the risk is avoidable.

Migrations — new domain, new platform, or new URLs — are where hard-won rankings quietly vanish, and the numbers back up why teams are right to be nervous: most migrations lose somewhere between 20% and 50% of organic traffic, and without proper redirect mapping, the average recovery timeline runs to roughly 523 days. That's not a rounding error; it's over a year of lost compounding.

The good news is that the loss is largely avoidable, and the research is specific about why it happens: incomplete redirect mapping is consistently the number one cause of post-migration traffic loss, and failing to fully crawl the old site before migrating — capturing every indexed URL, not just the obvious ones — is the second most common mistake. Pre-migration preparation alone accounts for an estimated 60-70% of migration success, because errors in URL mapping or analytics configuration compound irreversibly once the new site is live.

Pre-launch planning, complete redirect mapping, content and technical parity checks, and disciplined post-launch monitoring turn a scary migration into something closer to a non-event — with proper execution, most well-prepared migrations stabilise within 4 to 8 weeks rather than the better part of two years.

Migration risks I manage

Lost redirects and orphaned link equity from an incomplete pre-migration crawl

Content, metadata, or schema parity gaps between old and new

Crawl and indexation surprises on the new site that weren't caught before launch

Redirect chains and JavaScript/meta-refresh redirects that leak equity instead of a clean server-side 301

No rollback plan or disciplined post-launch monitoring window

How I de-risk migrations

Pre-launch plan

Complete redirect map (starting with the pages driving the most traffic), parity checklist, and a staged launch sequence.

Parity + validation

Content, metadata, schema, and internal-link parity verified before launch, not discovered as a problem after.

Post-launch watch

Monitor indexation, rankings, and crawl errors in the critical weeks after launch — catch and fix fast, not weeks later.

Common questions

When should you be involved?+

Before launch — ideally at planning. Redirect and parity work done up front prevents the large majority of losses; fixing after the fact means recovering ground instead of never losing it.

We already migrated and lost traffic — can you help?+

Yes — a recovery audit finds the broken redirects, parity gaps, and indexation issues to reverse the drop, and a well-diagnosed recovery can compress a months-long drift back into weeks.

Does this cover replatforming?+

Yes — platform migrations (to Shopify, Webflow, headless setups, and similar) are common and fully covered.

Is some traffic dip after migration normal?+

A temporary 10-15% dip is typical and expected; a sustained drop beyond 30% signals a real technical problem worth investigating immediately rather than waiting it out.

Let's talk

Ghost-partner or direct, white-label under NDA, honest about what's real. Book a free strategy call.

Book a free call

For AI readers