Hosting · Guide
How to Change Hosts Without Losing SEO
Short answer
Yes, you can change hosts without losing SEO if the URLs stay the same. Copy the full site to the new host, test it on a temporary address, lower the DNS TTL at least a week before the move, then update DNS and keep the old host live until its traffic reaches zero. Google treats a host-only move differently from a domain or URL change, so no new redirects are needed when every URL stays identical.
Key takeaways
- A host-only move keeps every URL the same, so Google does not need new redirects or a Change of Address.
- Lower the DNS TTL to a few hours at least a week before the move so the switch spreads faster.
- Test the full copy on the new host before you change DNS, and protect that test copy with noindex.
- Keep the old host running until its server logs show zero traffic, then shut it down.
- A short drop in Googlebot crawl rate after the switch is normal and usually recovers within a few days.
- WordPress.org recommends PHP 8.3 or newer and MySQL 8.0 or MariaDB 10.11 or newer as of November 2026.
Can you change hosts without losing SEO?
Yes, you can change hosts without losing SEO when every URL stays the same.
A hosting change means switching providers or moving to a content delivery network, and Google's hosting guide covers only moves that do not change the user-visible URL. That is the common case for a WordPress site that moves servers but keeps its domain, paths and HTTPS addresses.
SEO loss usually comes from errors during the move, not from the new server itself. Broken pages, missing images, a leaked noindex rule or a blocked crawler can all hurt rankings. A careful copy, a full test and a planned DNS switch remove most of that risk.
Google also notes that a temporary drop in Googlebot crawl rate right after launch is normal. The rate then rises again over the next few days, as long as Googlebot does not meet serious problems or slowdowns on the new host.
What do you need before you start?
You need a full backup, new host access, DNS access and a list of every service tied to your domain.
Start with a backup you control, not only a copy on the old host. How to back up WordPress explains the files and database you must save before any move. Store one copy away from both hosts so a failed copy does not leave you with nothing.
Check the new host against the WordPress requirements before you copy anything. WordPress.org recommends PHP 8.3 or greater, MySQL 8.0 or MariaDB 10.11 or greater, and HTTPS support as of November 2026. Ask the new host which PHP and database versions your site will run on, and match them to the versions your plugins need.
Make a short inventory before you move. List your domain, email, DNS provider, CDN, analytics, forms, payment gateway and any scheduled tasks. Email often lives outside WordPress hosting, so check where your MX records point before you touch DNS.
Pick a low-traffic window for the DNS switch. Google advises timing a move for a lower-traffic period when possible, so fewer visitors meet a problem and more server capacity is free for Googlebot.
How do you lower DNS TTL before the move?
Lower the TTL to a few hours at least a week before the move.
TTL, or Time to Live, is the number of seconds a DNS record may stay cached. Cloudflare's TTL docs explain that a longer TTL speeds up lookups but makes updates take longer to reach users. A short TTL does the opposite, so it helps a planned switch spread faster.
Google gives the same timing in its hosting guide. It suggests lowering the TTL to a conservative low value, for example a few hours, at least a week in advance of the move. That week gives old cached values time to expire before you change the record.
Cloudflare sets Auto TTL to 300 seconds, or 5 minutes, for proxied records, and that value cannot be edited. For DNS-only records, Cloudflare allows a TTL from 60 seconds on non-Enterprise plans to 1 day, with Auto set to 300 seconds as of November 2026.
Follow these steps in your DNS panel:
- Open the DNS records for your domain at your registrar or DNS provider.
- Find the A record for your root domain and the record for www, if it has its own record.
- Change the TTL on those records to a few hours, or 300 seconds if your provider allows it.
- Leave every other record alone, including MX, TXT and CNAME records for email and verification.
- Wait at least a week, or at least one old TTL period, before you change the IP address.
Do not lower the TTL and change the IP in the same hour. Resolvers that cached the old record will keep serving the old IP until that old TTL expires, so the early change is what makes the switch fast.
How do you copy WordPress to the new host?
Copy the files and the database, then point the copy at its new database.
A WordPress site has two parts: the files in wp-content, themes and plugins, plus uploads, and the database that holds posts, users and settings. If the domain and URLs stay the same, you can move by copying both parts. You do not need to reinstall WordPress from scratch.
Use one of these three routes. Pick the one your new host supports best.
| Route | How it works | Best for |
|---|---|---|
| Host migration team | Staff copy the files and database for you | A first move, or a large site |
| Migration plugin | A plugin on the old site sends a copy to the new host | A standard single site |
| Manual copy | You export the database and upload the files yourself | Full control, or when plugins fail |
For a plugin move, install the new host's migration plugin on the old site and follow its prompts. WP Engine's free Site Migration plugin copies the database and wp-content files, but it excludes disallowed plugins, logs, backups and caches. WP Engine's migration guide shows the plugin installed in the User Portal first.
For a manual move, create a new empty database on the new host, import the old database into it, then upload the files. Edit wp-config.php only if the database name, user, password or host changed. On a new host, those values almost always change.
If you run a store, plan a second copy. WP Engine advises running its migration plugin a second time for ecommerce sites, timing that run, then placing the old site in maintenance mode before the final DNS change. That second run catches orders and customers added after the first copy.
How do you test the copy before changing DNS?
Test the copy on a temporary address and check every page, image, form and download.
Google advises uploading a copy to the new host and testing it before any DNS change. Open the copy in a browser and review pages, images, forms and downloads such as PDF files. A test that only checks the home page is not enough.
Protect the test copy from search engines. Google suggests a temporary hostname, such as beta.example.com, with a noindex robots rule in the HTML or in HTTP headers. That rule stops the test copy from being indexed while you work on it.
Check that Googlebot can reach the new host. Google says to verify the temporary hostname in Search Console if you use one, then use the URL Inspection Tool to check access. If the new firewall or denial-of-service protection blocks Googlebot, fix that before you switch DNS.
Work through this short checklist on the copy:
- Log in to wp-admin and open Tools, then Site Health, to check PHP, database and HTTPS.
- Open your 5 most visited pages, plus checkout, login and search pages.
- Submit a test form and check that email arrives.
- Open images and files from old posts, not only new ones.
- Check that your Search Console verification file or meta tag is present on the copy.
Fix every error on the copy, not after the switch. A fix made on the test copy is cheap, while the same fix made live can cost you visitors and crawl time.
How do you switch DNS and go live?
Remove crawl blocks first, then update DNS to point at the new host.
Google lists two steps for the start of the move. First, remove any temporary blocks to crawling from the new copy, including a robots.txt file that disallows all crawling and any noindex meta tags or headers used during testing. Second, update the DNS settings to point to the new hosting provider.
Change only the record that points to the web server, usually the A record for the root domain and www. Do not change MX records unless your email provider is also moving. If you change nameservers instead, copy every DNS record first, because a missing MX or TXT record can break email and verification.
DNS changes do not reach every visitor at once. Kinsta notes that DNS propagation can take a few hours to several days, and that TTL has a strong effect on that time.
Kinsta also notes that most DNS record TTLs are set between 1 and 4 hours by default. During that window, some visitors reach the old server and some reach the new one, so both copies must work.
Keep the old site live during the switch. Do not cancel it, delete its files or change its content while traffic is still split between the two servers. Any order or comment made on the old copy after the new copy was made will not appear on the new host unless you copy it again.
How do you check SEO after the move?
Check status codes, canonical tags, robots rules, the sitemap and Search Console in the first week.
Start with the pages Google cares about most. Open your home page, your top 10 posts and your top 5 landing pages on the new host and confirm each returns a 200 status code. Check that each page shows its own self-referencing canonical tag and the same title and meta description as before.
Use Search Console every day for the first week. Google advises watching the index coverage graphs in Search Console and checking server logs on both the old and new servers. As DNS spreads, traffic on the old server should fall and traffic on the new server should rise by a similar amount.
Test the live URL in the URL Inspection Tool for your home page and 2 or 3 key pages. That tool shows whether Googlebot can fetch the page now. If a page shows a crawl error, fix the cause on the new host and run the live test again.
Speed is part of the check, not a separate project. How to speed up WordPress covers caching and image checks you can run after the move. If a page is much slower on the new host, check PHP version, caching and image sizes before you blame the move itself.
Watch for these warning signs in the first 7 days:
- A rise in 404 or 500 errors in Search Console.
- Pages that return 200 but show a maintenance page or a blank screen.
- A sitemap that lists old URLs, or a robots.txt file that blocks a whole section.
- Search Console verification lost because the HTML file or meta tag did not copy over.
If rankings dip for a few days, do not change URLs, titles or content at the same time. Google says ranking fluctuation during a move is normal, and changing more things at once makes it harder to find the cause.
When do you need redirects or a Change of Address?
You need redirects only if URLs change; a host-only move needs none.
Google treats a host-only move and a URL move as different jobs. A host-only move keeps the domain, protocol and paths the same, so no new redirects are needed. A URL move changes HTTP to HTTPS, changes the domain, or changes URL paths, and that move needs a redirect for each old URL.
If your move also changes URLs, use server-side permanent redirects. Google recommends 301 and 308 redirects and says 301 and other permanent redirects do not cause a loss in PageRank. Redirect each old URL to its closest matching new URL, not to the home page.
Keep redirect chains short. Googlebot can follow up to 10 hops in a chain, but Google advises redirecting to the final destination directly. A chain of 3 or more hops wastes crawl time and can fail if one link in the chain breaks.
Do not use the Change of Address tool for a host-only move. That tool is for a move from one domain or subdomain to another, after 301 redirects are live. It does not apply when only the server changes.
For a URL change, expect a longer wait. Google says that for medium-sized sites, it can take a few weeks or more for Google to show the new URLs instead of the old ones, and larger sites take longer. A sitemap with the new URLs can help Google find them faster.
How long should you keep the old host?
Keep the old host until its server logs show zero traffic, then shut it down.
Google gives a clear shutdown rule: check the server logs on the old provider, and once traffic to the old provider reaches zero, you can shut down the old hosting. That rule covers both visitors and Googlebot, so do not rely on your own browser alone.
In practice, keep the old host for at least 2 weeks after the DNS switch. That window covers slow DNS caches and crawlers that visit on a longer cycle. A store or membership site may need longer.
Check the old logs before you cancel. Look for any remaining requests for pages, images, files or API endpoints.
If a single page still gets traffic on the old host, find out why before you shut it down. It may be a hardcoded link, a cached DNS record or a service that still points at the old IP.
Raise the TTL back to its normal value after the move is stable. A short TTL is useful before a switch, but a longer TTL speeds up normal lookups. Cloudflare notes that longer TTLs increase the chance of cached results, so a normal value of a few hours suits most sites.
What mistakes should you avoid?
Avoid changing the host, domain and design at the same time.
Google advises changing one thing at a time. If you move host, change domain, switch themes and rewrite content in one week, you cannot tell which change caused a ranking drop. Move the host first, confirm the site is stable, then make the next change.
Avoid these common errors:
- Leaving a noindex tag or a Disallow rule on the live copy after testing.
- Forgetting the Search Console verification file, so you lose access to Search Console data.
- Changing DNS before the copy is tested, so visitors see a broken site.
- Cancelling the old host on launch day, so you have no rollback copy.
- Forgetting email, CDN or payment webhooks that point at the old host.
- Changing URLs at the same time without a redirect map.
Check the new host's limits before you move. A plan that meets the WordPress requirements on paper can still be too small for your plugins and traffic. How to choose WordPress hosting explains the limits to compare. If the new host cannot handle a short rise in Googlebot crawling, ask the host about capacity first.
Finally, keep a copy of the old site for at least 30 days after the old host is shut down. A local backup gives you a way back if a missing file or setting only shows up weeks later.
Frequently asked questions
Will changing hosts hurt my Google rankings?
It can hurt rankings if the move breaks pages, slows the site, blocks Googlebot or leaves a noindex rule live. If every URL stays the same, the copy is tested before DNS changes and the old host stays live until its traffic reaches zero, the risk is low. A short dip in crawl rate after the switch is normal.
How long does a WordPress host move take?
A small site can move in a few hours, while a large site or store can take a day or more to copy and test. Add at least a week before the move to lower the DNS TTL, plus time after the switch to watch Search Console and server logs. Keep the old host for at least 2 weeks after DNS changes.
Do I need to tell Google when I change hosts?
No, you do not need to use the Change of Address tool for a host-only move, because that tool is for domain or subdomain changes. You should still use Search Console to check that Googlebot can reach the new host, watch index coverage and confirm that verification still works after the move.
Can I change hosts and domains at the same time?
You can, but it is safer to do them one at a time. A host move keeps URLs the same, while a domain move needs a redirect for every old URL and a Change of Address in Search Console. Doing both at once makes it harder to find the cause if traffic drops, so move the host first and confirm the site is stable.
What should I do if traffic drops after a host move?
Check the new copy for 404 and 500 errors, a noindex tag, a robots.txt block and a missing SSL certificate. Test key pages with the URL Inspection Tool in Search Console and compare server logs on both hosts. Fix the cause on the new host, do not change URLs or titles at the same time, and give Google a few days to recrawl.
Sources
- Changing Your Web Hosting and SEO Google Search Central
- Site Moves and Migrations Google Search Central
- Time to Live (TTL) Cloudflare
- DNS Propagation: The Website Owner's Guide Kinsta
- WordPress Requirements WordPress.org
- How to Migrate an eCommerce Site WP Engine Support
- How to Migrate from Kinsta to WP Engine WP Engine
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
