SEO After Site Redesign: How to Maintain Rankings During a Website Migration
Complete guide to preserving SEO during a website redesign. Learn how to plan migrations, implement redirects, and recover from redesign mistakes.
Website redesigns are exciting—but they’re also one of the most common causes of SEO disasters. A poorly planned migration can wipe out years of ranking progress overnight.
Here’s how to protect your SEO during a redesign, and how to recover if things go wrong.
Pre-Redesign: Planning for SEO Success
Step 1: Benchmark Current Performance
Before any changes, document your baseline:
Traffic data:
- Monthly organic sessions
- Top landing pages (top 100)
- Organic keywords ranking
- Click-through rates
Technical data:
- All indexed URLs (site: search or crawl)
- Page-level backlinks
- Internal linking structure
- Current site speed metrics
Export and save:
- Google Analytics data
- Search Console data
- Backlink profile
- Full site crawl
Step 2: Create URL Mapping
The most critical SEO task in any redesign.
Map every URL:
| Old URL | New URL | Status | Redirect Type |
|---|---|---|---|
| /old-page/ | /new-page/ | Changed | 301 |
| /blog/post-name/ | /articles/post-name/ | Changed | 301 |
| /about-us/ | /about/ | Changed | 301 |
| /contact/ | /contact/ | Same | None needed |
| /outdated-page/ | N/A | Removed | 301 to relevant |
Rules for URL mapping:
- Every old URL needs a destination
- Redirect to most relevant equivalent page
- Don’t redirect everything to homepage
- Preserve URL structure where possible
Step 3: Preserve On-Page SEO Elements
For each migrating page, maintain:
- Title tags: Same or improved
- Meta descriptions: Preserve unless improving
- H1 tags: Keep topic focus
- Content: Same or expanded
- Internal links: Maintain or improve
- Image alt text: Preserve
Step 4: Check Robots.txt and Sitemap Plans
Ensure your new site:
- Won’t accidentally block Googlebot
- Will have an updated sitemap
- Preserves crawlability
During the Migration
Step 1: Implement 301 Redirects Properly
Server-level redirects are best:
- .htaccess (Apache)
- nginx.conf
- Server configuration
Not recommended:
- JavaScript redirects (Google may not follow)
- Meta refresh tags (slow, poor UX)
Example .htaccess redirects:
# Single page redirect
Redirect 301 /old-page/ https://example.com/new-page/
# Pattern-based redirect
RedirectMatch 301 ^/blog/(.*)$ https://example.com/articles/$1
Step 2: Update Internal Links
After implementing redirects, update internal links to point directly to new URLs. Redirects work, but direct links are better for:
- Faster page loads
- Cleaner crawl paths
- Better link equity flow
Step 3: Submit New Sitemap
- Update XML sitemap with new URLs
- Remove old URLs from sitemap
- Submit to Google Search Console
- Submit to Bing Webmaster Tools
Step 4: Monitor Crawling
Watch Search Console closely:
- Crawl stats (are pages being discovered?)
- Coverage errors (new issues appearing?)
- URL inspection (are redirects working?)
Post-Migration Checklist
Week 1
- All redirects working (test a sample)
- No accidental noindex tags
- Robots.txt not blocking important pages
- Sitemap submitted and processing
- Internal links updated
- Canonical tags correct
- Analytics tracking working
- Search Console verified on new domain/structure
Week 2-4
- Monitor crawl errors daily
- Track indexation of new URLs
- Watch for traffic changes
- Fix any 404 errors appearing
- Monitor Core Web Vitals
Month 1-3
- Compare traffic to baseline
- Track ranking changes
- Monitor Search Console coverage
- Address any persistent issues
Common Migration Mistakes
Mistake 1: No Redirects or Wrong Redirects
Problem: Old URLs return 404 or redirect incorrectly.
Fix:
- Implement proper 301 redirects
- Test every important URL
- Check redirect chains aren’t forming
Mistake 2: Redirecting Everything to Homepage
Problem: All old URLs redirect to homepage, losing page-specific relevance.
Impact: Google sees mass redirects to homepage as soft 404s.
Fix: Redirect each page to its most relevant equivalent.
Mistake 3: Blocking the New Site
Problem: Robots.txt from staging accidentally deployed.
# Accidentally blocking everything
User-agent: *
Disallow: /
Fix: Immediately update robots.txt and request re-indexing.
Mistake 4: Losing HTTPS
Problem: New site launches on HTTP or mixed content.
Fix: Ensure all pages and resources use HTTPS.
Mistake 5: Forgetting Canonical Tags
Problem: Pages have wrong or missing canonical tags.
Fix: Audit canonicals point to correct new URLs.
Mistake 6: Losing Internal Links
Problem: Redesign removes important internal link paths.
Fix: Recreate internal linking structure, especially to key pages.
Mistake 7: Changing Content Significantly
Problem: Pages that ranked well now have different content.
Fix: Preserve content that was ranking well, improve rather than replace.
Recovering from Migration Problems
If Traffic Dropped Significantly
Step 1: Identify the cause
- Check for crawl errors
- Verify redirects are working
- Look for indexation issues
- Compare before/after URLs
Step 2: Fix technical issues first
- Correct broken redirects
- Remove accidental blocks
- Fix canonical issues
- Repair broken internal links
Step 3: Request re-indexing
- Use URL Inspection for key pages
- Resubmit sitemap
- Build new backlinks if possible
Step 4: Wait and monitor
- Recovery can take 2-6 months
- Some losses may be permanent
Redirect Cleanup
If you have redirect chains:
Page A → Page B → Page C (bad)
Update to:
Page A → Page C (good)
Page B → Page C (good)
Content Recovery
If important content was lost:
- Check archive.org for old versions
- Restore content that was ranking
- Rebuild pages that were accidentally deleted
Migration SEO Checklist
Pre-Migration
- Current performance benchmarked
- All URLs mapped old → new
- Redirect rules prepared
- On-page elements preserved
- Robots.txt reviewed
- Sitemap plan ready
During Migration
- 301 redirects implemented
- Redirects tested on sample URLs
- Internal links updated
- Sitemap submitted
- Analytics configured
Post-Migration Week 1
- All redirects verified
- No blocking in robots.txt
- Sitemap processing
- Monitoring crawl errors
- Traffic tracking set up
Post-Migration Month 1
- Indexation improving
- Traffic recovery beginning
- All major errors fixed
- Core Web Vitals stable
Post-Migration Month 3
- Traffic compared to baseline
- Rankings monitored
- Any losses investigated
- Ongoing optimization begun
Special Situations
Domain Change
If you’re changing domains entirely:
- Add both domains to Search Console
- Use Change of Address tool in Search Console
- Implement full redirect map from old to new domain
- Keep old domain active for at least 1 year
- Update backlinks where possible
HTTP to HTTPS Migration
- Get SSL certificate installed
- Update internal links to HTTPS
- Update canonical tags to HTTPS
- Redirect HTTP → HTTPS
- Update Search Console to HTTPS property
- Update sitemap URLs to HTTPS
CMS Migration
When changing platforms:
- Export all content before migration
- Match URL structure if possible
- Rebuild on-page elements exactly
- Test redirects on staging first
- Check functionality of SEO features (sitemaps, canonicals, etc.)
Timeline Expectations
Ideal scenario (well-planned migration):
- Week 1-2: Minor fluctuations
- Week 3-4: Stabilization
- Month 2-3: Recovery to baseline
- Month 3+: Potential growth
Problem migration:
- Week 1-2: Significant drops
- Week 3-8: Diagnosis and fixes
- Month 2-4: Gradual recovery
- Month 6+: May not fully recover
Related Resources:
Tags:
Share this article:
Ready to improve your SEO?
Get a free SEO audit and see exactly what needs fixing on your site
Start Free Audit