Website Migration Without Losing Your Google Rankings
By Toy Wen Da, Co-Founder · · 7 min read · scored 95/100
A website migration is any major change to a site's domain, platform, URL structure, or design that can affect search visibility. The first thing to do before touching anything is to build a full list of your current URLs, because that list becomes the map for every redirect you'll need later.
Check Your Redirects Before You Do Anything Else
Before you plan, audit, or map anything, check whether your current redirects even work. Run your old and new URLs through the free Redirect Checker. It shows you the status code, the redirect chain, and whether a URL lands where it should. This matters because a broken or missing 301 redirect is the single most common reason a site migration tanks organic traffic. Catching it early, before launch, costs you nothing and saves weeks of recovery work later.
What Counts as a Website Migration
Not every site update is a migration. A typo fix isn't. A new blog post isn't. But any of these count:
- Moving to a new domain name (rebranding, acquiring a new URL)
- Switching platforms or content management systems
- Moving from HTTP to HTTPS
- Changing your URL structure (folders, slugs, or subdomains)
- A full visual redesign that changes templates or navigation
- Moving to a new web host or server environment
Any one of these can change how search engines read your pages. Combine two or three at once, a new CMS and a new domain, say, and the risk compounds fast.
Why Website Migration and SEO Are So Tightly Linked
Search engines rank URLs, not just content. When a URL changes without a proper signal pointing from old to new, Google treats the new page as unproven. It has to re-crawl, re-evaluate, and re-rank it from close to zero. That's why migration SEO planning focuses almost entirely on preserving the signals tied to each URL: redirects, internal links, canonical tags, and structured data.
The Website Migration Process, Step by Step
This is the order that keeps risk lowest, using the tools already built into most CMS dashboards and hosting panels.
1. Inventory Every Page on Your Site
Before you migrate anything, list every page, post, product, and document currently live. Most CMS platforms have an export or sitemap view under a setting like Pages or Content in the admin dashboard, use it to pull a full list. Note which pages get real traffic and which are dead weight. This inventory is also your chance to retire thin or outdated pages instead of carrying them forward.
2. Map Every Old URL to a New One
For every URL that will change, write down its destination. Spreadsheets work fine for a few hundred pages. This map becomes your redirect instruction list, nothing should move without a entry here.
3. Set Up 301 Redirects
In most CMS platforms, redirects live under a menu labeled Redirects, URL Forwarding, or inside the SEO plugin's settings panel. Add each old-to-new pair from your map. A 301 tells search engines the move is permanent and passes along the ranking value the old URL had built up.
4. Check Your Canonical Tags
If old and new versions of a page are both reachable during the move, common during staging or phased rollouts, canonical tags tell search engines which version is the real one. Check the page's SEO settings panel (often under a Canonical URL field) for every template type, not just a sample.
5. Verify Your robots.txt File
A single wrong line in robots.txt can block search engines from an entire section of your new site. Check it through your hosting or CMS settings before you announce the launch publicly. This file is usually editable from a File Manager or a dedicated robots.txt setting in your SEO plugin.
6. Confirm Analytics Is Still Tracking
Open your analytics dashboard and confirm data is still flowing from the new site's pages, not just the homepage. According to Google Analytics Help, tracking codes need to be present on every page you intend to measure, a template rebuild can silently drop them from an entire site section.
7. Submit a Fresh XML Sitemap
Once the new site is live, generate an updated sitemap reflecting the new URLs, and submit it through Google Search Console and Bing Webmaster Tools. This speeds up how fast search engines find and re-crawl your migrated pages, per Google Search Central's own crawling guidance.
8. Watch Traffic on Both Old and New URLs
For weeks after launch, keep checking whether the old site's traffic is declining normally while the new site's traffic grows. A legacy URL still pulling meaningful traffic months later usually means its redirect never got set up.
When Your Website's Own Tools Are Enough, and When They Aren't
This is the honest fork in the road. Not every migration needs outside help.
| Situation | Built-in tools usually enough? | Why |
|---|---|---|
| Fixing one broken redirect on one page | Yes | A single entry in your redirect settings panel solves it directly |
| Renaming a handful of URLs for a rebrand | Yes | Small volume, easy to map and verify by hand |
| Moving an entire site to a new domain | No | Hundreds or thousands of URLs need systematic mapping, not manual entry |
| Switching content management systems | No | Templates, metadata, and URL structure often change simultaneously |
| A recurring pattern of 404s after a past migration | No | Points to a structural redirect gap, not a one-off fix |
| Testing whether redirects work before launch | Yes, with the right tool | A free Redirect Checker covers this without extra setup |
If you're touching one URL, your CMS dashboard is enough. If you're moving the whole site, or if problems keep recurring, you need a full crawl and a tracked redirect map, not spot checks.
Common Website Migration Mistakes
- Skipping the content freeze. Making content edits while URLs are being mapped creates a moving target and missed redirects.
- Forgetting internal links. Redirects catch external traffic, but old internal links still point at outdated URLs, adding unnecessary redirect hops.
- Leaving noindex tags on from staging. A tag meant to keep a staging site out of search results sometimes survives into production and quietly de-indexes the whole site.
- Launching without pre-launch testing. Checking usability, mobile rendering, and redirects before go-live catches problems while they're still cheap to fix. A quick website speed test before launch also flags performance regressions the new template might introduce.
- Assuming the sitemap updates itself. An old sitemap still listing retired URLs slows down how fast search engines trust the new structure.
- Treating launch day as the finish line. Traffic and redirect health both need checking for weeks, not just on launch day.
If you're also evaluating a new platform as part of this move, it's worth comparing how different website builders handle SEO before you commit, see this comparison of website builders for SEO. And if a redesign is part of the plan, check whether your current bounce rate is a symptom worth fixing first, covered in this guide to website bounce rate.
FAQs
How long does a site migration take to recover lost rankings?
It varies by site size and how clean the redirects are. Sites with properly mapped 301s on every URL typically see rankings stabilize faster than sites that discover gaps weeks after launch.
What is website migration SEO, specifically?
It's the practice of preserving a site's existing search signals, rankings, links, and indexed pages, while the site's domain, platform, structure, or design changes underneath it.
Do I need a developer for a site migration?
For a small site with few URL changes, no. For a full domain or CMS change across hundreds of pages, a developer or SEO specialist reduces the chance of a redirect getting missed.
Will my traffic drop during migration?
Some temporary dip is common as search engines re-crawl new URLs. A sustained drop usually signals a missing redirect, a blocked robots.txt, or a canonical error.
What's the difference between a site migration and a redesign?
A redesign changes the look and layout. A migration involves anything that can change URLs or underlying infrastructure, a redesign only becomes a migration if URLs or platform change too.
Get Your Redirect Map Right Before You Launch
A site migration succeeds or fails on the boring details: redirects mapped correctly, canonicals pointing the right way, and a sitemap that reflects reality. Start by running your URL list through the free Redirect Checker, then compare your current SEO standing against what you expect after the move. Talk to the team to get a sample report showing exactly where your site stands before you move it.
Resources / References
Sources
About the author
SearchBlueprint researched, wrote and scored this article with the content pipeline our customers run on their own sites. The score in the byline is what our content engine gave this page before it published. Nothing here is reviewed by hand, which is the point: it is the product's output, published where anyone can check it.