Skip to main content

Why Google PR is quirky -- Google PR bug

Recently I have been informed that the PageRank provided by pagerankstatus, a Firefox extension is different from official Google Toolbar. Since, I have been slightly involved with the development of this extension, I have studied the reason behind it.

Example
Target site: http://benmccann.com/
Pagerankstatus's PR: 4
Official Google Toolbar's PR: 0
Reason: Google's bug
Analysis

Pagerankstatus
What pagerankstatus requests: ...features=Rank:FVN...
What Google returns: Rank_1:1:4
Official Google Toolbar (IE)
What Google Toolbar requests: ...features=Rank:...
What Google returns: Rank_1:1:0
Official Google Toolbar (FF)
What Google Toolbar requests: ...features=Rank...
What Google returns: Rank_1:1:0
Google info XML file: ...info:...
PR inside XML file: 4 (This might be the right PR. Same as of pagerankstatus.)

Conclusion (Google bug)

Official Google Toolbar has downgraded the category/directory option; that's why now not sending "FVN" as "FVN" is for category. But, Google is supposed to return same PR for "Rank:FVN" and "Rank:", but returning different results. Let's hope, Google will fix this bug soon.

Comments

Post a Comment

Popular posts from this blog

I'm Zend (PHP 5) Certified Engineer:-)

As of January 13, 2007, I'm ZCE/ Zend Certified Engineer (PHP 5)
2 comments
Read more

Tim Van Wassenhove's (PHP) Blogmarks

Tim Van Wassenhove , a c.l.php regular maintains wonderful blogmarks . Most of the blogs are PHP related and it is faster to access than my Sage, RSS reader . It is interesting to see that Tim has blogmarked my—this simple blog too:) IMHO, it would be better to display timestamps along with the links and to have a TOC of blogs in the top.
4 comments
Read more

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...
6 comments
Read more