A website migration can be stressful for any business. Whether you’re changing your domain name, moving to a new content management system (CMS), upgrading from HTTP to HTTPS or restructuring your site architecture, your search visibility is at risk.
When done properly, it’s normal for a site migration to have a negative short-term impact on rankings and visibility while search engines process the changes, but long-term, the results should be positive.
When things do go wrong (sometimes permanently so), the issue is rarely the migration itself. It's usually preventable technical errors that lead to catastrophic traffic drops and visibility losses, such as missing redirects or overlooked crawl blockers.
We’ve seen and done our fair share of website migrations here at The Digital Maze and we know it’s just as important to get the technical SEO side of things right as it is the design and web build.
Which is why we created this checklist, designed to help you navigate the migration process smoothly and protect your organic search presence.
What Is a Website Migration?
A website migration is a broad term used in SEO and web development for any major changes to a website’s environment, platform, structure or design, particularly those that could affect its search visibility or indexation.
It’s a bit like moving your shop to new premises, changing its name or giving it a refit. And sometimes all of those things happen at the same time.
Website migrations usually fall into one or more of the following categories:
Platform migration - moving from one CMS to another (e.g. from Shopify to WordPress)
Domain migration - changing your website’s name and web address, which will mean all your URLs will change and your content needs to move from oldsite.com to newsite.com. This also includes TLD (top-level domain) moves, such as moving from .com to .co.uk
Protocol migration - (i.e. moving from HTTP to HTTPS). Google recommends secure sites (and that's pretty standard now), but if you haven't done this yet, moving from HTTP to HTTPS means changing all your URLs
Structural changes - making changes to how your URLs are structured or linked together, such as changing blog posts from website.com/blog-article/ to website.com/news/blog-article/
All of these changes affect the paths search engines take to discover, process and index your content, which is why comprehensive redirect mapping and a robust technical checklist are needed.
Working with Developers for a Smooth Migration
A successful site migration relies heavily on clear and sustained communication between your marketing team and your developers. While the developers will be looking after the build itself, your SEO team’s job is to safeguard your organic visibility, and the foundation of that safeguard is laid during the build.
For a smooth transition from your old site to your new one, you’ll need to ensure your development team has a clear SEO specification before any building work begins. This specification should lay out explicit requirements for your new URL structure, how metadata should be handled, the types of content you need to include on the site and any essential functionality you need from the CMS.
Having a kickoff meeting early in the project - and bringing your SEO team in from the beginning - helps to prevent resource shortages, departmental conflicts and last-minute changes. By collaborating across teams from the start, you ensure that technical SEO requirements are built into the site, rather than added on as an afterthought.
Tools such as Monday.com, JIRA and dedicated Slack channels can be invaluable here.
Phase 1: Pre-launch (Strategy, Planning and Testing)
Properly planning your migration will give you the best chance of retaining rankings and avoiding the technical problems that lead to traffic drops. The pre-launch phase is about gathering your data, setting benchmarks and testing your new setup on staging.
1. Set goals and establish baseline analytics
Two to four weeks before your migration, you need to record exactly how your current site is performing. This baseline data allows you to track the impact of the migration and can help you identify bugs later.
Track traffic retention and targets: Be realistic. It can take some sites many months to fully regain their traffic, so keep this in mind when setting targets.
Gather Google Search Console data: Record your current keyword rankings, your number of indexed pages and your Core Web Vitals reports.
Log GA4 metrics: Document your organic traffic numbers, conversion rates and engagement metrics.
Audit your AI visibility: Use specialised tools to check your brand mentions, citations and sentiment inside LLMs like ChatGPT and Gemini to satisfy answer engine optimisation requirements.
Pinpoint high-value terms: Focus your preservation efforts on the high-value keywords that drive the most commercial value to your business.
Create a rollback plan - if something does go wrong, have a plan in place for restoring the old site.
2. Document architecture and audit the current site
You cannot recreate your site structure on a new platform if you do not know how it is currently built.
Map the site architecture: Document your URL structures, content hierarchy, navigation menus, footer links and page template types, as well as any third-party integrations, filters and search functions.
Map redirects: Map your existing pages to the corresponding pages on your new site, ensuring each redirect points toward a relevant URL (i.e. don’t just map everything to the new homepage). Redirects should also be 301 (permanent) redirects.
Conduct a pre-migration technical audit: Use a crawling tool (such as Screaming Frog or SEMRush) to check your live site's health. Find and fix any existing website errors, duplicate titles, structured data errors and hreflang conflicts before moving anything.
Assess content performance: Run a strategic content audit to find any underperforming pages. Decide whether to improve, consolidate or delete low-value content to preserve your overall topical authority and experience.
Tip
When mapping your redirects, you’ll need to build as comprehensive a list of your current URLs as possible, which means using a few different sources to compile your data, including:
✓ Crawling tools (e.g. Sitebulb or Screaming Frog)
✓ GA4
✓ Search Console
✓ XML Sitemaps
✓ Backlink tools (e.g. Ahrefs)
3. Build and test in a staging environment
A staging site is a copy of your website files and database hosted on a secure subdomain, e.g. staging.example.com. A staging site lets you test changes safely, without affecting your existing visitors.
Block search engines: You must prevent search engine crawlers from indexing your test site. Add password protection through your hosting control panel or use a plugin to keep out users and automated crawlers.
Apply temporary tags: Add a temporary noindex meta robots tag to every page on the staging site.
Match the live setup: If your live site uses a content delivery network to speed up content delivery based on user location, configure this on staging too.
Optimise during the build: Use the migration as an opportunity to compress images, implement lazy loading, check mobile responsiveness and fix your heading structures. Ensure there is only one H1 per page and a logical hierarchy of H2-H4 tags.
Run a technical audit on your staging site: Use a tool such as Screaming Frog, Sitebulb or SEMrush to crawl your staging site and identify any errors that you need to fix before launch.
Configure staging analytics: Set up a separate data stream in GA4 for your staging environment to verify that user interactions and events are tracking correctly before launch.
Set up GA4 and Search Console for the new site: If you’re moving to a new domain, set up and verify your new site as a property in Search Console and GA4, ready for launch.
Phase 2: During Launch (Launch Day Spot Checks)
Launch day is when technical issues are most likely to surface. Your checks must be quick, focused and methodical to prevent search engines from picking up any critical errors.
1. Execute technical switches and backups
Secure your backups: Your developers should take a complete backup of your old website files and database so you can quickly implement a rollback plan if something goes wrong.
Update DNS settings: Work with your hosting provider or developer to point your domain to the new server infrastructure.
Lift the indexing blocks: Crucially, confirm your developers have removed any password protection and deleted the temporary noindex tags from your pages so search engines can access the new live site.
2. Run immediate crawls and validations
Run an immediate live crawl: Crawl the new live website as soon as it goes live to find any unexpected errors.
Validate your URL mapping and redirects: Check that your permanent (301) redirects are working as they should. Make sure your old URLs resolve seamlessly to their correct new destinations and that your key pages load with no issues. You should also avoid redirect chains (where an old URL bounces through multiple pages before reaching its destination), as this dilutes link equity and slows down crawl speeds.
Spot-check critical search signals: Confirm that your robots.txt file is not accidentally blocking search engines and verify that your internal links, metadata and copy have migrated exactly as planned.
Check the XML Sitemap: Crawl the URLs in your XML sitemap and ensure they all return a 200 (OK) status.
Site Migration & SEO In Action
See how we helped long-term SEO client NoBlue2 through a complex site migration involving merging 4 domains into one brand new site, with no loss of search visibility
Phase 3: After Launch (Post-Migration Monitoring and Stability)
The first few days and weeks after launch are the most critical for catching hidden errors, stabilising performance and verifying long-term indexation.
1. Monitor indexation and search engine behaviour
Update Google Search Console: Submit your new XML sitemap to help search engines discover and process your new URL paths. Use the Change of Address tool if your migration involves a domain change.
Track crawl activity: Watch how search engines crawl and process the new site. Monitor indexation status reports closely to catch any unexpected drops or anomalies.
2. Review performance against your baselines
Monitor traffic and visibility changes: Check your daily and weekly rankings against your pre-migration benchmarks. Watch out for sudden drops in traffic or visibility so you can troubleshoot technical flaws before they compound.
Assess long-term stability: Compare your post-migration organic engagement and conversion rates against your original targets.
Decommission any old assets: Once you are confident that search engines have fully processed the migration, your URLs are all correctly indexed and your traffic has stabilised, safely cancel your old hosting accounts.
Conclusion
A website migration is a complex technical process, but following a structured framework reduces the risk of major issues (most web migrations will run into minor ones!).
By auditing your existing site, using a staging environment and closely tracking your search data before and after launch, you can take your website forward without sacrificing your hard-earned search rankings.
Keep your communication lines with your developers clear, use your baseline metrics to spot anomalies early and prioritise the technical health of your URLs to make your 2026 site migration a success.
Site Migration FAQs
How long does an SEO site migration take to stabilise?
Usually, traffic will stabilise within 4-8 weeks following a site migration, although this does depend on the size of your website. Search engines need time to recrawl the old URLs, process the permanent 301 redirects and index the new pages.
Will a website migration permanently hurt my organic traffic?
If you follow the above steps and work closely with your developers to ensure that technical SEO is built into your site from the ground up, a migration should not permanently harm your organic presence. Any big changes to a site do come with a risk, but the long-term benefits (a more up-to-date site, better user experience, faster page load times, etc) will normally outweigh the short-term instability.
Where issues are long-term or permanent, it’s usually because redirects haven’t been mapped correctly or high-traffic-driving content hasn't been migrated, meaning you lose rankings for crucial keywords completely.
Why do websites lose organic traffic during a migration?
Websites lose traffic during a migration mainly due to broken or missing redirects, accidental search engine blocks in the robots.txt file, or unremoved noindex tags carried over from the staging environment.
Should I change my content during a technical site migration?
No, you should avoid making major content changes at the same time as a technical migration. Separating big structural changes from content updates makes it much easier to isolate and troubleshoot the root cause of any performance drops.
What is the difference between a 301 and a 302 redirect during a migration?
A 301 redirect is a permanent change that tells search engines to transfer all ranking power and historical authority from the old URL to the new one. A 302 redirect is strictly temporary. Using 302 redirects during a site migration is a critical error, because search engines will keep the old URLs in their index and will not pass your hard-earned visibility over to the new ones.
How do I notify Google that my website has changed its domain name?
If you are changing your domain name, you need to use the official Change of Address tool inside Google Search Console. This tool alerts Google directly that there’s been a change and works alongside your permanent 301 redirects to speed up recrawling and the safe migration of your index signals from your old domain to the new.
What happens if a site migration goes wrong, and how do I fix it?
If your traffic drops completely immediately after launch, the first place to check is your robots.txt file. Look for any hidden noindex tags carried over from staging and test your redirects for any broken loops.
If the errors are catastrophic and cannot be resolved within a few hours, that's when your rollback strategy comes in. You can restore the old site backup while you diagnose the issues in a safe testing environment.
I’ve been working in digital marketing for over a decade now, both agency-side and in-house. Over the years, I’ve managed the SEO, PPC, email and affiliate campaigns for a major UK retailer, and the SEO, CRO and ongoing website updates for a well-known ISP. Agency side, I have run successful SEO and email campaigns for large high-street retailers, as well as for smaller local businesses. It’s fair to say that I have a broad range of experience in marketing, but SEO is where my heart truly lies!
