Skip to content
7 min read

Website migration to new hosting without losing Google rankings

Website migration does not hurt rankings by itself. Google rankings drop when a site goes offline during the move, loses its redirects, or exposes a staging copy to indexing. Below is a sequence that reduces those risks: what to collect in advance, how to test the new server, when to switch DNS and what to monitor in the first weeks. It is written for site owners in Uzbekistan and for anyone running a project together with a contractor.

What puts a site at risk during website migration

A search engine sees your site as a set of addresses. As long as every address returns 200, the content is unchanged and the server is stable, nothing has happened from Google’s point of view. Problems start in three places: the site returns 5xx or 404 errors during the switch, old URLs and redirects configured on the previous server stop working, or a copy on a technical domain gets indexed.

The second source of risk is speed and stability. If the new plan is weaker than the old one, pages will open more slowly. Before moving, compare resources: CPU, memory, disk type, PHP or Node.js version, process limits and database size. For audiences in Tashkent and the regions, geography matters too: a server closer to visitors usually responds faster, but decide by measuring response time, not by guessing.

If the domain, URL structure or CMS changes together with the hosting, this is no longer a simple move but a full migration that needs a redirect map. Avoid combining the two. Move the site to the new server unchanged first, and do everything else two or three weeks later. That way you can tell what actually affected traffic.

Preparation: what to collect before the move

Take a full copy: site files, a database dump, web server configuration (nginx, Apache, .htaccess), cron jobs, environment variables, certificates and the list of enabled PHP extensions. Keep the copy away from the old hosting, so it survives if you lose access to it.

Export a list of every URL from sitemap.xml, from a crawler (for example Screaming Frog) and from the Pages report in Search Console. Mark separately the addresses that bring leads and organic traffic. Record response codes and canonical URLs, because you will compare them after the move.

List the external services tied to the server: payment systems such as Payme and Click with their callback addresses, SMS gateways and APIs with IP allowlists, mailboxes, Telegram bots with webhooks, CRM integrations and analytics counters. Some of them will need to be reconfigured for the new IP or address. Also confirm who holds which access: domain registrar, DNS, hosting, Search Console.

At least a day ahead, lower the DNS TTL to 300 seconds. If you do it on the day of the move, the old value stays in provider caches until the previous TTL expires, and some visitors keep landing on the old server.

Moving the site and testing a staging copy

Deploy the site on the new server: upload files, import the database, fix paths and connection settings, and install the same language version and extensions. Versions matter: a site that ran fine on an older PHP version may throw errors on a newer one.

Open the site without changing DNS: through the host’s technical domain or by editing the hosts file on your own computer (a line like new-server-IP your-domain). This shows you the new server under the real name. Remove the line from hosts once testing is done.

Testing checklist: home page, categories, product pages, search, lead forms and email delivery, cart and payment in test mode, user account, image uploads, the 404 page, redirects, https and background jobs. Crawl the new copy and compare response codes with the list taken from the old site.

Block the staging copy from indexing at server level, using HTTP authentication or an X-Robots-Tag: noindex header. robots.txt alone is not enough, since a blocked address can still appear in search results through external links. Conversely, before launch make sure noindex did not travel to the live site with the config or a CMS setting. It is a common reason for traffic collapsing after a move.

The DNS switch and the SSL certificate

Pick the window with the least traffic: a night or a weekend, based on your own analytics. During the work, pause orders and registrations or warn managers, so leads do not get split between two servers. For shops and sites with user accounts, take a fresh database dump right before the switch and import it again on the new server.

Change only the records you need: usually the A record of the main domain and www (A or CNAME). Leave MX, SPF and DKIM alone if email stays with the current provider, otherwise messages may land in spam or disappear. If possible, keep DNS with the current provider and change only the IP, because changing nameservers propagates more slowly.

Right after the switch, issue or attach an SSL certificate on the new server (the free Let’s Encrypt is often enough). Check that it covers both the domain and www, and that http goes to https with a single 301 redirect and no chains. Keep the old server running for at least a few days, since some visitors will still reach it while DNS propagates.

After the move: what to monitor for two to four weeks

On the first day, crawl the URL list: every important page should return 200. Compare canonical URLs, sitemap.xml, robots.txt, robots meta tags and response headers. Resubmit the sitemap in Search Console and open the Crawl stats report, which shows server response time and errors.

For the first two weeks, watch crawl errors, the number of indexed pages, organic impressions and clicks, and server response speed. A sharp rise in 5xx errors or a drop in impressions means something did not make the trip, and it should be fixed right away. Small fluctuations in the first days are normal while Google recrawls the site.

Typical mistakes: not lowering TTL in advance; leaving noindex in place after testing; losing the .htaccess file with redirects; not moving cron jobs, so emails stop going out and price lists stop updating; not updating payment callbacks and allowlisted IPs; switching off the old hosting on the day of the move; forgetting to renew the domain or the certificate.

FAQ

How long does it take to move a website to new hosting? A small site on a ready-made CMS usually needs one or two days including testing. A shop with integrations takes from several days to a week or more. This is a guide only: the exact time depends on data volume and the number of integrations.

Can a site be moved without downtime? Yes, if you prepare the new server in advance, lower the TTL and switch only DNS. For a while some visitors will reach the old server and some the new one, so both must behave the same.

Will rankings drop after the move? If URLs, content and response codes are preserved and the site never goes offline, a noticeable drop should not happen. Small fluctuations in the first days are possible, but no result can be guaranteed, which is why post-move monitoring matters.

What should I do with the old hosting? Do not cancel it for at least one or two weeks: it serves as a fallback and a source of data if something did not transfer. Save a final copy before shutting it down.

Timelines and what the cost of a move consists of

The cost has three parts: the hosting itself, specialist work and side expenses. As a market guide for hosting: roughly 30,000 to 150,000 UZS per month for a small site on shared hosting and 150,000 to 700,000 UZS per month for a VPS. A specialist’s migration work is typically estimated at roughly 500,000 to 3,000,000 UZS. These are only guides, and real prices depend on the provider and the complexity of the project.

The price is affected by the size of files and database, the number of integrations (payments, SMS, CRM), whether the server has to be configured from scratch, urgency, and the preparation of a redirect map if the URL structure changes. Side expenses include SSL, backups and uptime monitoring.

If preparation shows that the site is outdated, slow or has nobody to maintain it, the move is a good moment to consider a new version. The 4 Digital studio in Tashkent builds turnkey websites from 1,399,000 UZS, and you can contact us for an assessment of your current site or help with a migration.

Need a website or ads? Let’s discuss your project.

Turnkey Website Development + CRM · от 2 399000 сум

We reply within 15 minutes during business hours. No spam.