Can relative links PLUS multiple hompage versions spell disaster?

[kimmiedawn]

I still see internal links to default.asp from every other .asp page even though I have updated most of the relative /default.asp links to www.site.com since I 301 redirected it. I am seeing this in Open Site Explorer for one.

(I'm sure my lack of understanding has to do with not quite getting the purpose of default.asp.) Anyways, I am wondering if all the relative links throughout the site pointing to other .asp pages need to be updated to absolute links (so www.site.com/page.asp instead of /page.asp) for me to avoid this problem. Does one even have anything to do with the other?

[JaneCopland]

Hi Kimberly,

Sorry this question has gone so long without a reply: I've just been directed to it.

If the internal links to /default.asp (relative links) result in a 301 redirect, taking people to www.site.com/, there is technically no problem with that set-up. It would be better if the links pointed directly to www.site.com/ as a small amount of authority is lost in a 301 redirect, but is not disastrous by any means.

I am not sure that updating internal links to point to www.site.com/page.asp instead of /page.asp is the solution to the home page will solve this problem though - did you manually update the relative links to absolute links that have been fixed?