Forum Moderators: Robert Charlton & goodroi
Stop looking at [64.233.187.104...] aka [gfe-jc.google.com...] when you should be looking at [gfe-eh.google.com...] aka [72.14.207.104...] instead...
On the latter DC there is a big cleanup of older Supplemental Results in progress.
[edited by: tedster at 3:53 am (utc) on Aug. 18, 2006]
Just to say there is some movement on the Mother of The New Infrastructure 72.14.207.104
Please check your testing key-words / key-phrases and tell us whether you see any changes.
Thanks!
Suddenly, now, all but just one internal page are completely gone. Index page gone too. Hmmmmm. Not my site.
All other things I watch are fine.
.
Oh, I see what the problem is. The gfe-eh DC, which updated Supplemental Results about a month ago, has reverted back to an older index, the same as the index that has been showing on gfe-gv for several months before. The Supplemental update at gfe-eh has been reverted back to how it was back 3 or 4 months ago.
What is probably happening is that gfe-eh is offline while something is being changed, and so all calls to that DC are routed to some other DC for the moment. Maybe the real change will be seen in a few days time. At the moment we are just looking at the curtains, and can't yet see the man behind.
I think it's a reversion. Can't wait to see what Google trots out in the near future.
For a short while, and maybe several times in short succession over a period of days, Google reverts to much older data (presumably by temporarily routing queries to some other datacentres) while the "real index" is taken offline and updated in some way.
Not all datacentres are done at the same time, but within a week or so, ever newer data begins to show up on most of them.
I think this may have been happening for, perhaps, almost a year now.
<beating head with can of soda>
For a short while, and maybe several times in short succession over a period of days, Google reverts to much older data (presumably by temporarily routing queries to some other datacentres) while the "real index" is taken offline and updated in some way.Not all datacentres are done at the same time, but within a week or so, ever newer data begins to show up on most of them.
I've seen this happen much moire frequently and in much less time frame. For exmaple my homepage was cachced on the 18th yet today the index has reverted back to saying it was cached on the 12th. I've watched a couple times where they index new content for several days then revert back to data from 7-10 days ago. This usally last 1-2 days until they start indexing new content again.
i like the look of 72.14.207.104
do you still think this will spread, MC indicated things will settle towards the end of this month, so maybe we'll be seeing movement soon.
MC indicated things will settle towards the end of this month, so maybe we'll be seeing movement soon.
UK_Web_Guy, can you point me to this? Thanks...
In essence, if a page hasn’t changed since the last time we fetched it, there’s no need to fetch it again.
What I dont understand is how would google bot know if the file had changed or not until it had been fetched? .. or am I just missing something here.
Justin
I see more changes (or changes continue) on 72.14.207.---
Wouldn't call big changes. One can say its a kind of White Revolution.
Something like;
The King is Dead. Long Live The Queen! :-)
That sort of update sees Supplemental Results that represent URLs that have been redirected, or have been 404, for the last year getting deleted from the SERPs at long last.
It also sees new Supplemental Results being created for any URLs that have recently been turned into redirects, or have recently gone 404.
Those new Supplemental Results will now hang around for a year before being deleted. They are there to help people who looked at your site before you made those recent changes and who now what to see that information again.
Finally, a Supplemental Update sees new Supplemental Results being created for URLs that still return a "200 OK" when accessed, but these are for pages that have recently been edited.
If you search for current content associated with that URL then it will show as a normal result. If you search for stuff that was previously at that URL but which was removed from the page some time in the last few months then that same URL will rank, but this time it will be shown as a Supplemental Result.
The only Supplemental Results that you need to woory about, the only ones that you can actually "fix", are those that still return a "200 OK" and which represent live Duplicate Content. That Duplicate Content may take many forms including: www vs. non-www, multiple domains, differing URL parameters for the same content, http vs. https, URL CaPiTaLiSaTiOn {IIS only!}, "index" vs. "/", as well as the unique title/meta description problem, and so on.
There was a Supplemental Update a few weeks ago at gfe-eh and a few other datacentres. That was briefly reverted a few days ago. It was re-applied today. maybe it is now spreading to other datacentres, for wider visibility? (I haven't checked). The Supplemental update has not been seen at gfe-gv at all, yet.
reseler ,have you noticed that the "Queen" have been spread since 15/9 to 45 DC's out of 50?
Guess that is what GG said that will be discussed at the end of summer :)
Yes, I have noticed som propagations. GoogleGuy is a man of his words ;-)
There are only 41 Class-C [webmasterworld.com] IP blocks [webmasterworld.com] in use.
72.14.207.--- loves keywords stuffing.
When runnig one of my test keyphrases, I see #2 site is a big farm of keyphrase stuffing.
Congrats Matt Cutts & Co :-)
[edited by: tedster at 5:46 am (utc) on Sep. 24, 2006]
I have no idea why.
These are Supplemental Results returned for a search query for a word that is no longer on the page, and has not been there for nearly two years.
I need to check my records. It might be only 18 months. :-(
Checking my rank, I noticed that on one datacenter (216.239.51.104) I don't rank at all whereas all other datacenters rank me at #7.
Upon checking the location of this datacenter, most websites state that it's supposed to be non-active.
Is this correct? If it is, then why am I seeing this datacenter? The serps are totally rubbish ont this datacenter by the way.
