A practical, evidence-backed playbook. A successful SEO website migration protects search visibility by combining careful measurement, conservative change management, and systematic testing.
The playbook used by technical SEO teams is simple in concept and exacting in execution:
Expect short-term movement in rankings. With a disciplined approach, most issues are avoidable, and the rest are recoverable within weeks to months.
This guide gives a step-by-step SEO migration plan, the technical checklist you must run through, the common mistakes that break SEO, and clear guidance on when to bring in migration specialists.
Why this matters: migrations introduce risk from the first change you make. A backup taken only "before final cutover" doesn't protect you from mistakes made earlier in the process, so this is step one, not a pre-launch afterthought.
What to back up:
Rollback planning
Why this matters: you cannot protect what you haven't measured. Benchmarks tell you where to focus effort and how to quantify impact after launch.
Action steps
Deliverables to produce before any change:
Why this matters: URL changes are one of the largest causes of migration-related ranking loss. A precise mapping prevents accidental orphaning and broken backlinks.
How to properly do it
Best practices
Why this matters: a migration can also be a legitimate opportunity to improve content and structure. The risk we most often find isn't in improving, it's in doing it unplanned and untested, at the same time as everything else.
Practical rules
Why this matters: 301 redirects are the standard mechanism for preserving link equity and preventing 404s. Improper redirects create chains, loops and lost authority, and can cost you traffic.
Implementation checklist
Testing the redirects
Why this matters: title tags, meta descriptions, H1s, canonicals and schema are on-page signals search engines use to understand relevance and to serve click-through in results. Losing or changing them unnecessarily erodes rankings.
Practical rules
Testing
Why this matters: internal linking is a primary crawling path and distributes link equity across the site. Relying on redirects internally reduces crawl efficiency and risks unnecessary chains.
Action steps
Why this matters: technical regressions (blocked crawling, loss of HTTPS, poor mobile or speed performance, broken JavaScript rendering) can drop rankings almost immediately.
Before launch (on staging)
<meta name="robots" content="noindex"> tag on staging.At launch
Testing & monitoring
Why this matters: Search Console and analytics are how you detect errors, observe indexation and measure impact.
Essential steps
Monitoring cadence
Why this matters: testing on a correctly blocked staging environment prevents premature indexing and stops untested redirects or dead pages from reaching search results.
Pre-launch QA checklist
Why this matters: resources are finite. Protecting the pages that drive revenue, traffic and backlinks reduces immediate business risk.
How to prioritise
Why this matters: a single "big bang" cutover concentrates all migration risk into one moment. On large sites, complex platforms, or anything commercially critical, migrating in phases (by section, template or subdomain) lets you validate real-world behaviour on a smaller slice before committing the whole site.
How to do it
This is a judgement call: for smaller sites, a well-tested single cutover is usually simpler and just as safe.
Why this matters: early detection enables fast fixes. Expect short-term fluctuation, recovery speed depends on execution quality.
Immediate post-launch checks (day 0-7)
Ongoing monitoring (weeks 1-12)
When to take corrective action
Mistake: No redirects, or a mass redirect to the homepage
Avoidance: Map and implement 301s for every changed URL; never redirect all old pages to the homepage.
Mistake: Breaking metadata, content or titles sitewide at launch
Avoidance: Migrate metadata and content unchanged, and improve selectively after baseline comparisons.
Mistake: Staging indexed or left unblocked
Avoidance: Use robots.txt/noindex and password protection for staging.
Mistake: Redirect chains and internal links left pointing to old URLs
Avoidance: Point internal links to final URLs and test for chains before launch.
Mistake: Forgetting Search Console, sitemap, hreflang or HTTPS
Avoidance: Prepare these assets pre-launch and verify them immediately after going live.
Mistake: Inadequate backups or no rollback plan
Avoidance: Take full backups and agree rollback triggers and procedures with stakeholders before work starts, not during an incident.
Mistake: Treating a big, complex migration as a single all-or-nothing cutover
Avoidance: Consider a phased rollout for large or high-risk sites.
Why this matters: changing domains moves the entire brand and historical trust signal at once, on top of everything else a migration already involves. It's not simply another step in the standard flow; instead, treat it as its own project with its own timeline.
If you must change domains
When to avoid a domain change
Consider external help if:
What specialists typically do
Hiring is a risk-management decision: the cost of expert help is often lower than the business impact of lost traffic and revenue.
At MJ Web Studio we offer a full SEO Migration Service.
A condensed, printable version of everything above.
Take full backups and agree rollback triggers with stakeholders.
Crawl and export all URLs; benchmark traffic, rankings and backlinks.
Create the full URL mapping spreadsheet and prioritise high-value pages.
Preserve content parity, metadata, canonicals and structured data.
Implement and test 301 redirects.
Update internal links to point to final URLs.
Block staging from indexing; test performance, mobile and rendering.
Prepare robots.txt, hreflang and XML sitemaps.
Verify GA4 and Search Console setup.
Decide whether a phased rollout makes sense for your site.
Remove staging blocks and deploy production.
Upload robots.txt and submit the sitemap.
Re-run crawls to validate redirects, status codes and metadata.
Monitor Search Console and analytics closely.
Check GSC and analytics daily for the first week, then weekly.
Review server logs for real crawler behaviour.
Fix crawl, indexation and redirect issues immediately.
Reach out to webmasters for backlink updates on high-value links.
Be patient, expect stabilisation over weeks to months.
Site migrations don't need to be traumatic events. The difference between a safe migration and a damaging one is planning and discipline: back up first, audit and benchmark, map and protect every URL, preserve content and metadata, implement clean 301 redirects, update internal links, block and test on staging, and monitor intensively after launch.
When complexity or risk increases, such as large sites, domain moves, or major CMS changes, bring in migration or SEO specialists to manage the work.
With the right checklist, the right order of operations, and disciplined execution, you can migrate with minimal SEO loss and confidence that any temporary disruption will resolve.
SEO migration costs £3,000-£15,000 depending on site size, complexity, and migration type. Small sites (under 500 pages) typically cost £3k-£5k. E-commerce sites cost £5k-£10k. Enterprise migrations cost £10k-£15k+. Consider this: the average failed migration loses 30-50% traffic permanently. Recovering that traffic costs £20k-£50k plus 6-12 months of lost revenue. Prevention is dramatically cheaper than recovery.
Proper SEO migration takes 6-12 weeks depending on site complexity. Planning and mapping take 2-4 weeks. Implementation and testing take 2-4 weeks. Launch and monitoring take 2-4 weeks. This timeline protects your rankings. Rushed migrations (2-4 weeks total) cause mistakes that destroy traffic. The extra time invested upfront prevents 6-12 months of recovery work later.
Simple migrations (HTTPS upgrades, minor redesigns) can be handled internally with careful planning. Complex migrations (platform changes, domain moves, major restructuring) require professional expertise. One redirect mistake, one technical error, one overlooked element can cause permanent ranking loss. Professionals have done hundreds of migrations and know every failure point. The investment in expertise prevents catastrophic mistakes.
Properly executed migrations maintain rankings with 0-5% fluctuation. Rankings may fluctuate temporarily (1-4 weeks) as Google re-crawls and re-evaluates the site, but should stabilize at or above pre-migration levels. Poorly executed migrations lose 20-60% of traffic permanently. The difference is comprehensive planning, perfect execution, and continuous monitoring that catches issues before they compound.
Professional migrations include rollback plans and immediate response protocols. If issues appear post-launch, we identify problems within hours, implement fixes immediately, and monitor continuously until resolved. Most issues caught quickly (first 48 hours) can be corrected with minimal impact. Issues that linger for weeks cause permanent damage. This is why continuous monitoring and expert oversight are non-negotiable during migration.
E-commerce migrations are highest-risk because of product page volume, category structures, and revenue dependence. We map every product URL, preserve category hierarchies, implement faceted navigation SEO, maintain product schema, test checkout processes, and verify all technical elements. Staged rollout (testing with small product subset first) minimizes risk. Continuous monitoring catches issues before they affect revenue.
Yes, post-migration support is included for 30-90 days depending on migration complexity. We monitor rankings, traffic, indexation, and technical health continuously. If issues emerge (ranking drops, crawl errors, indexation problems), we investigate immediately and implement corrections. Most migrations stabilize within 4-8 weeks, but we continue monitoring until performance confirms complete success.
Rushing the process. Most failed migrations happen because businesses set arbitrary deadlines (site launch dates, seasonal events) that force rushed execution. Proper migration takes time—comprehensive planning, thorough testing, and careful monitoring can't be compressed without consequences. The second biggest mistake is treating SEO migration as checklist rather than strategic process requiring expertise. Both mistakes cause permanent traffic loss.