You can use 301 redirects to keep traffic flowing to your Web site even after a major redesign.
After a certain period of time, you may have the desire to reorganize your Web site, spin-off part of your site to a new site, or move your entire site to a new domain because of a buyout or company name change.
But what happens to your search engine ranking and the incoming links to from other Web sites that now point to defunct pages? How do you keep from losing this traffic?
The answer is a 301 redirect. A good, in depth article on Changing Domains and Renaming Pages appeared in the High Rankings Advisor Newsletter by Michael Bluejay.
A 301 tells a requesting browser that the page requested has permanently moved, and where it now exists.
In short, a search engine spider or a visitor’s browser requests a page at your site that has been moved. A properly set up 301 Redirect will avoid that nasty 404 error (page not found) and redirect the browser to the new page or location. Michael gives some good examples in his article of how to set the 301 up.
Some of his examples include:
Redirecting an entire Web site to a new domain (assuming the file structure is identical):
Redirect 301 / http://www.newdomain.com
Redirecting a page to a new area of the Web site:
Redirect 301 /oldpage.html http://www.domain.com/newpage.html
Geek Alert! These changes are made to the .htaccess file that resides on the server. The 301 works on servers running Apache, so Windows-hosted sites need to find an alternate solution.
One item that Michael hadn’t mentioned was how to redirect a whole directory to a new domain. Back in 1997 I left my job to start a Web design company. I also left on a cross-country roadtrip with a laptop and a digital camera. My goal was to create a guerrilla Web site about my travels.
The site had been hosted at http://www.b1com.com/roadtrip (an old domain of mine.) I recently bought a new domain, http://www.roadtrip97.com, which I used to host the travelogue. Unfortunately, most of the traffic was still going to b1com.com/roadtrip or flyte.biz/roadtrip as those sites had been around for ages. Since they were clouding my traffic reports, I wanted those pages removed…permanently.
I had thought that the 301 redirect might be a solution, but I didn’t want to create hundreds of lines of code (one for each page that needed to be redirected.)
I followed up with Michael and he confirmed what I suspected: I could create a wildcard of sorts:
Redirect 301 /roadtrip http://www.roadtrip97.com
That single line would redirect all the traffic going to the roadtrip directory to the matching page at the new domain! Suh-weet!
BTW, if you are looking for a good way to waste an afternoon, please feel free to check out roatrip ’97. I’ve done my best NOT to fix anything on the site, but just to leave it as is. It’s not polished, but it will destroy your productivity for a while.
Rich Brooks
Cross-Country Traveler