Sitemaps and Javascript links for PR

This technique no longer working?

[James_Dale]

The old trick whereby site-wide links are written in javascript so they cannot be spidered, with the entry page of a site linking to a spiderable sitemap page, looks like it no longer works this index. Seems to be generating a PR0 penalty...

anyone else seeing this?

[Dolemite]

Just curious, but how is that a trick? Seems counter-productive to me.

[vincevincevince]

i think the idea is that PR is guarded on the first page, making the index page high in the results. i think the concept is flawed, but nevermind. i'd like to hear confirmation if this is in fact the intended purpose?

[Clever]

other reasons for hiding links:

- links are sometimes broken or unreachable
- be aware of linking to bad neighbourhood

I dont know exactly, but certainly both could
have negative effects in Google Ranking

If I have for example a directory site, it
is impossible to see if every included site/link
is reachable.

For this reasons hiding links with
java script would be ok for me.

PS: hope my english is ok

[James_Dale]

The idea is to either write the navigation bar in javascript, or put it into a robots.txt-excluded directory/file. Or both, to be doubly safe.

Since internal pages are then not going to be able to link amongst themselves (thereby distributing their voting PR amongst many nav-bar links), they are free to pass on the full whack of their voting PR to any desired target page.

These internal pages remain spiderable via the sitemap page, which contains spiderable links.

So, the distribution of PR (and link relevancy using link text) follows the path:
Homepage > Sitemap > Each internal page > target pages
rather than:
Homepage > All internal pages > All internal pages