Re: PR to Domain name - not to pages

On Sun, 9 Nov 2003 08:28:49 +0100, "René Løweneck" <rene (AT) loweneck (DOT) dk>
wrote:

Hi !

My domain have a PR2. All pages seem to have PR0.

Scenario :
When you enter a domainname in a browser, you normally would get ie.
default.asp. The browser normally just show the domainname. Then default.asp
should have the PR2 and links from this page would cary the PR2 to the pages
from these links or what?
Can a domainname really have a PR and (none of the)pages not?


Kind Regards

I believe it goes by URL, so www.domain.tld/ is different from
www.domain.tld/index.html. I would guess that since a web server can
be configured to serve any arbitrarily selected file as the root
index, Google opts not to assume equivalency.

If your root does have a 2, and pages linked directly from it don't
have a 1, there may be some other issue: frames, iframes,
misconfigured robots.txt, etc.

In article <of3uqvg6il245vlbetlc3joo3p26jhoel5 (AT) 4ax (DOT) com>,
no.john (AT) spammers (DOT) virginiaquilter.allowed.com says...

On Sun, 9 Nov 2003 08:28:49 +0100, "René Løweneck" <rene (AT) loweneck (DOT) dk
wrote:

Hi !

My domain have a PR2. All pages seem to have PR0.

Scenario :
When you enter a domainname in a browser, you normally would get ie.
default.asp. The browser normally just show the domainname. Then default..asp
should have the PR2 and links from this page would cary the PR2 to the pages
from these links or what?
Can a domainname really have a PR and (none of the)pages not?


Kind Regards

I believe it goes by URL, so www.domain.tld/ is different from
www.domain.tld/index.html. I would guess that since a web server can
be configured to serve any arbitrarily selected file as the root
index, Google opts not to assume equivalency.

If you check links for a site then '/' and '/index.html' give the same

results (if they're using index.html) so google certainly treats that
one specially.

In article <HBJrb.1145$ak4.398 (AT) news (DOT) get2net.dk>, rene (AT) loweneck (DOT) dk
says...

Hi Pete !

"Jacqui or (maybe) Pete" <porjes (AT) spamcop (DOT) net> wrote in message
news:MPG.1a196cc4af57cdf3989d46 (AT) news (DOT) individual.net...
If you check links for a site then '/' and '/index.html' give the same
results (if they're using index.html) so google certainly treats that
one specially.

Yes http://www.lowesite.dk/ = PR2
and http://www.lowesite.dk/default.asp =PR0

Interesting. I don't see any difference in PR for '/' or 'index.html',

so I guess 'default.asp' isn't in the list of things that google treats
specially.

On Mon, 10 Nov 2003 11:22:22 -0000, Jacqui or (maybe) Pete
<porjes (AT) spamcop (DOT) net> wrote:

Yes http://www.lowesite.dk/ = PR2
and http://www.lowesite.dk/default.asp =PR0

I've not looked at your site, so this is a guess.

Are your incoming links going to -

http://www.lowesite.dk/
http://www.lowesite.dk/default.asp

or
http://www.lowesite.dk/index.htm(l)

If it's the latter than you would expect the index.htm(l) to have the
PR.

Or has the default index page been changed on the server recently from
index.htm(l) to default.asp?

David
_
Free Search Engine Optimization, SEO and
Search Engine Placement Tips (updated 10/10/2003)
http://homepage.ntlworld.com/ooar123...-optimization/

On Mon, 10 Nov 2003 09:40:05 -0000, Jacqui or (maybe) Pete
<porjes (AT) spamcop (DOT) net> wrote:

I believe it goes by URL, so www.domain.tld/ is different from
www.domain.tld/index.html. I would guess that since a web server can
be configured to serve any arbitrarily selected file as the root
index, Google opts not to assume equivalency.

If you check links for a site then '/' and '/index.html' give the same
results (if they're using index.html) so google certainly treats that
one specially.

I've just been having this conversation in a web forum. The consensus
there was that '/' and 'index.html' are different pages with their own
PR. However I find that index pages in my site consistently have the
same PR wether or not I add the 'index.html' to the URL.

Anyway, I was advised to use a consistent linking method and I want to
go without the 'index.html' for index pages. My questions are:

Are www.domain.tld and www.domain.tld/ exactly the same page as far as
SEs are concerned? Is there any danger of splitting PR if some inbound
links use the trailing slash and others don't? Are there any other
SERP issues regarding the trailing slash? Which is better, trailing
slash or not?

Thanks,
Dave
---------------------------
http://www.mediacollege.com
Electronic Media Tutorials & Resources

On Tue, 11 Nov 2003 14:22:42 +1300, dave conz <not (AT) valid (DOT) addy> wrote:

On Mon, 10 Nov 2003 09:40:05 -0000, Jacqui or (maybe) Pete
porjes (AT) spamcop (DOT) net> wrote:

I believe it goes by URL, so www.domain.tld/ is different from
www.domain.tld/index.html. I would guess that since a web server can
be configured to serve any arbitrarily selected file as the root
index, Google opts not to assume equivalency.

If you check links for a site then '/' and '/index.html' give the same
results (if they're using index.html) so google certainly treats that
one specially.

I've just been having this conversation in a web forum. The consensus
there was that '/' and 'index.html' are different pages with their own
PR. However I find that index pages in my site consistently have the
same PR wether or not I add the 'index.html' to the URL.

A more telling test is whether they both get the same list of
backlinks. I use "/" for all mine, yet I get the same backlinks for
"/index.htm", "/index.html", "/", and hostname-only. Seems Google does
equate certain common root URLs.

Anyway, I was advised to use a consistent linking method and I want to
go without the 'index.html' for index pages. My questions are:

Are www.domain.tld and www.domain.tld/ exactly the same page as far as
SEs are concerned? Is there any danger of splitting PR if some inbound
links use the trailing slash and others don't? Are there any other
SERP issues regarding the trailing slash? Which is better, trailing
slash or not?

It's best not to assume that all SEs equate such URLs, or even if they
did that they always will. With Google it doesn't seem to matter.

I can't say what might happen if, say, you set up both an index.htm &
index.html with different content. If pages somewhere out there link
to each, Google may well detect that and begin to differentiate
between the two for your site, for all I know.

I've *heard* that "www.domain.tld/" is a little more computationally
efficient for web servers to parse, while, of course, using one more
byte each time the URL is transmitted in requests, links, etc., and,
maybe, written in access logs. I go with the assumption that what I've
heard is correct (or at least plausible) and lean towards possibly
greater server efficiency with "/".

JA

dave conz wrote:

I've just been having this conversation in a web forum. The consensus
there was that '/' and 'index.html' are different pages with their own
PR. However I find that index pages in my site consistently have the
same PR wether or not I add the 'index.html' to the URL.

They are different. If Google finds both and notices they are the
same, typically they get merged into one. However, this may not happen
instantaneous. Meaning theoretically it is better if all links are to
one or the other.

Anyway, I was advised to use a consistent linking method and I want to
go without the 'index.html' for index pages. My questions are:

Are www.domain.tld and www.domain.tld/ exactly the same page as far as
SEs are concerned? Is there any danger of splitting PR if some inbound
links use the trailing slash and others don't? Are there any other
SERP issues regarding the trailing slash? Which is better, trailing
slash or not?

Both would be the same for Google.
--
http://www.dextromethorphan.ws/
For information about the psychedelic drug DXM, including dangers.
Yet another murder by someone on Coricidin:
http://www.coricidin.org/kansas-coricidin-murder.htm