Establish a comprehensive baseline of your current organic performance before changing anything. Record keyword rankings for your top 200 keywords, export all indexed URLs from Google Search Console, document current organic traffic by landing page, and crawl your entire site to capture the current URL structure, internal linking, and technical configuration. This baseline is your reference point for measuring migration impact and diagnosing post-migration issues.
Identify every URL that receives organic traffic or has backlinks pointing to it. These are your critical URLs that must be redirected correctly -- losing them means losing their accumulated ranking signals and traffic. Export backlink data from Ahrefs or Semrush alongside Search Console traffic data to create a priority-ranked URL list. URLs with both backlinks and traffic are the highest priority; URLs with neither can be deprioritized or allowed to 404 without significant SEO impact.
Define the migration scope precisely. A domain change, a platform change, a URL structure change, and an HTTPS migration each carry different risk profiles and require different technical approaches. Combining multiple migration types (changing domain AND platform AND URL structure simultaneously) multiplies the risk and makes troubleshooting post-migration issues far more difficult. Where possible, sequence changes so that each can be validated independently before the next change is introduced.
Redirect mapping is the most important technical element of any migration. Every old URL that has organic traffic or backlinks must redirect to the most relevant equivalent URL on the new site via a 301 (permanent) redirect. A redirect to the homepage or a generic category page loses topical relevance and dilutes the link equity that was earned by the original page. Each redirect should point to the closest content match -- the new URL that best satisfies the same user intent as the old URL.
For large migrations involving thousands of URLs, automate redirect mapping using content similarity analysis. Extract page titles, H1 headers, and body text from both old and new sites, then use fuzzy matching algorithms or AI tools to identify the best match for each old URL. Manual review is necessary for the 10-20% of URLs where automated matching produces uncertain results, but automation handles the bulk of the work at a fraction of the manual effort.
Test every redirect before launch. A single misconfigured redirect rule can break thousands of URLs. Use Screaming Frog's list mode to crawl all old URLs and verify that each one returns a 301 status code pointing to the correct destination. Check for redirect chains (old URL redirects to intermediate URL which redirects to final URL) and eliminate them by pointing each old URL directly to the final destination. Redirect chains add latency and lose link equity at each hop.
Set up the new site on a staging environment that is blocked from search engine indexing (via robots.txt, password protection, or HTTP authentication). Crawl the staging site thoroughly using Screaming Frog or Sitebulb to verify that all pages are accessible, internal links are correct, canonical tags point to the right URLs, and no broken links exist. Compare the staging crawl data against your baseline crawl to identify discrepancies in page count, link structure, and technical configuration.
Validate all SEO elements on the staging site: title tags, meta descriptions, heading structures, structured data markup, hreflang tags, and Open Graph tags. Platform migrations frequently lose or alter these elements during content transfer. Build a validation spreadsheet that compares old and new values for a sample of 50-100 critical pages, verifying that nothing was lost or corrupted in the migration process.
Test page speed on the staging environment to ensure the new platform meets or exceeds current performance. Platform migrations often introduce new code, different hosting configurations, or additional third-party scripts that degrade speed. If the new site is slower than the current site, resolve performance issues before launch -- a migration that degrades Core Web Vitals may experience ranking losses even if all redirects are implemented correctly.
Schedule the migration during a low-traffic period to minimize user disruption and simplify monitoring. Implement all redirects simultaneously rather than in phases -- partial redirect implementations create confusing signals for search engines and make troubleshooting more difficult. Verify redirect implementation immediately after launch by spot-checking 50-100 critical URLs from different site sections.
Submit the new XML sitemap to Google Search Console immediately after launch and request indexing for your most important pages using the URL Inspection tool. If the migration involves a domain change, use the Change of Address tool in Search Console to formally notify Google. Remove any staging environment access restrictions (robots.txt blocks, noindex tags, HTTP authentication) that were in place during development -- a surprisingly common post-launch oversight that prevents indexing of the new site.
Monitor server logs and error rates in real-time for the first 24-48 hours after launch. Watch for 404 errors (indicating missed redirects), 500 errors (server problems), redirect loops (circular redirect configurations), and unexpected traffic patterns. Have your development team on standby to fix issues immediately -- every hour that a critical redirect is broken or a server error persists costs organic traffic that took months or years to build.
Post-migration SEO monitoring should continue for at least 90 days. Track keyword rankings daily for the first 30 days, then weekly for months 2-3. Expect some ranking fluctuation in the first 2-4 weeks as Google processes the redirect signals and re-evaluates the new URLs. A temporary 10-20% traffic dip is normal for well-executed migrations; drops exceeding 30% or lasting beyond 4 weeks indicate problems that need investigation.
Monitor Search Console's Index Coverage report daily for the first month. Watch for increases in excluded pages (particularly "Not found 404" and "Redirect error" categories), decreases in indexed pages, and crawl anomalies. If Google continues to index old URLs instead of new ones, verify that redirects return proper 301 status codes and that the new pages do not contain noindex tags or canonical references back to old URLs.
If organic traffic drops significantly post-migration, follow a systematic diagnostic process. First, verify redirects are working correctly for your highest-traffic pages. Second, check that no technical barriers (noindex, robots.txt blocks, canonical errors) are preventing indexation. Third, compare page content and structure between old and new versions to identify any content loss. Fourth, verify that internal linking on the new site distributes authority at least as effectively as the old site. Address issues in priority order based on the traffic value of affected pages, and document every change for future reference.
Part of our complete guide: International SEO →
This article is part of our comprehensive knowledge hub on international seo. Read the full guide for a complete strategic framework.
Our team helps companies implement the frameworks and strategies covered in this article.
Get in Touch