{"id":25572,"date":"2026-09-05T02:45:49","date_gmt":"2026-09-04T23:45:49","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/changing-your-hosting\/"},"modified":"2026-09-05T02:45:49","modified_gmt":"2026-09-04T23:45:49","slug":"changing-your-hosting","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/changing-your-hosting\/","title":{"rendered":"Changing your hosting"},"content":{"rendered":"<p>\n  Follow this guide to minimize the impact of changing your site&#8217;s hosting infrastructure on<br \/>\n  the site&#8217;s performance in Google Search. A change in hosting infrastructure means switching<br \/>\n  hosting providers or moving to a content distribution network (CDN). This guide is only for<br \/>\n  migrations that don&#8217;t affect the user-visible URL.\n<\/p>\n<aside class=\"note\">\n  <b>Changing the URLs?<\/b> If you&#8217;re making visible URL changes, start with<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/site-move-url-change\/\">Site moves with URL changes<\/a>.<br \/>\n<\/aside>\n<h2 id=\"overview\" tabindex=\"-1\">Overview<\/h2>\n<ol>\n<li>\n    <b><a href=\"#hosting-infrastructure\">Prepare the new hosting infrastructure<\/a><\/b>.<br \/>\n    Upload your content to the new servers or configure your CDN and your origin servers, and<br \/>\n    test it.\n  <\/li>\n<li>\n    <b><a href=\"#start-site-move\">Start the site move<\/a><\/b>. Change the DNS settings of your<br \/>\n    domain name to point to the new hosting infrastructure. This step is the actual site move<br \/>\n    step that starts the process of sending your traffic to the new infrastructure.\n  <\/li>\n<li>\n    <b><a href=\"#monitor\">Monitor traffic<\/a><\/b>. Keep tabs on the traffic served by the old<br \/>\n    and new hosting.\n  <\/li>\n<li>\n    <b><a href=\"#shut-down-old-hosting\">Shut down<\/a><\/b>. Shut down the old hosting<br \/>\n    infrastructure when you&#8217;re confident that all users, including Googlebot, are receiving<br \/>\n    content correctly from the new infrastructure and no one is using the old infrastructure.\n  <\/li>\n<\/ol>\n<h2 id=\"hosting-infrastructure\" tabindex=\"-1\">Prepare the new hosting infrastructure<\/h2>\n<p>This section covers steps to take before you start the actual infrastructure move.<\/p>\n<h3 id=\"copy-test-new-site\" tabindex=\"-1\">Copy and test your new site<\/h3>\n<p>\n  First, upload a copy of your site to your new hosting provider. What a &#8220;copy of your website&#8221;<br \/>\n  means depends entirely on your old content management platform; it may be actual HTML files<br \/>\n  that you replicate on your new hosting platform, or a database export that you have to<br \/>\n  import in the new location. Once you do that, verify that it works as expected by thoroughly<br \/>\n  testing all aspects of how your users interact with your site. Here are a few suggestions:\n<\/p>\n<ul>\n<li>\n    <b>Create a testing environment<\/b>, perhaps with IP-restricted access, through which you<br \/>\n    test all of the features before the website goes live.\n  <\/li>\n<li>\n    <b>Open your new site in a web browser<\/b> and review all elements of your site: pages,<br \/>\n    images, forms, and downloads (such as PDF files).\n  <\/li>\n<li>\n    <b>Allow for public testing<\/b> with a temporary hostname for your new infrastructure (like<br \/>\n    <code>beta.example.com<\/code>) so you can test accessibility by browsers. A temporary<br \/>\n    hostname can help you test whether Googlebot can reach your site or not. To prevent<br \/>\n    accidentally letting the test site get indexed, add the<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/block-search-indexing-with-noindex\/\"><code>noindex<\/code> <code>robots<\/code> rule<\/a><br \/>\n    to the HTML or the HTTP headers of your pages.\n  <\/li>\n<\/ul>\n<h3 id=\"check-googlebot-access\" tabindex=\"-1\">\n  Check that Googlebot is able to access the new hosting infrastructure<br \/>\n<\/h3>\n<p>\n  If you don&#8217;t already have a Search Console account,<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/answer\/34592\" class=\"external-link\">create a new account<\/a><br \/>\n  for your site to help you monitor Google access and traffic. If you created a temporary<br \/>\n  hostname for your new site, verify that property as well. Check that Googlebot can access your<br \/>\n  new infrastructure using the<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289\" class=\"external-link\">URL Inspection Tool<\/a><br \/>\n  in Search Console.\n<\/p>\n<aside class=\"caution\">\n  <b>Caution<\/b>: Check your firewall configuration or denial of service (DoS) protection. Make<br \/>\n  sure it does not block Googlebot&#8217;s ability to reach the DNS or the hosting provider&#8217;s servers.<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/verify-requests-from-google-crawlers-and-fetchers\/#use-automatic-solutions\">Learn how to verify Googlebot<\/a>.<br \/>\n<\/aside>\n<h3 id=\"check-ttl\" tabindex=\"-1\">Lower the TTL value for your DNS records<\/h3>\n<p>\n  You can help make your site move go faster if you lower your site DNS records&#8217; TTL value,<br \/>\n  which will allow the new settings to propagate to ISPs faster. DNS settings are usually cached<br \/>\n  by ISPs based on the specified<br \/>\n  <a href=\"https:\/\/wikipedia.org\/wiki\/Time_to_live#DNS_records\" class=\"external-link\">Time to Live (TTL) setting<\/a>.<br \/>\n  Consider lowering the TTL to a conservative low value (for example, a few hours) at least a<br \/>\n  week in advance of the move to refresh DNS caches faster.\n<\/p>\n<h3 id=\"review-search-console\" tabindex=\"-1\">Review Search Console verification<\/h3>\n<p>Make sure your Search Console verification will continue to work after the hosting move.<\/p>\n<p>\n  If you&#8217;re using the<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080#html_verification\" class=\"external-link\">HTML file method<\/a><br \/>\n  to verify ownership of your site in Search Console, make sure you don&#8217;t forget to include your<br \/>\n  current verification file in your new copy of the site.\n<\/p>\n<p>\n  Likewise, if you include in your content management system&#8217;s (CMS) templates a<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080#meta_tag_verification\" class=\"external-link\"><code>meta<\/code> tag<\/a><br \/>\n  veya<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080#google_analytics_verification\" class=\"external-link\">Google Analytics<\/a><br \/>\n  to verify ownership, ensure the new CMS copy includes these as well.\n<\/p>\n<h2 id=\"start-site-move\" tabindex=\"-1\">Start the move<\/h2>\n<p>The move process is as follows.<\/p>\n<ol>\n<li>\n    <b>Remove any temporary blocks to crawling<\/b>. While building the new copy of a site, some<br \/>\n    site owners use a robots.txt file to disallow all crawling by Googlebot and other crawlers,<br \/>\n    or use <code>noindex<\/code> <code>meta<\/code> tags or HTTP headers to block indexing of<br \/>\n    content. Be sure to remove any such blocks from the new copy of the site when you&#8217;re ready<br \/>\n    to start the move.\n  <\/li>\n<li>\n    <b>Update the DNS settings<\/b>. You start the move by updating the DNS records to point to<br \/>\n    the new hosting provider. Check with your DNS provider for how to do that.\n  <\/li>\n<\/ol>\n<h2 id=\"monitor\" tabindex=\"-1\">Monitor traffic<\/h2>\n<p>To monitor that your infrastructure change is going smoothly:<\/p>\n<ul>\n<li>\n    <b>Keep an eye on the server logs on both new and old servers.<\/b><br \/>\n    As DNS setting propagates and the site traffic moves, you&#8217;ll notice a drop in traffic<br \/>\n    logged on the old servers and a corresponding increase in traffic on the new servers.\n  <\/li>\n<li>\n    <b>Use different public DNS checking tools.<\/b><br \/>\n    Check that different ISPs around the world are updating to your new DNS settings correctly.\n  <\/li>\n<li>\n    <b>Monitor crawling.<\/b><br \/>\n    Monitor the<br \/>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203\" class=\"external-link\">Index coverage<\/a><br \/>\n    graphs in Search Console.\n  <\/li>\n<\/ul>\n<h3 id=\"googlebot-crawl-rate\" tabindex=\"-1\">A note about Googlebot&#8217;s crawl rate<\/h3>\n<p>\n  When you change hosting infrastructure, it&#8217;s normal to see a temporary drop in Googlebot&#8217;s<br \/>\n  crawl rate immediately after the launch, followed by a steady increase over the next few<br \/>\n  days, potentially to rates that may be higher than before the move.\n<\/p>\n<p>\n  This fluctuation occurs because we determine crawl rate for a site based on many signals, and<br \/>\n  these signals change when your hosting changes. As long as Googlebot doesn&#8217;t encounter any<br \/>\n  serious problems or slowdowns when accessing your new serving infrastructure, it will try to<br \/>\n  crawl your site as fast as necessary and possible.\n<\/p>\n<h2 id=\"shut-down-old-hosting\" tabindex=\"-1\">Shut down old hosting<\/h2>\n<p>\n  Check the server logs on the old provider and, once the traffic to the old provider reaches<br \/>\n  zero, you can shut down your old hosting infrastructure. This completes the hosting change.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Discover how to minimize the impact on your Google Search performance when transferring your site&#8217;s hosting infrastructure without changing your URLs.<\/p>\n","protected":false},"menu_order":51,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[692],"ar_kb_etiket":[],"class_list":["post-25572","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-site-moves-site-moves-and-changes"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25572","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25572\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27587"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=25572"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=25572"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=25572"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}