ENHEIT

payless.host

Moving Host Without Losing Your Google Rankings: A Step-by-Step Guide

Updated Nov 22, 2026

Before you begin

Moving a website without breaking search rankings requires planning, not speed. Set aside two hours when you can work without interruption. The move itself takes twenty minutes; the rest is verification.

Take a full backup from your current host before touching anything. Download it to your machine. If your host offers automated backups, download the most recent one — do not assume it will still be there after you cancel.

Check your domain registrar login works and that you can edit DNS records. If you registered through your current host, transfer the domain to a registrar like Namecheap first. A domain held by the host you are leaving is a domain you do not fully control.

Step 1: Set up the new host without pointing the domain

Sign up with the new provider but do not change your domain's nameservers yet. Upload your site to the new host using a temporary URL or staging domain — most hosts provide one automatically.

If you are moving to HostGator, upload files via cPanel. For DreamHost, use SFTP or the panel's file manager. The method varies, but every host documents it.

Import your database using phpMyAdmin or the host's import tool. Update the site's configuration file to point at the new database. For WordPress, that is wp-config.php.

Test the staging URL in a browser. Click through every major page. Forms, images, logins — if it breaks on staging, it will break when live.

Step 2: Lower your DNS TTL

Log into your domain registrar or DNS manager. Find the TTL (time to live) setting for your A record and lower it to 300 seconds.

This tells the internet to check for updates every five minutes instead of every few hours. Make this change twenty-four hours before the move. If you skip it, some visitors will see the old site for hours after you switch.

Step 3: Point the domain at the new host

Change your domain's A record to the IP address the new host provided. If the new host uses nameservers, update those instead.

DNS changes propagate gradually. Check progress by visiting your site in a private browsing window — no cache — and by running `nslookup yourdomain.com` in a terminal. When the IP matches the new host, DNS has updated for you. It may still be propagating elsewhere.

Leave both hosts running during propagation. The old host serves visitors still reaching it via cached DNS; the new host serves everyone else.

Step 4: Set up 301 redirects if URLs changed

If your URL structure is identical, skip this. If it changed — domain name, http to https, www to non-www — set up 301 redirects immediately.

For Apache servers, add redirects to .htaccess. For Nginx, edit the server block configuration. The redirect must run on the new host, not the old one, because it only affects visitors reaching the new server.

Test every redirect manually. A broken redirect is a lost ranking.

Step 5: Verify Google can reach the site

Log into Google Search Console within an hour of the DNS change. Check the coverage report for crawl errors. Submit the sitemap again, even if it has not changed.

Use the URL inspection tool on your homepage and three important internal pages. If Google can fetch them, the move succeeded from its perspective.

Step 6: Monitor for forty-eight hours

Check Search Console daily for a week. Crawl errors after a migration are normal — Google retries failed URLs — but a sudden spike in 404s or 5xx errors means something broke.

Watch organic traffic in Analytics. A drop of five to ten percent in the first week is ordinary as caches clear. A drop of thirty percent is not.

If rankings collapse, check that the new host has not blocked search engines in robots.txt or via a noindex tag. Both have happened.

What can go wrong

Mixed content warnings occur if the new host runs HTTPS but internal links still point to HTTP resources. Fix them in the database with a search-and-replace.

Email stops working if MX records were hosted with the old provider and you forgot to migrate them. Copy MX records from the old DNS settings before switching.

The site loads but assets are missing. Check file permissions on the new host. Uploaded files often default to unreadable.

When to stay on the old host longer

If your current host is InterServer at 7.00 USD a month after the first month, the urgency depends on what you are moving to and why. A move to Hostinger for cost reasons, or to SherlockHost at 2.49 GBP monthly, can wait until you have tested the staging site thoroughly. A move because the current host is unreachable or the site is offline cannot.

The providers in this article