Moving Your Website to a New Host Without Losing Google Rankings

A website migration is the most dangerous thing you can do to your online presence. I’ve watched businesses lose 70% of their organic traffic overnight because someone changed platforms without a plan. I’ve seen companies that took two years to recover. And I’ve seen some that never did.

The irony is that most migrations are done to improve the website. New design, better platform, faster hosting. But if you don’t handle the SEO side correctly, your shiny new website will be invisible to Google for months, or permanently. Here’s how to move without losing what you’ve built.

When you actually need to migrate

First, let’s be honest about when migration is necessary and when it’s vanity.

Good reasons to migrate: Your platform is end-of-life or insecure (like sites still running on old Joomla). Your current site physically can’t do what your business needs. You’re moving from a proprietary website builder to something you own. Your hosting is so bad that page speed is unfixable without moving servers.

Bad reasons to migrate: You’re “bored” with the design. Your competitor has a new website and you feel behind. A sales rep convinced you their platform is “better for SEO.” Someone told you WordPress is outdated (it powers 43% of all websites, it’s not going anywhere).

Every migration carries risk. If your current site is ranking well and generating leads, the bar for migrating should be high. You can often redesign within your existing platform and avoid the most dangerous part of migration: changing URLs.

The anatomy of a migration disaster

Let me tell you what goes wrong, because I’ve cleaned up dozens of these messes across Spain.

URLs change without redirects. This is the number one killer. Your old site had /services/web-design/, your new site has /our-services/website-design/. Without a 301 redirect from the old URL to the new one, every link pointing to that page, from Google, from other websites, from your Google Business Profile, hits a 404 error. Google sees a dead page, removes it from the index, and your ranking evaporates.

Content is “consolidated.” The agency decides that 15 service pages are “too many” and merges them into 5. Each of those 15 pages was ranking for specific keywords. Now that keyword targeting is destroyed, and 10 pages that were working simply cease to exist. This is not a design decision, it’s an SEO decision, and it should be made by someone who understands the traffic implications.

The new site launches on a different domain. Moving from olddomain.com to newdomain.com is a full domain migration, the riskiest move in SEO. Even with perfect redirects, expect a temporary ranking drop of 20-40% that can take 3-6 months to recover. If you don’t have perfect redirects, you might as well start from scratch.

Technical SEO is ignored. The new site doesn’t have an XML sitemap. Canonical tags are wrong or missing. The robots.txt accidentally blocks crawlers. Schema markup from the old site isn’t carried over. Meta titles and descriptions are reset to defaults. Each of these alone is fixable, but together, they tell Google your new site is a completely different, unoptimized entity.

The migration checklist that actually works

I’ve refined this process over dozens of migrations. Follow it exactly and you’ll preserve 90%+ of your traffic. Skip steps and you’re gambling.

Step 1: Crawl your existing site. Before touching anything, crawl your current site with Screaming Frog or a similar tool. Export every URL, its title, meta description, H1, word count, and HTTP status. This is your baseline. If you don’t have this, you can’t verify anything after migration.

Step 2: Identify your valuable pages. Go to Google Search Console. Export your pages by clicks and impressions for the last 12 months. Sort by clicks. The top 20-30 pages are your priority, these are generating your organic traffic. Every one of these pages must have a 1:1 equivalent on the new site. Non-negotiable.

Step 3: Build the redirect map. Create a spreadsheet: Column A is every old URL. Column B is the corresponding new URL. Every single page. Not just the important ones, every page. Because you don’t know which pages other websites link to. A redirect map for a 50-page site takes about 2 hours. For a 500-page site, maybe a day. This is the most important document in the entire migration.

Step 4: Preserve content and meta data. Every page’s title tag, meta description, H1, and body content should either stay the same or be improved on the new site. Never downgrade content during a migration. If a page had 1,500 words of useful content and the new design only fits 500, that’s a design problem, not a content problem. Fix the design.

Step 5: Test before going live. Set up the new site on a staging URL. Crawl it. Check every redirect works. Verify all meta data is correct. Test page speed. Check mobile rendering. Run it through Google’s Rich Results Test. Do this on staging, not in production. Fixing things after launch is exponentially harder.

Step 6: Launch and monitor. Implement all 301 redirects at the server level (not with JavaScript, Google doesn’t reliably follow JavaScript redirects). Submit the updated sitemap in Google Search Console. Monitor coverage reports daily for the first two weeks. Check for crawl errors, indexing drops, and 404 spikes.

The timeline nobody tells you about

Even with a perfect migration, expect this:

Week 1-2: Google discovers the changes. Some pages may temporarily drop from the index as Google processes the redirects. This is normal. Don’t panic.

Week 2-4: Most redirects are processed. Your pages start reappearing at their previous (or close to previous) rankings. Some fluctuation is normal.

Month 1-3: Rankings stabilize. If you did everything right, you should be within 10% of your pre-migration traffic by month 2. If you’re down more than 20% after 6 weeks, something went wrong in the migration.

Month 3-6: Full recovery or improvement. If the new site is genuinely better (faster, better content, better UX), you may actually see rankings improve beyond pre-migration levels. This is the goal.

Anyone who tells you a migration will have “zero impact” is lying. Even Google’s own documentation acknowledges that migrations cause temporary ranking fluctuations. The question is whether you lose 10% temporarily or 60% permanently.

Platform-specific traps I see in Spain

Wix to WordPress: Common migration. Wix URLs have a specific structure (/post/your-blog-post) that doesn’t map cleanly to WordPress. Every URL needs manual redirect mapping. Also, Wix’s SEO meta data doesn’t export easily, you’ll need to rebuild it.

HTML to WordPress: Old static HTML sites often have .html extensions. Make sure your WordPress redirects handle the extension properly. I’ve seen migrations where /about.html redirected to /about/ everywhere except the server config, which served a 404.

Shopify to WooCommerce: Shopify’s URL structure (/collections/, /products/) is different from WooCommerce. Product URLs, collection URLs, and image URLs all need redirecting. Shopify also doesn’t give you server-level access, so you need to implement redirects before canceling your Shopify subscription.

Any platform to a JavaScript SPA: This is the one I fight clients on most. Migrating from a server-rendered site to a single-page React or Vue app is an SEO risk that’s rarely justified for a business website. If you absolutely must, use server-side rendering (SSR) or static site generation (SSG). Client-side rendering alone will hurt your indexation.

What to do if the migration already went wrong

If you’re reading this after a botched migration, your traffic dropped and nobody set up redirects, here’s the recovery plan:

Immediate: Implement 301 redirects for your top 50 pages (by traffic) right now. Today. Every day without redirects is lost authority.

Week 1: Complete the full redirect map for all pages. Submit the new sitemap in Search Console. Request indexing for your most important pages.

Week 2-4: Monitor Search Console for crawl errors. Fix 404s as they appear. Check that Google is re-indexing your pages with the correct URLs.

Month 1-3: Be patient. Google needs time to process the changes. Focus on creating new content and building fresh links to your new URLs to accelerate recovery.

Full recovery from a botched migration typically takes 3-6 months. If redirects are never implemented, the old authority is permanently lost and you’re essentially starting SEO from scratch.

The cost of getting it right vs. getting it wrong

A properly managed migration costs an extra €500-2,000 in SEO planning and execution on top of the web design cost. That covers the crawl, the redirect map, the meta data preservation, and post-launch monitoring.

A botched migration can cost you 6-12 months of lost organic traffic. If your site generates €5,000/month in leads through organic search, that’s €30,000-60,000 in lost business. The math is painfully obvious.

I’d rather spend two extra days on redirect mapping than two extra years trying to recover lost rankings. And with proper hosting, the technical migration itself is smoother and faster, reducing the window where things can go wrong.

If you’re planning a migration, get the SEO right first. Everything else is secondary.