Forum Moderators: LifeinAsia
Birdman
You don't have to keep the actual pages, just put 301 Permanent server redirects on those old
URLs, and point them to the new equivalent page, your home, or your site map, whichever is more
appropriate for each case.
This can easily be done on Apache using either mod_alias or mod_rewrite, and I'm sure there's
an equivalent for other popular servers.
Plan on leaving these redirects in place for a long time or forever - as long as you get any
significant traffic to the old URLs.
Hope this helps,
Jim
You are correct. That is why a server-generated 301 permanent redirect is recommended. It
tells the robot, "Look, this page is moved to this new URL, and it won't be back." Therefore,
there is no duplicate-content issue, which is what the search engines dislike.
Some SEs profess a dislike for meta-refresh redirects, because the timing of the redirect can mess
them up if done too fast or too slow. Most of them won't follow client-side scripted redirects -
for example, JavaScript - since they don't interpret these scripts, either.
A 301 permanent redirect, implemented correctly, will cause the search engine to update the URL
it is using to find the page, and stop using the old one. Google, for example, will transfer the
PageRank of the old URL to the new URL when it sees the 301 redirect.
All links internal to your site should be updated to use the new URLs, and get as many sites
as possible which link to your pages to update their links as soon as possible, too.
Jim
Try here [webmasterworld.com]. This is for IIS which may or may not be what you mean by "Windows Server". I'm an old Apache
guy, so I no speakee Windoze...
Best,
Jim
Since you're hosted on a Win2K machine, and the posters here on this thread so far have limited
knowledge of how that works, you might want to re-post with a new title like, "How do I do per-
page 301 permanent redirects on a Win2K Server?" That might get you some more specific help.
Other than that, make a note to never host with anyone who won't give you full ability to control
(and mess up) your own domain(s) - that's my #1 requirement for a host. The upside is that I can do
anything I want with my sites, the downside is that I have to wait until the wee hours to change my
.htaccess file, and before I do that, I open a second browser window - ready to test my site the
instant the new file goes up. If the new .htaccess file doesn't work, I can back it out pretty
fast (and I've had lots of practice!). :o
Best,
Jim