Are you a Google Analytics enthusiast?
More SEO Content
Moving To A Different Server/hosting Company
Posted 18 October 2008 - 02:31 AM
I rank on the first page of google for my keywords but I have to move my entire site to a different server and hosting company - can anyone advise me if there is something I ought to be doing to ensure that the transition is seamless?
The reason for the move is because my programmer has rebuilt the site using a much better CMS system. Do you think that slightly different URL structure will confused SE's? By this I mean, my site is now www.mysite.com/my/content.html - it will become www.mysite.com/my/different/content.aspx - therefore slightly different - is that a potential problem?
All replies and advice are always gratefully received!!
Posted 18 October 2008 - 06:13 AM
Posted 18 October 2008 - 08:26 AM
1. Moving the site to a new server/hosting company. This one is pretty easy to deal with these days, thankfully. Matt Cutts has an older post on his outlining the best case scenario. The trick is to get the DNS update propagated as quickly as possible. Which isn't all that much of a big deal these days since changing the nameservers for the domain will typically cause global dns to propagate within 24-72 hours.
You can make it immediate and seamless by editing the local DNS settings on the old server. When you do this simply change the IP numbers on all of the records there so that they point to the IP address of the new server.
2. The other issues is the change in the url structure of the site. This is a bit more involved, but not really all that hard if you plan it out prior to flipping the switch. What you'll want to do is make a list of all of the current (old) urls. You can do this in a text file or spreadsheet, whichever works best for you.
Next to each of these old urls note the corresponding new url that'll be live on the newly designed site. Then on the new server you'll want to set up 301 redirects from each of these old urls to the corresponding new urls. The only trick being to make sure it's a 301 Moved Permanently redirect, as opposed to something like a 302 redirect.
How to do this depends a good bit upon what type of server the new site will be on (Unix/Linux or IIS) and what capabilities the new server has. If you're on a *nix machine with Apache's mod_rewrite module installed many times you can use regular expressions in an .htaccess file to handle the redirects for multiple pages, if there's some consistency between the old and new urls. If not, you'd need to individual redirects for each individual page.
Lots more info on this subject in the pinned thread above, as well as the other threads in the Redirects forum.
Posted 09 November 2008 - 09:42 PM
I am in a very similar situation and have read Matt Cutts post, however I am still a bit confused on handling the move.
(Newbie syndrome I suppose)
I am with host1.com with my-site.com and plan to move to host2.com.
Some of the steps from Matts post:
Step 1. Find a good web host and sign up for an account.
Done. I have a primary account based on a different domain name called mysite.com and a bunch of other parked domains.
(the 301 redirects from my-site.com to mysite.com will be the subject of more FAQ and HR forum post reviews on my part once I actually accomplish the straight
up my-site.com move from host1 to host2)
Step 2: Make a back-up of your site at the new webhost.
I can do that without any issue. But where do I put it? my-site.com doesn't exist on host2 yet right?
Step 3: Change DNS to point to your new web host.
This is where I get confused. Specifically with repsect to transfer locks. I've moved some parked domains from host1.com to host2.com without any trouble
by unlocking on host1 and requesting transfer of domain name to host2.com on host2.com's control panel. But I wasn't worried about getting it right with respect
to not losing ranking etc. as I didn't have content associated with them.
This time it's different as I don't want to mess up my ranking. I just want to change the hosting but am a bit confused as to the actual transfer of the domain name
Apologies if this is out there somewhere already, but I've been perusing posts for a week or so here and haven't found the same scenario.
Posted 09 November 2008 - 11:18 PM
So once you have all of your site's files uploaded to the new server/host you switch the nameserver info (there should be at least two, a primary and secondary) at your domain registrar, and the propagation process starts. This can typically take anywhere from 24-72 hours to complete. During which time you'll want to have the site available on both servers, just in case.
Once you see the traffic cease at the old server, usually within a few days, you can disable it.
If the above doesn't make sense still, shoot me off a PM with the domain details and whatever the new host has told you to use as nameserver pointers. All of the old info is public, so I should be able to point you in the right direction.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users