Black FridayCyber Monday 2026
14Days
15Hrs
34Mins
40Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

How to Move WordPress to a New Host Without Losing Traffic or Rankings

Moving hosts is where sites lose orders, emails and rankings by accident. Copy first, test on the new server, lower DNS TTL, switch DNS, then keep the old host until traffic is gone.

wpallsolution 9 min read

Move WordPress to a new host is one of those jobs that looks like a copy-and-paste and then quietly costs you orders, emails and rankings. A new host is not the risky part. The risky part is the switch: DNS caches, a forgotten “discourage search engines” box, a form that does not send, a firewall that blocks Googlebot. This guide gives you a plan that lets you test everything before real visitors arrive, and tells you what to watch after.

Quick answer

Make a full backup of files and database, upload a copy to the new host and test it thoroughly before anything public changes. Check that Googlebot can reach the new server and that no test block (robots.txt disallow or noindex) is left on the copy. Lower your DNS TTL at least a week before the move, switch the DNS records when you are ready, and then watch the traffic on both old and new servers. Keep the old host until traffic to it reaches zero. If your visible URLs also change, you are doing a different, bigger job: use Google’s site move guide.

How this guide was prepared: the steps follow Google Search Central’s hosting-change guide and the WordPress handbook listed under Sources, read on October 21, 2026. Items marked as our own advice are general practice, not quotes from those documents. We did not migrate your site, and every host has its own tools, so use your new host’s documentation for the technical details.

Before you change anything

  • Back up files and database and keep a copy outside the old host. The WordPress handbook starts the “moving to a new server” advice with exactly this. See Is your WordPress backup really safe?
  • Do not cancel the old hosting until the move is complete and traffic has stopped arriving there.
  • Pick a quiet time. Google advises timing a move for lower traffic where you can.
  • Write down everything that depends on the old host: email accounts, cron jobs, redirects, SSL, CDN and any firewall rules.

Move WordPress to a new host: the decision tree

Move WordPress to a new host flowchart: five questions covering URL changes, backups, a tested copy, crawl blocks and orders during the move
Five checks before you point your domain at the new server.
  1. Are your visible URLs staying the same? If not, follow Google’s site move guide for URL changes (Step 1).
  2. Do you have a full backup of files and database? If not, stop and make one (Step 2).
  3. Does the copy work on the new host before DNS changes? Fix it before you switch (Steps 3 and 4).
  4. Is a test noindex or crawl block still on the new copy? Remove it before launch (Step 5).
  5. Does the site take orders, bookings or sign-ups? Plan a freeze window (Step 6).

Symptoms and likely causes

What goes wrongLikely causePrevent it with
Site disappears from search after the moveNoindex or robots block left on the new copyStep 5
Googlebot cannot reach the new serverFirewall or DoS protection blocks itStep 4
Some visitors see the old site, some the newDNS caches with a long TTLStep 3
Orders arrive on the old host after the switchTwo live copies at onceStep 6
Forms or emails stop workingMail settings tied to the old hostStep 4
Search Console loses verificationVerification file or tag not copiedStep 5

7 steps to move WordPress to a new host safely

Step 1: Confirm that this is a hosting move, not a URL change

Google separates two cases. If you only change the hosting provider or move to a CDN and the visible URLs stay the same, use its hosting guide. If the domain, the HTTP or HTTPS version or the URL structure also changes, you need Google’s site move guide, which asks for a URL mapping and redirects. Do not combine both at once if you can avoid it: Google advises making big changes one after another, not everything at the same time. If you must change the site address, the WordPress handbook explains the WP_HOME and WP_SITEURL settings and warns not to leave temporary code in functions.php.

Step 2: Take and verify a full backup

Back up the WordPress files, uploads, plugins and the database. Then check the backup: do the files open, and is the database export complete? Keep one copy off the old host. If your old host offers a migration tool or a plugin migrates the site for you, still make your own backup first.

Step 3: Lower the DNS TTL a week ahead

Google suggests lowering the TTL of your DNS records to a conservative low value, for example a few hours, at least a week before the move, so that new DNS settings spread faster. Ask your DNS provider where to change it. This single step reduces the time when some visitors reach the old server and some reach the new one.

Step 4: Upload a copy and test it before DNS changes

Put the copy on the new host and test it thoroughly. Google suggests a test environment, perhaps with IP-restricted access, or a temporary hostname such as beta.example.com so you can check that the site works and that Googlebot can reach it. Open the pages, images, forms and downloads. For a shop, test a full order in a test payment mode, and check that emails send. As our own advice, resave permalinks, clear caches and check that the SSL certificate is installed on the new host. Google also warns that you should check your firewall or DoS protection does not block Googlebot’s access to the new servers.

Step 5: Remove test blocks and keep Search Console verification

Google specifically warns about this: while building a copy, many owners block crawling with robots.txt or add noindex tags or headers, and these must be removed from the new copy when you are ready. In WordPress, also check Settings → Reading and make sure “Discourage search engines from indexing this site” is off. Google also reminds you to carry over your Search Console verification file or tag, or ownership verification will stop working after the move. If you use Rank Math or another SEO plugin, check its robots settings as well.

Step 6: Plan the switch, especially for orders and sign-ups

If your site takes orders, bookings or registrations, new data can land on the old host after you copy the database. Decide on a short freeze window: pause orders or content changes, take a fresh copy, restore it on the new host, and switch DNS straight after. This is our own practical advice. After the switch, remember that some visitors may still reach the old host for a while, so keep it running until traffic stops. Also plan email: if your mail is hosted with the old provider, do not change the records that deliver it unless you have moved the mailboxes.

Step 7: Switch DNS, then watch both servers

Google describes the DNS change as the actual move. After you update the records, keep an eye on server logs on both hosts: you should see traffic drop on the old one and rise on the new one. Check that different networks see the new site. Google notes that a temporary drop in Googlebot’s crawl rate right after a hosting change is normal, followed by a steady increase over the next few days, as long as Googlebot does not meet serious problems. When traffic to the old host reaches zero, you can shut it down. Keep your backup for a while longer.

Version and hosting differences

  • Many hosts offer their own migration tools or staging, which can replace some manual steps.
  • Multisite installations need extra care. The WordPress handbook covers them separately.
  • CDNs, page caches and security plugins may keep settings for the old host.
  • Very large sites can take longer to copy and to be recrawled.

How to verify the fix

  • Your home page, a post, a form and (for shops) a test order work on the new host.
  • The page source has no noindex tag, and robots.txt allows crawling.
  • Search Console still shows you as a verified owner and can fetch your pages.
  • Emails from forms and orders arrive, and the SSL padlock shows on every page.

How to prevent it from happening again

Frequently asked questions

Will moving hosts hurt my rankings?

It does not have to. If your URLs stay the same, the site stays reachable and nothing blocks Google, a hosting move should not remove you from search. Google says to expect temporary fluctuations.

How long does DNS take to change?

It depends on your DNS records and caches, which is why Google suggests lowering the TTL a week ahead.

Should I move on a weekday?

Pick a low-traffic time for your site. Google suggests timing a move to coincide with a recurring dip in traffic.

What if something breaks after I switch?

Keep the old host running, point DNS back if you must, and see WordPress critical error or emergency WordPress fixes.

What to do next

Back up, copy, test, lower the TTL and only then switch. If you would rather have someone check the plan, wpallsolution offers independent plugin support and emergency WordPress fixes if a move goes wrong. We cannot promise zero downtime without seeing your site and hosts.

Sources and official documentation

Last reviewed: October 21, 2026. WordPress is a trademark of the WordPress Foundation. wpallsolution is not affiliated with or endorsed by the WordPress Foundation, Automattic or Google.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us