So, on webmasterfmradio, Matt says there are only 3 'live BD DC's....the original 2 plus 22.214.171.124
He thinks the switchover to all DC's for BD will be mid March....one a week from now on.
He says that redirect and canonical issues will be dealt with over the next few months.
Further feedback will be requested later this week.
Thanks. I am going to cut and paste that answer every time someone says "are we there yet?" in the next 6 weeks.
As I said the other day "Much better if we stick to the facts" ;-)
Thanks for the report on MCs radio coments. That helps us see the whole picture.
A bit confused why G DC had changed from 126.96.36.199 to 188.8.131.52?
Moreover, 184.108.40.206 shows redirecting site at first position for the query sf giants. But now the dc had changed to 220.127.116.11 which shows non-redirected site.
[edited by: engine at 8:20 am (utc) on Feb. 3, 2006]
"redirect and canonical issues will be dealt with over the next few months"
Months! its been months since Jagger when my problems started and many people have been waiting a lot longer.
What a pathetic admission by Google.
More emtpy promises I fear and excuses for an index that it failing in more and more ways each month....:(
A Fantastic Entry on Matt Cutt's blog on Big Daddy. After the last 2 months on anticipation, excitement and possibly dread for thousands of webmasters ... the following post was left.
January 30, 2006 @ 6:22 am
What the hell is Big Daddy.
Absolutely great and probably quite poignant ... lol ;-)
All the best for today
Breath of fresh air...:)
That was fun and might remind GG's that they keep us waiting for some time now.
While We Are Waiting for Allegra-II Update
Good morning Folks
Tough times waiting for us during the few coming days/weeks. And tough times require tough measures. For example purchasing large quantities of the Danish brand Cappuccino :-)
Lets have some facts about where to see BigDaddy at this moment (things are changing all the time) :-)
64.233.171.* (i.e [18.104.22.168...] etc..)
Wish you all a great sunny day.
I wonder if it is really big daddy on my local google.de. Results are almost the same as on the well known BD-DCs.
Results are ok for me there. But I doubt that this is already BD which should spread mid-may according to Matt.
Oh, and good morning reseller ;-) I just had one cup of espresso this morning. Cappuccino will follow soon.
Whish you all a pleasant day. And remember: tomorrow is Allegra's first anniversary.
>>Oh, and good morning reseller ;-) I just had one cup of espresso this morning. Cappuccino will follow soon.<<
Good morning to you too, taps. Yes more espresso and Cappuccino..please :-)
>>And remember: tomorrow is Allegra's first anniversary. <<
I know. It was the day where I lost 75% of Google's referrals (:(
Lets hope Allegra-II will be a nice guy and pays back what Allegra-I took away from us.
>>>>>He says that redirect and canonical issues will be dealt with over the next few months.
Heard that before. Hope so :).
The other day someone mentioned the xml query that brings up search results in an XML format with the tag <RK> which by looking on other forums and here is thought of the page rank tag.
It is intresting to know that the <RK> tag shows vastly different values in the BD dcs to the non-BD dcs for some sites.
If this is tag does show page rank - it does look like PR has been or is being recalculated for canonical/hijack problem sites but it does not look like the PR value has been applied to the serps (eg as mentioned no significant ranking update so far).
As it stands I dont think there is much to see until those internally recalculated values are applied to the serps.
For those that say PR does not mean anything - well often it means very little - but it does mean something when you are showing a PR0.
>>>Further feedback will be requested later this week.
Wonder if there will be further developments that require further feedback - as it is there is little more to say in feedback etc than there was at the last call.
>>For those that say PR does not mean anything - well often it means very little - but it does mean something when you are showing a PR0. <<
PR0 = problems
a new page/site
Soooooo. It could be that your old caninical-site has suddenly returned back to the index with a PR0 and as brand new and young as ever. Lucky you Dayo_UK :-)
Wish the same is possible for old people. You give them a Google PR0 and they retur back young and "productive" again :-)
Reseller & Others,
As reported by me yesterday and contrary to Matts radio broadcast there are actually twelve Big Daddy DC,s live that have been showing big daddy reesults for over 24 hours:
All of the above return giants.mlb.com/ in a sf giants search and are therefore definately Big Daddy.
I hope that more are now added on a daily basis.
Yes, BD is on more DC than MC says.
However, MC probably refers to DC by C-Class so :-
are just one DC C-Class.
You can rank with a PR0 on a new site - but not on an old - totally different kettle of fish. However on the BD DCs using the XML Query PR is back on some PR0 I have monitored.
I a have also noticed that cache dates on 22.214.171.124 (original BD DC) are different (newer and same as default)to all the other 11 BD DC's that have slightly older cache dates.
No idea why.
Agreed but that still 5 DC's by C block rather than 3!
[edited by: Ellio at 10:49 am (utc) on Feb. 1, 2006]
Yep and [126.96.36.199...] is not consitently BD - I think the cache dates you are seeing are not BD cache dates - do they match the other non-BD caches?
The current live DC on google.co.uk is fresher for my site than the bigdaddy sites.
Would google put the fresher data into bigdaddy before doing a full roll out?
|Yep and [188.8.131.52...] is not consitently BD - I think the cache dates you are seeing are not BD cache dates - do they match the other non-BD caches? |
Dayo, the cache i am seeing on 184.108.40.206 as its part of a result for a page of our site that only shows up on Big Daddy - so I am certain this Cache is in the big daddy index. Same search on other BD DC's returns the page in exactly the same place but with an older cache 15.12.06 instead of 28.12.06.
|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 220.127.116.11 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?
This non-BD baby displays a very fresh cache of my homepage; 29 Jan 2006 17:11:00 GMT.
exactly the same fresh cache as on BD datacenter
[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 18.104.22.168 = 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 22.214.171.124 definately shows a different cache date than the other Big Daddy DC's. This has been the same for 48 hours now 126.96.36.199 updated the cache but the other did not.
My point was that the cache date on 188.8.131.52 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.
Sorry did not mean to imply you were 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.
184.108.40.206 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.
By watching the Mozilla Googlebot/Normal Googlebot crawls.
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.
OK so we no that Big Daddy cache pages have different dates to the default index because they use a different crawl.
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]
>>>>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?
Yes, pretty sure on that.
Obviously they can get updated and they may spread to some DCs before the other - although that process is normally quick.
As that DC has the exact cache (even to the nearest minute/second) as the non-BD dc then it is not showing an update Mozilla Googlebot cache IMO but a Normal Googlebot cache.
Of course as time goes on things change and we may see a merge or something.
>>>We assumed new links and text changes were calculated at this point and used in the new serps?
Well to a degree in the past this was true - however there has always been underlying indexes etc - which means you can rank on words that no longer appear on the newly cached page etc. G1smd has a frustrating experience in this area.
BD is obviously a bit different - MC is saying no ranking changes for one - so it would not surprise me if the ranking structure of said pages is based on different data to what the Mozilla Googlebot/Big Daddy crawl has gathered aswell. EG Perhaps ranks are based on Normal Googlebot crawl.
Of course this is speculating a bit now.
[edited by: Dayo_UK at 11:54 am (utc) on Feb. 1, 2006]