Website Migration SEO Questions — Answered Without Jargon

The weeks before migration determine success or failure. These questions cover the foundational steps most teams overlook.

Do I need to tell Google about my migration? Yes. Create a change of address property in Google Search Console pointing from old domain to new domain (if domain-changing). If staying on the same domain, Google detects the changes through Search Console sitemaps and crawling. Either way, submit a fresh sitemap of new URLs immediately after launch.

What's a staging environment and do I need one? A staging site is a private copy of your website where you test the migration before going live. You can catch redirect errors, missing pages, broken internal links, and CSS/JavaScript issues without affecting your live traffic. Most teams report critical bugs only surface during live testing—staging prevents costly surprises.

How far in advance should I plan? Start planning 6-8 weeks before launch. This timeline gives you time to audit your current site, map redirects, test thoroughly, and brief your team. Rushed migrations (2-3 weeks notice) increase error rates significantly.

These questions address the mechanics of the move itself—the phase where most SEO damage happens.

How do I prevent redirect chains? A redirect chain (old URL → intermediate URL → final URL) slows crawling and dilutes authority. Build your 301 redirect map to point directly: old URL → new URL in one hop. If you're also changing domain, test that the chain doesn't exceed 3 hops from the oldest domain to final destination.

Should I migrate in waves or all at once? All at once is cleaner for Google. Partial migrations create confusion: old pages still rank, new pages compete with them, and your authority gets split. If your site exceeds 50,000 pages, coordinate waves with Google through Search Console, but migrate all high-traffic pages in the first wave.

What about image and file URLs? Every image URL, PDF, video embed, and downloadable file that changes needs its own redirect. Many teams forget this, causing broken media links that damage user experience and create crawl errors. Audit your old site for all assets and map them in your redirect list.

Do subdomains vs. subdirectories matter for SEO? Subdomains (blog.example.com) are treated as separate domains by Google. Subdirectories (example.com/blog) are part of your main domain. If you're consolidating a subdomain into a subdirectory, expect a temporary traffic dip as Google realizes they're the same entity. See our migration timeline guide for typical recovery windows.

Post-migration monitoring catches problems while they're recoverable. These questions address the critical 30-day window after launch.

How quickly should I see traffic recover? Most sites see Google re-crawl old URLs within 3-7 days and detect the migration. Recovery varies: some high-authority pages regain ranking within 2 weeks, others take 4-6 weeks depending on market competition and your site's crawl budget. See our expectations by phase for realistic timelines.

What metrics should I watch in Google Search Console? Monitor these daily during week one: (1) Coverage report—increase in valid pages, decrease in errors; (2) Performance report—traffic and clicks by URL (look for drops in your top 50 pages); (3) Crawl stats—Google's crawl rate and whether it increases after migration. Sudden drops or error spikes signal redirect or indexing problems.

My rankings dropped after migration. Is this normal? Short-term drops (2-3 rank positions for 1-2 weeks) are normal as Google re-evaluates. Drops of 10+ positions or drops lasting 4+ weeks signal a problem: likely bad redirects, crawl errors, or duplicate content. Run a post-migration audit to diagnose the cause.

When can I delete old redirects? Wait at least 6 months before removing 301 redirects. Industry benchmarks suggest Google fully processes migrations in 3-4 months, but keeping redirects active for longer protects against late-updating external links. After 6 months, track old URL crawls in Search Console—if Google stops requesting them, redirects are safe to remove.

What if I'm moving to a completely new domain? Domain changes are the riskiest migration type. Expect 25-50% temporary traffic loss even with perfect 301 redirects. Set up the change of address tool in Search Console, redirect all pages, and monitor closely for 8-12 weeks. See our domain change checklist for the complete process.

How do I handle duplicate content during migration? If your old and new sites overlap temporarily (running both live), mark old pages with rel=canonical pointing to new pages. This tells Google which version to rank. Remove the old version from search results manually in Search Console's URL Inspection tool to speed up consolidation.

Should I keep my old site live as a backup? Keep it live for 2-4 weeks as a safety net, but make sure old pages don't rank: add a noindex meta tag or robots.txt block to the old domain. Otherwise Google indexes both, you compete with yourself, and recovery takes longer.

What about local landing pages or location-specific content? If you operate in multiple service areas with location-specific pages, preserve the URL structure during migration. Moving /service-area/denver to /denver damages local SEO signals. If you must change structure, set up location-aware redirects and rebuild local citations (Google Business Profile, directories) with exact new URLs. See our full checklist for location handling.

Below are additional questions we see frequently from teams planning or executing migrations. Each answer includes a link to deeper content if you need to dive into detail.