19th Common Wealth Games Website - Confusing Medals Tally - Bad Official Website CWG

I am totally confused on seeing the medals tally from homepage and Medals page of official Common wealth games website

If I try to right click and open the new page by clicking on the Homepage images it is saying page not found.

Please I request people who is taking care of it to set things right.

Medals tally is totally confusing – Update it at least once a day.

Home Page Medals Tally

Medals Page Tally

Who is incharge for updating the website. Even i can enter the details correctly and which will not make much time for updating in the website.

I think some lazy company with lazy employees handling this website may be Kalmadi relative?

Wtz ur opinion on this????????????????????????

Google – Master in search engines but duplicate Google Instant and developing strategy

Recently, if you might have visited google.com you might have found a change in the search result display which google themselves named it as Google Instant. Everyone, might think that google is very intelligent enough to showcase the results but the true fact it is just a copy from a another website named http://keyboardr.com/

Also, one important factor which might affect them is the Adwords. Google also informed that the clicks for adwords has decreased a lot. This is good for such a big search engine to showcase instant results but it is not that much creative from them to showcase it.

Even http://keyboardr.com/ is showing results from Google, but they where able to find out how to retrieve results so quickly from other google and other websites. I would really appreciate http://keyboardr.com/ instead of google.com instants.

Check out the snap shots of Google instants and http://keyboardr.com/

HTML Error Codes - From Google Webmaster Tools

Status codes that indicate a provisional response and require the requester to take action to continue.

100 (Continue)	The requestor should continue with the request. The server returns this code to indicate that it has received the first part of a request and is waiting for the rest.
101 (Switching protocols)	The requestor has asked the server to switch protocols and the server is acknowledging that it will do so.

2xx status codes

Status codes that indicate that the server successfully processed the request.

200 (Successful)	The server successfully processed the request. Generally, this means that the server provided the requested page. If you see this status for your robots.txt file, it means that Googlebot retrieved it successfully.
201 (Created)	The request was successful and the server created a new resource.
202 (Accepted)	The server has accepted the request, but hasn't yet processed it.
203 (Non-authoritative information)	The server successfully processed the request, but is returning information that may be from another source.
204 (No content)	The server successfully processed the request, but isn't returning any content.
205 (Reset content)	The server successfully proccessed the request, but isn't returning any content. Unlike a 204 response, this response requires that the requestor reset the document view (for instance, clear a form for new input).
206 (Partial content)	The server successfully processed a partial GET request.

3xx status codes

Further action is needed to fulfill the request. Often, these status codes are used for redirection. Google recommends that you use fewer than five redirects for each request. You can use Webmaster Tools to see if Googlebot is having trouble crawling your redirected pages. The Web crawl page under Diagnostics lists URLs that Googlebot was unable to crawl due to redirect errors.

300 (Multiple choices)	The server has several actions available based on the request. The server may choose an action based on the requestor (user agent) or the server may present a list so the requestor can choose an action.
301 (Moved permanently)	The requested page has been permanently moved to a new location. When the server returns this response (as a response to a GET or HEAD request), it automatically forwards the requestor to the new location. You should use this code to let Googlebot know that a page or site has permanently moved to a new location.
302 (Moved temporarily)	The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.
303 (See other location)	The server returns this code when the requestor should make a separate GET request to a different location to retrieve the response. For all requests other than a HEAD request, the server automatically forwards to the other location.
304 (Not modified)	The requested page hasn't been modified since the last request. When the server returns this response, it doesn't return the contents of the page. You should configure your server to return this response (called the If-Modified-Since HTTP header) when a page hasn't changed since the last time the requestor asked for it. This saves you bandwidth and overhead because your server can tell Googlebot that a page hasn't changed since the last time it was crawled.
305 (Use proxy)	The requestor can only access the requested page using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.
307 (Temporary redirect)	The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you shouldn't use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.

4xx status codes

These status codes indicate that there was likely an error in the request which prevented the server from being able to process it.

400 (Bad request)	The server didn't understand the syntax of the request.
401 (authentication error)	The page requires authentication. It's likely that you do not intend this page to be indexed. If this page is listed in your Sitemap, you can remove it. However, if you leave it in your Sitemap, we won't crawl or index it (although the page will continue to be listed here with this error).
403 (Forbidden)	The server is refusing the request. If you see that Googlebot received this status code when trying to crawl valid pages of your site (you can see this on the Web crawl page under Diagnostics in Google Webmaster Tools), it's possible that your server or host is blocking Googlebot's access.
404 (Not found)	The server can't find the requested page. For instance, the server often returns this code if the request is for a page that doesn't exist on the server. If you don't have a robots.txt file on your site and see this status on the robots.txt page of the Diagnostic tab in Google Webmaster Tools, this is the correct status. However, if you do have a robots.txt file and you see this status, then your robots.txt file may be named incorrectly or in the wrong location. (It should be at the top-level of the domain and named robots.txt.) If you see this status for URLs that Googlebot tried to crawl (on the HTTP errors page of the Diagnostic tab), then Googlebot likely followed an invalid link from another page (either an old link or a mistyped one).
405 (Method not allowed)	The method specified in the request is not allowed.
406 (Not acceptable)	The requested page can't respond with the content characteristics requested.
407 (Proxy authentication required)	This status code is similar to 401 but specifies that the requestor has to authenticate using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.
408 (Request timeout)	The server timed out waiting for the request.
409 (Conflict)	The server encountered a conflict fulfilling the request. The server must include information about the conflict in the response. The server might return this code in response to a PUT request that conflicts with an earlier request, along with a list of differences between the requests.
410 (Gone)	The server returns this response when the requested resource has been permanently removed. It is similar to a 404 (Not found) code, but is sometimes used in the place of a 404 for resources that used to exist but no longer do. If the resource has permanently moved, you should use a 301 to specify the resource's new location.
411 (Length required)	The server won't accept the request without a valid Content-Length header field.
412 (Precondition failed)	The server doesn't meet one of the preconditions that the requestor put on the request.
413 (Request entity too large)	The server can't process the request because it is too large for the server to handle.
414 (Requested URI is too long)	The requested URI (typically, a URL) is too long for the server to process.
415 (Unsupported media type)	The request is in a format not support by the requested page.
416 (Requested range not satisfiable)	The server returns this status code if the request is for a range not available for the page.
417 (Expectation failed)	The server can't meet the requirements of the Expect request-header field.

5xx status codes

These status codes indicate that the server had an internal error when trying to process the request. These errors tend to be with the server itself, not with the request.

500 (Internal server error)	The server encountered an error and can't fulfill the request.
501 (Not implemented)	The server doesn't have the functionality to fulfill the request. For instance, the server might return this code when it doesn't recognize the request method.
502 (Bad gateway)	The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503 (Service unavailable)	The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
504 (Gateway timeout)	The server was acting as a gateway or proxy and didn't receive a timely request from the upstream server.
505 (HTTP version not supported)	The server doesn't support the HTTP protocol version used in the request.

Google Crawling - My WebPage is 1 Trillion+1 Indexed

1,000,000,000,000+1 is my Web Page
1 Trillion Webpages + 1 is my webpage (MYGoogleOnline)
Just for Fun

Google 1 Trillion Web Pages in its Index - Still Crawling

Google vs Internet

We know that Internet is huge. Google started its index in 1998 by 26 million pages and by 2000 Google reached the index of around 1 billion. Over the past eight years Google have seen a lot of content and information in the web. Recently Google engineers was astonishing about the web in recent internet revolution, they proudly announces that Google systems over reached a milestone of 1 trillion (as in 1,000,000,000,000) unique URL's in its index

Google Crawling for Informations

Google engineers explain how they crawl the above mentioned dream number. They started indexing the URL's with some initial pages and then they start follow the links of each pages they indexed, then they followed the links from the new pages they indexed and so on. To be frank they have more than 1 trillion pages but they are not sure that all the pages are unique and have only one URL because some of the pages have two or more URL's. So we avoid all those URL's and pages and reached 1 trillion and we are indexing billions of unique pages and unique links every day.

Infinite Internet Web Pages

To be open minded, web is infinite so we can’t crawl all the pages but we will try our level best to crawl all the unique pages.

They also admit that all the trillion pages are not unique because in Google calendar everyday it will show up new pages but it will mostly have same content so we can't avoid such criteria. But they are very much proud that they have the most comprehensive index of any search engines, and their goal is to crawl all the world information’s and display to searchers.

Some of the important points from Googlers:

“To keep up with this volume of information, Google systems have come a long way since the first set of web data Google processed to answer queries. Back then, we did everything in batches: one workstation could compute the PageRank graph on 26 million pages in a couple of hours, and that set of pages would be used as Google's index for a fixed period of time. Today, Google downloads the web continuously, collecting updated page information and re-processing the entire web-link graph several times per day. This graph of one trillion URLs is similar to a map made up of one trillion intersections. So multiple times every day, we do the computational equivalent of fully exploring every intersection of every road in the United States. Except it'd be a map about 50,000 times as big as the U.S., with 50,000 times as many roads and intersections.
As you can see, our distributed infrastructure allows applications to efficiently traverse a link graph with many trillions of connections, or quickly sort petabytes of data, just to prepare to answer the most important question: your next Google search.”

From this we can come to a conclusion that Google the leader of all search engines and it will go on to search for more information and index trillions and zillions of pages in its system for answering to the customer queries.