Migrating Hosts Without Losing Rankings

Checklist for migrating a WordPress site to a new host without losing rankings

Quick answer: A hosting migration protects rankings when you stage a full copy on the new server, test it thoroughly, lower DNS TTL in advance, and switch during a low-traffic window. Downtime and mixed content cause most drops, not the server change itself.

Key takeaways

  • Most ranking drops after a hosting migration come from avoidable mistakes: downtime, mixed content, broken redirects, or a missed database table.
  • Stage and test the full site on the new host before touching DNS, using a hosts-file entry or temporary domain.
  • Lower TTL at least 24–48 hours before the switch so DNS propagates in minutes, not a day.
  • Watch Search Console and analytics for 14 days after the move; normal shuffling settles, a real drop keeps falling.

What actually breaks in a migration and why rankings drop

Search engines do not penalise you for changing hosts. They penalise the symptoms of a bad move: pages that return errors, resources that fail to load, and redirects that stop working. When a crawler hits a 500 error or a mixed-content warning, it may drop those URLs from the index or lower their ranking until the next successful crawl. On a small site, that can look like a sudden loss of traffic even though the content never changed.

Downtime is the most obvious risk, but it is rarely the whole story. A migration that finishes in ten minutes can still cause problems if the new server serves a different PHP version, if the SSL certificate does not cover the www and non-www versions, or if the database copy missed a table that a plugin uses. Each of those issues produces errors that crawlers treat as quality signals.

Changed IP addresses are normal and expected. Google and Bing handle IP changes well as long as the site stays reachable. The trouble starts when the old server is switched off before DNS has fully propagated, leaving some visitors and crawlers hitting a dead IP. That is why the order of operations matters more than the speed of the move.

Mixed content is a quiet killer. If your site loads over HTTPS but a stylesheet, script, or image still points to an http:// URL on the old domain, browsers may block it. The page looks broken to visitors, and crawlers see a degraded experience. A search-and-replace on the database usually fixes it, but only if you remember to run it after the import.

Lost redirects are another common cause. If you had redirects set up in .htaccess, in a plugin, or at the registrar level, they need to exist on the new host too. A missing redirect turns a previously consolidated URL into a 404, and any link equity pointing at it stops flowing. The same applies to permalink settings: if the new WordPress install defaults to plain permalinks, every URL on the site changes and rankings collapse until you fix it.

Plugin data is easy to overlook. Some plugins store settings in the database, some in files, and some in both. A migration that copies only wp-content and the main database tables can leave a form plugin without its entries or a cache plugin with stale configuration. The site may look fine on the surface while key functionality is broken underneath. That is why testing on the new host is not optional.

Plan the cutover window and take a backup you have actually tested

Choose a cutover window when traffic is lowest and when you can be available for at least two hours afterwards. For most small businesses, that is late evening or early morning on a weekday. Avoid Friday afternoons and public holidays. If the site takes orders, check whether the business has a quiet period and use it. The goal is not to hide the move but to have time to fix problems before anyone notices.

Before you touch anything, take a full backup: files, database, and email if the host handles mail. Use your host’s backup tool, a migration plugin, or a manual export via SFTP and phpMyAdmin. Then test the backup. Restore it to a local environment or a temporary directory and confirm that the site loads, the admin login works, and a test order or form submission goes through. An untested backup is a hope, not a plan.

Write down the current DNS records. Export the zone file or take screenshots of every A, CNAME, MX, and TXT record. You will need them to recreate the setup on the new host or at the registrar. If the domain is registered with the same company that hosts the site, consider whether moving the registration makes sense. Services like Namecheap can handle both hosting and domains, which simplifies DNS when you want one provider to manage everything.

Check the new host’s limits before you commit. Disk space, inode count, PHP memory limit, and database size all matter. A WooCommerce store with thousands of products and order records can hit limits that a brochure site never touches. If you are moving to a cheaper plan, read about the costs that show up after moving to a cheap plan so you are not surprised by overage fees or forced upgrades.

Finally, tell the client or the business owner what is happening and when. Give them a short window when the site may be briefly unavailable and ask them not to make content changes during the migration. Coordination prevents the classic problem of a new blog post being written on the old server after the database has already been copied.

The safe order of operations

The sequence that causes the fewest problems is: stage on the new host, prepare DNS, copy files and database, test, then switch. Doing it in that order means the live site stays up until the moment you are ready, and you always have a working copy to fall back on.

Start by creating a staging environment on the new host. Many hosts offer a one-click staging site or a temporary domain. If not, you can use a subdomain like staging.yourdomain.com or a hosts-file entry on your own computer. Install WordPress fresh or use the host’s installer, then import your files and database. Do not point DNS at the new server yet.

Next, prepare the DNS changes without applying them. Lower the TTL on your A record and any CNAME records to the lowest value the provider allows, usually 300 seconds or five minutes. Do this at least 24–48 hours before the switch so the old TTL expires. If you are also moving the domain registration, start that transfer early; it can take several days and you do not want it pending during the cutover.

Copy the files and database. Use a migration plugin, rsync over SSH, or SFTP. For the database, export from the old host and import to the new one, or use a plugin that handles serialised data correctly. If you use a search-replace tool, run it on the staging copy first and check the result. Serialised data in WordPress options and widget settings breaks if you do a naive find-and-replace, so use a tool designed for the job.

Test the staging copy thoroughly before you switch. Log in, submit every form, run a test checkout if you have a store, check that emails send, and confirm that cron jobs are running. Only when the staging site passes your checks should you change DNS. The switch itself should take minutes if TTL was lowered in advance.

DNS and TTL strategy so the switch is a minute, not a day

DNS is the part that makes people nervous, but it is predictable if you prepare. The TTL, or time to live, tells resolvers how long to cache a record. A high TTL means changes take hours to propagate. A low TTL means changes take minutes. Lower it before you need it, not during the migration.

Most DNS providers let you set TTL per record. Set the A record for your root domain and the CNAME for www to 300 seconds. Wait at least the old TTL period, then make the switch. If your old TTL was 24 hours, you need to wait a full day after lowering it before the new low TTL takes effect everywhere. Plan that into your timeline.

When you are ready, update the A record to the new server’s IP address. If you use a CDN or proxy service, update the origin there instead. Keep the old server running for at least 48 hours after the switch so that any resolver still holding the old IP gets a working response. Turning it off too early is how a clean migration turns into a partial outage.

If the domain registration is moving at the same time, use a registrar that gives you clear DNS controls. Dynadot is one option for domain and DNS management when you need to point records at a new server during a transfer. Whatever registrar you use, export the zone file before you start so you can recreate MX, TXT, and any verification records.

After the switch, check propagation from multiple locations using a DNS checker. Do not rely on your own browser, which may be caching the old record. Use a tool that queries public resolvers. Once the new IP is visible from most locations, you can begin post-switch cleanup.

Staging on the new host and how to check the copy really works

A staging copy is only useful if you test the things that matter. Start with the basics: the homepage loads, the admin login works, and permalinks are set correctly. Then move to the functional checks that catch most migration problems.

Test every form on the site. Contact forms, newsletter signups, quote requests, and support forms all need to send. Check that the confirmation message appears and that the email arrives. If you use SMTP, confirm the settings are correct on the new host; many hosts block PHP mail and require an SMTP plugin.

For a WooCommerce store, run a full test order. Add a product to the cart, go through checkout, and confirm that the order appears in the admin and that the confirmation email sends. Test a refund or a status change if those are part of your workflow. Payment gateways often have separate test and live modes, so check that the live credentials are in place. If you are choosing a host for a store, what a WooCommerce store needs from a host covers the server requirements that affect checkout reliability.

Check that scheduled tasks run. WordPress cron handles plugin updates, email queues, and some backup jobs. On the staging site, trigger wp-cron manually or wait for a scheduled event and confirm it fires. If the new host disables cron or uses a system cron, make sure it is configured.

Look for mixed content. Open the browser console and check for blocked resources. Use a tool that scans for http:// references in the database. Fix them on staging before you switch so the live site never shows a broken padlock.

Finally, check the SSL certificate on the staging domain. If the host provides a free certificate, confirm it covers both the root and www. If you use a paid certificate, install it on the new server before the switch. A certificate error on the live site is one of the fastest ways to lose trust and rankings.

What to do about email when the host also handles mail

If your email is hosted on the same server as your website, a hosting migration can take email down too. Decide early whether you are moving email or separating it. Many small businesses now use a dedicated email provider, which removes this risk entirely. If you are still on host-based email, plan the move carefully.

Export your mailboxes before you switch. Use IMAP to copy messages to a local client or to the new provider. Create the same addresses on the new host or email service, then update the MX records. MX changes propagate on their own TTL, so lower those records in advance as well. Keep the old mailboxes active for a few weeks so you do not lose messages sent to the old server.

Check that transactional email from the website still sends. Order confirmations, password resets, and form notifications often use the host’s mail server. If you move to a new host that blocks PHP mail, those messages will silently fail. Install an SMTP plugin and authenticate with a real mailbox before the switch.

If email and hosting are separate, the migration is simpler. You only change the A record for the website and leave MX records alone. That is one reason to separate the two services, even if it costs a little more. The trade-off is another bill to manage, but the reduced risk during a migration is usually worth it.

Post-switch cleanup: search and replace, SSL, redirects, caching, sitemap, analytics

Once DNS points to the new server and the site loads, do a cleanup pass. Start with a search and replace on the database if the domain or URL structure changed. Replace the old staging URL with the live URL, and check for any remaining http:// references. Use a tool that handles serialised data, and take another backup before you run it.

Confirm SSL is active and that both https:// and www versions resolve correctly. Set up a redirect from http to https and from www to non-www (or the reverse) so there is only one canonical version. If you had redirects on the old host, recreate them. Check that old URLs still resolve and that the redirect chains are short.

Clear every cache: the host’s cache, any CDN, and any caching plugin. A stale cache can serve old pages or old URLs after the switch. Purge everything, then load key pages in a private browser window to confirm they are fresh.

Regenerate the sitemap and submit it in Search Console. If you use Yoast or Rank Math, resave the permalinks and the sitemap settings. Check that the sitemap URL is correct and that it returns a 200 status. Analytics should also be checked; if you use a tag manager or a plugin, confirm that tracking still fires on the new server.

Review the server error log for anything that appeared during the switch. A few 404s for missing images or old plugin files are common and easy to fix. Persistent 500 errors point to a PHP or database issue that needs attention before crawlers see it.

The 14-day watchlist: real drop or normal shuffle

After a migration, expect some movement. Search engines recrawl the site, and rankings can fluctuate for a few days. The key is to distinguish normal shuffling from a real problem. Set up a simple watchlist and check it daily for two weeks.

Watch impressions and clicks in Search Console, not just positions. A temporary dip in position for a few queries is normal. A sharp drop in impressions across many pages suggests a crawl issue. Check the coverage report for new errors, and use the URL inspection tool on your most important pages to confirm they are indexed and reachable.

Monitor uptime. If the site goes down for more than a few minutes, note the time and check the server logs. Repeated downtime in the first two weeks is a sign that the new host is not coping, and you may need to adjust resources or move again. Keep a simple uptime monitor running.

Check analytics for traffic sources. If organic traffic falls but direct and referral traffic stay steady, the issue is likely search-related. If all traffic falls, the problem is technical. Look at the bounce rate and page load time on key pages; a slow new server can hurt engagement and rankings.

Compare the 14-day period after the switch with the same period before. A small dip that recovers within a week is normal. A decline that continues past two weeks, or a sudden loss of indexed pages, needs investigation. Common culprits are a noindex tag left on from staging, a robots.txt file that blocks crawlers, or a redirect that sends everything to the homepage.

Decision checklist to run before you move

Before you commit to a hosting migration, run through this checklist. It takes an hour and prevents most of the problems described above. If you cannot tick every item, fix that first.

  • Full backup taken and successfully restored to a test environment.
  • New host meets the site’s requirements for disk, memory, PHP version, and database size.
  • DNS records exported and TTL lowered at least 24 hours in advance.
  • Staging copy tested for login, forms, checkout, email, and cron.
  • SSL certificate ready for both root and www versions.
  • Email plan decided: move, separate, or leave in place.
  • Cutover window scheduled when traffic is low and you are available.

If the site is a client site, add a step for client sign-off on the staging copy. If it is a store, add a test order and a refund test. The checklist is not bureaucracy; it is the difference between a calm switch and a panicked rollback.

Comparison: migration approaches

Approach Best for Downtime risk Effort
Managed migration plugin Small WordPress sites with standard plugins Low if staged first Low to medium
Manual files + database Sites with custom code or large databases Medium; depends on testing Medium to high
Host-assisted migration Businesses without technical time Low if host stages Low, but less control
Rebuild on new host Sites that need a redesign anyway High if content is not migrated carefully High

The right choice depends on how much custom code you have and how comfortable you are with the command line. A managed plugin is usually enough for a brochure site. A store with custom checkout logic may need a manual approach and more testing. If you are unsure which hosting model suits the destination, the hosting models explained can help you match the plan to the site.

Cost is part of the decision. Renewal prices are often the trigger for a move, as covered in why renewal pricing drives migrations. But the cheapest plan is not always the cheapest move if it lacks staging, SSH, or adequate resources. If you are moving to managed WordPress, when managed WordPress hosting earns back the migration effort explains the trade-offs.

Frequently asked questions

Will changing hosts affect my SEO?

Changing hosts does not inherently hurt SEO. Rankings drop when the migration causes downtime, broken pages, mixed content, or lost redirects. If you stage the site, test it, and switch DNS cleanly, search engines should barely notice the change beyond a normal recrawl.

How long should I keep the old host active after the switch?

Keep the old server running for at least 48 hours after DNS changes, and ideally a week. Some resolvers cache records longer than expected. Keeping the old server up ensures that any stragglers still reach a working site instead of an error page.

Do I need to tell Google about a hosting migration?

No special notification is required if the domain and URLs stay the same. If URLs change, set up redirects and submit a new sitemap. You can use the change of address tool in Search Console when moving to a new domain, but a host change alone does not need it.

What is the biggest cause of traffic loss after a migration?

Mixed content and missing redirects are the most common culprits. A page that loads over HTTPS but pulls in an insecure script can look broken, and a redirect that disappears turns a consolidated URL into a 404. Both are fixable with a search and replace and a redirect audit.

Can I migrate a WooCommerce store without losing orders?

Yes, if you copy the full database and test checkout on staging before switching. Orders live in the database, so a complete export and import preserves them. Run a test order on the new host and confirm that payment gateways and confirmation emails work before you change DNS.

What to do next

Open your current host’s control panel and download a full backup now, even if you are not moving today. Restore it to a local or staging environment and confirm it works. That single step turns a future migration from a risk into a routine task.

Then write your cutover plan: the date, the window, the DNS records you need to change, and the person who will be available afterwards. Lower your TTL 48 hours before the switch. Stage the site on the new host and run the checklist above. When everything passes, change the A record, watch the logs for two weeks, and keep the old server running until the dust settles.

If you are still choosing a destination, compare the hosting models and read the renewal terms before you commit. The best migration is the one you only have to do once.

Disclosure: some links in this article are affiliate links. If you buy through them we may earn a commission at no extra cost to you.

Looking for a domain instead?

We hold a curated portfolio of premium .com and .si names — short, brandable, and ready to launch. Every listing shows a fixed price and a direct purchase path.

Browse premium .com domainsExplore .si names

Leave a Comment

Your email address will not be published. Required fields are marked *

D-Marketing Assistant

Hello! How can I help you regarding D-Marketing services today?

Please provide your details so we can get back to you.

share facebook Share to Facebook whatsapp Share to Whatsapp twitter Share to Twitter linkedin Share to linkedin