Why migrations put your rankings at risk
A website migration is any major change to how your site is structured or delivered: moving to a new platform, redesigning with new URLs, switching domains, or changing from HTTP to HTTPS. Done carefully, nobody notices. Done carelessly, you can wipe out years of search rankings overnight, and recovery can take months.
The danger is that Google has built up an understanding of your old site: which URLs exist, which pages have authority, and which keywords each page ranks for. A migration can sever those connections. If Google can't find the new home of an old page, the rankings that page earned simply evaporate.
The good news is that a website migration without losing SEO is entirely achievable. It just demands a methodical plan rather than a hopeful "flick the switch and see". The single biggest cause of migration disasters is rushing the redirect work, and that's exactly what this guide helps you avoid.
Before you start: crawl and benchmark the old site
You can't protect what you haven't recorded. Before touching anything, create a complete inventory of your current site. Use a crawler such as Screaming Frog (free for up to 500 URLs) to export every existing URL, page title and meta description. This list is the backbone of your entire migration.
Next, benchmark your current performance so you can tell afterwards whether anything broke. Note your top-ranking keywords and positions, your highest-traffic pages, and your overall organic traffic. Pull this from Google Search Console and Google Analytics, and save dated screenshots you can compare against later.
Identify your most valuable pages specifically, the ones that bring traffic, rankings or backlinks. These are the pages you protect at all costs. A handful of pages usually drive the majority of organic results, and losing one of them hurts far more than losing a forgotten archive page.
Map old URLs to new URLs (the critical step)
If your URLs are changing, this is the step that makes or breaks the migration. Build a spreadsheet with every old URL in one column and its exact new destination in the next. Every meaningful old page should map to the most relevant new page, ideally an equivalent one covering the same topic.
Avoid the lazy shortcut of redirecting everything to the homepage. Google treats a flood of homepage redirects as "soft 404s" and passes on little or no ranking value. A retired services page should redirect to the new services page, not to the front door. Relevance is what preserves the authority.
Where an old page has no direct equivalent, choose the closest related page rather than dropping it. Only deliberately remove pages you genuinely want gone, and even then, decide consciously rather than by accident. This mapping document becomes the instruction sheet for your redirects.
Set up 301 redirects correctly
A 301 redirect is a permanent instruction that tells browsers and Google "this page has moved here for good", and it passes the large majority of the old page's ranking value to the new one. This is the mechanism that carries your SEO across the migration, so it has to be right.
Use 301s, not 302s. A 302 signals a temporary move and won't reliably transfer authority, a classic, costly mistake. Implement every mapping from your spreadsheet, then test a sample by visiting old URLs and confirming they land on the correct new page in a single hop, with no chains of multiple redirects.
Watch for redirect chains and loops, where one URL redirects to another which redirects again. Each hop leaks a little authority and slows the page. Aim for one clean redirect from old to final destination. It's tedious work, but this is precisely where careful migrations beat careless ones.
- check_circleUse 301 (permanent), never 302 (temporary), for moved pages
- check_circleRedirect each old URL to its closest relevant new page, not the homepage
- check_circleAvoid chains — one hop from old URL to final destination
- check_circleDon't forget redirects for old image and PDF URLs that earned links
- check_circleKeep the redirect rules in place for at least a year, ideally permanently
Preserve on-page SEO and technical signals
Redirects move the addresses; you also need to carry over the content signals Google relies on. As you rebuild pages, keep the page titles, meta descriptions, headings and core body content as close to the originals as you can. A redesign that quietly rewrites every title and slashes word counts can drop rankings even with perfect redirects.
Check the technical plumbing too. Make sure each new page has the correct canonical tag pointing to itself, that your robots.txt isn't accidentally blocking the site, and, critically, that the temporary "noindex" or "discourage search engines" setting used during the build is switched off at launch. Forgetting that one toggle has de-indexed countless sites.
Regenerate your XML sitemap so it lists only the new, live URLs with current dates, and keep your internal links pointing directly to new URLs rather than relying on redirects. Clean internal signals help Google re-map your site far more quickly.
Launch day and the first 48 hours
Where possible, launch during a quieter traffic period so any issues affect fewer visitors and you have headroom to react. The moment the new site is live, run through a short launch checklist before you relax: the site must be indexable, redirects must fire, and forms and key pages must work.
Immediately submit your new sitemap in Google Search Console and use the URL Inspection tool to request indexing of your most important pages. This nudges Google to recrawl quickly rather than waiting days to discover the changes on its own. If you've moved domains, use Search Console's Change of Address tool.
Then watch closely. Spot-check a spread of old URLs to confirm they redirect properly, and crawl the live site again to catch broken links or pages that slipped through. The first 48 hours are when fixable problems are cheapest to fix; a missed redirect caught on day one is trivial, but caught a month later it may have already cost rankings.
Monitor, fix and recover after launch
Some short-term wobble in rankings and traffic is normal as Google re-processes your site; a dip in the first week or two doesn't mean disaster. What you're watching for is whether it stabilises and recovers, or keeps sliding. Compare against the benchmarks you saved before launch.
Live in Google Search Console for the following weeks. The Coverage and Pages reports flag URLs Google can't index; the crawl errors highlight broken pages and missed redirects. Each error is a clue, fix the underlying redirect or page and request reindexing. Most post-migration losses trace back to a handful of overlooked redirects.
Give it time. Even a flawless migration can take a few weeks for rankings to fully settle as Google recrawls and re-evaluates. If you've crawled, mapped, redirected and monitored properly, the typical outcome is that rankings hold steady or return to where they were, which is exactly the point of doing the work.
Frequently asked questions
Will I lose my Google rankings when I migrate my website?expand_more
You don't have to. Rankings are lost during migrations mainly when old URLs aren't redirected to their new equivalents, or when content and technical signals are stripped out in a redesign. With a full URL inventory, careful one-to-one 301 redirects, preserved page content and close monitoring in Search Console, most sites hold their rankings or recover them within a few weeks.
What is the difference between a 301 and a 302 redirect?expand_more
A 301 is a permanent redirect that tells Google a page has moved for good and passes on the large majority of its ranking value. A 302 is a temporary redirect and won't reliably transfer that authority. For website migrations where pages are moving permanently, always use 301s, using 302s by mistake is a common and costly cause of lost rankings.
How long does it take to recover rankings after a migration?expand_more
Expect some short-term fluctuation in the first one to two weeks as Google recrawls and re-evaluates your site. A well-executed migration usually sees rankings stabilise or fully recover within two to four weeks. If they're still declining beyond that, it normally points to a technical issue, most often a missing or incorrect redirect, that needs fixing.
Do I need to redirect old pages if I'm just redesigning, not changing domain?expand_more
Only if the URLs change. If a redesign keeps every URL identical, you may not need redirects, but you must still preserve titles, headings and content, and ensure the site isn't accidentally left set to block search engines at launch. If any URLs change during the redesign, each old URL needs a 301 to its new equivalent to protect its rankings.