Technical SEO
Website Migration SEO Checklist 2026: Don't Lose Your Rankings
Step-by-step 2026 SEO migration checklist: 301 redirects, sitemap, Search Console, schema rebuild. Recover rankings in 2-4 weeks instead of months.
Quick Answer
You can migrate your website without losing rankings if you map every old URL to its new destination with 301 redirects, resubmit your sitemap, and monitor Google Search Console daily for the first two weeks. Most well-executed migrations recover fully within 2 to 4 weeks.
Migrating a website is one of the highest-risk SEO events a business can go through. Change your URLs, switch your platform, or move to a new domain without proper planning, and months of hard-earned rankings can vanish overnight. Google does not automatically know that your new site is the same business. You have to tell it, clearly and completely.
The good news is that migrations done right can actually improve your rankings, especially if you are moving from a slow legacy platform to a faster, modern architecture. This checklist walks you through every step.
Phase 1: Pre-Migration Audit (6 to 8 Weeks Before Launch)
The work that prevents ranking loss happens before you touch the new site. Start your preparation at least 6 weeks before your planned launch date.
Crawl and Document Your Existing Site
Use a crawler like Screaming Frog or Sitebulb to capture every URL on your current site. Export the full list including:
- All indexed pages (check Google Search Console for the definitive list)
- Pages with organic traffic (pull from Google Analytics)
- Pages with backlinks (check in Ahrefs, Moz, or Google Search Console)
- Current meta titles and descriptions
- Internal link structure
This inventory is your migration map. Every URL on this list needs a destination on the new site or a deliberate decision to remove it.
Build Your URL Mapping Spreadsheet
Create a spreadsheet with four columns: old URL, new URL, redirect type, and notes. Map every old URL to its equivalent on the new site. For pages you are consolidating, map both old URLs to the single new destination. For pages you are removing, decide between a 301 redirect to the closest relevant page or a 410 (Gone) response.
Not sure which pages have SEO value worth preserving? We can audit your current site and build the redirect map for you.
Phase 2: Technical Setup (2 to 4 Weeks Before Launch)
With your URL map complete, set up the technical infrastructure that will preserve your rankings.
Configure 301 Redirects
Implement permanent 301 redirects for every URL in your mapping spreadsheet. Key rules:
- Point directly from old URL to new URL (no redirect chains)
- Each redirect should resolve in under 2 seconds
- Test every redirect before going live
- Use server-level redirects, not JavaScript redirects (search engines may not follow JS redirects)
For static sites on Cloudflare Pages, you can configure redirects in a _redirects file or through Cloudflare’s bulk redirect rules. For other platforms, configure them at the server or CDN level.
Prepare Your New Sitemap
Build your XML sitemap with all new URLs. Remove any old URLs, staging URLs, or pages you are intentionally dropping. Keep it clean. Your sitemap should only contain pages you want Google to index.
Verify Page Speed on the New Site
Run your new site through PageSpeed Insights before launch. If your new site is slower than the old one, fix it before migrating. Slower pages mean less crawl budget from Google, which delays indexation and extends your recovery period.
A move to a modern website architecture should dramatically improve your speed. If you are going from WordPress to a static site on a CDN, expect your PageSpeed score to jump from 40 to 70 up to 90 to 100.
| Pre-Launch Check | Why It Matters |
|---|---|
| 301 redirects tested | Prevents ranking loss from broken URLs |
| New sitemap ready | Helps Google discover new URL structure |
| Page speed verified | Protects crawl budget and Core Web Vitals |
| Structured data updated | Preserves rich snippets in search results |
| Internal links updated | Points to new URLs directly, not through redirects |
| Canonical tags set | Prevents duplicate content signals |
Planning a migration and want to make sure nothing falls through the cracks? Get a free migration audit and we will review your setup before you go live.
Phase 3: Launch Day
Launch day should be calm, not chaotic. If you did the preparation right, this is mostly about flipping the switch and monitoring.
Go Live and Submit
- Deploy your new site
- Activate all 301 redirects
- Submit your new sitemap to Google Search Console
- Submit your new sitemap to Bing Webmaster Tools
- If changing domains, use the Change of Address tool in Google Search Console
- Verify that robots.txt is not blocking any pages you want indexed
Verify Redirects Are Working
Spot-check at least 20 to 30 redirects manually. Test your highest-traffic pages, your pages with the most backlinks, and a random sample of other pages. Verify that each returns a 301 status code and lands on the correct new page.
Phase 4: Post-Launch Monitoring (First 2 Weeks)
The first two weeks after launch are critical. Monitor daily and fix issues immediately.
What to Watch
- Crawl errors in Google Search Console: Look for spikes in 404 errors. Each one is a missed redirect that needs fixing.
- Index coverage: Your indexed page count should stay roughly the same. A sudden drop means pages are not being indexed.
- Organic traffic by landing page: Compare to pre-migration baselines. A 10 to 20% dip in the first week is normal. A 50% drop means something is broken.
- Keyword rankings: Track your top 20 to 30 keywords daily. Individual keyword fluctuations are normal. Across-the-board drops are not.
- Crawl stats: If Google’s crawl rate drops significantly, check for server errors or slow response times.
When to Take Action
A temporary dip is expected. Do not panic if rankings fluctuate in the first week. However, act immediately if:
- Multiple high-traffic pages return 404 errors
- Your indexed page count drops by more than 20%
- Organic traffic is down more than 30% after one week
- Crawl errors are increasing rather than decreasing
The fix is almost always a missing or incorrect redirect. Check your mapping spreadsheet against actual behavior and fill any gaps.
Your SEO monitoring setup should catch these issues automatically. If you do not have automated monitoring, check Google Search Console manually every day for the first two weeks.
Summary
- Crawl and document every indexed URL on your old site before touching the new one
- Build a complete URL mapping spreadsheet and implement 301 redirects for every page
- Resubmit your sitemap to Google Search Console and Bing on launch day
- Monitor crawl errors, index coverage, and rankings daily for 2 weeks post-launch
- A 10 to 20% temporary traffic dip is normal; full recovery happens within 2 to 4 weeks with proper redirects
References
- Google Search Console Change of Address Tool - Official tool for notifying Google about domain migrations
- Google URL Inspection Tool - Verify how Google sees your redirected pages
- HTTP Status Codes (MDN Web Docs) - Reference for 301, 302, 404, and 410 status codes
- Cloudflare Pages Redirects - How to configure redirects on Cloudflare Pages
- Google Search Central: Site Moves - Best practices for site migrations and redirects
A website migration does not have to mean losing your rankings. Plan it right, redirect everything, and monitor closely. Your traffic will recover, and if you moved to a faster platform, it may end up higher than before.
Frequently Asked Questions
How long does SEO recovery take after a website migration?
Most well-executed migrations see ranking stabilization within 2 to 4 weeks. Some competitive keywords may take 6 to 8 weeks to fully recover. The key factor is redirect accuracy. Sites with complete, correct 301 redirects recover fastest. Sites with missing redirects or redirect chains can take months to recover.
Do I need 301 redirects when changing domain names?
Yes, 301 redirects are absolutely required for domain changes. Every indexed URL on your old domain needs a permanent 301 redirect to its equivalent page on the new domain. Without redirects, Google treats the new domain as a brand new site and your old rankings are lost entirely.
Will I lose rankings if I change my URL structure?
A temporary dip of 10 to 20% is normal even with perfect redirects. However, if you map every old URL to its correct new destination with 301 redirects, update your sitemap, and resubmit to Google Search Console, rankings typically recover within 2 to 4 weeks. The risk increases dramatically if redirects are missing or incorrect.
Should I migrate my website all at once or in phases?
For most small business websites (under 500 pages), a full migration is simpler and cleaner. Phased migrations are useful for large sites with thousands of pages where you want to monitor the impact section by section. Regardless of approach, every old URL must redirect to the correct new page from day one.
How do I handle pages I want to remove during migration?
If a page has backlinks or receives organic traffic, redirect it to the most relevant existing page on the new site. If a page has no traffic and no backlinks, you can let it return a 410 (Gone) status code, which tells Google to remove it from the index. Never leave old URLs returning 404 errors if they had any SEO value.
Should I resubmit my sitemap after migration?
Yes. Update your XML sitemap with all new URLs, remove any old URLs, and resubmit it in both Google Search Console and Bing Webmaster Tools. This signals to search engines that your site structure has changed and helps them discover and index your new pages faster.
Does website speed affect migration recovery?
Yes. If your new site is slower than the old one, it will hurt your Core Web Vitals scores and slow down crawling. Google allocates less crawl budget to slow sites, which delays indexation of your new pages. Always ensure your new site is at least as fast as the old one, ideally faster.
What is the biggest mistake people make during website migrations?
Forgetting redirects. It sounds basic, but incomplete redirect mapping is the number one cause of traffic loss after migration. The second most common mistake is not crawling the old site before migration to capture every indexed URL. If you do not know what exists, you cannot redirect it.
About the author
vaza.ai
Marketing Team
The vaza.ai team helps small businesses modernize their websites and eliminate the cost, maintenance, and security headaches of legacy platforms.
Related reading
Want this running on your own site?
See how the AI SEO platform monitors, fixes and publishes on autopilot.
Get a free audit