How to change hosting for your Google site

Follow this leadership to minimize the impact of hosting changes on the performance of your site in Google Search. Changing hosting includes the transition to the new hosting supplier or the use of a content delivery network (CDN). This guide is intended only for migrations that do not change the visible URL of your site.

Do URLs change? If you change the visible URL addresses, start with the "transfer of sites with a URL change".

Review of hosting changes for your site in Google

• Prepare a new hosting. Download the content to new servers or configure your CDN and servers, and then test them.
• Start moving the site. Change your domain DNS settings so that it indicates a new hosting. This step actually launches the process of transferring traffic to a new infrastructure.
• Monitor traffic. Follow the traffic served by the old and new hosting.
• Close the old infrastructure. Disconnect the old hosting when make sure that all users, including Googlebot, receive content from the new hosting, and no one uses the old infrastructure.

Preparing a new hosting for your site in Google

This section describes the steps that must be performed before the real change in the hosting infrastructure of your site begins.

Copying and testing a new site

The first step up the copy of your site on the new hosting supplier. What is a "copy of the site" depends on your previous content management platform. It can be simple files that need to be transferred to a new hosting, or an export of a database that needs to be imported to a new place. After that, be sure to test so that the site works as expected. Here are a few recommendations:

• Create a test environment with limited access to test all functions before the site becomes available to the public.
• Open a new site in the browser and check all the elements of the site: pages, images, shapes and files for download (for example, PDF).
• Let the public test a site with a temporary name of the host for the new infrastructure (for example, Beta.example.com) to check the availability of the site for browsers and Googlebot. To prevent random indexing of a test site, add the Noindex tag to or HTTP settings of your pages.

Check if Googlebot can access the new hosting infrastructure of your site

If you still do not have an account in Search Console, create a new one to track Googlebot access and traffic. If you have created a temporary host for your new site, also confirm this resource in Search Console. Check that Googlebot can access the new infrastructure using the URL testing tool in Search Console.

Attention: Check the settings of your firewall or protection against DOS attacks so that they do not block Googlebot access to DNS or servers of the new hosting supplier.

Reducing TTL values for your DNS records

To accelerate the transfer process, reduce TTL (Time to Live) for your DNS records. This will allow new settings to spread faster among ISP. DNS records are usually celled by Internet suppliers, depending on the set life time (TTL). It is recommended to reduce TTL to the minimum value (for example, several hours) a week before the transfer to speed up the DNS update process.

Check confirmation in Search Console

Make sure that the confirmation of your site in Search Console will remain a worker after the hosting transfer. If you used the confirmation method using the file, do not forget to enable the confirmation file on the new site. Similarly, if you used meta-tags or Google Analytics to confirm, make sure that they are present in the new CMS.

Launching your site move to Google

The transfer process is as follows:

• Remove temporary blocking for a detour. Some site owners use the Robots.txt file or Noindex metata to block the Googlebot bypass during the construction of the new site. Make sure that all such locks are removed from your site when you are ready to transfer.
• Update DNS settings. The transfer begins with the update of the DNS records so that they indicate a new hosting supplier. Check with your DNS supplier how to do it.

Monitoring traffic on your website in Google

To control, so that the transition is successful, follow the following parameters:

• Follow the server logs on old and new servers. When the DNS settings are updated, you will see a decrease in traffic on old servers and the growth of traffic on new ones.
• Use public DNS testing tools. Check that various ISP around the world correctly update DNS settings.
• Monitor the bypass. Follow the schedules of indexing in Search Console.

Deviations in the speed of Googlebot bypass

When you change hosting, it is quite normal to observe a temporary decrease in Googlebot bypass immediately after the transfer, followed by a gradual increase in speed in the next few days, possibly to the values exceeding the previous ones.

This fluctuation is due to the fact that we determine the speed of the bypass for the site based on many signals, and these signals change when hosting changes. If Googlebot does not face serious problems when accessing the new hosting, he will try to go around your site as quickly as possible and necessary.

Closing the old hosting of your site in Google

Check the log of the server of the old hosting supplier and, as soon as the traffic at the old hosting reaches zero, you can complete the process by turning off the old infrastructure. This will complete the transition to a new hosting.

If you have questions, you can contact the SEO of "Seo.computer" for any issue on email info@seo.computer Or through WhatsApp +79202044461.

ID 188