SEO Migration Checklist: How to Relaunch Without Losing Rankings
An seo migration — whether it's a platform change, domain move, URL restructure, or full site redesign — is one of the highest-risk activities in digital marketing. Done poorly, a migration can eliminate years of accumulated organic rankings in days. Done correctly with a comprehensive checklist, you can preserve virtually all your existing ranking equity and sometimes even improve rankings in the process.
This guide provides a complete seo migration checklist with pre-launch, launch day, and post-launch tasks.
⠀
Types of SEO Migrations and Their Risk Levels
⠀
Not all migrations carry equal risk:
Domain name change (highest risk):
Moving from old-domain.com to new-domain.com. Requires sitewide 301 redirects plus the GSC Change of Address tool. Full ranking recovery can take 3-6 months even with perfect execution.
Platform migration (high risk):
Moving from WordPress to Shopify, or Squarespace to Wix. URL structures change, templates change, and content may be restructured. Requires comprehensive redirect mapping.
URL structure change (high risk):
Restructuring URLs from /blog/2022/03/post-title to /blog/post-title while keeping the same domain. Requires redirects for every changed URL.
Site redesign without URL changes (medium risk):
New design, same URLs. Lower risk if content isn't removed or restructured. Still requires checking that all on-page elements are preserved.
HTTPS migration (low risk, high importance):
Moving from HTTP to HTTPS. Well-understood process with minimal ranking impact when done correctly.
⠀
Pre-Migration Checklist (Weeks Before Launch) ve Seo Migration
⠀
The most important work happens before you launch anything.
Inventory and documentation:
Crawl the current site with Screaming Frog. Export all URLs (HTML pages, images, JS, CSS). Save this as your baseline.
⠀
Document all current rankings. Export your top 200+ keyword rankings and positions from Ahrefs, SEMrush, or your rank tracker. This is your benchmark for recovery tracking.
⠀
Document top-traffic pages. Pull 12 months of organic traffic from GA4 by landing page. Your top 20-50 pages by organic traffic are the highest-priority pages to preserve.
⠀
Map existing URLs to new URLs. Create a comprehensive URL mapping spreadsheet: Column A = old URL, Column B = new URL. Every old URL needs a corresponding new URL or a designated redirect target.
⠀
Document all existing backlinks. Export your backlinks from Ahrefs or SEMrush. Identify the most valuable links (by DR of linking domain) — these are the links you most need to redirect correctly.
⠀
Export and preserve existing meta data. Document the current title tags, meta descriptions, and H1s for all top-priority pages. Preserve or improve these — don't let a CMS migration reset your carefully crafted metadata.
⠀
Prepare your redirect map:
Classify each URL: Stays the same | New URL | Redirect to most relevant page | Noindex (if no longer needed)
⠀
Test redirects in staging. Before going live, implement and test all redirects in your staging environment. Every old URL should return a 301 (not 302) to the correct new URL.
⠀
Check for redirect chains. No redirect should chain through more than one hop. Old URL → New URL directly, not Old URL → Intermediate URL → New URL.
⠀
⠀
Launch Day Checklist
⠀
⠀
⠀
Launch day requires executing several critical tasks in the right order:
Launch outside peak traffic hours. For most sites, launch at 2-4am local time or on a low-traffic day (Friday afternoon in some industries) to minimize impact of any immediate issues.
⠀
Verify redirects are live. After launch, immediately test a sample of your most important old URLs to confirm they return 301 redirects to the correct new URLs. Use Screaming Frog list mode or a redirect checker tool.
⠀
Verify new pages are returning 200. Crawl a sample of new URLs to confirm they're live and returning 200 status codes, not 404s or server errors.
⠀
Check that noindex tags are not live site-wide. Development environments often have <meta name="robots" content="noindex"> on all pages or in robots.txt. Verify this is not on your live site.
⠀
Verify robots.txt is correct. The live site's robots.txt should not block Googlebot from any important sections.
⠀
Submit updated sitemap to Google Search Console. Log into GSC and submit your new sitemap immediately. If this is a domain change, add the new domain as a separate property first.
⠀
Use the Change of Address tool (for domain changes only). GSC > Settings > Change of Address. This tells Google you've moved the site and accelerates the authority transfer.
⠀
Request indexing for your highest-priority pages. Use the URL Inspection Tool > Request Indexing for your top 20-50 most important pages.
⠀
⠀
Post-Migration Monitoring (First 90 Days)
⠀
The work isn't over at launch. Careful monitoring for 90 days identifies and addresses issues before they compound.
Monitor GSC Coverage Report daily for 2 weeks. New 404 errors in Coverage are redirects that are broken or missing. Every new 404 should be investigated and fixed immediately.
⠀
Monitor organic traffic in GA4. Compare daily and weekly organic sessions to pre-migration baseline. Some decline is normal in the first 1-2 weeks; significant decline (30%+) requires immediate investigation.
⠀
Monitor keyword rankings in your rank tracker. Check your documented pre-migration rankings weekly. Significant position drops for previously stable keywords indicate specific issues.
⠀
Check for new 404s from Googlebot. GSC > Coverage > Not Found. These are pages Googlebot is trying to access that return 404 — usually broken redirects.
⠀
Verify your top backlinks are redirecting correctly. Ahrefs > Backlinks. Filter by your top referring domains and check that the URLs they link to are returning 301 redirects, not 404s.
⠀
Recovery timeline expectations:
A well-executed migration typically shows:
Week 1-2: Some rankings fluctuation as Google processes redirects
Week 3-4: Gradual rank recovery for most stable keywords
Month 2-3: Close to pre-migration ranking parity for most pages
Month 3-6: Full recovery and potential improvement (especially if the migration included content improvements)
⠀
⠀
Common Migration Mistakes
⠀
⠀
⠀
Mistake 1: Going live without a complete redirect map
Every old URL without a redirect becomes a 404. Backlinks lose their value, users see error pages, and ranking equity evaporates. Never launch without 100% redirect coverage.
Mistake 2: Using 302 instead of 301 redirects
302 is a temporary redirect; 301 is permanent. 302s don't pass full link equity. All migration redirects should be 301.
Mistake 3: Removing or changing content at the same time as migration
Combining platform migration with content restructuring doubles the risk. Migrate first (preserving all content and URLs as closely as possible), then make content improvements as a separate post-migration project.
Mistake 4: Not verifying staging before launch
Many migrations fail because redirects were configured and tested in staging but not correctly deployed to production. Test after going live, not just before.
Mistake 5: Forgetting internal links
After URL changes, update all internal links to point to the new URLs directly rather than relying on redirects. Redirect chains within a site waste crawl budget and dilute link equity.
Mistake 6: Launching with staging noindex active
The most devastating mistake: launching the site with robots.txt Disallow: / or noindex tags active from development. All pages become invisible to Google. Check this immediately after launch.
Blakfy has managed dozens of SEO migrations and provides pre-migration auditing, redirect mapping, launch day support, and post-migration monitoring as a complete service.
⠀
Frequently Asked Questions
⠀
How long does it take to recover rankings after a migration?
With a well-executed migration using complete 301 redirects, expect 80-90% ranking recovery within 6-8 weeks for most keywords. Full recovery for all keywords can take 3-6 months. Domain changes (different domain name) take longer than URL structure changes on the same domain. Poor execution — missing redirects, 302s instead of 301s, removed content — extends recovery significantly.
Should I migrate platforms and redesign simultaneously?
Ideally, no. Separating the technical migration (platform change, URL restructure) from the design and content overhaul reduces the number of variables if something goes wrong and makes it easier to diagnose the cause of any ranking changes. If business requirements force simultaneous changes, plan extra carefully and monitor more intensively post-launch.
Do I need an SEO agency for a migration, or can I DIY?
Small sites (under 500 pages) with straightforward URL changes can be handled carefully by an experienced SEO without agency support, using this checklist. Large sites (5,000+ pages), domain changes, and e-commerce migrations with complex URL structures and extensive backlink profiles benefit significantly from professional SEO oversight. The cost of poor migration execution on a large site — months of lost revenue while rankings recover — far exceeds the cost of professional migration support.
