301 Redirect

Change all links to the new pages or leave links to 301'd pages initially?

[jacuzzi]

I just changed over my pages from .html to .aspx , I've put a 301 redirect on the .html pages to the .aspx pages. But I am not sure whether to change to links on my home page to the new .aspx pages right away.
I'd like to get the new .aspx pages into the index as soon as possible, but I fear if I link to them right now they will trip the Dup Content filter.

Any thoughts..?

[Span]

Mm.. how did you put 301's on the html pages?

I think you need a server-side global 301 html > aspx rewrite. And since your old pages aren't accessible anymore after that, you can simply delete them.
But wait for an expert to second this..

[geebee2]

Why not leave the pages as html but serve them using aspx?

Thats the standard approach I have adopted.

[coburn]

On the topic of 301's - what do you use for a windows based server?
We have a .com site which has been eclipsed by the .co.uk site. We've got IISRewrite running to redirect all requests for .com to .co.uk
Not yet out of the 'sandbox' (2.5 months so far), so we don't know whether we're being penalised in the SERP's yet for being new or for duplication of content.

So is the IISRewrite the best option for SE's like G?

Thx

[my3cents]

just my 3 cents...

I had 301'd pages months ago and google still doesn't have it right, the 301'd pages still show as fully indexed, but then again, I have pages that were not 301'd that haven't existed in over 6 months that are still fully indexed.