Stay organized with collections Save and categorize content based on your preferences.

Move a site without URL changes

This guide shows how to minimize the impact on your Google Search performance when migrating your site's hosting infrastructure. For example, when switching hosting providers or moving to a content distribution network (CDN). This guide is only for migrations that don't affect the user-visible URL.


  1. Review FAQs and basic information about site moves. Know what to expect, and how it might affect your users and rankings.
  2. Prepare the new hosting infrastructure. Upload your content to the new servers or configure your CDN and your origin servers, and test it.
  3. Start the site move. Change the DNS settings of your domain name to point to the new hosting infrastructure. This step is the actual site move step that starts the process of sending your traffic to the new infrastructure.
  4. Monitor traffic. Keep tabs on the traffic served by the old and new hosting.
  5. Shut down. Shut down the old hosting infrastructure when you're confident that all users are receiving content correctly from the new infrastructure and no one is using the old infrastructure.

Prepare the new hosting infrastructure

This section covers steps to take before you start the actual site move.

Copy and test your new site

First, upload a copy of your site to your new hosting provider. Once you do that, verify that it works as expected by thoroughly testing all aspects of how your users interact with your site. Here are a few suggestions:

  • Open your new site in a web browser and review all elements of your site: webpages, images, forms, and downloads (such as PDF files).
  • Create a testing environment, perhaps with IP-restricted access, through which you test all of the features before the website goes live.
  • Allow for public testing with a temporary hostname for your new infrastructure (like so you can test accessibility by browsers. A temporary hostname can help you test whether Googlebot can reach your site or not.
  • Test the new site with a small portion of your live traffic if possible.

Check that Googlebot is able to access the new hosting infrastructure

If you don't already have a Search Console account, create a new account for your site to help you monitor Google access and traffic. If you created a temporary hostname for your new site, create an account for that hostname as well. Check that Googlebot can access your new infrastructure using the URL Inspection Tool in Search Console.

Lower the TTL value for your DNS records

You can help make your site move go faster if you lower your site DNS records' TTL value, which will allow the new settings to propagate to ISPs faster. DNS settings are usually cached by ISPs based on the specified Time to Live (TTL) setting. Consider lowering the TTL to a conservative low value (for example, a few hours) at least a week in advance of the site move to refresh DNS caches faster.

Review Search Console verification

Make sure your Search Console verification will continue to work after the site move.

If you're using the HTML file method to verify ownership of your site in Search Console, make sure you don't forget to include your current verification file in your new copy of the site.

Likewise, if you include in your content management system's templates a meta tag or Google Analytics to verify ownership, ensure the new CMS copy includes these as well.

Start the site move

The move process is as follows.

  1. Remove any temporary blocks to crawling. While building the new copy of a site, some site owners use a robots.txt file to disallow all crawling by Googlebot and other crawlers, or use noindex meta tags or HTTP headers to block indexing of content. Be sure to remove any such blocks from the new copy of the site when you're ready to start the move.
  2. Update the DNS settings. You start the site move by updating the DNS records to point to the new hosting provider. Check with your DNS provider for how to do that. Because the DNS cache setting is cached, the records takes some time to fully propagate to all users on the internet.

Monitor traffic

Here are three things you can do to make sure your move is going smoothly:

  • Keep an eye on the server logs on both new and old servers.
    As DNS setting propagates and the site traffic moves, you'll notice a drop in traffic logged on the old servers and a corresponding increase in traffic on the new servers.
  • Use different public DNS checking tools.
    Check that different ISPs around the world are updating to your new DNS settings correctly.
  • Monitor crawling.
    Monitor the Index coverage graphs in Search Console.

A note about Googlebot's crawl rate

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 weeks, potentially to rates that may be higher than before the move.

This fluctuation occurs because we determine crawl rate for a site based on many signals, and these signals change when your hosting changes. As long as Googlebot doesn't encounter any serious problems or slowdowns when accessing your new serving infrastructure, it will try to crawl your site as fast as necessary and possible.

Shut down old hosting

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. This completes the site move.