Skip to content

SEO Migrations

SEO migrations that replatform or redesign without losing rankings.

An SEO migration is how you change your site, new platform, new design, new URLs, without throwing away the rankings and traffic you already have. Done carefully it's invisible; done carelessly it erases years of work overnight.

Proof this works

Relevant client result

Recovering Jackson Heating & Cooling's hacked domain meant clearing 291,851 spam pages. While the new site earned its first 44 clicks and 5 calls.

From a combined website-and-SEO program. Shown as relevant proof of the approach, not isolated attribution to this one discipline.

Read the Jackson Heating & Cooling case study

Why redesigns tank traffic

The classic disaster: a business invests in a beautiful new website, launches it, and organic traffic falls off a cliff. URLs changed with no redirects, content was 'cleaned up' and deleted, the new stack blocks crawlers, and the equity built over years is simply gone. Usually discovered weeks later when the leads stop.

None of that is inevitable. A migration is a known, manageable risk when it's planned: mapped redirects, preserved content and metadata, a crawlable build, and monitoring through the switch. The failures come from treating SEO as an afterthought to the design.

Scope

What an SEO migration covers.

Before, during and after the switch. The whole risk window.

Pre-migration audit and mapping

A full inventory of current URLs, rankings and content, and a one-to-one redirect map so nothing lands on a 404.

Content and metadata preservation

Carrying over the titles, copy and structure that earn your current rankings, rather than silently dropping them.

Redirect implementation

301s in place at launch, tested, with redirect chains and loops eliminated.

Launch monitoring

Watching crawling, indexing and rankings through the switch so a problem is caught in days, not discovered in a quarterly report.

When you need this

Any time you change platform, domain, URL structure or do a substantial redesign. If a rebuild is on your roadmap, the migration plan should exist before the design is signed off, not bolted on at launch.

If you've already migrated and traffic dropped, the same work runs in reverse. Diagnosing what broke and recovering what's recoverable. The sooner it's caught, the more comes back.

Questions

Before you commit.

We're redesigning, when should you be involved?

Before the URLs and content are finalised, ideally at the planning stage. The cheapest migration is the one designed correctly; the expensive one is the recovery after launch.

Will we lose rankings during a migration?

A well-executed migration usually sees a brief, small fluctuation that recovers within weeks. A botched one can lose the lot. The difference is entirely in the preparation.

Our traffic already crashed after a relaunch. Can you help?

Often yes. We diagnose what broke, missing redirects, blocked crawling, deleted content, and implement the recovery. Speed matters, so the sooner we look, the better the outcome.

Start here

Planning a redesign? Talk to us before you launch.

Tell us what's changing. Platform, domain or design. You'll get a straight read on the migration risk and what it takes to keep the rankings you've already earned.