Quick answer
To migrate a website without losing rankings, benchmark your current performance, crawl and map every old URL to its new equivalent, keep content and titles consistent where they rank, test everything on staging, launch with 301 redirects live, then monitor Search Console, analytics and rankings for at least 90 days and fix issues quickly.
Last updated: November 2026
A redesign, a platform move or a domain change can be the best or the worst thing you do for your SEO. Done carefully, you keep your rankings and gain a faster, better site. Done carelessly, you can lose half your organic traffic overnight and spend months recovering.
Most migration disasters come from the same few causes: missing redirects, changed content and URLs without a plan, blocked crawlers, and nobody checking the results afterwards.
This guide gives you a practical, phased plan for UK business websites, with the checks that matter before, during and after launch.
In this guide
- Types of migration and their risk
- Phase 1: Benchmark and plan
- Phase 2: Crawl and map every URL
- Phase 3: Preserve what already works
- Phase 4: Build and test on staging
- Phase 5: Launch day checklist
- Phase 6: Monitor for 90 days
- Common migration mistakes
- Migrating to WordPress or Shopify
- A realistic scenario
- Do you need help?
- FAQs
Types of migration and their risk
- Redesign on the same domain and URLs: lowest risk, but content and structure changes still matter.
- Platform change, for example Wix to WordPress or Magento to Shopify: URLs and templates often change.
- URL structure change: higher risk, because every changed URL needs a redirect.
- Domain change or rebrand: high risk, requires careful redirects and Search Console change of address.
- HTTP to HTTPS or subdomain moves: usually simple, but must be complete.
The more that changes at once, the higher the risk. Where possible, separate big changes into stages so you can isolate problems.
Phase 1: Benchmark and plan
Before touching anything, record your current performance: organic traffic, top landing pages, rankings for key terms, conversions, backlinks and Core Web Vitals. Export Search Console data and save a full crawl of the existing site.
This baseline lets you judge success and identify losses. Decide which pages drive leads and revenue, since they get the closest attention. Set a launch date that avoids your busiest season and does not coincide with other major changes.
Phase 2: Crawl and map every URL
Crawl the old site and list every URL, including pages, images, PDFs and blog posts. Add URLs from Search Console, analytics and your backlink tool, since some pages are not linked internally but still earn traffic or links.
Create a redirect map in a spreadsheet: old URL, new URL, status and notes. Map each page to its closest equivalent. Where pages are merged or removed, choose the most relevant replacement. This map is the single most important document in a migration.
Phase 3: Preserve what already works
Pages that rank well should keep their core content, headings, titles and meta descriptions unless you have a strong reason to change them. Changing too much at once makes it impossible to know what caused a drop.
Keep internal linking logic where possible, preserve schema markup, and carry over image alt text and structured data. If you must restructure, improve while retaining the topics and intent that earn traffic.
Phase 4: Build and test on staging
Build the new site on a staging environment that is blocked from search engines using password protection, not just robots.txt. Test templates, forms, tracking, mobile layouts, speed and accessibility. Crawl the staging site and compare it with your old crawl to find missing pages, changed titles and broken links.
Test your redirect map on staging by loading a sample of old URLs and confirming each lands on the right new page with a single 301. Check that canonical tags, hreflang tags if relevant, structured data and sitemaps are ready, and that analytics and Search Console tracking are installed.
Phase 5: Launch day checklist
- Switch the site live and remove any staging block or noindex tags.
- Confirm the live robots.txt allows crawling and the WordPress search visibility option is off.
- Activate 301 redirects and test a wide sample of old URLs immediately.
- Submit the new XML sitemap in Search Console and request indexing for key pages.
- Check canonical tags, titles, and key pages in a live crawl.
- Verify forms, phone links, tracking and conversion events.
- For domain changes, use the Change of Address tool in Search Console.
Phase 6: Monitor for 90 days
Check Search Console daily for the first week, then weekly. Watch for spikes in 404s, drops in indexed pages, crawl errors and changes in impressions. Compare traffic and rankings to your baseline, allowing for normal fluctuations in the first weeks as Google reprocesses the site.
Fix issues fast: add missing redirects, correct broken links, restore pages that were removed by mistake. A temporary dip is common, but a continuing slide usually points to a fixable technical problem.
Common migration mistakes
- No redirect map, or redirecting everything to the homepage.
- Launching with noindex or a robots.txt block still in place.
- Changing URLs without need.
- Removing content that ranked, including blog posts and location pages.
- Forgetting images, PDFs and old campaign URLs.
- Losing tracking, so nobody can see what happened.
- Declaring victory on launch day and not monitoring.
Migrating to WordPress or Shopify
When moving to a new platform, URL formats often change, for example /blog/post-name becoming /post-name or /products/ replacing /shop/. Decide on the new structure early, build the redirect map around it and test it thoroughly.
Our WordPress website design service and Shopify service include migration planning and redirects as standard, so your SEO value moves with you.
A realistic scenario
A Nottingham accountancy firm moves from an old custom site to WordPress. The firm records its top 30 landing pages, maps 140 old URLs to new ones, keeps the titles and key headings of pages that rank, and tests redirects on staging. On launch day it removes the staging password, confirms robots.txt, submits the sitemap and checks 50 old URLs.
During the following weeks, Search Console flags a dozen missed URLs, which the team redirects the same day. Traffic dips slightly for ten days and then recovers above its baseline, helped by better speed and clearer service pages. The result came from planning, testing and monitoring, not luck.
Do you need help?
Migrations reward preparation and punish improvisation. If your site generates meaningful leads, consider getting a specialist to review the plan. A website SEO audit before the move shows what to protect, and our technical SEO service can handle redirect mapping, launch checks and post-launch monitoring so you do not have to.
Whoever leads the move, agree responsibilities in writing. Decide who owns the redirect map, who signs off staging, who checks the live site on launch day and who monitors results afterwards. Set a rollback plan too: if something critical breaks, you should know how to restore the old site or fix the issue within hours. A clear timeline and named owners turn a risky project into a routine one.
Technical SEO Services
Crawling, indexing, speed and schema fixed properly.
Frequently asked questions
How long does it take to recover rankings after a migration?
A well-managed migration may see only a brief fluctuation of a few weeks. Poorly managed ones can take months, and some losses are permanent if redirects and content were not preserved.
Do I need to redirect every old URL?
You should redirect every URL that has traffic, links or rankings to the closest relevant new page. Truly worthless URLs can return a 404.
Should I change my domain and redesign at the same time?
Avoid it if possible. Separating the changes makes it easier to identify and fix problems.
What should I check first after launch?
Robots.txt, noindex tags, redirects, sitemap submission and Search Console errors, followed by key page rankings and conversion tracking.