Welcome to WebmasterWorld Guest from 126.96.36.199
Rank_1:1:6 Rank_1:1:5 Rank_1:1:4 Rank_1:1:4 Rank_1:1:5 Rank_1:1:6 Rank_1:1:5 Rank_1:1:0 Rank_1:1:1 Rank_1:1:5 Rank_1:1:2 Rank_1:1:3 Rank_1:1:0 Rank_1:1:0 Rank_1:1:3
These figures are for a site that has a current toolbar of PR4.
I searched the web for an explanation, but failed to get a good one.
Is there any idea as to what all these magical numbers mean?
I think we need more examples in order to determine anything actually. Like if we have about 5 examples with the same thing we can make a conclusion but I don't think before as there is A LOT of factors in the rankings ...
I am not really tracking SERPs so I can't give any. And it seems like it's only you, me and Hanu following this thread so I am not sure how we will do about this, hehe.
With the way MC has talked about Big Daddy so far then this is probably related to all the "under the hood" infastructure changes he has been talking about.
With him saying that most people will not see any ranking changes at this stage it just feels to me that perhaps those <rk> values are just waiting to be applied rather than already effecting the serps on Big Daddy.
Have a look at Bluefind (Which I always believed was Canonical issues which resulted in the loss of PR)
On Big Daddy <rk> is 6 - however search on Bluefind returns the site anywhere between 30 odd and 60 - but not stronger in Big Daddy despite <rk> 6 compared to 0.
188.8.131.52 RK 6 Rank: 51
184.108.40.206 RK N/A (error on the tool?) Rank: 39
220.127.116.11 RK 0 Rank: 51
But Bluefind is not a good example. I am 95% sure it is under penalty for making money on selling PageRank.
I will start to make a sheet I think with RK figures and SERP rankings for some sites I own.
Maybe, in fact other sites which look like they might have penalties are having <rk> values returned in Big Daddy DCs.
Hmmz Toxic Lemon shows <rk> too on Big Daddy - not sure what to make of that - I was sure that was banned - could also have been canonical - but might be stretching my imagination there a bit - must have been a ban surely?
I was 95% sure that it was a canonical issue with Bluefind and as Big Daddy purpose is largely to sort this out then the return of a <rk> value could be seen as an improvement in this area.
The BigDaddy indexes are double as big than the rest!
I checked one site which it shows RK 5 on half and 7 on the rest (bigdaddy).
I used this query on the different DCs:
-link:http://www.example.com in Google (all sites not linking which is the whole index).
Some of the BigDaddy (RK 7):
18.104.22.168 gives 18,210,000,000 hits
22.214.171.124 gives 18,200,000,000
126.96.36.199 gives 25,270,000,000
188.8.131.52 gives 9,640,000,000 (?)
184.108.40.206 gives 25,270,000,000
220.127.116.11 gives 18,210,000,000
18.104.22.168 gives 25,270,000,000
22.214.171.124 gives 18,210,000,000
Some of the Rest (RK 5):
126.96.36.199 gives 9,640,000,000 hits
188.8.131.52 gives 9,650,000,000 hits
184.108.40.206 gives 9,640,000,000 hits
220.127.116.11 gives 9,570,000,000 hits
18.104.22.168 gives 9,650,000,000 hits
22.214.171.124 gives 9,660,000,000 hits
Actually same on both ... strange?
Otherwise it could be that as the BigDaddy versions has much bigger indexes they have found more of the backlinks and thus higher RK.
Not consistently Big Daddy - probably not when you queried.
With such huge differences between Big Daddy and non Big Daddy there should be more noticable ranking changes between the two.
Which makes me thing that the ranking changes <rk>? that will result from the Big Daddy infastructure are not in place yet.
Roll on Big Daddy.
To be fair to Toxic Lemon they look much cleaner than they used to be - was sure it was a ban though
This is my only hope that Google can now fix the problems that have blighted the index.
On Big Daddy the <RK>s are showing values again for sites that went to PR0 due to Canonical and Hijack problems - these sites however still dont rank in Big Daddy.
Fingers crossed that once Big Daddy roll out is complete then a PR update (internal or external) may result in changes for these sites.
I Still think that those RK (well the BD ones) values are the calculation by Mozilla Googlebot for Big Daddy and have not been applied to the serps yet. (must be soon though now rollout is complete - if they are going to be - MC has talked about an imminent PR update)
These values can be 0 as is shown currently without changes appearing in the serps.
Whether it is 0 to hide or just a temp situaton is the question. <rk> values are still there on a info:domain.com search (which is TBPR) - Lots of tools use that query to get current PR - so if G wanted to stop them why not stop that too.
Purge and refresh IMO.
[edited by: tedster at 4:10 am (utc) on Mar. 26, 2006]
Things should get real interesting, real soon.
Lets look at some of the facts.
So we should be near a situation where the Mozilla Googlebot generated/calculated PR/BL and other ranking factors take over from normal Googlebot PR/BL ranking factors. For a lot of people that is not a big deal as both normal and mozilla Googlebot should come to a similar calculation of PR/BL and the other ranking factors - but for sites which had crawling difficulties under the old Googlebot serp and crawling changes should be significant.
It could certainly be a purge and refresh but I actually think more that Google didn't like that value disclosed and all kind of guys making tools about it and so just put it to 0. Why would he then read my article? And the refferer URL is some strange Google URL redirecting to my article.
Frankly, I don't know. Could be either one.
Let's see. This is interesting. If we are lucky MC will blog about it :)
Examples of fine questions include:
- Is Bigdaddy fully deployed?
- What’s the story on the Mozilla Googlebot? Is that what Bigdaddy sends out?
- Any new word on sites that were showing more supplemental results?
- Is the RK parameter turned off, or should we expect to see it again?
- What’s an RK parameter?
Now, it seems that he have something to say about the Mozilla and <RK>, and will probably say them soon!
Q: “What’s an RK parameter?”
A: It’s a parameter that you could see in a Google toolbar query. Some people outside of Google had speculated that it was live PageRank, that PageRank differed between Bigdaddy and the older infrastructure, etc.
Well he didn't really answer. He just said "Some people outside of Google had speculated that it was live PageRank". He didn't say it was not Live PageRank :(
I interpretate his answer as:
"This is not for you guys".
Also he writes "Google toolbar query", which is also called RK but is something else ... not the the SERP XML RK.
Either MC don't know so much about it or he perhaps intentionally makes it confusing.
Just my 2 cents.
Anyway, I leave this subject now.
Some people outside of Google had speculated that it was live PageRank, that PageRank differed between Bigdaddy and the older infrastructure, etc.
what i could judge from mc's answer is that it was definatly something important and google was embarassed to notice that we could logicaly find out the importance of one of their confidential tool. I believe that they are now disguising rk value as something else and hiding it somewhere else.