Quick answer
To migrate a website without losing SEO: record a Search Console and Analytics baseline, crawl the old site, map every old URL to its closest new URL, keep the content that ranks, and password-protect staging. On launch, remove staging blocks, switch on single-hop 301 redirects, update internal links, canonicals and the sitemap, and use Change of Address for domain moves. Then monitor Search Console daily and keep redirects for at least a year.
Key takeaways
- Record a baseline before anything changes.
- Map every old URL to its closest new URL; never redirect everything to the homepage.
- Keeping the content that ranked matters as much as the redirects.
- Google advises keeping redirects for at least one year.
- Expect temporary fluctuation; a steady drop means something is missing.
A redesign, a new CMS, a move to https or a new domain can wipe out years of search traffic in a week if URLs change without a plan. It can also go almost unnoticed by Google when it is done carefully. The difference is a checklist followed before, during and after launch.
This is the checklist we use. It follows Google’s site move guidance and adds what we have learned from WordPress, Shopify and custom-built sites. A migration is one of the projects our technical SEO services handle end to end.
Before launch: plan and map
- Record a baseline. Export Search Console performance by page for the last 3 to 12 months, plus Analytics landing pages and conversions. You need this to judge the migration later.
- Crawl the old site and list every URL that returns 200, plus important PDFs and images.
- Find the URLs that matter: pages with clicks, conversions or external links. These must not lose their content.
- Build a redirect map. One row per old URL, pointing to the closest matching new URL. Avoid sending everything to the homepage.
- Keep the content. Moving pages is fine; deleting the text that earned rankings is what loses them. Decide consciously what to merge, and use our content consolidation approach for old posts.
- Protect the staging site with a password, not just noindex, so it is never indexed.
Launch day: redirects and signals
- Remove staging blocks. Check robots.txt and that no live page carries
noindex. - Switch on 301 redirects from every old URL to its new one, in a single hop. Google’s redirects guide explains why permanent server-side redirects are best.
- Update every internal link to the new URLs, so the site does not rely on its own redirects.
- Check canonicals point to the new URLs, not the old domain or staging.
- Submit the new sitemap in Search Console.
- Domain change? Verify both domains in Search Console and use the Change of Address tool.
- Re-check tracking: Analytics, Tag Manager, ads conversion tags and call tracking.
After launch: monitor and fix
- Test the redirect map with a crawler: every old URL should return a 301 to a page that returns 200.
- Watch Search Console daily for two weeks: Page indexing, 404s, Crawl stats and performance on both old and new URLs.
- Expect some movement. Google says visibility may fluctuate temporarily during a move. A steady drop on specific pages after a few weeks usually points to a missing redirect or lost content.
- Keep the redirects. Google advises keeping them for as long as possible, generally at least one year. We recommend never removing them.
- Update external profiles: Google Business Profile, social profiles and directories that link to you.
Migration checklist by phase
| Phase | Tasks |
|---|---|
| Before | Baseline, full crawl, priority URLs, redirect map, content decisions, password-protected staging |
| Launch day | Remove blocks, 301s in one hop, internal links, canonicals, new sitemap, Change of Address (domain moves), tracking |
| Weeks 1-2 | Crawl old URLs, Search Console daily, fix 404s and missing redirects |
| Months 1-12 | Compare with baseline, keep redirects, update external profiles |
What goes wrong most often?
- Old URLs redirected to the homepage instead of matching pages.
- The new site launched with the developer’s
noindexstill on. - Service pages shortened during the redesign, so the content that ranked is gone.
- Menus rebuilt in JavaScript that crawlers struggle to follow; see JavaScript links and AI crawlers.
- Duplicate versions left live (old and new paths both returning 200). Our canonical vs noindex guide explains how to resolve them.
Content changes during a migration need the same care as URLs; our content SEO services can rewrite and merge pages while keeping what ranks. For a real example of rebuilding a site’s technical foundations, see our Jeep Nepal case study.
Want a second opinion on your site? Ask us for a free SEO review and we will tell you what to fix first, in plain language.
Explore More
Reviewed by
K.K. Bhatta
K.K. Bhatta is a general digital marketer at Queens Digital Agency: hands-on across SEO, paid media, and whatever platform changes next. A lifelong learner rather than a one-topic specialist, he tests ideas on live campaigns before writing about them, and stays skeptical of anything that has not actually been tried.
Every claim in this article was checked against a live source before publishing.
It can if URLs or content change without redirects and planning. With a redirect map, kept content and post-launch checks, most sites keep their visibility.
Google says visibility may fluctuate temporarily. Well-planned moves usually settle; persistent losses point to missing redirects or removed content.
Google advises as long as possible, generally at least one year. We recommend keeping them permanently.
Only when moving to a new domain. It is not used for redesigns on the same domain.
Sources and references
Facts in this guide come from the sources below, checked live on 8 November 2026. Everything else is our own working practice, stated as such.