How to Set Up a WordPress Staging Site and Push Changes Live Safely
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
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.
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.
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.

| What goes wrong | Likely cause | Prevent it with |
|---|---|---|
| Site disappears from search after the move | Noindex or robots block left on the new copy | Step 5 |
| Googlebot cannot reach the new server | Firewall or DoS protection blocks it | Step 4 |
| Some visitors see the old site, some the new | DNS caches with a long TTL | Step 3 |
| Orders arrive on the old host after the switch | Two live copies at once | Step 6 |
| Forms or emails stop working | Mail settings tied to the old host | Step 4 |
| Search Console loses verification | Verification file or tag not copied | Step 5 |
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.
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.
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.
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.
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.
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.
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.
robots.txt allows crawling.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.
It depends on your DNS records and caches, which is why Google suggests lowering the TTL a week ahead.
Pick a low-traffic time for your site. Google suggests timing a move to coincide with a recurring dip in traffic.
Keep the old host running, point DNS back if you must, and see WordPress critical error or emergency WordPress fixes.
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.
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.
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
Most break-ins start at the login screen. Use this practical checklist for passwords, two-step login, admin accounts, attempt limits and HTTPS.
Care plans give agencies steady work after launch. See how white label WordPress maintenance works, what to include and what to agree…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout