Welcome to WebmasterWorld Guest from 22.214.171.124
Forum Moderators: mack
I run a site on a Windows server (.asp) and am moving to a new server. Was thinking of leaving the 'old' server there for about a month or so.
I understand I need to put a 301 redirect so I will still be picked up by search engines? How?
I'm new. Basic HTML skills. Where do I put this message? Separate .asp file? .txt file? Within every page? BTW, I need specifics ... totally clueless :) Can you provide a sample of exactly how this 'line' should look like?
Thanks for any help at all.
1. Say your existing site is www.abc.com running off ip address 126.96.36.199. Just leave it running.
2. Establish your site at the new server. It will still be www.abc.com, but will be running off of ip address 188.8.131.52
3. Change your nameserver for abc.com to point www.abc.com to 184.108.40.206 instead of to 220.127.116.11.
4. Wait a while. The amount of time will depend on parameters set up in your dns nameserver, but, a week is almost always sufficient - usually 2-3 days will suffice if you are pressed). The new dns will take awhile to propogate from your authoritative nameserver to all the other nameservers across the country. In the mean time, your site will be served from both servers until the new ip address has fully propogated.
5. Shut down your site on the old server.
The 301 redirect would only be required if you want to move from one domain name (say, www.abc.com) to another domain name (say, www.def.com). The 301 redirect indicates that requests for a particular url will now be served from a new url. Since, you are not changing urls, but are only changing ip address, 301 redirect is not relavent.
I've heard that some search engines spider according to the IP address, no the URL - so when I terminate the 'old' server the spiders wouldn't know that I've moved, but rather simply think that the site doesn't exist anymore. Is this true?
1. You enter a on the browser address line, or you click on a url from another page.
2. Your browser uses dns to get the ip address for the domain extracted from the url you requested.
3. Your browser uses http to send the request through the web to url at that ip address.
Two requests are performed. First, DNS is requested to get the ip address for the url. Then, the page is requested from the internet with that ip address and url.
Usually, these requests are performed within a second of each other.
SEs do not, really, crawl by ip address. They use urls. It is only that Google, and some other spiders, for performance reasons, will do the dns lookup days before the page is actually requested. Essentially, google caches the dns translation information.
This technique may cause google and many other search engines to continue to request pages from an old ip address even after you have changed the authoratitive name server for the domain. This effect might cause some people to erroneously conclude that SE's "spider according to IP address" instead of according to the URL.
The worst case timing is like this.
1. You change the ip address in the name server for the domain.
2. The change propogates to the other name servers over a period of, typically, a couple of days.
3. If Google crawled at the worst possible time (just before your change was available to them through dns), they might still request at your old ip address after looking it up in their dns cache. I have seen the cache be as old as a week.
Which means that you should expect that some SEs might continue to request pages from the old ip address for 10 days after you change the ip address in you authoratitive name server. A month of overlap to run both servers while the change is being propogated is a good amount. Two weeks would probably be adequate.