Google "Bigdaddy" Datacenter update !!!



Google has announced a major update that will affect the ranking of web pages in Google's index. In contrast to the usual algorithm updates, this update will be much bigger because it changes the way Google works behind the scenes. Google has given the update the name "Bigdaddy".

Bigdaddy is now visible at two data centers: 66.249.93.104 and 64.233.179.104.*The upcoming Bigdaddy update is not an algorithm update but a change in Google's data center infrastructure.* Reason for the new data center infrastructure is that Google wants to be able to index different content types. Google is now testing a new search engine spider that is based on the Mozilla browser.The new spider should be able to index more than traditional search engine spiders, possibly links within images, JavaScripts or Flash files.According to Google's search engineer Matt Cutts, the update will be live in February or March :)

visit : http://www.mattcutts.com/blog/bigdaddy/and http://www.searchenginegenie.com/seo-blog/2006/01/review-on-new-google-update-big-daddy.html

In addition to 66.249.93.104 and 64.233.179.104, Bigdaddy is now up at 216.239.51.104.

* * * Ravi * * *

1 comments:

Chris said...
Wednesday, February 15, 2006 5:47:00 PM

Apart from the “Big Daddy” data center new code for examining the web, it focuses mainly on two issues namely “ Canonicalization” and “302 redirects”

Canonicalization is the process that determines how various equivalent forms of a name are resolved to a single standard name. The single standard name is also known as the canonical name. For example, on a specific computer, the names c:\dir\test.dat, test.dat, and ..\..\test.dat might all refer to the same file. Canonicalization is the process that maps such names to a name that is similar to c:\dir\test.dat.

When a URL is received by a Web server, the server maps the request to a file system path that determines the response. The canonicalization routine that is used to map the request must correctly parse the URL to avoid serving or processing unexpected content. For more information about canonicalization, visit the following Microsoft Web site:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/THCMCh04.asp

The above information is taken from http://support.microsoft.com/?kbid=887459

An explanation of the page hijack exploit using 302 server redirects. This exploit allows any webmaster to have his own "virtual pages" rank for terms that pages belonging to another webmaster used to rank for. Successfully employed, this technique will allow the offending webmaster ("the hijacker") to displace the pages of the "target" in the Search Engine Results Pages ("SERPS"), and hence (a) cause search engine traffic to the target website to vanish, and/or (b) further redirect traffic to any other page of choice.

For more information visit
http://clsc.net/research/google-302-page-hijack.htm