Page Rank: default.asp V http://www.website.com/

Why is it different?

[Phil_C]

I've noticed that one of my sites has default.asp listed as PR 3 while simply visiting http://www.website.com/ gives a PR of 4.

Given that http://www.website.com/ throws default.asp back to the client (this is the only default page set in IIS), how can they be different?

[troels nybo nielsen]

This is really beyond my level of expertise, but might it be a question about where links are pointing? Some months ago I changed a lot of links from mysite.dk/index.htm to mysite.dk/

That made a lot of my SERPs look sick for some weeks.

[killroy]

Well think about that, how does the search engine, google, know what your IIS setiigns are? It cannot possibly, so any IIS settings are of ABSOLUTELY NO CONSEQUENCE to Google.

So, if you want google to understand, you have to use something google knows, such as the HTTP protocol for example. i.e. place a 301 (moved permanently) redirectfomr default.asp to domain.com/

SN

[Furmanov]

oh, I have just asked a similar question in "how many home-page have you lost?" thread

[ciml]

/index.html and /index.htm are treated as /

Google doesn't even fetch them and any links to those URLs are credited to / instead. I think that index.cgi is in this category too.

index.shtml, iNdEx.HtmL, default.htm, default.asp, index.php, index.py are not merged and if Google doesn't find identical content they'll be listed separately, each with their own backlinks.

[troels nybo nielsen]

Sorry for having confused matters. Strange. Then I must have been doing something else at the same time that created those problems.

[Furmanov]

ciml

index.shtml, iNdEx.HtmL, default.htm, default.asp, index.php, index.py are not merged and if Google doesn't find identical content they'll be listed separately, each with their own backlinks.

why then when I search for link:www.domain.com and for link:www.domain.com/index.shtml I get absolutely the same backlinks dmoz and all external links included?

I posted with similar questions here

[webmasterworld.com...]

would really love to clear this up, earlier in some post Brett mentioned that many of those who lost their index-pages are dealing with duplicate content issue, hope somehow this but not some filters is the case with us, we do not have much to de-optimize anyway :(

[runboy]

I had the same problem on my site a few weeks ago. On my case it was [website.com...] that had a PR of 6 and [website.com...] had a PR of 5.

The reasón was that all my "Home" links were pointing to [website.com...]
I changed it to [website.com...] and now [website.com...] has a PR 6

"I think that index.cgi is in this category too."

I don't think so. You can do a simple experiment. In my case I use default.asp.
If I check PR on [website.com...] I get 6. If I change what is after "/" I will in some cases get a PR indication even though there is no page. I get the following results which indicates that index.cgi is NOT considered the same page:

[website.com...] - PR 6
[website.com...] - PR 6 (That page is on the server)
[website.com...] - PR 6 (That page is NOT on the server)

[website.com...] - PR 6 (That page is NOT on the server)

[website.com...] - NO PR (That page is NOT on the server)
[website.com...] - NO PR (That page is NOT on the server)

[GoogleGuy]

Yah, I would try to use just www.domain.com instead of www.domain.com/anypagenamelikedefaultorindex.htm. We do our best to find any dupe pages and collect them together correctly, but my general rule of thumb is that the easier it is for any spider to get it right, the more likely it is that it will be right. :)

[Phil_C]

Excellent feedback guys - thanks very much. I do have a number of links in the site linking back to default.asp, so I'll change these. Cheers!

- Kilroy - I'm not suggesting google knows my IIS settings. Read my question again.