Website Migration SEO: Preserve Rankings During Redesign

Google processes domain migrations gradually over 2–6 weeks after the redirects are implemented and the new domain is submitted in Search Console. Use the Change of Address tool in Search Console for domain-level migrations. Full ranking transfer can take 2–3 months for high-authority domains.

A redirect map is a spreadsheet listing every old URL and its corresponding new URL, used to implement 301 redirects during a migration. How to create one: (1) Crawl your existing site with Screaming Frog to export all URLs, (2) Create a spreadsheet with two columns: Old URL and New URL, (3) For every old URL, identify the best matching new URL (ideally same or similar content; if removed, redirect to the closest parent category page), (4) Prioritize: URLs with backlinks (export from Ahrefs), URLs with organic traffic (from Search Console), and all currently indexed URLs, (5) Have a developer implement all 301 redirects from the map before launch, (6) Test every redirect using Screaming Frog's List Mode or a redirect checker tool to verify each old URL returns 301 status to the correct new URL. No URL should return a 404 after migration.

Redirect chains occur when URL A redirects to URL B which redirects to URL C — each hop loses approximately 15% of link equity and slows page load. They are common in migrations that build on previous migrations. Prevention: (1) Audit existing redirects before migration using Screaming Frog (crawl → Response Codes → 301 → export), (2) Update your redirect map so all old URLs point directly to the final destination (A → C, not A → B → C), (3) Update all internal links on the new site to point directly to new URLs rather than relying on redirects, (4) After migration, run Screaming Frog again and check for redirect chains in the Redirects report. Post-migration: schedule a crawl 4 weeks after launch to catch any new chains created by site updates.

Post-migration Search Console monitoring checklist: (1) Coverage report — check for spike in 404 errors (missing redirects) or "Excluded" pages (indexation issues), (2) Performance report — compare clicks and impressions to pre-migration baseline (expect some fluctuation; major drops in week 2+ signal issues), (3) Core Web Vitals — confirm new site is not worse than old site on performance metrics, (4) Sitemaps — submit new sitemap.xml immediately after launch and verify it is being processed without errors, (5) URL Inspection — test your most important pages individually to confirm they are indexed and rendering correctly, (6) Manual Actions — check for any new penalties triggered by migration errors. Monitor daily for the first 2 weeks, weekly for the following 6 weeks. Set up GSC email alerts for Coverage errors.