How to Migrate Website Without Losing SEO: CMS Move vs Domain Move

Most migrations don’t fail on launch day. They fail weeks earlier, in a planning call where somebody says “while we’re at it, let’s clean up the URLs too.” That one sentence has cost more rankings than any server error I can think of.

So how do you migrate website without losing SEO? Start by deciding what is actually changing. If only the CMS is changing, keep every URL exactly as it is, and you won’t need redirects at all. If the domain is changing, map every old URL to its new match and 301 them one to one.

That one decision shapes your redirect plan, your timeline, and how long recovery takes. If you came here looking for how to migrate a website without losing rankings, this is where it starts, not in the redirect spreadsheet. Below is the plan I follow, split by what you are moving.

Decide What You Are Actually Moving Before Anything Else

When someone asks me how to migrate website without losing SEO, my first question back is always the same: what exactly is changing? There are only two moves that matter here. You are changing the CMS, or you are changing the domain.

Everything else sits inside one of those two, whether it’s a redesign, a host switch or an HTTPS upgrade. Treat both as the same job and you’ll either apply redirects you never needed, or skip the ones you did.

The link between website migration and organic traffic is boring once you see it. Google has to recrawl your pages, work out which new URL replaces which old one, and move the signals across. The less of that work you create, the less traffic you put at risk.

Most SEO risks during website migration come from stacking changes on top of each other. New domain, new design, new URL structure, new CMS, all in one weekend, and when traffic drops nobody can say which change did it. Google’s guidance is to change one thing at a time and launch during a quiet traffic period, which also happens to be the only way you can debug it afterwards.

Export Every URL Before You Touch Anything

Before a single file moves, export a complete list of your current URLs. Crawl the live site, then pull your top pages from Google Search Console and your landing page report from GA4. That export becomes your redirect map, your QA checklist, and your proof of what was working before.

This is the least glamorous step in any guide on how to migrate website without losing SEO, and it’s the one people skip. Do it first, because the moment the old CMS is switched off, that list is gone. Rebuilding it from memory never works, and the pages people forget are never the homepage. They are the old blog posts quietly earning half of your long tail traffic.

Save the Search Console data too: clicks, impressions, and average position for at least the last 12 months. After launch, that file is the only honest answer to “did we lose anything?” Without it, every post migration conversation turns into guesswork and vibes.

How to Migrate Website Without Losing SEO When Only the CMS Changes

If you are only changing the CMS, keep the URL structure exactly the same. Same paths, same trailing slashes, same casing. Do that and you need zero redirects, which means zero redirect risk, and the move barely registers with Google at all.

A lot of guides treat this as optional, or even suggest tidying up the URLs while you are in there. I disagree, and strongly. When you change URLs on a CMS move, you are asking Google to deindex the old URL and index a new one for no benefit, and in my experience the results of that are not reliable.

Yes, a 301 is a permanent redirect, and yes, Google honours it. But honouring a redirect and reprocessing thousands of them at the speed you would like are two very different things. So why spend that goodwill on a URL change nobody asked for?

Sometimes the new platform forces your hand. Some systems insist on a /blog/ prefix, a different product path, or a trailing slash you can’t remove. If that happens, stop calling it a CMS move and run it as a URL migration instead, with a full redirect map and the domain checklist below.

The rest of a same URL move is mostly infrastructure. Google’s advice for changing hosting is to drop your DNS TTL to a few hours at least a week before launch, noindex the staging copy, then remove that noindex before you switch DNS. Use URL Inspection to confirm Googlebot can actually reach the new setup, watch the logs on both servers, and keep the old host running until its traffic hits zero.

The most common way this goes wrong is forgetting to remove the staging block. One stray noindex tag or a leftover Disallow line in robots.txt will quietly deindex a site that migrated perfectly. Check it on launch day, then check it again the next morning.

How to Migrate Website Without Losing SEO When the Domain Changes

On a domain move, the URL structure matters far less. Every URL is changing anyway, so you’re redirecting the whole site whether the paths stay the same or not. What matters is that the mapping is one to one and that nothing lands on a page it does not belong on.

Use server side permanent redirects, 301 or 308, and point each old URL straight at its final destination. Google asks you to keep redirect chains to no more than three hops, and warns against dumping a pile of old URLs onto the new homepage. Redirecting unrelated pages to the homepage is the quickest way to turn a migration into a traffic loss.

For a domain or subdomain change, file a Change of Address in Google Search Console. It applies to domain level moves only, so don’t reach for it on an HTTP to HTTPS switch or a www change on the same domain. You need both properties verified under the same account, and every variant of the old domain submitted, including the ones you never actively used.

That request forwards signals for 180 days, and Google recommends keeping your redirects live for at least a year. Keep paying for the old domain for that long as well, so nobody else picks it up and inherits your links.

Now the myth worth killing. You’ll read everywhere that 301s leak 10 to 15 percent of your link equity, and it’s one of those numbers that gets repeated until it sounds official. Google’s documentation says redirects do not lose PageRank, so you don’t need to worry about losing link credit at all.

So the real answer to how to preserve SEO rankings during migration is something fairly dull: a complete, accurate map, applied once, with no chains. Expect some wobble anyway, because Googlebot has to visit every old and new URL at least once before the move settles. Google says most pages on small and medium sites move across within a few weeks, and larger sites take longer.

Make the New Site Faster Than the Old One

People search for how to migrate website without losing SEO and almost never think about page weight. Whether you are moving CMS or domain, the new site should be lighter and faster than the one it replaces. Not the same, faster. A migration is the one moment where you get to throw out years of plugin bloat and bad theme decisions for free.

Set the target before the build, not after. Google’s Core Web Vitals thresholds are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less, and a CLS of 0.1 or less, measured at the 75th percentile of real page loads. Run your top 20 templates through PageSpeed Insights on staging and compare each one against the same page on the live site.

Here’s the catch, and it’s a real one. Shipping a brand new design, new URLs, and a new domain in the same week means you’ll never know what caused what. If the redesign is heavy, launch it on the existing URLs first, let it settle, then move the domain.

Your First 48 Hours After Launch

Everything you did to migrate website without losing SEO can still be undone in the first two days by one stray line in robots.txt. Launch isn’t the finish line, it’s the start of the part that decides the outcome. Treat the next 48 hours as your website migration SEO checklist and work through it in order:

1. Check robots.txt and meta robots. Confirm no staging Disallow rule or noindex tag survived the launch.
2. Spot check redirects. Test your top 50 pages by traffic plus a sample of old blog posts, and confirm each lands directly on its match with a single 301.
3. Submit sitemaps. Push the new sitemap in Search Console, and keep a sitemap of the old URLs so you can watch that index count fall to zero.
4. Verify Search Console. Both properties verified, Change of Address filed if the domain moved, and the new property collecting data.
5. Check analytics is firing. Confirm your GA4 tags survived the template change, because losing tracking on launch day is a problem you discover far too late.
6. Watch the server logs. Googlebot will hit the new site harder than usual, so make sure there is headroom.

Then stop touching it. Resist the urge to publish new content, rewrite titles, or optimise anything for the next couple of weeks. You want one variable in play if something goes sideways, not six.

Rankings will move around while this settles, and that’s normal rather than proof you broke something. The question is whether the trend recovers over a few weeks or keeps sliding. If it’s still sliding after a month, go back to the redirect map, because that’s where the answer usually is.

FAQs

Does a website migration always cause a traffic drop?

No, a well planned migration can move with almost no visible dip, especially when the URLs stay the same. Some short term fluctuation is normal while Google recrawls and reindexes, because it has to visit every old and new URL at least once. What isn’t normal is a drop that keeps deepening after a few weeks, which usually points to redirects or an indexing block.

How do you migrate website without losing SEO when you only change hosting?

A hosting change keeps your URLs, so no redirects and no Change of Address are needed. Lower your DNS TTL about a week beforehand, test the copy on the new host, remove any noindex or robots.txt block before you switch DNS, then watch the logs on both servers. Keep the old host running until its traffic reaches zero.

How do you migrate website without losing SEO on a large ecommerce site?

Move it in sections rather than all at once, which is what Google recommends for larger sites. Release your highest traffic templates first, confirm that batch is redirecting and reindexing cleanly, then move the next one. Expect the whole thing to take longer than a small site, because Googlebot still has to crawl every old and new URL before the move settles.

How long should I keep 301 redirects after moving domains?

Keep them for at least one year, which is what Google recommends, and leave them in place indefinitely if you can. External links to your old URLs will keep arriving for years, and every one of them needs somewhere to land. Hold on to the old domain registration for that period too.

Do I need redirects if I am only changing CMS?

Not if you keep every URL identical, which is exactly why you should. Redirects are only needed when a URL actually changes, so a same URL CMS move skips the riskiest part of the whole job. If your new platform forces a path change, treat it as a URL migration instead.

Final Thoughts

Strip away the noise and most SEO best practices for website migration fit on a sticky note. Know exactly what is changing, export your URLs before anything moves, keep the URL structure when only the CMS changes, map one to one when the domain changes, and ship something faster than what you had.

The sites that lose traffic are almost never the ones that missed a clever technical trick. They are the ones that changed four things at once and had no list to check against afterwards. Boring and well documented wins here, every time.

If you remember one thing about how to migrate website without losing SEO, make it this: the riskiest decision happens in a planning meeting, not on a server. Get that decision right and the rest is careful, unglamorous work. Get it wrong and no redirect map is going to save you.