Service 05 · Risk control
Website Migration SEO: Protect Rankings Through Every Release
Replatforms, redesigns and domain moves planned as engineering releases — with a redirect matrix, pre-flight checks and rollback criteria agreed before launch.
Most migration traffic losses aren’t bad luck. They come from unmapped URLs, redirect chains and staging settings that ship to production. As your SEO migration consultant, we treat the move like any other release: inventoried, tested on staging, verified on launch day and monitored until search engines have fully re-processed the site.
migration-scope.yml
INVENTORY
every indexed, linked & trafficked URL
MAPPING
one-to-one redirect matrix, zero chains
STAGING
indexability, canonicals, render parity
LAUNCH
redirects, robots.txt, sitemaps, tracking
MONITOR
logs, coverage & rankings for 8–12 weeks
Sound familiar?
Signs your migration needs an SEO plan.
A replatform or redesign has a launch date — but no redirect plan yet.
The new site lives on staging and nobody has crawled it as Googlebot.
The plan for retired URLs is “redirect everything to the homepage”.
You’re changing domain, merging subdomains into subfolders or moving to HTTPS.
Traffic fell after a launch and the old URL list no longer exists.
Agency, developers and marketing each own part of the move — and nobody owns search.
The difference
Why migrations lose traffic — and how to avoid it.
Website migration SEO is the discipline of changing a site’s platform, structure or address without breaking the signals search engines have built up for every URL.
Rankings belong to URLs. When those URLs change, Google has to discover each new address, follow the redirect, re-crawl, re-render and re-evaluate the page before its signals consolidate. Every missing redirect, redirect chain, changed canonical, lost internal link or stripped block of content adds friction — and across thousands of pages the losses compound. Most post-launch drops trace back to a handful of template-level mistakes, not to Google simply “needing time”.
We plan migrations from the server outward: crawl and log data define what must be preserved, the redirect matrix is version-controlled alongside your code, and staging is validated before a single DNS record changes. If you need a clean baseline first, start with a technical SEO audit. Moving a store to Shopify or another platform? Pair this with our ecommerce technical SEO work — and if the new front end is a JavaScript framework, JavaScript SEO checks rendering parity before launch.
What’s included
Every migration type, one controlled process.
Four kinds of move put organic traffic at risk. Four workstreams keep it — whichever combination your project involves.
Replatforming SEO
Moving to Shopify, headless or a new CMS: URL patterns, faceted navigation, templates and app-injected markup mapped before the switch.
Domain changes
Rebrands and domain consolidation with Search Console Change of Address, edge-level redirects and backlink equity preserved.
Redesigns & URL restructures
New information architecture without orphaned pages: internal links, breadcrumbs and category hierarchies rebuilt deliberately.
HTTPS & subfolder consolidation
Folding subdomains into subfolders or switching protocol without mixed content, split signals or canonical conflicts.
URL inventory & benchmark
Every URL from crawls, sitemaps, logs, analytics and backlinks — with traffic, rankings and vitals captured as the baseline.
Redirect mapping
A one-to-one redirect matrix with pattern rules, tested for chains, loops and non-200 targets, delivered as code-ready config.
Staging pre-flight
Crawl and render tests on staging: indexability, canonicals, hreflang, structured data and content parity with production.
Launch & monitoring
Launch-day verification, log monitoring and a defined rollback threshold, then weekly reporting through re-indexing.
How a migration works
Five phases, each with a go/no-go.
Deliverables
URL inventory & pre-launch benchmark
Redirect matrix (CSV + server/edge config)
Staging pre-flight report with blocker tickets
Launch-day checklist & sign-off
Rollback criteria agreed in writing
8–12 weeks of monitoring reports
Inventory & benchmark
We build the master URL list from crawls, XML sitemaps, server logs, analytics and backlink data, then snapshot rankings, traffic, indexation and Core Web Vitals per template — the yardstick every post-launch number is measured against.
Redirect matrix
Every legacy URL gets one destination with the closest equivalent content — never a blanket redirect to the homepage. Pattern rules handle scale, exceptions are listed by hand, and the whole matrix is tested for chains, loops and non-200 targets before it ships.
Staging pre-flight
We crawl staging as Googlebot, diff raw and rendered HTML against production, and check canonicals, hreflang, structured data, internal links and page weight. Blockers become tickets with acceptance criteria.
Launch-day checks
On release we verify robots.txt, noindex removal, redirects at sample and full scale, XML sitemaps, Search Console settings and analytics tags — within the first hours, not the first week.
Monitoring window & rollback
For 8–12 weeks we watch logs, coverage, 404 rates and rankings by template. Rollback criteria are agreed before launch, so a bad release is reverted on evidence instead of debated.
What changes
Launch day becomes a checklist instead of a gamble. Your team knows which URLs move where, what “healthy” looks like after release, and exactly when to act if it isn’t.
Sample output
A redirect matrix, tested before it ships.
Every legacy URL mapped to one destination and validated for chains, loops and status codes — plus a launch-day checklist with pass/fail criteria your team signs off together.
redirect-map.csv · illustrative
OLD URL
NEW URL
STATUS
CHECK
/products/blue-widget-xl
/products/widget-blue-xl
301
✓
/category/widgets?page=2
/collections/widgets?page=2
301
✓
/blog/2019/05/replatform-guide
/blogs/guides/replatform-guide
301
✓
/old-shop/sale
/sale → /collections/sale
301×2
✗
/about-us.html
/pages/about
301
✓
1,842 URLs mapped · 5 shown
1 chain detected → fix before launch
launch-day.log · sample
robots.txt
✓ pass
canonicals
✓ pass
noindex removed
✓ pass
sitemap submitted
✓ done
404 rate · 0.3%
⚠ watch
T+2h after release · re-check at T+24h
When to bring us in
Who migration SEO is for.
REPLATFORM
Ecommerce replatforms
Moving from Magento, WooCommerce or a custom build to Shopify or headless — where product, category and filter URLs all change at once.
REBRAND
Domain & structure changes
A new brand name, a consolidated domain, or country sites folded into subfolders — where every backlink and signal has to follow.
RECOVERY
Migrations that already went wrong
Traffic dropped after launch. We rebuild the old URL set from logs, analytics, archives and backlinks, then repair redirects, content and internal links.
Investment
Fixed scope, quoted upfront.
Pricing depends on URL count, platform and how many migration types are combined. You’ll receive a fixed quote after a 30-minute scoping call — ideally eight or more weeks before your launch date.
Related services
Often paired with a migration.
Technical SEO Audit
Establish a clean baseline before you move, so the migration fixes technical debt instead of carrying it over.
Explore the audit →
Ecommerce Technical SEO
For catalogue migrations where faceted navigation, variants and pagination change with the platform.
Explore ecommerce SEO →
Core Web Vitals Optimization
So the new templates launch faster than the old ones — and field data proves it.
Explore Core Web Vitals →
FAQ
Website migration SEO questions.
Anything else? Ask us directly — we reply within two working days.
When should SEO be involved in a website migration?
As early as possible — ideally while the new platform and URL structure are being chosen, and at least six to eight weeks before launch. Redirect mapping and staging fixes take time, and URL decisions made without SEO input are the most expensive to reverse later.
Will we lose traffic during a migration?
Some short-term fluctuation is normal while Google re-crawls and re-processes the site. A well-executed migration usually stabilises within weeks; sustained losses almost always point to missing redirects, changed content or indexability problems that can be identified and fixed.
What is redirect mapping?
Redirect mapping pairs every legacy URL with the most relevant new URL and implements a permanent (301 or 308) redirect. Good maps are one-to-one where possible, avoid chains and loops, and never send unrelated pages to the homepage — Google tends to treat those as soft 404s.
Do you handle Shopify and other replatforming projects?
Yes. Replatforming SEO is a core part of this service — including moves to Shopify, where fixed URL prefixes such as /products/ and /collections/ make careful mapping essential, as well as WordPress, headless and custom stacks.
Can you recover a migration that has already gone wrong?
Usually, yes. We reconstruct the pre-migration URL set from server logs, analytics, backlink data and web archives, identify what was lost, and restore redirects, content and internal links in priority order. The sooner recovery starts, the more signal is retained.
How long should redirects stay in place?
Treat them as permanent. Google recommends keeping redirects for at least a year, but backlinks and bookmarks keep sending people to old URLs far longer — so we recommend leaving them in place indefinitely and keeping the matrix in version control.
Next step
Launch the new site without losing the old one’s rankings.
Tell us what’s moving, where to and when. You’ll get a scoped migration plan with a fixed price within a few days.