Forum Moderators: Robert Charlton & goodroi
This is just odd.
The 64.* DC's return about 300 pages from my site.
The 216.* DC's return about 46,000 pages from my site.
And the 66.* return 69,000 pages from my site.
Currently I have about 65,000 pages.
If I go to google.co.uk I get 46,000 pages. If I go to google.com from my US based server I get the same 46,000 results.
It is all very odd and confusing.
[edited by: tedster at 9:56 pm (utc) on Jan. 30, 2006]
The current live DC on google.co.uk is fresher for my site than the bigdaddy sites.
That's the point I was making but 66.249.93.104 is returning big Daddy results AND newer caches.
This is interesting in my opinion.
I am definetly see non-BD cache dates on that DC.
Go to a non-BD dc and type cache:yourpage.com/ngkerkg.html - do you get the same cache date as that DC?
[72.14.207.104...]
exactly the same fresh cache as on BD datacenter
[66.249.93.104...]
[edited by: reseller at 11:20 am (utc) on Feb. 1, 2006]
Let me try to re-explain.
Search for our keyword non big daddy DC = Knowhere
Search for our keyword on any big daddy DC = No.6
No6 Result on BD 66.249.93.104 = cache date 28.1.06
No.6 Result on BD other 11 DCs = cache date 15.1.06
Cache date for this page for other terms on default non BD = cache date 28.1.06
I cannot be clearer than that!
The Big Daddy result on 66.249.93.104 definately shows a different cache date than the other Big Daddy DC's. This has been the same for 48 hours now 66.249.93.104 updated the cache but the other did not.
My point was that the cache date on 66.249.93.104 is the same as default (28.1.06)WHEN delivery Big Daddy results. While the other BD DC.,s have the 15.1.06 cache date.
You will have to trust me that I understand Big Daddy, DC's and their workings and am really not getting confused.
It is just that the serp results and cache results are not matching on all DCs.
EG on the DC in question you are seeing Big Daddy/Mozilla Googlebot crawl results without the cache from Mozilla Googlebot - it is just using the default cache.
Mozilla Googlebot crawl in general = Big Daddy Results.
Normal Googlebot crawl = Other results.
You are just seeing the normal Googlebot crawls cache on that DC - but the serps are still showing Mozilla Googlebot results. In some circumstances it results in no cache being displayed as the page has not been crawled by normal Googlebot.
That DC has acted this way before and other DCs are acting the other way around - eg Cache is from Mozilla Googlebot, results seem to be from normal Googlebot crawl - it resulted in a spate of posts of wrong cache, missing cache etc a while back.
Yes, as my above post.
66.249.93.104 is not using cache from Mozilla Googlebot. But the serps are still as at Mozilla Googlebot crawl.
EG on the DC in question you are seeing Big Daddy/Mozilla Googlebot crawl results without the cache from Mozilla Googlebot - it is just using the default cache.
If am interested in how you know this is the case and not simply a seperate caching by that Big Daddy index alone?
If the answer is obvious I apologise in advance.
I have a whole site only cached by Mozilla Googlebot - the serps have not changed for this site on the DC - but as normal Googlebot has not crawled this site all the cache links go to a non cache found page.
As I know these pages have only been crawled by Mozilla Googlebot I know exactly which DCs are using Mozilla Googlebot crawl as cache - I posted this a few days back.
Although they are using Mozilla Googlebot crawl data as cache not all of them are showing BD results yet.
It seems the serps data and the cache data dont have to match with each other.
Do the individual BD DC's cache pages with a seperate crawl or do they use a common Mozilla Googlebot crawl to cache pages for all Big Daddy index DC's?
If the answer is common then I understand your previous answer - thanks.
It seems the serps data and the cache data dont have to match with each other.
This is odd as our serps normally change when the cache is updated.
We assumed new links and text changes were calculated at this point and used in the new serps? (MSN even claim that results are based on cached pages)
[edited by: Ellio at 11:49 am (utc) on Feb. 1, 2006]
