{"id":2427,"date":"2008-07-29T15:34:11","date_gmt":"2008-07-29T20:34:11","guid":{"rendered":"http:\/\/magic1host.com\/blog\/2008\/07\/29\/how-to-move-your-website\/"},"modified":"2008-07-29T15:34:11","modified_gmt":"2008-07-29T20:34:11","slug":"how-to-move-your-website","status":"publish","type":"post","link":"https:\/\/magic1host.com\/blog\/?p=2427","title":{"rendered":"How to Move Your Website"},"content":{"rendered":"
by Matt Hedges<\/div>\n

It is not something new that there are many people around us who raise the issue of switching to another web host or IP address being devoid of any sort of hiccups in Google. In this article, the experience of moving mattcutts.com from one IP to another IP just with the aid of altering the host is elucidated. It’s easier to accomplish having a static website than a dynamic website. The idea doesn’t vary but it is better if you can spend a day while your website can swing between 2 IP addresses. Some steps are there.<\/p>\n

Step 1: You need to sign up with a good web host provider<\/p>\n

You can do some research work or follow some references to find a good web host for yourself. I preferred by present web host (csoft.net), which I selected after research, and I also found that the readership of the site was growing beyond my expectation. A non-SEO friend of mine used pair.com. Let me refer to the example using IP addresses. If we move from csoft.com to pair.com, the IP would change from 63.x.x.x to 65.x.x.x. DNS is a system used for mapping websites to the IP address which a machine uses, like, say, 61.115.6.132.<\/p>\n

Step 2: Create a backup of your website on the new web host<\/p>\n

Having a static website is good as that would mean that just copying the whole file to the new web host – that is all. Having a blog<\/a> makes it harder as it usually involves MySQL for storage of posts. Some e-commerce websites are more difficult for this reason as the database is always synced. In this case, you may have to set up a replica of the database between the old and new locations during the switch.<\/p>\n

Let us cite an example of a WordPress blog using MySQL database which can deal with being down for two hours without too much trouble. Assume that you have used the FTP or tar for copying the static files from one web host to another. You will then need to make a fresh MySQL database on the new host. Usually you can give the same username and database name. if that is not allowed, you can tweak the WordPress wp-config.php on the new location to update the username, database name, and other relevant matters.<\/p>\n

You now have a new SQL database so that you can get away with the old one, copy it to the new one, and then load the database there.<\/p>\n

One has to bear in mind that it’s not only about a username and a password for both the web hosts but it’s about having dissimilar usernames and passwords for the database at every single location. I exhibited the host option while database reinstatement because you can be endowed with MySQL database stored on a distinctive location. In fact, WordPress can’t get into the database if notwithstanding the new host having a unique option for the database, you don’t edit wp-config.php file.<\/p>\n

You have similar copies of your website at two different locations. If your blog is just updated with a few comments daily, it is not a big deal if a comment is posted or if someone changes your database during a time when the transition is taking place. However, if your site is huge and based on e-commerce, you will need to work hard to keep both databases synchronized.<\/p>\n

Step 3: Changing the DNS to point to the new web host<\/p>\n

One needs to have an acquaintance with the term DNS because it’s of paramount significance. Your IP address is indispensable for any agent striving to get to your site-be it Googlebot or anybody else. Rechecking the IP address after 500 fetches in order to determine the authenticity or making sure if some hours have gone are common factors. TTL (Time to Live), calculated in seconds, does have an impact if you have DNS-enabled browsers. It states that your fetched IP address is going to be safe for ‘x’ seconds and for this much time, the address can be stored. The browser is expected to proceed very slowly simply because the IP address is meant for everything on each webpage of your site.<\/p>\n

Sites like Google, Yahoo!, MSN, etc. possess a bit short DNS TTL setting (300-900 seconds) because you intend to have one of them in order to make the data center mechanics perfect for endowing the machines with good data provided you have several data centers. TTL is immensely important as a short TTL lets you drag the IP address of a data center out of the rotary motion very quickly.<\/p>\n

This also explains the days of “Google Dance” that went by. It would last for a week or so, and based on the data center which the user hit, they would see the old as well as the new results. The main reason was that every data center was brought down and brought back, after loading it with new data. It required many days to switch the data to all the centers. During the period, webmasters checked out www2.google.com or www3.google.com since they led them to the latest data centers. Nowadays, the production system is properly equipped for switching these things around in lesser time.<\/p>\n

Step 4: The need to wait while the DNS change is propagated through the Internet<\/p>\n

Being mainly a TTL function, it banks upon the fact if you are really getting to the name servers present in the DNS at this time. Remember that DNS is hierarchical and the process of DNS caches getting into flushes is time-consuming as the TTL is exceeded. This switch gets faster with a smart registrar and a recognized set of the new name servers and it slabs place at the root of DNS. In order to be sure if the new name server is there on the root server, one can employ ‘dig+trace domain’ in UNIX and Linux.<\/p>\n

Step 5: You are almost done with your task when you are sure that Googlebot is fetching from the new web host and the IP address. In such a case, the old website can be shut down.<\/p>\n

With the aid of your domain, your IP address can be verified. Make yourself familiar with the proceedings and remember that the new visitors should be endowed with the new IP address, whereas, it is possible for the previous visitors to employ the old IP address from their DNS store. Permitting a couple of days is recommended because it is possible for some people to possess long TTL set, although, these are mostly meant for a day or even less. So, get rid of hosting<\/a> on the old location after a day. In order to have an infallible verification on this, test your logs and it is perfect if your log doesn’t show any previous visitors.<\/p>\n

\n
About the Author:<\/div>\n
This article is published with permission from WebHostingMadness.com, a publisher of hosting company ratings<\/a>, articles and helpful guides on web hosting.<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

It is not something new that there are many people around us who raise the issue of switching to another web host or IP address being devoid of any sort of hiccups in Google. In this article, the experience of moving mattcutts.com from one IP to another IP just with the aid of altering the host is elucidated. It’s easier to accomplish having a static website than a dynamic website. The idea doesn’t vary but it is better if you can spend a day while your website can swing between 2 IP addresses. Some steps are there.<\/p>\n","protected":false},"author":791,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[51],"tags":[122],"class_list":["post-2427","post","type-post","status-publish","format-standard","hentry","category-ecommerce","tag-ecommerce"],"_links":{"self":[{"href":"https:\/\/magic1host.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2427","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/magic1host.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/magic1host.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/magic1host.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/791"}],"replies":[{"embeddable":true,"href":"https:\/\/magic1host.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2427"}],"version-history":[{"count":0,"href":"https:\/\/magic1host.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2427\/revisions"}],"wp:attachment":[{"href":"https:\/\/magic1host.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2427"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/magic1host.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2427"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/magic1host.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2427"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}