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

Popular posts from this blog

Converting PSD with PHP/ImageMagick

After seeing feature rich options in Imagick PECL extension at Mikko Koppanen 's (the author) website and also impressed with ImageMagick 's features, I have decided to use it for the PSD to XHTML conversion website that I'm architecting and managing. Since, the team wants programming help for converting PSD images, I have tried it (documentation is sparse on PSD handling) Converting PSD to PNG/JPEG/etc Note that, flattenImages() is needed for layered/multi-page PSD file. <?php $im = new Imagick('test.psd'); $im->flattenImages(); $im->setImageFormat('png'); $im->writeImage('test.png'); ?> Extracting PSD layers One by one <?php $im = new Imagick('test.psd'); $im->setImageFormat('png'); for ($i = 0, $num_layers = $im->getNumberImages(); $i $im->setImageIndex($i); $im->writeImage('layer' . $i . '.png'); } ?> Note that, there is a better version below In a single call with writeIm...

BehaviorS.js - An alternative to Behaviour.js, event:Selectors and Low Pro libs for unobtrusive JavaScript programming

BehaviorS.js yet another unobtrusive JavaScript library similar to Behaviour.js and event:Selectors but in implementation uses hash based lookup without extending elements; so presumably it should be faster than the rest. The original script and idea was by JLof ; I extended it for DOMContentLoaded support, optimized a bit to avoid scanning of more depths, and added new rules support. I wanted to document the plug a long time and just got time to do it. For the time being BehaviorS.js is available here Update (2006-09-11) : Coralized the link to BehaviorS.js so as to save the load on free brinkster.com webpage Update (2006-09-27) : If the coralized link to BehaviorS.js doesn't work, use http://www21.brinkster.com/guideme/BehaviorS/ Update (2025-06-07) : Now available in https://github.com/rrjanbiah/behaviorsjs

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...