Welcome to WebmasterWorld Guest from 54.80.189.255

Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Change from .asp to .aspx - 301 & 302 redirect worries

     
5:42 pm on Feb 8, 2008 (gmt 0)

New User

10+ Year Member

joined:Feb 8, 2008
posts: 2
votes: 0


Hello all,

I'm currently working on a website upgrade project, part of which has been to make the move from ASP Classic to the ASP.NET 2.0 Framework. Our current website is well indexed in Google and I'm worried about losing all of this because of the filename extension .NET files have (.aspx) compared to ASP Classic's .asp.

I've been very careful with file names and content is very similar (though with different HTML due to the design change) for example say we have the following page currently: http://www.example.com/aboutus.asp

The new URL for this page would be: http://www.example.com/aboutus.aspx

My plan was to upload all of the new pages and then use a Response.Redirect("aboutus.aspx") ASP Classic code to redirect the user from the old pages to the new, however after a bit of research on the subject of 301 and 302 redirects I've found a lot of horror stories of websites that have been completely dropped by Google due to this sort of action.

Have any of you had experience of this sort of language upgrade and the effects of the redirects on your Google indexing?

[edited by: Robert_Charlton at 5:48 pm (utc) on Feb. 8, 2008]
[edit reason] changed to example.com - it can never be owned [/edit]

6:28 pm on Feb 8, 2008 (gmt 0)

Senior Member

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:May 26, 2000
posts:37301
votes: 0


Here is a thread from our Microsoft ASP Forum with a report on a successful changeover:

Converting from .asp to .aspx what can I do to stay ranked? [webmasterworld.com]

If you are very precise technically, you can make the change with a minimal disruption - but make sure that your redirects are retruning a 301 status and not 302. Also take car not to introduce any duplicate urls that point ot the same content. I find it's best to deploy the new site in a test environment first to find all the bugs.

3:33 pm on Feb 11, 2008 (gmt 0)

New User

10+ Year Member

joined:Feb 8, 2008
posts: 2
votes: 0


Thanks for the reply tedster, some very mixed views on that thread but all good info. Has anybody else had similar experiences?
7:27 pm on Feb 11, 2008 (gmt 0)

New User

10+ Year Member

joined:May 5, 2005
posts:32
votes: 0


Yes. We changed our site from all .html pages to .aspx - over 600 pages old .html pages to about 130 new .aspx pages.

This was about a year ago. I believe the thread Tedster refers to mentions using isapi for your redirects.

We had no ranking drops to speak of - a temporary minor glitch with a relatively unimportant page - someone had stolen our content and the change brought this issue to the fore.

I think Tedster means to say that you should take care to not introduce different urls (not duplicate urls) that point to the same content.

As long as your are methodical and accurate with your isapi redirects and maintain the content/focus of your new pages you should not have many issues.

I guess "conventional wisdom" says that you should plan on a 3 to 6 month drop - we did plan for this and were ready with an adwords budget in case our organics tanked. Fortunately, they didn't.

Tedsters advise to test is sound.

 

Join The Conversation

Moderators and Top Contributors

Hot Threads This Week

Featured Threads

Free SEO Tools

Hire Expert Members