To move WordPress to new host servers without losing SEO, keep your URLs the same, test the full copy on the new host before you touch DNS, then switch DNS and keep the old host running until traffic has moved. Google has a guide for site moves without URL changes, and it follows this order. Most hosting moves go wrong in the details, not the steps: a search setting left on, server rules not copied, or email records forgotten.
This checklist covers each stage. Our WordPress website migration service can do the move for you. We checked Google’s and WordPress.org’s pages on 14 November 2026.
Move WordPress to new host: the checklist
Before you start
- Take a full backup: all files and the database. Store a copy away from both hosts. Test that it restores.
- Save your current numbers: top pages and clicks from Search Console, and a speed test of your main pages.
- Write down every DNS record: A, CNAME, MX, TXT. Mail records are the ones people forget.
- Check where your email lives. If mailboxes are on the old host, plan their move first.
- List everything that runs on the old server: cron jobs, caching rules, security rules, redirects in .htaccess or server config, SSL certificates, CDN settings.
- Check the new host meets WordPress and your plugins’ requirements for PHP and database versions.
- Lower the DNS TTL at least a week before the switch. Google suggests a conservative low value, such as a few hours.
- Choose a quiet day and time for the switch.
Build the copy on the new host
- Copy the site files to the new host.
- Export the database from the old host and import it on the new one.
- Update wp-config.php if the database name, user or password changed.
- Test the copy before DNS changes. Use a temporary hostname or your computer’s hosts file. WordPress’s guide also describes temporarily changing the siteurl and home values for testing.
- Keep the test copy out of search results (noindex) while you test, and remove that block before launch.
- Reset permalinks if your custom links do not work. Save the Permalinks settings again.
- Copy over the rules from your old server: redirects, caching, security.
- Confirm that Googlebot can reach the new host and that no firewall blocks it. Google’s URL Inspection tool helps.
- Carry over your Search Console verification, such as the HTML file or meta tag.
Be careful with search-and-replace tools on the database. The WordPress guide says that if the database and URL stay the same, you can move by copying the files and the database. Search-replace belongs to moves where the domain or URLs change, and the guide warns that a blanket replace can break serialised data. It also says never to change the GUID column.
Switch DNS
- Test the new copy one last time. Forms, logins, checkout, search, images.
- Pause content changes on the old site, or plan a final sync.
- Update the DNS records to point to the new host. This starts the real move.
- Remove any robots.txt block or noindex tag that you used while testing.
- Check the WordPress setting that discourages search engines is off (Settings, then Reading).
After the switch
- Compare server logs on old and new hosts. Traffic should shift steadily to the new one.
- Use a public DNS checker to see the new records spread.
- Watch the indexing and crawl reports in Search Console. Google says crawl rate can dip right after a move and then recover.
- Test every form and place a test order if you run a store.
- Send and receive an email on every mailbox.
- Check SSL on every page. Look for mixed content warnings.
- Run a crawl for 404 errors, broken images and redirect chains.
- Keep the old host running until its logs show no more traffic. Then cancel.
Plan for new content and orders during the move
Your site keeps changing while you build the copy. Comments arrive, posts get edited and, on a store, orders come in. The database you copied on day one is out of date by switch day. Decide how you will catch up:
- Freeze edits on the old site for the last few hours before the switch.
- Take a fresh database export just before you point DNS to the new host.
- For a store, pause checkout briefly, or compare order lists on both hosts after the switch.
- Tell your team the date and time, so no one edits the old site afterwards.
A short freeze is cheaper than lost orders or lost comments. Because DNS changes spread unevenly, some visitors may still reach the old host for a while. That is another reason to keep it running.
What can go wrong, and the usual cause
| Symptom | Usual cause | Fix |
|---|---|---|
| Pages drop out of Google | A noindex tag, a robots.txt block or the search-engine discouragement setting left on after testing | Remove the block and request indexing in Search Console |
| Inner pages show 404 errors | Permalinks need resaving, or server rewrite rules are missing | Save permalinks again; copy the rewrite rules |
| Old redirects stopped working | Redirects lived in the old server config, not in WordPress | Recreate them on the new host |
| Images missing | Uploads folder not fully copied, or wrong file permissions | Copy the uploads folder again and check permissions |
| Padlock missing or mixed content warnings | SSL not issued yet, or some links still use http | Install the certificate; fix http links |
| Email stopped | MX records changed or missing | Restore the old MX records |
| Site slower than before | Cache not set up, different PHP settings or no CDN | Configure caching and compare PHP settings |
| Forms do not send | Mail settings differ on the new host | Check SMTP or mail settings and send a test |
When the URLs or domain change too
Everything above assumes your URLs stay the same. If the domain, the URL structure or the protocol changes, it is a bigger move. You then need a URL map and 301 redirects. Google’s guide for moves with URL changes says to use permanent server-side redirects, send each old URL to its final page, and keep the redirects for at least a year. Google’s Change of Address tool is only for moving to a different domain. It is not needed when only the host changes.
Change one thing at a time. A new host, a new theme, a new domain and a rewrite together make any traffic drop hard to explain. Move first, then redesign. For scope and pricing of larger moves, see our guide to website migration service costs, or our website migration services.
Migration plugin or manual move?
WordPress.org lists several migration and backup plugins, including UpdraftPlus and WP Migrate Lite. A plugin saves time on a simple site. A manual move gives you more control over large databases and custom server rules. Read each plugin’s page for limits before you use it. Our checklist applies to both routes. The plugin moves the files and database. You still need the checks before and after.
Do it yourself or hire someone?
| Situation | Likely fit |
|---|---|
| Small brochure site, standard plugins, you have time to test | DIY is reasonable |
| Store with live orders | Get help. Orders placed during the move can be lost without a plan |
| Business email on the same host | Plan the mail move first, or get help |
| Custom server rules, multisite or a very large database | Get help |
| Search traffic pays the bills | Get a second pair of eyes on the checklist |
At WebUncles, a website migration starts from US$49 (₹3,000), depending on complexity. A same-domain host move is usually at the simple end. A store, a multisite network or a large site costs more. We give a fixed quote after a free consultation.
Book a free consultation before migration. Tell us your current host, your new host, and whether email and a store are on the site. We will tell you what the move involves. Afterwards, our maintenance plans keep backups and updates running.
FAQ
Will moving WordPress to a new host hurt my SEO?
Not if the URLs stay the same and the move is done carefully. Google has a guide for moves without URL changes. Problems come from mistakes such as a leftover noindex tag or missing server rules, not from the move itself.
Do I need 301 redirects when I change host?
Only if your URLs change. With the same domain and the same URLs, you do not need new redirects. You do need to copy any existing redirects from the old server.
How long does DNS take to switch?
It depends on the TTL you set. Lower it ahead of time, as Google advises. Google suggests a few hours, set at least a week ahead. Then use a public DNS checker to watch the change spread.
Do I need the Change of Address tool?
No, not for a host change. It is for moving from one domain to another.
How do I test the new host before switching DNS?
Use a temporary hostname or the hosts file on your computer. WordPress’s guide also mentions temporarily changing the siteurl and home values. Keep the test copy out of search results while you test.
When can I cancel the old host?
Wait until its logs show no more traffic and you have checked email, forms and SSL on the new host. Google advises keeping the old server running until then.
Can I use a plugin to move my site?
Yes. Migration and backup plugins exist, such as UpdraftPlus and WP Migrate Lite. Read each plugin’s limits first, and still run the checks before and after the move.
