Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developers.google.com/search/docs/crawling-indexing/site-move-no-url-changes below:

Changing Your Web Hosting and SEO | Google Search Central | Documentation

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

Follow this guide to minimize the impact of changing your site's hosting infrastructure on the site's performance in Google Search. A change in hosting infrastructure means 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. Prepare the new hosting infrastructure. Upload your content to the new servers or configure your CDN and your origin servers, and test it.
2. 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.
3. Monitor traffic. Keep tabs on the traffic served by the old and new hosting.
4. Shut down. Shut down the old hosting infrastructure when you're confident that all users, including Googlebot, are receiving content correctly from the new infrastructure and no one is using the old infrastructure.

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

First, upload a copy of your site to your new hosting provider. What a "copy of your website" means depends entirely on your old content management platform; it may be actual HTML files that you replicate on your new hosting platform, or a database export that you have to import in the new location. 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:

• Create a testing environment, perhaps with IP-restricted access, through which you test all of the features before the website goes live.
• Open your new site in a web browser and review all elements of your site: pages, images, forms, and downloads (such as PDF files).
• Allow for public testing with a temporary hostname for your new infrastructure (like beta.example.com) so you can test accessibility by browsers. A temporary hostname can help you test whether Googlebot can reach your site or not. To prevent accidentally letting the test site get indexed, add the noindex robots rule to the HTML or the HTTP headers of your pages.

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, verify that property as well. Check that Googlebot can access your new infrastructure using the URL Inspection Tool in Search Console.

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 move to refresh DNS caches faster.

Make sure your Search Console verification will continue to work after the hosting 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 (CMS) templates a meta tag or Google Analytics to verify ownership, ensure the new CMS copy includes these as well.

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 move by updating the DNS records to point to the new hosting provider. Check with your DNS provider for how to do that.

To monitor that your infrastructure change 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.

When you change hosting infrastructure, 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, 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.

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 hosting change.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-03-06 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-06 UTC."],[[["Changing hosting infrastructure involves switching providers or moving to a CDN, impacting site performance in Google Search."],["Before the move, prepare the new hosting by copying and testing your site, ensuring Googlebot access, and lowering DNS TTL values."],["Initiate the move by updating DNS settings to point to the new hosting, then monitor traffic on both old and new servers."],["After traffic to the old server ceases, shut down the old hosting to complete the infrastructure change."],["Expect temporary fluctuations in Googlebot's crawl rate after the move, eventually stabilizing and potentially increasing."]]],["To change hosting without altering URLs, first, prepare the new infrastructure by uploading and testing a copy of your site. Verify Googlebot's access via Search Console and temporarily lower DNS TTL values. Next, initiate the move by updating DNS settings to point to the new host. Monitor traffic on both old and new servers, using server logs and public DNS checking tools. Remove any crawl blocks. Lastly, shut down the old hosting once traffic completely shifts to the new infrastructure.\n"]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4