Utilizing Google Translator within your WebPage

0

Posted by Pradeep | Posted in | Posted on 12:47 AM

Expand your audience globally




How long would it take to translate all the world's web content into 50 languages? Even if all of the translators in the world worked around the clock, with the current growth rate of content being created online and the sheer amount of data on the web, it would take hundreds of years to make even a small dent.

Today, we're happy to announce a new website translator gadget powered by Google Translate that enables you to make your site's content available in 51 languages. Now, when people visit your page, if their language (as determined by their browser settings) is different than the language of your page, they'll be prompted to automatically translate the page into their own language. If the visitor's language is the same as the language of your page, no translation banner will appear.


After clicking the Translate button, the automatic translations are shown directly on your page.


It's easy to install — all you have to do is cut and paste a short snippet into your webpage to increase the global reach of your blog or website.


Automatic translation is convenient and helps people get a quick gist of the page. However, it's not a perfect substitute for the art of professional translation. Today happens to be International Translation Day, and we'd like to take the opportunity to celebrate the contributions of translators all over the world. These translators play an essential role in enabling global communication, and with the rapid growth and ease of access to digital content, the need for them is greater than ever. We hope that professional translators, along with translation tools such as Google Translator Toolkit and this Translate gadget, will continue to help make the world's content more accessible to everyone.

An Improved Local Information in web search

0

Posted by Pradeep | Posted in | Posted on 12:45 AM

Quick, in-browser viewing of Google Docs



We've incorporated the "Gview" tool from Google Docs on search results. Instead of the old "View as HTML" view, PDFs on search results now have a "Quick View" link that shows you Gview's image-rendered version, which preserves tables and graphics from the document. This means you can view PDF documents quickly and easily right in your browser.
Example search: [1099] (note the "Quick view" links on the first two results)

An improved interface for local information in web search
We changed our interface for local business information when it occurs in search results. It's now much more readable (larger fonts) and friendlier to use (easier to click on just what you want).Example search: [pizza palo alto]

Here are before and after shots for the search [bakeries san francisco]:

Click on either image for a larger version

Access to multiple providers in weather results
We also changed the interface for our weather results when they occur in web search. Now you'll see an array of different weather providers to choose from, including The Weather Channel, Weatherunderground and AccuWeather, if you want more detailed weather information. This way, you get the weather information you need, in the layout you prefer, from the service you choose.
Example search: [washington dc weather]

And here are before and after shots for the search [weather] (when done from the Googleplex, since the location is auto-detected):

Click on either image for a larger version

Public service information for searches related to poison control
While it's relatively infrequent, people do occasionally turn to Google during medical emergencies. Our goal in these cases is to get our users the help they need as quickly as possible. As of this week, searches related to [poison control] trigger a special result with the phone number for the poison control hotline.
Example searches: [poison control], [first aid bleach poisoning]

Search options panel for mobile
This week on mobile search, we added a Search Options panel so now you can get all of the same slice-and-dice functionality you have from your desktop when you search the web on your phone. Try doing a search from your phone and you will see an "Options" link on the righthand side above the results. Click on it and you see the same panel that you are accustomed to on search from your desktop.

Crawling AJAX
We also made an exciting announcement this week about making AJAX crawlable. Web applications are becoming increasingly popular, but much of what is contained with a web application is usually inaccessible to our crawlers and thus can't be found in our search. Our team has been busy working on techniques for how to crawl AJAX. This announcement just represents the start, as it's currently in the prototype phase, but it does demonstrate that we are constantly working on how to improve search — our features, ranking, and, in this case, our comprehensiveness. We're always very excited to include new content in our search to make our results even better.

Solution For Crawling AJAX WebPages

0

Posted by Pradeep | Posted in | Posted on 12:40 AM

A proposal for making AJAX crawlable

Today we're excited to propose a new standard for making AJAX-based websites crawlable. This will benefit webmasters and users by making content from rich and interactive AJAX-based websites universally accessible through search results on any search engine that chooses to take part. We believe that making this content available for crawling and indexing could significantly improve the web.

While AJAX-based websites are popular with users, search engines traditionally are not able to access any of the content on them. The last time we checked, almost 70% of the websites we know about use JavaScript in some form or another. Of course, most of that JavaScript is not AJAX, but the better that search engines could crawl and index AJAX, the more that developers could add richer features to their websites and still show up in search engines.

Some of the goals that we wanted to achieve with this proposal were:
  • Minimal changes are required as the website grows

  • Users and search engines see the same content (no cloaking)

  • Search engines can send users directly to the AJAX URL (not to a static copy)

  • Site owners have a way of verifying that their AJAX website is rendered correctly and thus that the crawler has access to all the content


Here's how search engines would crawl and index AJAX in our initial proposal:
  • Slightly modify the URL fragments for stateful AJAX pages
    Stateful AJAX pages display the same content whenever accessed directly. These are pages that could be referred to in search results. Instead of a URL like http://example.com/page?query#state we would like to propose adding a token to make it possible to recognize these URLs: http://example.com/page?query#[FRAGMENTTOKEN]state . Based on a review of current URLs on the web, we propose using "!" (an exclamation point) as the token for this. The proposed URL that could be shown in search results would then be: http://example.com/page?query#!state.

  • Use a headless browser that outputs an HTML snapshot on your web server
    The headless browser is used to access the AJAX page and generates HTML code based on the final state in the browser. Only specially tagged URLs are passed to the headless browser for processing. By doing this on the server side, the website owner is in control of the HTML code that is generated and can easily verify that all JavaScript is executed correctly. An example of such a browser is HtmlUnit, an open-sourced "GUI-less browser for Java programs.

  • Allow search engine crawlers to access these URLs by escaping the state
    As URL fragments are never sent with requests to servers, it's necessary to slightly modify the URL used to access the page. At the same time, this tells the server to use the headless browser to generate HTML code instead of returning a page with JavaScript. Other, existing URLs - such as those used by the user - would be processed normally, bypassing the headless browser. We propose escaping the state information and adding it to the query parameters with a token. Using the previous example, one such URL would be http://example.com/page?query&[QUERYTOKEN]=state . Based on our analysis of current URLs on the web, we propose using "_escaped_fragment_" as the token. The proposed URL would then become http://example.com/page?query&_escaped_fragment_=state .

  • Show the original URL to users in the search results
    To improve the user experience, it makes sense to refer users directly to the AJAX-based pages. This can be achieved by showing the original URL (such as http://example.com/page?query#!state from our example above) in the search results. Search engines can check that the indexable text returned to Googlebot is the same or a subset of the text that is returned to users.



(Graphic by Katharina Probst)

In summary, starting with a stateful URL such as
http://example.com/dictionary.html#AJAX , it could be available to both crawlers and users as
http://example.com/dictionary.html#!AJAX which could be crawled as
http://example.com/dictionary.html?_escaped_fragment_=AJAX which in turn would be shown to users and accessed as
http://example.com/dictionary.html#!AJAX

View the presentation

We're currently working on a proposal and a prototype implementation. Feedback is very welcome — please add your comments below or in our Webmaster Help Forum. Thank you for your interest in making the AJAX-based web accessible and useful through search engines!