SEO Migration · Replatforms · Domain changes · URL restructures

SEO migration services that keep the traffic you earned.

Moving from Lightspeed to Shopify, relaunching a WooCommerce or PrestaShop shop, changing domain or restructuring URLs: this is where most sites lose their rankings, usually weeks after launch. I plan the migration before the build starts, test it before go-live and monitor it for six weeks after.

100%
URLs mapped before launch,
no orphan redirects
4-8
Weeks planning lead time
before go-live
6
Weeks of monitoring
after launch
1
Consultant. No
account layer.
What an SEO migration actually requires

Four moving parts most teams underestimate.

An SEO migration is one of the few jobs where doing nothing is usually better than doing it carelessly. These four parts need real attention, in this order.

URL mapping, done completely

Every old URL mapped to its closest new equivalent, not just the top 100 by traffic. Long-tail pages carry link equity in aggregate; skipping them is where traffic loss compounds. I build the map from a full crawl, Search Console and Ahrefs exports.

Redirects in one hop

Old to new in a single 301, no chains, no loops, no redirects to the homepage. Every rule tested server-side before launch and crawled again the moment the new site is live.

Hreflang and schema preserved

International shops lose locale targeting if hreflang is not rebuilt on day one, a common cause of post-launch drops in DE or BE. Structured data, canonicals and sitemaps move with it.

Index recovery monitored

For six weeks after launch I check crawl status, indexation and rankings per category, so issues are fixed while Google is still re-crawling, not three months later.

How I work

Three phases, with the planning before the build.

Most migrations fail because the SEO planning starts after development. The order needs to flip.

01 / PRE-MIGRATION
Map everything before code moves

Full URL inventory of the current site, traffic and links per URL, the mapping to the new structure, the redirect sheet, hreflang and schema plan. This is 60% of the work and starts weeks before launch.

Screaming FrogAhrefsSearch Console exportsURL map sheet
02 / LAUNCH WEEK
Test, launch, stay in the room

Redirects deployed and tested, the new site crawled the moment it is live, schema and hreflang verified, sitemaps submitted. I am available during the launch window, and where the stack allows I implement fixes myself rather than queueing tickets.

Pre-launch crawlRedirect testingGSC submission
03 / POST-LAUNCH
Six weeks of active monitoring

Daily crawl and indexation check, rankings compared per category, drops investigated within 48 hours. You get a running change log and a short weekly update, so you always know what was done and why.

Daily crawlPer-category rankingsLooker Studio
Why this approach

The work most teams discover too late.

A migration is high stakes and rarely repeated. A botched one costs months of recovery; a good one launches with the SEO equity intact and room to grow. The difference is discipline, not luck.

Plan-heavy

Most of the work happens before launch day. Surprises after launch are the cost of skipping that.

Stack-aware

Lightspeed to Shopify, WooCommerce relaunches, PrestaShop, custom to headless, subdomain to ccTLD. I have worked on these stacks and know where each one breaks.

Hands-on

I read server logs, write SQL and configure redirects. When the fix is small, I ship it instead of writing a ticket about it.

Independent

No conflict of interest with your developer or platform vendor. I represent the SEO outcome.

Planning a replatform, domain change or URL restructure?

Book a free 30-minute consultation. Share what you are migrating and when, and I will sketch the risks and a realistic timeline. Even if we do not end up working together, you leave with something actionable.

Book a consultation
30-minute call, no obligation.
Migration scope review before we talk.
Concrete next steps to keep.
Scroll to Top