00Services / Site migrations
Move platform with your rankings intact.
Move to the stack you need with your rankings and traffic intact, and a measurable performance gain on the other side. The migration is treated as a search problem first.
Fixed scope · Rankings held · Staged, reversible cutover
How a migration keeps your rankings.
Rankings are held by treating the move as a search problem first. Redirects are mapped one-to-one, content and metadata parity is checked against the old site, and the cutover is staged so it is observable and reversible. Performance is measured before and after.
The move is where rankings are won.
When a site outgrows its platform, the migration itself is where search traffic is won or lost. We treat it as a search problem first.
Redirects are mapped one-to-one, content and metadata parity is checked against the old site, and the cutover is staged so it is observable and reversible. Performance is measured before and after, so the gain is visible.
What a site migration includes
The work that keeps a replatform from costing rankings.
- Framework, platform or CMS migration
- One-to-one, SEO-safe redirect mapping
- Content, metadata and structured-data parity checks
- Content and data migration
- A measurable performance uplift, before and after
- A staged cutover with a rollback path
How the engagement runs.
01
Scope & audit
We map the current URL, ranking and redirect footprint, then agree a fixed scope before anything moves.
02
Rebuild
The site is rebuilt on the new stack search-led, so the architecture is corrected in the move rather than carried over broken.
03
Parity & redirects
Redirects are mapped one-to-one and content parity is checked against the old site, so nothing of value is dropped silently.
04
Staged cutover
The switch is staged and observable, with a rollback path. Performance is measured before and after, then the repository is handed over.
What you can hold us to
The acceptance criteria, stated plainly.
- Redirects mapped one-to-one.
- Parity checked against the old site before the switch.
- A staged cutover with a rollback path.
- Performance measured before and after, so the uplift is visible.
Worth reading next
Tools and answers that go deeper on migrations.
- Guide: migrate without losing rankings
The full discipline: URL equity, one-to-one redirects, parity, a staged cutover.
- Free redirect-map auditor
The check we run before a cutover: catches chains, loops and unmapped URLs. Run it yourself, no sign-up.
- Can you migrate without losing rankings?
The migration question, answered in full in the FAQ.
- How search-led design works
Why a migration is the moment to correct the architecture.
Move without losing rankings.
Tell us what you're moving off. You'll have a fixed scope and a migration plan that protects your traffic.
Start a project