Website migrations are among the highest-risk activities in digital marketing. Whether you are changing domains, switching platforms, restructuring URLs, or moving to HTTPS, a poorly executed migration can erase years of SEO progress in days. Conversely, a well-planned migration can preserve your rankings and even improve them when combined with a site upgrade.
This guide covers the essential best practices for executing a website migration without losing the traffic and authority you have built.
Types of Website Migrations
Understanding which type of migration you are undertaking determines your risk level and planning requirements. Domain change (e.g., oldsite.com to newsite.com) carries the highest risk to SEO. Platform change (e.g., Wix to WordPress) involves URL structure and technical changes. HTTPS migration (HTTP to HTTPS) is lower risk but still requires careful redirect handling. URL restructuring (e.g., changing /blog/post to /resources/post) affects internal and external links. Site redesign with URL changes combines multiple risk factors. Each type may overlap, and the more changes you make simultaneously, the harder it is to diagnose any post-migration issues.
Pre-Migration Planning
Comprehensive Crawl
Before touching anything, crawl your existing site completely. Use Screaming Frog, Sitebulb, or a similar tool to capture every URL on the site (HTML pages, images, PDFs, all resources), each URL’s traffic (from Google Analytics), each URL’s backlinks (from Ahrefs, Moz, or SEMrush), current redirects already in place, meta data (titles, descriptions, canonicals), and internal linking structure. This crawl is your migration map. Every URL with traffic, backlinks, or business value must either exist on the new site or redirect to the most relevant equivalent page.
Build Your Redirect Map
The redirect map is the most critical migration document. For every old URL, specify the corresponding new URL. Rules for redirect mapping include one-to-one redirects wherever possible (old page to its direct new equivalent), using 301 (permanent) redirects, not all URLs redirecting to the homepage (this is treated as a soft 404), preserving URL structure where possible, redirecting old images and PDFs to new equivalents, and ensuring redirect chains do not exceed two hops (ideally, one). For large sites, automate redirect generation using patterns (regex) where URL changes follow consistent rules, and manually handle exceptions.
Staging Environment Testing
Build the new site on a staging environment (with noindex, nofollow, and password protection or IP restriction). Test all redirects by crawling the staging site and verifying that every old URL reaches its intended destination. Check that the new site has no broken internal links, that all meta data, schema, and tracking codes are in place, that page speed meets your targets, and that mobile experience is fully functional.
Migration Day Execution
Choose Your Timing
Migrate during a low-traffic period. For most businesses, this means early in the week (Monday or Tuesday), during off-peak hours, avoiding seasonal peaks or marketing campaign periods, and allowing yourself the full week for monitoring and fixes.
Implementation Checklist
Execute in this order: implement all redirects, verify redirects are working (test a sample of high-value URLs), update internal links on the new site to point to new URLs (not relying on redirects for internal navigation), update XML sitemap with new URLs, submit new sitemap in Google Search Console, add both old and new properties in Search Console, use the Change of Address tool (for domain moves), update Google Analytics to track the new domain/URLs, verify all tracking codes are firing, test all forms, checkout processes, and conversion points, and update external profiles (Google Business Profile, social media, directories) with new URLs.
Post-Migration Monitoring
Week 1: Intensive Monitoring
Check daily: redirect functionality (crawl the old URLs and verify they reach the correct new pages), Google Search Console for crawl errors and indexing issues, traffic patterns compared to baseline, Core Web Vitals on the new site, and user-reported issues. Fix any broken redirects immediately — every day a high-traffic page returns a 404, you lose link equity and user trust.
Weeks 2-4: Indexing Verification
Monitor how Google is indexing the new site. Track the number of new URLs indexed, the number of old URLs still appearing in search results, ranking positions for priority keywords, and crawl stats in Search Console. It is normal for rankings to fluctuate during this period. A temporary dip of 10-20% is common and typically recovers within 4-8 weeks for a well-executed migration.
Months 2-6: Recovery and Growth
By month two, the initial indexing transition should be complete. Focus on comparing organic traffic against baseline month-over-month and year-over-year, identifying specific pages or sections that lost traffic, analysing whether lost traffic is a ranking issue or an indexing issue, and monitoring for 404 errors from external links pointing to unmapped old URLs. Keep redirects in place permanently. Removing redirects after a few months is one of the most common causes of late-stage migration traffic loss.
Common Migration Mistakes
Incomplete redirect mapping: Missing even a few high-traffic URLs can cause significant traffic loss. Crawl the old site thoroughly and verify every redirect.
Redirecting everything to the homepage: This signals to Google that the old pages no longer exist — their rankings and authority are lost.
Removing redirects too early: Keep 301 redirects in place indefinitely. There is no penalty for maintaining them, and backlinks from external sites pointing to old URLs will continue passing authority through the redirect.
Not updating Google Search Console: Use the Change of Address tool for domain moves. Without it, Google takes longer to understand the migration.
Changing too many things at once: Combining a domain move, a redesign, a URL restructure, and a content overhaul in one migration makes it impossible to diagnose the cause of any traffic changes. Make changes incrementally where possible.
Conclusion
A website migration is a significant undertaking that requires meticulous planning, careful execution, and patient monitoring. The investment in thorough preparation — comprehensive crawling, detailed redirect mapping, and staging environment testing — pays for itself many times over by preserving the traffic and authority you have spent years building. Treat migration as a high-priority project with dedicated resources, not a side task, and you will emerge with your SEO equity intact and a stronger site to build upon.
