Implications of a Site 301 re-direct

[ross3485]

I wanted to know if anyone had converted from an ASP site to an ASP.NET (.aspx) site using a 301 re-direct. We have a large e-commerce site which has been build on .asp and we are converting to .aspx extension. I have been told that we would need to do a server 301 re-direct of our current site to the new .aspx pages, however, I wanted to know if anyone knew the implications from a SERP ranking stand point.

[Gooner151078]

Your intention should be to direct each page to it's new place

asp1 -> aspx1
asp2 -> aspx2
asp3 -> aspx3
etc.

If you do a 301 server side redirect your rankings should in theory be unaffected. In practice this has not always been the case but these situations are often a bit more complex.

Having completed as similar transfer recently, I can emphasize with the decisions you are going through. I took the risk and made the change however and am now reaping the benefits of keyword heavy URL's.

[jimbeetle]

You might see a bit of a negative impact at first as the SEs digest the redirects. Then, over time, things should be sorted out. I've seen that, depending on depending, be as short as a month to as long as six months. Google, as far as I know the only SE to give any guidance on this, says to keep the redirects in place for six months. I'd say once you put the redirects in place to keep them there permanently.