Forum Moderators: open

Message Too Old, No Replies

Saving Pagerank

saving internal PR with robots.txt or js links

         

squared

7:33 pm on Sep 12, 2002 (gmt 0)

10+ Year Member



I'm trying to use PR efficiently on my site. I have a TOS and privacy policy that are linked to. Since I'm interested in getting more PR to my content pages, I'd like to stop the PR leak to the TOS and PP. If I were to disallow Googlebot from crawling my TOS and privacy policy pages with robots.txt, would this stop PR from leaking to these pages? Or should I use javascript links instead? Or are there any other ways to stop the PR leak?

-Squared

weisinator

7:44 pm on Sep 12, 2002 (gmt 0)

10+ Year Member



"PR Leak" is misleading. The page containing the outbound links does not lose pagerank simply because it has links.

OTOH, if a page has five links instead of three, the PR transferred by those five links (per link) is less than the PR transferred by three links (per link).

squared

7:48 pm on Sep 12, 2002 (gmt 0)

10+ Year Member



weisinator,

Correct. The page that contains the outbound links does not lose PR, BUT I'm interested in channeling that PR effectively and I think sending it to my TOS and PP isn't needed.

-squared

born2drv

8:03 pm on Sep 12, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I had the same problem. I used a small js code to create the links for my "about us", "contact us", "privacy policy", "shipping", etc. Hoping that my content pages get more PR. No results to report yet, I'll let you know what happens after the next update ;)

AkanDian rain

8:36 pm on Sep 12, 2002 (gmt 0)

10+ Year Member



Squared
You logic seems sound... At the very least blocking some of your internal pages wont likely hurt your PR, so why not try it. I would be interested to know if it works.

brotherhood of LAN

9:15 pm on Sep 12, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



The topic has been discussed a bit in regards to both, found using the site search [searchengineworld.com],

For Javascript
[webmasterworld.com...]
and the latter half of [webmasterworld.com...]

I don't think anyone is 100% sure about pagerank being passed on to robots.txt pages, or whether it is preserved sort of thing.

Either way, IMO its a good thing to exclude things like TOS pages and site specific information, but not javascripting outbound links type thing :)

WebGuerrilla

9:20 pm on Sep 12, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member




The absolute best way to control your PR flow is to cloak.

Humans get the page with the TOS link, and Google doesn't.

A much better solution than trying to rely on robots.txt or JS tricks.

squared

10:48 pm on Sep 12, 2002 (gmt 0)

10+ Year Member



WebGuerrila,

If Google found out, do you think they would penalize me? Or, is this a case where cloaking would be okay?

P.S. Is the best way to cloak with mod-rewrite?

DaveN

10:53 pm on Sep 12, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If Google found out, do you think they would penalize me?

depends on whether or not google thinks you are doing it to again PR or an advantage in the serps.

My guess would be, google would never find out.

DaveN

On cloaking

Once you go to the darkside you will never return ;)

martin

11:10 pm on Sep 12, 2002 (gmt 0)

10+ Year Member



>Is the best way to cloak with mod-rewrite?

Depends on what you have available.

>On cloaking
Once you go to the darkside you will never return

What do you mean? I'm cloaking a left/right sidebar, I think that left is more usual for humans. What's wrong about it?

I don't see myself cloaking content in the near future.

squared

11:11 pm on Sep 12, 2002 (gmt 0)

10+ Year Member



DaveN,

That makes me thinks I shouldn't be doing it. After all, I am interested in getting better results with my other pages. If Google were to look at it, that IS why I'm doing it.

GoogleGuy, care to chime in?

Jane_Doe

4:26 am on Sep 13, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I did a trial run with a noindex, nofollow meta tag on the "contact me" and "disclaimer" pages of one of my sites to see what would happen with the PR. After the next update, the tool bar showed the same PR as it had before I put in the meta tag.

DaveN

7:54 am on Sep 13, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Squared,

You should really be ok,

Cloaking is widely used in spamming SE's once you have learnt how to cloak you may find the tempatation to High.

Famous Last Words
"I'll Just cloak this page so that the SE can't see it........What the Hell I might as well show the SE a Content Rich Page and The Customers my Terms And Conditions it can't hurt"

DaveN

TheDuke

10:25 am on Sep 13, 2002 (gmt 0)

10+ Year Member



Boys, boys boys....
One Advice ! DO NOT CLOACK !
Don't use any "tricks", just optimize your site "by the book". Any violations will be picked up sonner or later by google and you will get banned !

[edited by: ciml at 12:43 pm (utc) on Sep. 13, 2002]
[edit reason] identifying keyword snipped [/edit]

nutsandbolts

10:44 am on Sep 13, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Never, ever cloak. Simple. Google will catch you - and when they do - you will be booted out. Be squeaky clean, add lots of good quality content and get good quality links. It's that simple, really ;)

If I was you, I would use your terms and conditions/Privacy page in a positive way. You can add lots of information about your site and services in there (which can be found via a search if you're clever about it) and, of course, that makes 2 more pages for the Googlebot to chew on. Man, that Googlebot loves pages ;)

glengara

11:39 am on Sep 13, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



IMO, all this messing about with methods of "channeling" PR is just storing up trouble for the future.

GoogleGuy once said -

*If you work really hard to boost your authority-like score while trying to minimize your hub-like score, that sets your site apart from most domains.*

Sounds like you wouldn't want to do that, so just let the PR flow, man!

Markus

12:09 pm on Sep 13, 2002 (gmt 0)

10+ Year Member



By "channeling" PR, you can also maximize your "hub-like-score". Sometimes, the only reason for having one site is to transfer PR to another one.

IMO, JS links and robots.txt exclusion are both appropriate for getting a better PR distribution and they're not part of Google's "Don'ts". If a page is good for getting external inbound links I use JS links to link to it internally, if not, I exclude it by robots.txt.

ciml

1:14 pm on Sep 13, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



squared, if you link from your TOS and privacy policy to at least one other page on your site then the leakage is likely to be very small.

If you link from those pages out to other sites, then you might want to make sure that those pages have at least a few links.

WebGuerrilla

5:44 pm on Sep 13, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



>>Never, ever cloak. Simple. Google will catch you - and when they do - you will be booted out.

Way too broad of a statement. There is a huge difference between using IP delivery to cheat your way to the top and using it to properly control a particular bot.

When I go to www.google.co.uk I am served a different set of links than someone who is located in the U.K. This happens because Google has detected my IP and made the determination that certain links simply won't be relevant to me because I'm in the U.S.

Other high-profile sites detect UA/IP's so that they can server their pages without any advertising. It is extremely common. The fact that you check IP's before determining what configuration to use to deliver your content does not make you a spammer.

Using IP detection to deliver navigation that prevents Google from crawling content that will never provide any relevant information to a Google user is beneficial to both parties. And the intent behind using such a system is exactly the same as excluding the pages using a robots.txt file. The only difference is that using IP detection [b]works much better{/b].

With IP, I'm in control, and I don't have to trust the fact that Google will actually stay out of my excluded content. I also don't have to display to the world a list of every page on my site that I don't won't showing up in a search engine. Nor do I have to deal with the annoying habit Google has of returning excluded pages in their SERPS.

If not serving a particular link improves PR flow to important pages with valuable content, while excluding pages via robots.txt does not, then that is a flaw in how Google deals with robots excluded pages. If I exclude them, then Google shouldn't look at them, and the links pointing to those pages should not be used to calulate any PR scores.

nutsandbolts

5:55 pm on Sep 13, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Way too broad of a statement. There is a huge difference between using IP delivery to cheat your way to the top and using it to properly control a particular bot.

Let's be honest here - cloaking is more often than not used to provide the search engine with content (not seen by the Web page visitor) to increase search engine placement. Google says "Don't Cloak" on their Webmaster page. So - Don't Cloak with Google...

squared

5:58 pm on Sep 13, 2002 (gmt 0)

10+ Year Member



I'd just like to thank everyone for their input. I'm still a little confused as to what I should do. Oh well. I'll put some thought behind it and figure it out soon.

best to everyone,
Squared

jatar_k

5:59 pm on Sep 13, 2002 (gmt 0)

WebmasterWorld Administrator 10+ Year Member



If you are providing valid content and ranking better for relevant keywords why is it any different than using H1 tags or good link text or tweaking content?

<added>OK so that is a little OT, squared, look at ciml's post again #18. I think you could take that as an allaying of your worries. I agree that if you don't have external links on those pages and they link to other pages on your site the leakage shouldn't be a worry.

squared

6:10 pm on Sep 13, 2002 (gmt 0)

10+ Year Member



jatar_k,

Yes, but the site is only 20 pages. The home page is a 7. If I were to exclude the TOS and PP, I would be gaining 10% more PR to my other pages.

jatar_k

6:16 pm on Sep 13, 2002 (gmt 0)

WebmasterWorld Administrator 10+ Year Member



Then I would say test block them through robots.txt and see if that makes a difference.

As ciml said I don't think it is a major issue but if you feel it will help then by all means test and analyze.

ciml

6:49 pm on Sep 13, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



squared:
> If I were to exclude the TOS and PP, I would be gaining 10% more PR to my other pages.

The log scale on the Toolbar makes a big difference. A 10% loss is about one twentieth of a notch on the Toolbar - the difference between 6.00 and about 5.95.

The effect of PR on ranking is applied in some similar manner, otherwise PR10 pages (which have many thousands times the PR of PR5 pages) would score top for all their words.

martin

11:14 pm on Sep 13, 2002 (gmt 0)

10+ Year Member



>I did a trial run with a noindex, nofollow meta tag on the "contact me" and "disclaimer" pages of one of my sites to see what would happen with the PR. After the next update, the tool bar showed the same PR as it had before I put in the meta tag.

Jane Doe, the toolbar is showing guessed PageRank not real.

>block them through robots.txt and see if that makes a difference.

As long as PageRank is a property of pages within the Google index, and not all pages, it should make a difference.

Jane_Doe

12:17 am on Sep 14, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



> Jane Doe, the toolbar is showing guessed PageRank not real.

The PR on the pages with the metatags came out higher (5) than what new pages at the same level were usually assigned as a "guess" (4), so I didn't think it made a difference.

How can you tell a "guessed" PR from a real PR?

Chris_R

12:32 am on Sep 14, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



glengara is right IMHO.

All this PR saving is just going to put you on the map as a PR Miser in googles little algos - now or the future.

It's not that I am against it in theory - it is just the advantages are so small compared to the possible huge disadvantages.

The PR you save by doing this isn't going to help you much. The other things that will no longer be in the algo could hurt you.

It is not necessarily a BAD thing to give other site PR.

Think very very carefully before you do something like this.

Marcia

12:53 am on Sep 14, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



>Yes, but the site is only 20 pages. The home page is a 7.
If I were to exclude the TOS and PP, I would be gaining 10% more PR to my other pages.

It doesn't quite work 100% that way. If your homepage is PR7, and assuming your other pages are PR6 and all linked to from the homepage and each other, now there 19 PR5 interior pages linking to each other and back to the homepage. If you put the two pages, PP and TOS in an /information/ directory and exclude that directory with robots.txt that's 17 interior pages linked to from the homepage - 2 less, and 2 less PR6 pages linking to the rest of the site.

Are all the pages linked to from the homepage and with each other now, or are some in directories? And how competitive is the category you're in? Are you competing against 3 million pages, a million or 500K?

Added:
>It is not necessarily a BAD thing to give other site PR.

Agreed. And if some check and catch it, it could cost some good links and create some bad feelings. We don't have to, however, give away a disproportionately large amount of Page Rank when we link back to people. There are honest ways to control that without looking like a miser.

martin

10:33 pm on Sep 14, 2002 (gmt 0)

10+ Year Member



>How can you tell a "guessed" PR from a real PR?

If the page is in the cache it is real, otherwise it is guessed.

This 35 message thread spans 2 pages: 35