Site Migration SEO: Move Your Site Without Losing Rankings
Site migrations — whether a domain change, CMS switch, URL restructure, or platform relaunch — are one of the highest-risk technical SEO operations you can perform. Without proper planning, a migration can wipe out months or years of accumulated ranking signals in a matter of days. The good news is that a well-executed migration can be nearly invisible to Google: rankings hold, traffic continues, and the new site inherits all the authority of the old one. The difference lies entirely in preparation and execution.
Before migration: baseline documentation
Document everything before you change anything. Export your current sitemap and save all URLs. Screenshot your Google Search Console Performance data for the last 6 months - clicks, impressions, and top queries. Export your top 50 pages by organic traffic from Google Analytics. Note your current Core Web Vitals scores. This baseline is essential for diagnosing any traffic drops after migration and for measuring recovery.
URL mapping and redirect planning
If any URLs are changing (domain change, URL structure change, or CMS migration), create a complete URL mapping document before launching. Every old URL needs a 301 redirect to its new destination. Map old URL to new URL for every single page - not just your homepage. Use a crawler to export all current URLs. Never launch a migration with unmapped URLs.
Pre-launch checks on staging
Before going live, verify on staging: all redirects work correctly and go to the right destinations, not to the homepage, not to 404. The new site is blocking search engines in robots.txt (correct for staging). Canonical tags point to the correct production URLs. Structured data is valid. Core Web Vitals are equal or better than the current site. SSL is configured correctly. All internal links use the new URL structure.
Launch day checklist
Remove the noindex/disallow from the staging environment or enable it on production. Verify robots.txt on production allows crawling. Submit the new sitemap to Google Search Console immediately. Use URL Inspection to request indexing for your most important pages. Monitor Google Search Console for crawl errors in real time. Set up a 404 error alert if possible.
Post-migration monitoring
Check Google Search Console daily for the first two weeks: Coverage report for new crawl errors, Performance report for impressions and clicks, and Core Web Vitals for any regressions. In Google Analytics, compare organic traffic week-over-week. Some temporary traffic fluctuation is normal during a major migration. A drop of 10-20% during processing is common and usually recovers within 4-8 weeks if redirects are implemented correctly.
Informing Google about domain changes
If your migration involves a domain change (e.g., old-domain.com to new-domain.com), use Google Search Console's Change of Address tool after launching. This sends a direct signal to Google that speeds up the transfer of authority from the old domain to the new one. The tool is found in Search Console under Settings. Both the old and new domain must be verified properties. Keep the old domain's Search Console property active for at least 6 months after migration so you can monitor crawl activity and catch any indexing issues on the old domain.
Managing internal links during a URL structure change
When URLs change as part of a migration, it is not enough to just set up 301 redirects — you should also update every internal link in your content, navigation, and templates to point directly to the new URLs. Relying on redirects for internal links wastes crawl budget on every hop and reduces the efficiency of PageRank flow through your site. Run Screaming Frog against your new site immediately after launch and filter for internal links that still point to old URLs, then batch-update them in your CMS or database.
Handling CMS-to-CMS migrations
CMS migrations (e.g., from WordPress to Webflow, or Drupal to Next.js) frequently introduce URL structure changes, different canonical formats, and altered metadata templates. Before switching, export every live URL from your current CMS and confirm each one has a matching entry in the new CMS or a redirect. Pay special attention to auto-generated URLs for tags, categories, author archives, and pagination — these are often overlooked and result in hundreds of new 404 errors. Test your new CMS template output for correct title, description, canonical, and robots meta tags before going live.
Re-building internal link equity after migration
A site migration resets the crawl depth distribution of your content. Pages that were well-linked internally may become orphaned if navigation templates change. After migration, run an internal link audit using Screaming Frog or Ahrefs site crawler to identify pages with zero or very few internal links pointing to them. Prioritize adding internal links to your highest-value pages from relevant existing content. Pages discovered only through sitemaps and not through internal links are crawled less frequently and receive weaker authority signals.