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]
MC is probably talking about C-classes so 3 vs 8.
I would have thought that MC is talking about DCs which maybe are more consitently showing BD - but there is no doubt that there are more than the three he named at this time.
>>reseler
[66.102.9.99...]
[66.102.9.104...]
[66.102.11.99...]
[66.102.11.104...]
those are not BD DC's<<
I know, my friend ;-)
IMO, we shouldn't focus only about changes on BD DCs.
I would have thought that MC is talking about DCs which maybe are more consitently showing BD - but there is no doubt that there are more than the three he named at this time.
Although MC maybe talking about C Blocks it is the individual DC's that are on the rotation so the total number (18) really does matter in increasing the chances of getting a BD DC to supply your serps.
Again my opinion only.
Mozilla Googlebot directs regular Googlebot/2.1
Last Updated: 2005-04-04 01:07:09We have been watching the Mozilla Googlebot "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" for some time now. It appears that this bot is a sort of pre-sorting mechanism for the older Googlebot "Googlebot/2.1 (+http://www.google.com/bot.html)"
To us, this makes sense. Spidering the web is a very complex task and highly server-intensive. Why not send out a simplier bot (Mozilla Googlebot) that can visit sites and determine how to schedule the main bot (Googlebot/2.1). We believe that the Mozilla Googlebot is something of a datebook and calculator for the real Googlebot. The Mozilla Googlebot can also used to do the job of the Googlebot for less important spider visits (e.g. supplemental results).
In essence, the Mozilla Googlebot seems to be a filter to help Googlebot around the billions of pages on the web.
On a side note, including the name "Mozilla" in the user agent would support this hypothesis. Having the word Mozilla in the user agent would help to find poorly cloaked pages where it is popular as an easy cloaking solution to use Mozilla in the user agent. This would thus filter out content that Googlebot would not then need to visit.
Interesting...
No links Insert
<Sorry, no personal URLs.
See Terms of Service [webmasterworld.com]>
[edited by: tedster at 2:22 am (utc) on Feb. 4, 2006]
Maybe to an extent if you are comparing PR2 to P5 or PR1 to PR2 but when you get a PR0 it is slightly different.
Ellio
Cant think of anything more to say about BD until something else happens.
With ref to that quote re Mozilla Googlebot - that might be out of date now - Mozilla Googlebot became more heriachal in its crawling activity (as in what you might expect from a normal Gbot) just before BD appeared.
But who knows - it might be building the framework and then when G are happy normal Googlebot will follow the path lead by Mozilla Googlebot.
The following DCs showing only one cached page of my site that is Home Page.
66.102.9.99
66.102.9.104
66.102.11.99
66.102.11.104
216.239.59.104
While following DCs showing 30 cached pages..
[216.239.51.104...]
[216.239.51.99...]
What do i conclude.. DCs starting from (66) hve BD applied on them?
I think that is a common factor for a few of us.
Some new sites internal pages only exist in BD DCs at the moment.
The ones you listed showing only 1 page are not BD Dcs.
Matt has stated several times that BigDaddy is a switching over to a new infrastructure. If that is the case, then BigDaddy should be considered as an update, according to Matt own definition:
What’s an update? September 8, 2005 @
[mattcutts.com...]
"Usually, what registers with an update to the webmaster community is when we update an algorithm (or its data), change our scoring algorithms, or switch over to a new piece of infrastructure."
Thoughts?
"But this is neither an update nor a data refresh; this is new infrastructure. It should be much more subtle/gentle than an update."
can't get clearer than that, but then:
"Usually, what registers with an update to the webmaster community is when we update an algorithm (or its data), change our scoring algorithms, or switch over to a new piece of infrastructure."
It is clear that he is not clear!
However I believe that first statement was simply making it clear that this change was not related to algo updates like Florida, Bourbon, Jagger etc.
Hi Folks
Some of us have expected an update around 2nd Feb 2006. What you are looking at today is the update underway in the shape of BigDaddy migrating to the rest of DCs.
For the first time in Google's history, we have had the privilege to watch step-by-step Google engineers working on an update. Fantastic!
And Matt has actually been posting weather reports about the progress of Update BigDaddy!
And now you know why I'm a Matt fanboy. Inigo is smart...very smart :-)
One with homepages fixed and reapearing and the other with old hijacked/bugged results.
Ok now I want a PR update, let's keep it fun afterall :)
I think that the PR toolbar is being flaky for the past 6 months.
Do you guys think that GG will add the BL and PR update to the current infrastructure change?
--Dooooh!
Priority is moving to larger sites with multiple city pages and multiple city subdomains.
Seems G believes that sites that list companies are more important than the companies themselves on general terms.
The big question remains as to why all of the sudden there are 35 million results when a few weeks ago there were only 10 million.
Did G accidentally misplace 25 million pages?
:)
With my test phrase, I've been ranking around 120, but I just checked (based on seeing an increase in traffic from Google) and I'm sitting at number 25. It's the start of the weekend, perhaps an up**** is starting.
Anyone else seeing big movement?
I do like this update!