SEO Site Migration: How to Plan Without Losing Traffic

This guide walks you through planning an SEO site migration—whether you’re changing domains, moving to HTTPS, or restructuring URLs—so you can preserve your organic rankings and traffic. You’ll learn the pre-migration audits, technical steps, and post-launch monitoring needed to minimize losses.

What You’ll Need

• Access to your current site’s analytics (Google Analytics or similar)
• Access to Google Search Console (GSC) for the old and new domains
• A crawler tool (e.g., Screaming Frog, Sitebulb, or a free online crawler)
• A staging environment for the new site (or a test subdomain)
• Backup of your old site’s files and database
• List of all current URLs, ideally exported from your CMS or crawler
• Access to your server’s .htaccess or nginx config for redirects

Step-by-Step

1. Audit your current site. Export a full list of URLs from your crawler. Note which pages get organic traffic, which have backlinks, and which are indexed. Use GSC to export your top pages by clicks and impressions for the last 6–12 months.
2. Map old URLs to new URLs. Create a spreadsheet with columns: old URL, new URL (or ‘no replacement’), redirect type (301 or 410). For every page that has traffic or backlinks, plan a 301 redirect to the most relevant new page. For pages that are truly gone, use a 410 to signal permanent removal.
3. Check for redirect chains. Ensure no old URL redirects to another old URL that then redirects to the new one. Keep redirects direct: old → new, not old → intermediate → new.
4. Update internal links. Before launch, update all internal links in your content, navigation, and sitemaps to point to the new URLs. This reduces crawl waste and passes link equity more cleanly.
5. Set up the new environment. Build the new site on a staging URL (e.g., staging.example.com) and test it thoroughly. Ensure the staging site is blocked from search engines via robots.txt or a noindex meta tag.
6. Test the redirects on staging. If possible, test your redirect rules on the staging server to confirm they work before going live. Check for correct status codes (301, not 302) and that no redirect loops occur.
7. Prepare your new sitemap. Generate an XML sitemap of all new URLs. Submit it to GSC after launch. Also update your robots.txt to reference the new sitemap.
8. Launch the new site. On launch day, switch DNS (if changing domains) and deploy the new site. Ensure the old site either redirects to the new one (via 301) or is taken down with proper 410s.
9. Implement redirects on the old server. If you’re moving domains, set up server-level redirects (e.g., in .htaccess or nginx) to send all old URLs to the corresponding new URLs. If you’re just changing URLs on the same domain, implement redirects on the same server.
10. Submit the change of address (if domain change). In GSC, use the ‘Change of Address’ tool under Settings to tell Google your site has moved. This helps preserve your indexation signals.
11. Monitor GSC and analytics daily. After launch, check GSC for coverage errors, crawl errors, and indexation status. Watch your organic traffic in analytics. Expect some fluctuation for a few days, but a sudden drop may indicate a problem.
12. Fix issues promptly. If you see 404s for important pages, check your redirect map and fix them. If pages aren’t indexing, submit the new sitemap and request indexing for critical pages.
13. Monitor backlinks. Use a backlink tool (like Ahrefs or Majestic) to see if any external links are still pointing to old URLs. If so, reach out to webmasters to update them, or ensure your redirects are solid.
14. Keep the old site live (if possible) for a while. If you’re moving domains, keep the old domain up with redirects for at least 6–12 months. This allows search engines to process the redirects fully.

Common Mistakes

• Using 302 redirects instead of 301. 302s tell search engines the move is temporary, so they may not transfer ranking signals.
• Redirecting everything to the homepage. This loses the specific value of individual pages. Always map each old URL to the most relevant new one.
• Ignoring URL case sensitivity. Ensure your server treats URLs case-insensitively or that your redirects account for variations.
• Forgetting to update internal links. If you only rely on redirects, you waste crawl budget and slow down indexation.
• Launching without testing. A typo in your redirect rules can cause a massive 404 wave. Test on staging first.
• Not monitoring after launch. The job isn’t done at launch. You need to watch for weeks to catch issues early.

Tips

• Keep your URL structure as similar as possible to the old one to minimize the impact.
• Prioritize the pages with the most traffic and backlinks when mapping redirects.
• Use a spreadsheet to track every URL and status—this is your source of truth.
• Set up a custom alert in GSC for spikes in 404 errors.
• If you’re changing domains, consider using a temporary 302 for a short period before switching to 301? Actually, no—always use 301 from the start.
• Communicate the migration to your team and any external partners who might link to your site.

Troubleshooting

Traffic drops after launch: Check GSC for coverage errors—look for ‘Server error (5xx)’ or ‘Redirect error’. Also verify that your redirects are returning 301, not 302 or 404. If you see a sudden drop, check your analytics to see if it’s across all pages or specific ones. If specific, those pages may have broken redirects.

Pages not indexing: Submit your new sitemap in GSC and use the URL Inspection tool to request indexing for critical pages. Ensure your robots.txt isn’t blocking them and that the pages return 200 status.

Rankings fluctuate: Some fluctuation is normal for 1–2 weeks. If it persists, check that your redirects are passing link equity—use a tool to see if backlinks are being followed. Also, check for duplicate content issues if you have both old and new versions live.

404s on old URLs: If you’re seeing 404s in GSC for old URLs, your redirects aren’t working. Test a few old URLs in your browser to see what happens. If they don’t redirect, check your server config for syntax errors.

Mixed content warnings (if moving to HTTPS): Ensure all resources (images, scripts, CSS) are loaded over HTTPS. Use a tool like ‘Why No Padlock’ to find insecure resources.

Frequently Asked Questions

How long does it take for rankings to recover after a migration?

It varies, but typically 1–3 months. Some sites recover faster if redirects are clean and the site structure is similar. Monitor GSC for indexation and traffic trends.

Should I use 301 or 302 redirects?

Use 301 for permanent moves. 302s are for temporary changes and won’t pass the same ranking signals.

What if I can’t map an old URL to a new one?

If the page has no equivalent and no traffic/backlinks, use a 410 Gone. If it has some value, redirect to the closest category or homepage.

Can I migrate without changing URLs?

Yes, if you’re only changing design or platform, you can keep URLs the same. That’s the safest type of migration, but you still need to test and monitor.

Do I need to update backlinks manually?

No, but it helps. Redirects handle most of it. For high-value links, reach out to webmasters to update the URLs directly.

What’s the biggest cause of traffic loss?

Broken redirects, redirecting to irrelevant pages, and forgetting to update internal links are the top causes. Also, launching without a full backup can be disastrous.

Related

• MW4 Incoming Achievement Trophy Guide
• Catch Dragons to Defend Guide: Best Upgrades & Rare Dragon Catching
• VR Headsets vs AR Glasses: What Each Is Good For