Welcome to WebmasterWorld Guest from 220.127.116.11
# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 18.104.22.168 rhino.acme.com # source server
# 22.214.171.124 x.acme.com # x client host
When a new export occurs, that is the most recent data you can see, and it may only be a couple weeks old. And then it continues to age until the next update - usually in about 3 more months.
The present time value for PR is continually updated privately by Google and folded into your ranking calculations all along. But the toolbar report shows this historical snapshot that begins at a few weeks old when first exported, and then ages for however many months go by until the next export.
I've just checked my old-established PR5 site on 20 data centres.
About 70% are showing PR5, and 30% showing PR0.
This site has been PR5+ for years - and I can't see any reason it would be penalised.
Not sure if this means we're on the verge of a penalty of some sort, or if it's just an artifact of the update.
Rankings are fine.
I can't find any other sites with such inconsistent results across data centres.
Anybody got any ideas what it might mean?