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

Post a Comment

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
Post a Comment
Read more

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...
Post a Comment
Read more