Changing File Extensions

From .cfm to .asp

[Bob_K]

I'm switching my site from coldfusion to asp.net which will also change the extensions in my URLs. Would it be best to use a 301 redirect from the old urls to the new ones?

I will also most likely be using an ISAPI Rewrite to fix the URLS for my dynamic pages. Would it be easier just to do everything in the Rewrite, or just fix the URLs with the Rewrite and stick with the 301 redirects from the old URLs to the new URLs?

[mrMister]

You don't want to be changing file extensions unless you can help it.

Go to the IIS Manger.

Under the Web Sitres folder, right click on your site and select properties.

Click on the "Home Directory" tab

Press the "configuration" button

Edit the cfm application extension and select edit

In the Executable textbox, type in the full path to your aspnet_isapi.dll

(eg. C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll)

Then Press OK

Now all your .cfm files will operate in the same way as .aspx files (they will run under the .NET framework).

[mattglet]

I'm sorry, but I've always thought that solution is not the best. Just create proper 301's and everything will be fine. You'll take a small dip with SE's, but you will definitely gain it back soon. I've done it multiple times, and have had the same results every time: Your deep pages take a hit, and come back to normal.

Mapping file extensions through your desired application executable is just a band-aid, IMO. Do it the correct way the first time.

[mrMister]

I would disagree to the band aid statement. The solution is to not change the URI at all. By placing a 301 to a redirect is a band aid fixing the problem of a changed URI.

I refer you to Tim Berners-Lee's article:

Cool URIs don't change [w3.org]

I agree that 301s used to work really well. However have you tried them in Google lately. I've noticed a distinct change in how Google handle's 301s since a few months ago.

I've tried 301s with a number of sites recently and they have not recovered in Google to the same extent that they used to. This is a recent change.

The ideal situation is not to change your URI at all. A 301 should only be used as a last resort if you can not possible keep the URI the same.

Luckily, with IIS, there's no need to change it.

[mattglet]

As for your article:

Tell that to eBay, Amazon, Microsoft, Best Buy, Staples, etc. etc. etc.

I'm pretty sure they aren't having any problems.

[mrMister]

Absolutely,

Bob_K, If you're site is a world recognised brand name or a Fortune 500 listed company, I wouldn't worry too much about the search engines ;-)

[Bob_K]

Thanks for your replies. I'll use this information when I decide what to do.

[mattglet]

Well, there's no link dropping, so how else am I supposed to show that proper 301'ing works fine?

Bob-
I suggest you do some research on the hundreds of other posts regarding your topic within WebmasterWorld that ask the same question. You'll see a lot better responses from people that actually know what they are talking about.