Skip to main content

Google Indexing and PageRank Algorithm: How does it work?

Google indexing works in ways that I don't understand. Well all I know is that the spiders got to me and doing a search on "optimizing firefox", I was 3rd on the list. Now ain't that cool!

PageRank Algorithm:

PgRnk(pg1) = (1-d) + d { PgRnk(pg2)/C(pg1) + ... + PgRnk(pgn)/C(pgn) }

Well OK it's simple math here.

o PgRnk(pg1)..PgRnk(pgn) = Page Rank's of Pages
o C(pg1)..C(pgn) = Number of outgoing links from those pages.
o d = damping factor(value of d between 0 and 1) usually set to 0.85

And how does it work?


Basically it all comes down to
  • Incoming links: They are all welcome, and even the bad one's will do nothing but enhance your position on the Google's indexing world. Worst come worst, it'll merely do *nothing*, if it was a negative link. So you're safe (kind of).
  • Outgoing links: The fewer the better, the one's with same pagerank and the with the least outgoing links will be the one that'll give you a better position on the index.
Page Rank Calculation: Well having all the incoming (and harmful links, if you will) will not just be bunged in the calculation. It's all cleverly calculated and preserved. See how a pagerank calculation works here. Mark Horrell has done enough work there so he deserves the credit too.

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op