How to Migrate a WordPress Site to a New Host Without Losing SEO Rankings

Migrate WordPress to a New Host Without Hurting Your SEO

Changing hosting providers is one of those tasks that scares most site owners. The fear is understandable: a bad migration can break your site, lose visitors, and worst of all, tank the search rankings you’ve worked months or years to build. The good news? When you migrate WordPress to a new host in the correct order, your traffic and rankings should stay exactly where they are.

This guide walks you through the entire process step by step, from your first backup to the final post-migration SEO checks. Whether you’re moving because of slow load times, poor support, or rising renewal prices, this walkthrough is designed for beginners who want a safe, zero-downtime transition.

Why a Bad Migration Can Hurt Your SEO

Before jumping into the steps, it helps to understand what actually puts your rankings at risk during a host change:

Extended downtime while Googlebot tries to crawl your site
Broken internal links after files or database tables are missing
Missing redirects for changed URLs
Indexing issues caused by leftover “noindex” tags from staging environments
Slower server response times on the new host (Core Web Vitals impact)

Avoiding these five pitfalls is essentially what the rest of this article is about.

Pre-Migration Checklist

Before touching anything, prepare your environment. A calm, organized start prevents 90% of migration disasters.

Item	Why It Matters
Current host login (cPanel, FTP, database)	Needed to export files and SQL data
New host account ready	Destination must be configured first
Domain registrar access	Required to update DNS / nameservers
Google Search Console access	To monitor crawl errors post-migration
Full site audit (URLs + status codes)	Benchmark to compare after the move

Step 1: Lower Your DNS TTL (24 to 48 Hours Before)

This is the step most tutorials forget, yet it makes the biggest difference for zero-downtime migrations. Log into your DNS provider and change the TTL (Time To Live) of your A record and CNAMEs to 300 seconds (5 minutes).

When you later switch the IP to your new host, propagation will happen in minutes instead of hours. Less downtime means less chance of Googlebot hitting an unavailable server.

Step 2: Create a Complete Backup

You need two things: all WordPress files and the MySQL database. You can do this manually or with a plugin.

Option A: Plugin Method (Recommended for Beginners)

Duplicator creates a single installable package
All-in-One WP Migration exports everything to one .wpress file
UpdraftPlus sends backups to cloud storage automatically

Option B: Manual Method (Maximum Control)

Connect via FTP/SFTP and download the entire public_html (or your WordPress root) folder
Open phpMyAdmin on your old host, select your WordPress database, and click Export (SQL format, Quick method)
Store both files locally and on a cloud drive

Step 3: Set Up WordPress on the New Host

On your new hosting account:

Create a new MySQL database and user, then save the credentials
Upload your WordPress files via FTP to the new server’s root directory
Import your .sql file into the new database via phpMyAdmin
Edit wp-config.php with the new database name, user, and password

Step 4: Test Before Switching DNS

Never change your DNS until you’ve confirmed the site works on the new server. Two safe methods:

Hosts file edit: temporarily point your computer to the new IP by editing your local hosts file. You’ll see the new server while everyone else still sees the old one.
Temporary domain: most hosts provide one (e.g. yoursite.newhost.com) so you can preview the site

Click through key pages, test forms, check the admin panel, and verify images load. If anything is broken, fix it now while the old site is still serving live traffic.

Step 5: Update DNS and Switch Traffic

Once testing is successful, point your domain to the new host:

Update the A record to the new server’s IP, or
Change the nameservers at your registrar if your new host manages DNS

Because you lowered the TTL in Step 1, most visitors will see the new site within 5 to 15 minutes. Keep the old host active for at least 7 days as a safety net.

Step 6: Handle Redirects (Only If URLs Change)

If you’re only changing host but keeping the same domain and URL structure, no redirects are needed. Your SEO stays intact automatically.

However, if you’re also switching domains or moving from HTTP to HTTPS, set up 301 redirects in your .htaccess file:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^olddomain\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.olddomain\.com$
RewriteRule (.*)$ https://www.newdomain.com/$1 [R=301,L]

Also use the Change of Address tool in Google Search Console if the domain changes.

Step 7: Post-Migration SEO Checks

This is where you protect the rankings you migrated for. Run these checks within the first 48 hours:

Robots.txt check: ensure it doesn’t say Disallow: /
Search Console settings: confirm Settings > Reading > Discourage search engines is unchecked in WordPress
Submit a fresh sitemap through Search Console
Use URL Inspection on 5 to 10 key pages to confirm they’re indexable
Check Core Web Vitals, since a new host means new server performance
Crawl your site with Screaming Frog or a similar tool and compare against your pre-migration audit
Verify SSL is properly installed and there are no mixed content warnings
Monitor 404 errors in Search Console for 30 days

Step 8: Decommission the Old Host

After 7 to 14 days of monitoring, when DNS has fully propagated and traffic looks normal, you can safely cancel your old hosting account. Download one final backup of the old server before doing so, just in case.

Common Mistakes to Avoid

Cancelling the old host too early. Always wait at least a week.
Forgetting email accounts. If your old host also handles email, migrate those too or set up new MX records.
Leaving caching plugins active during migration. Disable them, migrate, then reactivate.
Not testing SSL before the DNS switch.
Skipping the staging test and going live blindly.

Final Thoughts

Migrating WordPress to a new host doesn’t have to cost you a single ranking position. The secret is sequencing: lower TTL first, test before switching, monitor afterward. Thousands of sites move hosts every day without traffic drops because they follow this exact order.

If you’re moving to Kelio-Host, our support team handles the entire migration for free on most plans, including the SEO checks above. You focus on your business, we handle the technical details.

Frequently Asked Questions

How long does a WordPress migration take?

For a typical small to medium site, expect 1 to 3 hours of active work, plus a few hours of DNS propagation. Large sites with heavy databases may take longer.

Will I lose any traffic during the migration?

If you lower your DNS TTL in advance and keep both hosts running during the switch, downtime should be under 5 minutes. Most visitors won’t notice anything.

Do I need to tell Google I’m changing hosts?

No, not when only the host changes. Google only needs to be notified if your domain name changes, via the Change of Address tool in Search Console.

What’s the easiest migration plugin in 2026?

For sites under 512 MB, All-in-One WP Migration remains the easiest. For larger sites, Duplicator Pro or Migrate Guru handle big databases without size limits.

Should I migrate manually or use a plugin?

Plugins are faster and safer for beginners. Manual migration gives you more control and is preferred for very large sites, custom configurations, or when plugins fail due to server limits.

What if my rankings drop after migration?

Check first for crawl errors, server response time, and accidental noindex tags. Minor fluctuations in the first 2 weeks are normal as Google recrawls. If drops persist beyond 30 days, run a full technical audit comparing pre and post-migration data.