RSS-based PageRank™ Monitoring Tool

[pneuma]

Stało się, mozemy już korzystać dowolnie z checksum PR:

Short Version:

Recent revelations have made it very easy to determine the checksum necessary to request a URL's PageRank from Google. Some people, for commercial, egoistical or other reasons, are interested in knowing when the PR of certain URLs changes. As a result, I've whipped up pagerank2rss.pl, a simple Perl script that outputs (in the RSS format) the PR of a list of URLs. Simply drop it in your web server's cgi-bin directory and point your aggregator at it. To change the URLs that it monitors, open it up in a text editor, and modify the %pageRankURLs hash with the URL and its checksum, as computed with the help of this site.

Long Version:

It is argued that Google's PageRank is dead. Though that debate is still unsettled (and will continue to be so, unless Google states outright that they are discontinuing it), one PageRank-related thing is in fact dead. Until recently, the only way to get a site's PageRank was to use the Google Toolbar, which relied on a private "channel" to find out the information from Google's servers. This appears to consist of a private URL to which one can pass as arguments, a URL and its checksum, and in return receive that page's rank.

Lately, this (obfuscated) barrier has been dented, with the advent of Prog (née Proogle) and the attempted auction of the (reverse-engineered) algorithm on eBay. This culminated today in the public domain distribution of an implementaion.

What Google will do about this (if anything - Prog has been up and running for a while, and the eBay auction was not stopped, though thankfully no one was clueless enough to bid either) remains to be seen. Regardless, in the meantime there are a few interesting things than can be done with this bit of information. The first that came to my mind was a simple script that monitors the PR of URLs and reports the results as an RSS feed. Hooked up to an aggregator, it's now possible to see when an URL's rank changes. Presumably this is old news to SEO-types that already have similar tools for doing this, but it may be useful to those that need their egos stroked on a regular basis.

The net result is pagerank2rss.pl, a Perl script that can be dropped in a web server's cgi-bin directory. It relies on curl, since that's available by default on Mac OS X, but with a few tweaks it could be made to use wget or LWP. The list of URLs to monitor is stored in the %pageRankURLs hash, along with their computed checksums (using this handy web interface). It is obvious that this is a 20-minute quick and dirty script - I could've computed the checksums myself and the list of URLs could be made accessible via a friendlier web interface. However, given the limbo-ish status of the methods that it uses, I figured it would not have been worth it to spend more time on something that might go away soon.

Hammers

https://persistent.info/archives/2004/06/27...27/pagerank2rss

#!/usr/bin/perl -w



use strict;



my %pageRankURLs = ('https://persistent.info/' => '61576108155',

   	'https://www.mscape.com/' => '6155344674',

   	'https://www.google.com/' => '64222138902');



my $kRequestURLTemplate = 'https://www.google.com/search?client=navclient-auto&ch=%s&features=Rank&q=info:%s';



print <<HEADER;

Content-type: text/xml



<?xml version="1.0" ?>

<!-- RSS generated by pagerank2rss 1.0 -->

<rss version="2.0">

<channel>

 <title>PageRank™ Monitor</title>

 <link>https://www.google.com/</link>

 <ttl>30</ttl>

HEADER



foreach my $pageRankURL (keys %pageRankURLs)

{

my $pageRankRequestURL = sprintf($kRequestURLTemplate, $pageRankURLs{$pageRankURL}, $pageRankURL);

open(CURL, "curl -s "$pageRankRequestURL"|") or die("can't launch curl");



my $pageRank = 'Not found';



while (<CURL>)

{

 chomp;

 

 $pageRank = $1 if (/Rank_1:d+:(d+)/); # the first set of numbers is how many digits there are in the pagerank

}



close(CURL);



print "<item><title>$pageRankURL: $pageRank</title></item>n";

}



print <<FOOTER;

</channel>

</rss>

FOOTER

osoby które sprzedawaly cheksum są baaaardzo niezadowolone:

OK, you don't want to pay anything. So here's another deal: could you place

a link to www.airport1.de to any or several of your sites with pagerank 6

for 6 months? I think this is a fair deal. Textlink or banner.

I was a little bit shocked that someone published the algorithm to public. I

had much effort to do the script code, and now nobody wants to pay anything

for what cost me days and hours

MfG,

  Airport1 (Marc Bufe)

--

https://www.airport1.de  -> Your Airport One <-

[Kil Bill]

No i dobrze i tak było wiadomo że PR nie jest zbyt ważny przy pozycjonowaniu pojawiają sie nowe filtry w Googlach

Pozdrawiam

[pneuma]

Masz rację ale dopiero teraz Google podało informację że zmienia algorytm oceniania stron przy wyswietlaniu reklam, jest to zapewne związane z powyższym.

Google Alters AdWords; Sharpens Relevancy Matching

Google sent an e-mail to AdWords advertisers today announcing an algorithmic change to the matching of ads and keywords. For now, the change affects only broad-matched keywords associated with AdWords ads displayed on Google.com, but Google promises the improved relevance will ultimately affect other matching options and other portions of the advertising network. Characteristically, Google is not divulging specifics. But it is clear that broad matching will no longer be as broad. Although Google expresses a somewhat defensive tone in the e-mail and related FAQ, the truth is that this change should be good news for advertisers, especially those who rely on broad matching to eliminate the work of fine-tuning keyword. Here is the example Google uses—

”For example, an advertiser specializing in Alaskan cruises may have selected cruises (broad-matched) for their campaign. Previously, this keyword may have been disabled due to poor performance on more popular queries such as Hawaiian cruises. Instead of disabling all broad match variations of cruises, we will now show this ad for specific query variations that are more relevant to the ad, such as Alaskan cruises.”

The big question is HOW—how will Google determine niched relevancy in an ad? Is the change really algorithmic as I stated above, or will human resources be used to evaluate ads? (The second possibility is far less likely than the first.)

One implication seems clear: Google is de-emphasizing broad matching in favor of exact matching. This is a change long-awaited by careful advertisers who would rather eat glass than throw a broad match into their carefully regulated campaigns. The benefit for advertisers who continue to use broad-matching is that entire keyword sets (determined by a broad match) will not necessarily be disabled due to poor clickthrough rates. If the keywords are matched more intelligently to start with, the chances of poor performance are lessened. Is it possible that Google is using this after-the-fact determination to refine the matching relevancy? Nobody outside Google knows, but some posters at WebmasterWorld are already seeing changes in ad positioning.

sem.weblogsinc.com/entry/5450225134623213/

oprócz tego google rozpoczęło cahceować stron wylącznie w formie tekstowe bez obrazków -

Oto kopia strony https://www.forum.optymalizacja.com/ zrobiona przez G o o g l e.

Kopia G o o g l e to obraz strony jaki znaleźliśmy przy ostatnim przeszukiwaniu Sieci.

Z upływem czasu strona mogła się zmienić. Tutaj znajduje się aktualna wersja strony.

Kopia może zawierać odwołania do obrazów, które nie są już dostępne. Kliknij tutaj, aby otworzyć kopię tekstową strony.

Aby utworzyć łącze lub zakładkę do tej strony, użyj następującego adresu url: https://www.google.com/search?q=cache:sEe73...cja.com/+&hl=pl 

czyli kopia tekstowa wygląda tak

zmienia to trochę problem ukrytegi tekstu - bo teraz widac prawie wszystko!

[melassa]

czyzby to oznaczalo ze rozwiaja w innym kierunku niz teraz wyszukiwanie grafiki ??

moze zastosuja nowe mechanizmy lub tez zupelnie sie z tego wycofaja ??