SEO Migration Checklist
Share
On this page: Quick jump links to help you
- What Is an SEO Migration
- Types of SEO Migrations
- Pre-Migration Planning and Preparation
- Complete SEO Migration Checklist
- URL Mapping and Redirect Strategy
- Content and On-Page Migration
- Post-Migration Monitoring
- Common Migration Mistakes and How to Avoid Them
An SEO migration checklist is a comprehensive plan and verification list that guides organizations through moving their website in ways that preserve or enhance search engine visibility. Website migrations carry significant SEO risk; a poorly executed website migration SEO plan can cause dramatic traffic loss that takes months or years to recover. Well-planned and executed migrations preserve all accumulated authority, maintain or improve rankings, and minimize disruption to search visibility. This guide provides the detailed checklist and strategic guidance needed to execute migrations that protect and enhance your SEO position.
Site migration can take many forms: moving to a new domain, changing your site architecture dramatically, migrating from HTTP to HTTPS, moving from one CMS to another, or consolidating multiple websites. Each type of migration carries specific risks and requires different preparation. Without proper planning, migrations frequently result in loss of rankings, pages removed from index, traffic drops of 20-70%, and significant business impact. The good news is that with proper planning and execution, migrations can be completed successfully with minimal impact.
This guide walks through types of migrations, pre-migration planning and preparation, detailed checklists for migration execution, URL mapping and redirect strategies, handling content and on-page elements properly, post-migration monitoring, and common mistakes to avoid. Whether you're planning your first migration or executing a complex multi-domain consolidation, this framework provides the detailed guidance for successful migration.
What Is an SEO Migration
An SEO migration is any significant change to your website's structure, technology, or location that impacts how search engines crawl, index, or rank your content. Unlike content updates or routine optimization, migrations are substantial changes that typically happen infrequently but carry high risk if not executed properly.
What constitutes a migration requiring comprehensive SEO planning? Changes that require migration planning include: moving to a new domain or subdomain; changing your URL structure significantly; converting from HTTP to HTTPS; switching to a new CMS or platform; major site redesigns with structural changes; consolidating multiple websites into one; launching responsive design dramatically different from previous version; moving website to different server or infrastructure; and implementing significant information architecture changes.
Not all website changes are migrations. Routine content updates, minor design tweaks, performance optimizations, and parameter changes typically don't require migration planning. However, when something impacts your overall site structure, technology foundation, or crawlability, migration planning should be involved.
The reason migrations are high-risk is that they affect the foundations on which your search visibility rests. If you change URLs, all your accumulated link equity needs to transfer through redirects. If you change your CMS, technical SEO implementation needs to be replicated in the new system. If you restructure your site architecture, internal linking patterns change. These foundational changes can disrupt rankings unless managed carefully.
Types of SEO Migrations
Different types of migrations carry different risks and require different migration strategies. Understanding your migration type helps you plan appropriately.
| Migration Type | Description | Risk Level | Key Challenges | Timeline |
|---|---|---|---|---|
| Domain migration | Moving from one domain to a completely different domain | Very High | Transferring all link equity; updating all external links; 301 redirects at scale; authority transfer lag | 6-12 months recovery |
| Subdomain to root domain | Moving content from subdomain (blog.example.com) to root domain (example.com) | High | Authority consolidation; URL mapping; potential mixed signals; duplicate content during transition | 3-6 months recovery |
| HTTPS migration | Converting from HTTP to HTTPS (SSL/TLS encryption) | Medium | Redirect setup; mixed content issues; external link updates; certificate installation | 2-4 weeks stabilization |
| CMS migration | Moving from one CMS platform to another (WordPress, HubSpot, custom platform) | High | URL structure changes; technical SEO replication; 301 redirect setup; content migration accuracy | 4-8 weeks recovery |
| Site architecture restructure | Significant changes to site information architecture and URL structure | High | URL mapping complexity; internal linking changes; sitemap updates; 301 redirect chains | 3-6 months recovery |
| Consolidated domain merge | Combining multiple domains into a single domain | Very High | Managing multiple sets of redirects; consolidating authority; duplicate content; complex mapping | 6-12 months recovery |
| HTTPS + domain migration | Combining domain migration with HTTPS conversion | Extremely High | All risks of both migrations simultaneously; difficult to isolate which changes cause problems | 9-18 months recovery |
| Mobile-first redesign | Major redesign optimizing for mobile-first experience | Medium | Maintaining desktop experience; JavaScript rendering; mobile-specific UX; Core Web Vitals | 2-4 weeks stabilization |
The most risky migrations combine multiple changes simultaneously (domain migration plus HTTPS plus CMS migration, for example). When possible, break migrations into phases so you can isolate problems and recover from issues more easily. A less risky approach would be: Phase 1 move to HTTPS on old domain with old CMS, Phase 2 migrate to new CMS on same domain, Phase 3 migrate to new domain. This breaks the migration into manageable pieces.
Pre-Migration Planning and Preparation
Successful migrations don't happen by accident; they require extensive planning and preparation before the migration date. Typically, pre-migration planning takes 4-12 weeks depending on website size and complexity.
Establish project governance: Create a migration project team with clear roles. Designate a migration project manager who owns timeline and coordination. Identify SEO lead, technical lead, content lead, QA lead, and business owner. Establish decision-making authority—who makes final decisions if conflicts arise? Schedule regular meetings so team stays coordinated and issues surface quickly.
Document current state: Create comprehensive documentation of your current website before migration begins. Document all URLs, title tags, meta descriptions, heading structure, internal links, and important content. Document technical implementation details like canonical tags, robots directives, structured data, redirects, and any other elements that affect SEO. This documentation serves as reference if you need to troubleshoot issues after migration.
Complete SEO audit: Run comprehensive SEO audit before migration. Document current rankings, organic traffic by page and keyword, technical issues, and content performance. This baseline is critical for measuring migration impact. You'll compare post-migration performance against this baseline to identify what's working and what needs adjustment.
Set realistic expectations: Educate stakeholders that all migrations cause some performance disruption. Search engines need time to recrawl your site, reindex, and reestablish rankings. Expect 2-4 weeks for stabilization on smaller migrations, 2-4 months on larger ones. Set baseline expectations so stakeholders understand that some ranking drops are normal during migration recovery.
Plan URL mapping: Create detailed URL mapping document showing how every old URL maps to new URLs. For each mapping, note whether it's direct 1-to-1 mapping, consolidation of multiple pages to one, or splitting of one page to multiple. This mapping drives your 301 redirect setup and ensures no pages are orphaned during migration.
Design redirect strategy: Plan how redirects will be implemented. Most use 301 redirects at the web server level (Apache, Nginx) for maximum efficiency. Some use .htaccess rules for pattern-based redirects. Others use CMS-level redirects if server-level redirection isn't available. Map out your strategy before migration so implementation is smooth.
Test technical implementation: Test all technical SEO implementation in your new environment before going live. Test that canonical tags point correctly, robots.txt works properly, XML sitemap is complete and valid, structured data validates, HTTPS certificate works, redirects function correctly, and page speed is acceptable. Test with crawling tools to verify everything works before switching over.
Content migration planning: For migrations involving content changes, plan how content will be migrated. If migrating from old CMS to new CMS, determine how content fields will map between systems. Determine if any content rewriting is needed for new system. Plan whether you'll launch with existing content as-is or refresh content during migration.
Communicate with stakeholders: Keep stakeholders informed throughout planning. Share your URL mapping, redirect strategy, testing plan, and expected timeline. Address concerns and gather feedback. Good communication prevents surprises and builds support for the migration.
Complete SEO Migration Checklist
This comprehensive SEO migration checklist covers all elements of successful migration execution.
| Phase | Task | Owner | Due Date | Verification | Status |
|---|---|---|---|---|---|
| Pre-Migration Phase | Create URL mapping document for all pages | SEO Lead | Week 1 | All old URLs have corresponding new URLs; mapping documented and reviewed | Pending |
| Design and document redirect strategy | Technical Lead | Week 1 | Strategy documented; method selected; tools identified | Pending | |
| Complete current SEO audit and documentation | SEO Lead | Week 2 | Baseline metrics documented; current rankings captured; technical issues identified | Pending | |
| Test technical implementation in staging environment | Technical Lead | Week 3 | All technical elements verified; redirects test correctly; no broken internal links | Pending | |
| Conduct pre-migration site crawl and QA | QA Lead | Week 4 | Full site crawled; no critical issues found; checklist items all verified | Pending | |
| Migration Execution | Implement 301 redirects for all URL changes | Technical Lead | Migration Day | All redirects live; spot-check sample redirects work | Pending |
| Deploy new site code to production | Technical Lead | Migration Day | New site fully live; all pages accessible | Pending | |
| Verify HTTPS certificates and redirects from HTTP | Technical Lead | Migration Day | SSL certificates valid; HTTP pages redirect to HTTPS | Pending | |
| Update XML sitemap and submit to GSC | SEO Lead | Migration Day | New sitemap created; submitted to Google Search Console | Pending | |
| Update robots.txt for new site structure | Technical Lead | Migration Day | robots.txt updated; allows crawling of important content; blocks duplicate/private areas | Pending | |
| Verify all technical SEO elements in production | SEO Lead | Migration Day +1 | Canonical tags correct; robots meta tags appropriate; structured data validates | Pending | |
| Submit updated sitemaps and crawl URLs to GSC | SEO Lead | Migration Day +1 | New URLs submitted for crawling; GSC begins reindexing | Pending | |
| Notify major partners of URL changes | Business Owner | Migration Day | Partners notified; major referring domains aware of changes | Pending | |
| Post-Migration (First Week) | Daily crawl error monitoring in GSC | SEO Lead | Daily | Crawl errors trend downward; investigate any spikes | Pending |
| Monitor indexation progress in GSC | SEO Lead | Daily | New URLs being indexed; indexed count approaches expected total | Pending | |
| Test all critical user journeys and conversions | QA Lead | Daily | All critical paths working; conversion tracking working | Pending | |
| Monitor organic traffic and analytics | SEO Lead | Daily | Traffic tracked; looking for unexpected drops; monitor by source and page | Pending | |
| Check page speed and Core Web Vitals | Technical Lead | Daily | Performance meets targets; no degradation from old site | Pending | |
| Address any critical issues immediately | All | Ongoing | Critical issues identified and fixed same day | Pending | |
| Post-Migration (Weeks 2-4) | Verify redirect chain elimination and efficiency | Technical Lead | Week 2 | No redirect chains; all old URLs direct to new destination | Pending |
| Analyze indexation patterns and coverage issues | SEO Lead | Week 2 | Identify any patterns in pages not being indexed; address root causes | Pending | |
| Monitor ranking changes by category | SEO Lead | Weekly | Track which content categories recovering rankings; which still declining | Pending | |
| Track referrer migration (external links pointing to new URLs) | SEO Lead | Week 3 | Backlinks pointing to new URLs; old URL references updating over time | Pending | |
| Check for duplicate content or indexation issues | SEO Lead | Week 4 | No significant duplicate content; coverage issue resolved | Pending | |
| Post-Migration (Months 2-3+) | Monitor ongoing ranking recovery | SEO Lead | Monthly | Rankings steadily recovering toward baseline; major categories recovered | Pending |
| Identify and fix legacy issues impacting recovery | SEO Lead | Monthly | Issues blocking recovery identified and addressed | Pending | |
| Optimize pages based on new performance data | SEO Lead | Monthly | Content refreshed; pages optimized based on new data | Pending | |
| Plan follow-up optimizations to exceed pre-migration performance | SEO Lead | Month 3 | Plan for improvements beyond recovery; new opportunities identified | Pending |
URL Mapping and Redirect Strategy
Proper URL mapping and redirect implementation is the technical foundation of successful migration. Mistakes here can cause lasting problems.
URL mapping types: URL mapping can follow different patterns. One-to-one mapping is ideal—old URL maps directly to new URL with similar content. Consolidation mapping occurs when multiple old pages combine into one new page; all old URLs redirect to the new page. Split mapping occurs when one old page becomes multiple new pages; the old URL redirects to the most relevant new page. Deletion mapping occurs when content is removed; the page should either 404 or redirect to most relevant related content. Each type requires different handling.
301 versus 302 redirects: Always use 301 redirects (permanent) for migrations, not 302 (temporary). 301 redirects signal to search engines that the old URL permanently moved, and they transfer link equity to the new URL. 302 redirects don't fully transfer link equity and might cause the old URL to continue ranking. Use 301 exclusively for migrations.
Redirect implementation methods: Server-level redirects via .htaccess (Apache) or Nginx configuration are most efficient and preferred. These are processed before the page loads. CMS-level redirects using plugins or built-in redirect managers work but add slight overhead. JavaScript or meta refresh redirects are least desirable and shouldn't be used for SEO redirects. Choose server-level redirects when possible.
Redirect chains: Avoid redirect chains where old URL A redirects to B which redirects to C. Chains waste crawl budget and slow down crawling. Map old URLs directly to their final destination. If you have chains in your redirect rules, consolidate them. Use crawling tools to detect and fix any chains that exist.
Pattern-based redirects: For predictable URL structure changes, pattern-based redirects are efficient. For example, if you're changing from /blog/article-title to /articles/article-title, a pattern-based redirect handles all blog articles. Regular expressions in .htaccess or similar tools make this practical. Document your pattern rules so others understand the logic.
Monitoring redirects: After implementation, verify all redirects work. Test a comprehensive sample of old URLs to ensure they redirect to correct new pages. Use redirect checker tools to test URLs. Monitor crawl logs to ensure old URLs aren't causing crawl errors. Fix any broken redirects immediately.
Redirect persistence: Keep redirects in place for at least 6-12 months after migration. Some sources recommend keeping them permanently. Removing redirects too early risks external links still pointing to old URLs not finding content. Search engines also need time to update their internal link graphs to point to new URLs.
Content and On-Page Migration
Beyond technical redirects, migrations often require attention to content and on-page elements to ensure nothing is lost and optimization continues.
Content duplication during migration: During migrations, temporary duplication can occur if both old and new URLs are live simultaneously. Use canonical tags to point old URLs to new URLs, or use robots meta noindex on old URLs to prevent indexing. Be explicit about which version is canonical to avoid confusing search engines.
Title tags and meta descriptions: If your migration includes URL structure changes, review title tags and meta descriptions. If they reference the old URL structure, update them. Ensure all pages in new structure have optimized titles and descriptions. Avoid situations where multiple pages have identical titles or descriptions.
Internal linking updates: Update internal links throughout your site to point to new URLs rather than relying on redirects. Redirects work but are inefficient; direct links are better. This is especially important for navigation, footers, and frequently-linked pages. Use find-and-replace tools to systematically update internal links.
Content refresh during migration: Migrations present opportunities to refresh content. As you migrate content, evaluate whether updates are needed. Update outdated information. Improve thin content. Add missing sections. Content refreshes combined with migrations often result in better performance than content alone would achieve.
Preserving structured data: If your content has structured data (JSON-LD, microdata, etc.), ensure it migrates correctly to new pages. Schema.org markup for articles, products, FAQs, and other content types should be replicated exactly in new locations. Test structured data validation in new environment.
Handling pagination: If your migration affects pagination structure, handle it carefully. Update rel=next and rel=prev annotations if they exist. Update sitemap entries to reflect new pagination structure. If pagination structure changes, consider canonical handling to avoid duplicate content.
Post-Migration Monitoring
The first weeks after migration are critical. Active monitoring catches problems early when they're easier to fix.
Immediate post-migration (Day 1-7): The first week focuses on identifying and fixing critical issues. Monitor crawl errors in Google Search Console daily; any spike should be investigated immediately. Monitor indexation progress; new URLs should start getting indexed within days. Test critical user journeys and conversions to ensure nothing is broken. Monitor organic traffic for significant drops. Track Core Web Vitals to ensure performance hasn't degraded.
Initial recovery phase (Week 2-4): As search engines begin indexing new content, focus shifts to ensuring indexation completes correctly. Verify indexation patterns—ensure important pages are indexed and less important pages are properly noindexed. Monitor ranking changes; expect fluctuation as Google processes the migration. Track which content categories recover rankings quickly and which are slower. Identify patterns to understand if specific content types are affected differently.
Extended recovery monitoring (Month 2-3+): Full ranking recovery typically takes 2-4 months for significant migrations. Monitor trends across this period to ensure rankings are recovering toward baseline. Identify content categories or pages that aren't recovering as expected; prioritize fixes for these areas. Once major recovery has stabilized, begin optimization work to exceed pre-migration performance levels.
Key metrics to track: Monitor organic traffic overall and by page. Track rankings for priority keywords. Monitor crawl error trends. Monitor indexation metrics in GSC. Track Core Web Vitals and page speed. Monitor conversion rate from organic. Compare performance against pre-migration baseline to quantify impact.
Common Migration Mistakes and How to Avoid Them
Many organizations make preventable mistakes during migrations that cause prolonged recovery periods. Learning from common mistakes helps you avoid them.
Mistake 1: Combining multiple migrations simultaneously: Don't migrate your domain AND change your CMS AND redesign your site all at once. When multiple things change together, you can't isolate which change caused problems. Break migrations into phases. Migrate to HTTPS first, then change CMS, then change domain. This makes troubleshooting far easier if issues emerge.
Mistake 2: Inadequate URL mapping: Failing to map old URLs properly results in orphaned pages, broken redirects, or lost content. Create comprehensive URL mapping before migration. Map every old URL to its new destination. Verify completeness. Missing mappings cause 404 errors and lost traffic.
Mistake 3: Redirect chain creation: Poorly planned redirects create chains (A→B→C). Search engines follow chains but they waste crawl budget and slow discovery of final destination. Verify all redirects are direct mappings. Use crawl tools to detect and eliminate chains.
Mistake 4: Removing redirects too early: Removing redirects weeks after migration while external links still point to old URLs causes those external links to 404. Keep redirects in place for at least 6-12 months. External link equity flows to new URLs through redirects; removing redirects breaks that flow.
Mistake 5: Not notifying search engines: Don't assume Google will discover your changes automatically. Submit your updated XML sitemap to Google Search Console. Use the URL Inspection tool to request crawling of important new URLs. Explicitly notify Google of major changes through change of address tool if doing domain migration. Active notification speeds up migration processing.
Mistake 6: Inadequate QA and testing: Launching migration without thorough testing causes problems that could have been prevented. Test redirects extensively. Test all technical SEO elements. Test critical user journeys. Run comprehensive site crawl and fix issues before going live. The time spent testing pays for itself many times over by preventing problems.
Mistake 7: Not monitoring post-migration: Migrating and then not actively monitoring allows problems to fester unnoticed. Assign someone to monitor crawl errors, indexation, rankings, and traffic daily first week, then regularly after. Problems caught and fixed early cause minimal disruption; problems left unattended compound.
Mistake 8: Losing content or metadata: During migrations, content sometimes gets lost—old descriptions don't transfer, metadata disappears, or pages get simplified. This is often avoidable with planning. Document existing content before migration. Verify new content matches old content. Update content intentionally during migration rather than losing it accidentally.
Mistake 9: Changing content strategy during migration: Migration is stressful and high-risk. Don't simultaneously change what content you're targeting, how you're optimizing pages, or your content strategy. Keep content strategy consistent through migration. After migration stabilizes, refine strategy based on migration results. Separating migration from strategy changes makes both more successful.
Mistake 10: Inadequate stakeholder communication: When migrations go poorly, one reason is often that leadership wasn't properly informed about expected recovery timeline. Set expectations upfront that migrations cause short-term disruption but that recovery is expected and planned. Communicate progress regularly. Keep stakeholders informed so unexpected results don't trigger panic.
Successful website migration SEO requires careful planning, comprehensive preparation, meticulous execution, and active post-migration monitoring. Organizations that treat migrations as major projects with dedicated resources, clear governance, and detailed planning execute successfully. Those that treat migrations casually often discover too late that traffic has dropped and recovery will take months. The investment in proper migration planning, execution, and monitoring pays for itself many times over in preserved and recovered organic visibility.