Site Migration SEO: Move Your Website Without Losing Rankings
A site migration that goes wrong can cost you 30-70% of organic traffic and take months to recover. Done correctly, a migration should result in less than 5-10% temporary traffic fluctuation that recovers within a month. The difference is preparation and execution.
Step 1: Crawl the current site before touching anything
Use Screaming Frog or a similar crawler to generate a complete list of all current URLs, their titles, meta descriptions, H1s, and canonical tags. Export your full sitemap. Check Google Search Console for your top-performing pages by clicks and impressions. This baseline is essential - you cannot confirm a successful migration without it.
Step 2: Map every old URL to its new URL
Create a spreadsheet with every old URL and its corresponding new URL. For domain migrations: old.com/page maps to new.com/page. For URL restructures: /old-slug maps to /new-slug. For pages with no direct equivalent, map to the most relevant existing page or to the new homepage as a last resort. Every old URL must have a destination - broken redirects are the most common cause of post-migration traffic loss.
Step 3: Implement 301 redirects before going live
Set up 301 redirects from every old URL to its new destination. Test every redirect before launch. Use a tool like httpstatus.io to verify each old URL returns a 301 with the correct Location header. Never use 302 for a site migration - 302 tells Google the move is temporary and full PageRank transfer does not happen. Redirect chains (old URL to temp URL to new URL) lose equity at each hop - make sure all redirects go directly to the final destination.
Step 4: Update your sitemap immediately
As soon as the new site is live, publish a sitemap.xml containing only the new URLs. Submit it to Google Search Console immediately. Remove the old property from Search Console or leave it to track crawl errors. Submit the new sitemap to Bing Webmaster Tools as well. The updated sitemap signals to Google that the new URLs are the canonical versions.
Step 5: Update internal links
Internal links still pointing to old URLs create redirect hops on every page load and waste crawl budget. Do a database-level find-and-replace to update all internal links to the new URLs. In WordPress, use the Better Search Replace plugin. In a custom CMS, run SQL updates. In static sites, update in source files. Verify no internal links point to old URLs after the update.
Step 6: Monitor for 4 weeks post-migration
Check Google Search Console daily for the first two weeks and weekly for the next two. Watch for: crawl errors on new URLs (configuration issues), drop in indexed pages (redirect problems), sharp traffic drops on specific pages (missed redirects or canonical issues). Most migration traffic drops are temporary - Google typically re-stabilizes within 2-4 weeks as it processes the redirects and re-crawls the new structure.