Website Migration SEO Checklist: How to Preserve Rankings During a Site Move
A comprehensive guide to protecting your organic traffic and search rankings during website migrations, covering every critical step from pre-migration planning to post-launch monitoring.
Website migrations are among the highest-risk SEO activities you'll undertake. Whether you're rebranding, changing platforms, restructuring URLs, or moving to a new domain, one misstep can erase years of organic growth in a matter of days. Yet migrations are often necessary for business evolution, technical improvements, or user experience upgrades. The key is executing them with surgical precision, following a comprehensive website migration SEO checklist that protects your hard-earned rankings.
This guide walks through every critical phase of a migration, from initial planning to post-launch monitoring. Used properly, these steps will help you maintain—and sometimes even improve—your organic visibility through the transition. Whether you're handling a simple domain change or a complete platform overhaul, treating SEO as a first-class concern throughout the process is non-negotiable.
Pre-Migration Planning and Audit
The foundation of any successful migration is laid weeks before launch day. Start by conducting a comprehensive technical SEO audit of your current site to establish a baseline. Document everything: which pages rank, which keywords drive traffic, current crawl budget allocation, and existing technical issues. You need this snapshot to measure success and identify problems after launch.
Crawl your entire site using tools like Screaming Frog or Sitemap Generator to capture every URL that currently exists. Export this complete URL inventory—you'll use it to build your redirect map. Pay special attention to pages with existing backlinks, high organic traffic, or conversion value. These are your VIP pages that require extra protection during the move.
Set clear success metrics before you begin. Define what "preserving rankings" means quantitatively: is it maintaining 95% of organic traffic within 30 days? Keeping your top 20 keywords within three positions? Having specific targets lets you objectively evaluate the migration outcome rather than relying on gut feeling. Document current performance in Search Console, Google Analytics, and your rank tracking tool of choice.
The most successful migrations are those where SEO stakeholders are involved from day one of the project, not brought in a week before launch to "check redirects." Early involvement means influencing URL structure, template design, and technical architecture before they're set in stone.
URL Mapping and Redirect Strategy
Your redirect map is the single most critical deliverable of the entire migration process. This spreadsheet maps every old URL to its new equivalent, ensuring no page gets left behind. Start with your crawl data and match old URLs to new ones based on content equivalency, not just similar paths. The goal is one-to-one mapping wherever possible—each old page should redirect to the most relevant new page.
Use 301 (permanent) redirects exclusively for migrations, never 302 (temporary) redirects. A 301 signals to search engines that the move is permanent and passes the vast majority of ranking authority to the new URL. Implement redirects at the server level (via .htaccess, Nginx config, or your platform's redirect manager) rather than JavaScript or meta refresh, which don't pass authority reliably.
Handling Edge Cases and Deleted Content
Not every old URL will have a perfect new match. For outdated content you're intentionally retiring, redirect to the most relevant category or parent page rather than the homepage—homepage redirects dilute relevance signals and frustrate users. If you're consolidating multiple old pages into a single comprehensive resource, redirect all variants to that new page. Document your logic for each edge case so stakeholders understand the decisions.
| Old URL Scenario | Redirect Target | Rationale |
|---|---|---|
| Exact content equivalent exists | New URL (1:1 mapping) | Preserves rankings and user experience |
| Content consolidated into new page | Consolidated page | Maintains topic relevance and authority |
| Outdated content, no direct match | Relevant category/parent page | Better than homepage, maintains context |
| Duplicate/thin content being retired | Canonical version or category | Cleans up index, consolidates signals |
| Completely irrelevant legacy page | 410 Gone (intentional deletion) | Signals deliberate removal, faster deindexing |
Test your redirects thoroughly in a staging environment before launch. Check for redirect chains (A→B→C), loops (A→B→A), and orphaned redirects pointing to non-existent pages. Every redirect should resolve in a single hop with a 200 status code at the destination. Tools like Redirect Path browser extension or bulk redirect checkers can validate hundreds of redirects quickly.
Technical Implementation Checklist
Beyond redirects, dozens of technical elements need attention during a migration. Update all internal links to point directly to new URLs rather than relying on redirects—this reduces redirect hops and preserves crawl budget. If your new platform uses different URL parameters or session IDs, configure canonicalization properly to avoid duplicate content issues.
Migrate your XML sitemaps to reflect the new URL structure, ensuring they only contain canonical URLs with 200 status codes. Submit the new sitemap through Google Search Console immediately after launch. Keep your old sitemap live temporarily to help search engines discover redirects, but ensure old URLs return proper 301 codes, not 200s.
Preserve your existing robots.txt file unless you're intentionally changing crawl directives. Accidentally blocking important sections during migration is a common catastrophe that tanks rankings overnight. Similarly, verify that meta robots tags, X-Robots-Tag headers, and noindex directives match your pre-migration configuration unless you have specific reasons to change them.
If you're moving to a new domain, update all structured data (Schema.org markup) to reference new URLs. Verify that organization markup, local business data, and breadcrumb schemas still validate correctly. Update your NAP (Name, Address, Phone) citations if domain or branding changes affect your local SEO presence. For multilingual sites, ensure hreflang tags point to correct new URLs across all language versions through proper multilingual SEO strategy.
Core Web Vitals and Performance
Migrations often coincide with platform or hosting changes that impact page speed. Before launch, test Core Web Vitals (LCP, INP, CLS) on the new site to ensure performance isn't regressing. A migration that improves technical SEO but tanks page speed trades one problem for another. Run Lighthouse audits on representative pages and compare scores to your current site.
Pay special attention to mobile performance, since Google uses mobile-first indexing. Ensure responsive design works correctly, touch targets meet accessibility guidelines, and viewport configuration is proper. Test on actual devices, not just browser emulators, since real-world performance can differ significantly from lab conditions.
Launch Day Execution
Schedule your migration during your lowest-traffic period—typically weekends or early weekday mornings—and never during peak business seasons. Have your full technical team available for at least 24 hours post-launch to address urgent issues. Create a rollback plan with clear decision criteria: if traffic drops more than X% or critical errors affect Y% of pages, you need a predefined process to revert quickly.
Immediately after launch, smoke-test critical paths: homepage loads correctly, key landing pages return 200 codes, high-value conversion pages function properly, and redirects from important old URLs work as expected. Check Search Console for crawl errors and Coverage report anomalies. Monitor server logs for unusual patterns of 404 errors or redirect loops that might indicate mapping mistakes.
Use the Change of Address tool in Google Search Console if you're moving domains. This signals Google about the migration and helps maintain rankings during the transition. Update all Google Business Profile locations to reflect new URLs if you're changing domains. Notify Bing Webmaster Tools similarly—while Google dominates, ignoring Bing means abandoning 10-15% of potential traffic.
Audit a sample of pages using "site:" searches to verify they're being indexed under new URLs. Check that title tags, meta descriptions, and heading structures migrated correctly. Review a handful of high-value pages manually to ensure on-page optimization elements like internal linking, image alt text, and content hierarchy survived the move intact.
Post-Migration Monitoring and Recovery
The first 30 days after launch require intensive monitoring. Track organic traffic daily, comparing to pre-migration baselines and accounting for normal seasonality. Watch keyword rankings for your most valuable terms—some fluctuation is normal, but sustained drops of more than 5-10 positions signal problems requiring immediate investigation.
Monitor Search Console's Coverage report for indexing issues. A spike in excluded pages or errors indicates redirects failing or new pages blocked from crawling. Check the "Discovered - currently not indexed" status, which can increase temporarily as Google recrawls your site but shouldn't grow indefinitely. Review the Enhancements reports to ensure structured data remains valid.
Analyze your backlink profile to identify external links still pointing to old URLs. While redirects preserve link equity, direct links to new URLs are ideal. Reach out to high-authority sites linking to important pages and request URL updates. Update any links you control directly: social media profiles, business directories, partner sites, and press releases.
Set up custom alerts in Google Analytics for unusual traffic patterns: sudden drops in sessions from organic search, spikes in bounce rate, or decreases in pages per session. These can indicate user experience issues or content not matching search intent on new URLs. Segment your data by landing page to identify specific pages underperforming post-migration.
If you notice ranking drops, diagnose methodically. Check the specific URLs that lost rankings—are they redirecting correctly? Does the new page maintain content parity with the old version? Are internal links pointing to it from relevant pages? Sometimes rankings dip temporarily as Google reassesses the new URLs, but persistent drops beyond 2-3 weeks require intervention. Working with an experienced team that offers technical SEO audit services can help identify subtle issues you might miss.
Document everything you learn during the migration. Note which assumptions were correct, which issues caught you by surprise, and what you'd do differently next time. This institutional knowledge is invaluable for future migrations or when advising other teams. A migration is never truly "done"—vigilant monitoring should continue for at least 90 days, with periodic check-ins quarterly for the first year to ensure long-term stability.