No. Moving your website to a new host does not move your Google rankings on its own, as long as every web address stays exactly the same. What costs people is the switch itself: a server that starts answering with errors, a test block left switched on, or an old host turned off too early.

Google publishes a guide for this exact move

Google Search Central has a page called “Changing your hosting”. That page was last updated December 10, 2025.

It opens: “Follow this guide to minimize the impact of changing your site’s hosting infrastructure on the site’s performance in Google Search.” It defines the job the way you would: “A change in hosting infrastructure means switching hosting providers or moving to a content distribution network (CDN).”

Now read what that page does not say. It never says your rankings will drop. It is a four step checklist, and the reason it stays that short is that your addresses are not changing.

The one wobble it does name sits in the crawling, not the ranking: “It’s normal to see a temporary drop in Googlebot’s crawl rate immediately after the launch, followed by a steady increase over the next few days.”

You do not have to tell Google you moved

There is no form to fill in. Google’s Search Console Help page for the Change of Address tool lists cases where you should not use it. Yours is on the list: “Moving a site without any user-visible URL changes (that is, when your site URL remains the same but you are changing hosting providers or CDNs).” That page carries no update date.

The same goes for redirects. A redirect is a note left at an old address. If no address changed, there is no old address to leave a note at. Changing your domain name is a different job with a different answer, and the Change of Address tool is built for that one.

What actually puts a ranking at risk

Four things, and none of them is the host change itself.

  • The server answering with errors. Google’s page on how HTTP status codes affect Google’s crawlers, last updated February 4, 2026, says “5xx and 429 server errors prompt Google’s crawlers to temporarily slow down with crawling.” The same page: “Any content Google receives from URLs that return a 5xx status code is ignored.” A half finished server that throws errors for two days is a real problem. A clean switch is not.
  • The test block left on. Google tells you to put a copy on a temporary address like beta.example.com and to add a noindex rule, which is a line telling Google not to list the page. Step two of the guide is to take those rules back off. It is in there for a reason. People forget. A noindex rule left on the live site is the fastest way to vanish from Google, and nothing about it looks broken to a visitor.
  • Googlebot getting blocked. New host, new firewall, new bot protection. Google’s line: “Check that Googlebot can access your new infrastructure using the URL Inspection Tool in Search Console.”
  • Search Console verification breaking. Google again: “Make sure your Search Console verification will continue to work after the hosting move.” Lose it and you lose your view of the move on the day you need it most.

There is a fifth, and it is the common one. The old host gets switched off while part of the internet still points at it, which is also how a site goes dark during a move. Google puts the rule in step four of the same guide: “Check the server logs on the old provider and, once the traffic to the old provider reaches zero, you can shut down your old hosting infrastructure.” Zero, not “it loaded fine on my phone.” Turn the old server off early and it starts answering with errors, which puts you back on the first item in this list.

Will a faster host lift you instead?

This is where people get sold something. Read it slowly.

Speed is in the ranking systems. Google’s page “Understanding page experience in Google Search results”, last updated December 10, 2025, says it plainly: “Core Web Vitals are used by our ranking systems.” The same page draws the limit. Good numbers in Search Console or a third-party tool are no promise of a top ranking, and Google adds that there is “more to great page experience than Core Web Vitals scores alone.”

The number to go check is Largest Contentful Paint, the moment the biggest thing on the screen finishes loading. Google’s own guidance on web.dev, updated September 4, 2025, sets the target: “sites should strive to have Largest Contentful Paint of 2.5 seconds or less,” measured at “the 75th percentile of page loads, segmented across mobile and desktop devices.” Put your address into PageSpeed Insights and read it off. Free, one minute.

Here is the honest part. If your page already lands under 2.5 seconds, a new host has nothing left to give you there, and paying for one is money you could spend on anything else. If it lands over, the weight travels with you, and the four parts that decide load time are worth reading in order. The HTTP Archive Web Almanac measured the median mobile page for its 2025 Page Weight chapter, published January 15, 2026, at 911 KB of images and 632 KB of JavaScript. A faster server sends those files faster. They are the same size when they arrive.

The crawl worry you can drop

Somebody will tell you a host move burns your crawl budget. Google’s “Optimize your crawl budget” page, last updated July 22, 2026, is written for a size of site you almost certainly do not run. It names “Large sites (1 million+ unique pages) with content that changes moderately often (once a week)” and “Medium or larger sites (10,000+ unique pages) with very rapidly changing content (daily).” Then it says: “If your site doesn’t have a large number of pages that change rapidly, or if your pages seem to be crawled the same day that they are published, you don’t need to read this guide.”

A plumbing site with 30 pages is not in that band.

One limit runs under everything above. Every source on this page is Google writing about Googlebot. None of them covers what ChatGPT or any other AI assistant does after your host changes, so nothing here should be read as an answer to that. What you can do is write down where you stand before you move. A free scan asks the assistants what a customer would ask and records which businesses get named.

What to do next

  1. Ask whether the move is worth making. If the site is up, quick, and fairly priced, a host change on its own is not a ranking move. Move when the site is slow, when the host stops answering the phone, or when the site is getting rebuilt anyway.
  2. Copy the site to the new host on a temporary address. Open every page there. Send yourself a test through every form.
  3. Take off the noindex rules and any crawl block before you point the domain at the new host. Check the live pages afterward with the URL Inspection Tool.
  4. Confirm your Search Console verification still works after the switch.
  5. Switch, then change nothing else that week. No new wording, no new addresses, no new photos. One change at a time is the only way to read what happened after.
  6. Keep paying the old host for a week or two. That week turns a bad cutover into a slow one nobody notices.
  7. Watch Search Console for two weeks. A crawl dip in the first few days is what Google says to expect. Pages dropping out of the index is not, and that needs looking at the same day. If clicks fall instead, read the two reports that show what actually moved before anyone blames the host.

There are no client case studies here. The only proof on offer is this site itself, which scored 100 on Google’s PageSpeed test on desktop and mobile, when it launched in August 2026. Scores move a few points from run to run, and you can run that test yourself. If a rebuild is already on the table, do the rebuild and the host move together and touch the domain once. What that build involves is written out in full.

Written by Galloping