Wednesday, September 30, 2009
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.
Friday, September 25, 2009
We generate these deep links completely algorithmically, based on page structure, so they could be displayed for any site (and of course money isn't involved in any way, so you can't pay to get these links). There are a few things you can do to increase the chances that they might appear on your pages. First, ensure that long, multi-topic pages on your site are well-structured and broken into distinct logical sections. Second, ensure that each section has an associated anchor with a descriptive name (i.e., not just "Section 2.1"), and that your page includes a "table of contents" which links to the individual anchors. The new in-snippet links only appear for relevant queries, so you won't see it on the results all the time — only when we think that a link to a section would be highly useful for a particular query.
Posted by Raj Krishnan, Snippets Team
Monday, September 21, 2009
Posted by Matt Cutts, Search Quality Team
Thursday, September 17, 2009
original post and if you want to participate fill out the form as soon as possible, because we will only be selecting 3-5 websites from the first 200 submitted for this Site Clinic, so don't miss out!
Posted by Esperanza, Search Quality Team
Tuesday, September 15, 2009
Last month, I gave a talk at the Search Engine Strategies San Jose conference on Duplicate Content and Multiple Site Issues. For those who couldn't make it to the conference or would like a recap, we've reproduced the talk on the Google Webmaster Central YouTube Channel. Below you can see the short video reproduced from the content at SES:
You can view the slides here:
Posted by Greg Grothaus, Search Quality Team
Monday, September 14, 2009
Most of the recommendations we've made in the past are for individual webmasters running their own websites. We thought we'd offer up some best practices for websites that allow users to create their own websites or host users' data, like Blogger or Google Sites. This class of websites is often referred to as freehosts, although these recommendations apply to certain "non-free" providers as well.
- Make sure your users can verify their website in website management suites such as Google's Webmaster Tools.
Webmaster Tools provides your users with detailed reports about their website's visibility in Google. Before we can grant your users access, we need to verify that they own their particular websites. Verifying ownership of a site in Webmaster Tools can be done using a custom HTML file, a meta tag, or seamless integration in your system via Google Services for Websites. Other website management suites such as Yahoo! Site Explorer and Bing Webmaster Tools may use similar verification methods; we recommend making sure your users can access each of these suites.
- Choose a unique directory or hostname for each user.
Webmaster Tools verifies websites based on a single URL, but assumes that users should be able to see data for all URLs 'beneath' this URL in the site URL hierarchy. See our article on verifying subdomains and subdirectories for more information. Beyond Webmaster Tools, many automated systems on the web--such as search engines or aggregators--expect websites to be structured in this way, and by doing so you'll be making it easier for those systems to find and organize your content.
- Set useful and descriptive page titles.
Let users set their own titles, or automatically set the pages on your users' websites to be descriptive of the content on that page. For example, all of the user page titles should not be "Blogger: Create your free blog". Similarly, if a user's website has more than one page with different content, they should not all have the same title: "User XYZ's Homepage".
- Allow the addition of tags to a page.
Certain meta tags are reasonably useful for search engines and users may want to control them. These include tags with the name attribute of "robots", "description", "googlebot", "slurp", or "msnbot". Click on the specific name attributes to learn more about what these tags do.
- Allow your users to use third-party analytics packages such as Google Analytics.
- Help your users move around.
Tastes change. Someone on your service might want to change their account name or even move to another site altogether. Help them by allowing them to access their own data and by letting them tell search engines when they move part or all of their site via the use of 301 redirect destinations. Similarly, if users want to remove a page/site instead of moving it, please return a 404 HTTP response code so that search engines will know that the page/site is no longer around. This allows users to use the urgent URL removal tool (if necessary), and makes sure that these pages drop out of search results as soon as possible.
- Help search engines find the good content from your users.
Search engines continue to crawl more and more of the web. Help our crawlers find the best content across your site. Allow us to crawl users' content, including media like user-uploaded images. Help us find users' content using XML Sitemaps. Help us to steer clear of duplicate versions of the same content so we can find more of the good stuff your users are creating by creating only one URL for each piece of content when possible, and by specifying your canonical URLs when not. If you're hosting blogs, create RSS feeds that we can discover in Google Blog Search. If your site is down or showing errors, please return 5xx response codes. This helps us avoid indexing lots of "We'll be right back" pages by letting crawlers know that the content is temporarily unavailable.
Posted by Greg Grothaus, Staff Software Engineer, Search Quality Team
<meta name="title" content="Baroo? - cute puppies" />RDFa (Yahoo! SearchMonkey):
<meta name="description" content="The cutest canine head tilts on the Internet!" />
<link rel="image_src" href="http://example.com/thumbnail_preview.jpg" />
<link rel="video_src" href="http://example.com/video_object.swf?id=12345"/>
<meta name="video_height" content="296" />
<meta name="video_width" content="512" />
<meta name="video_type" content="application/x-shockwave-flash" />
<object width="512" height="296" rel="media:video"
<param name="movie" value="http://example.com/video_object.swf?id=12345" />
type="application/x-shockwave-flash" width="512" height="296"></embed>
<a rel="media:thumbnail" href="http://example.com/thumbnail_preview.jpg" />
<a rel="dc:license" href="http://example.com/terms_of_service.html" />
<span property="dc:description" content="Cute Overload defines Baroo? as: Dogspeak for 'Whut the...?'
Frequently accompanied by the Canine Tilt and/or wrinkled brow for enhanced effect." />
<span property="media:title" content="Baroo? - cute puppies" />
<span property="media:width" content="512" />
<span property="media:height" content="296" />
<span property="media:type" content="application/x-shockwave-flash" />
<span property="media:region" content="us" />
<span property="media:region" content="uk" />
<span property="media:duration" content="63" />
Tuesday, September 1, 2009
During my stint on the "How Google Works Tour: Seattle", I heard plenty of questions regarding News Search from esteemed members of the press, such as The Stranger, The Seattle Times and Seattle Weekly. After careful note-taking throughout our conversations, the News team and I compiled this presentation to provide background and FAQs for all publishers interested in Google News Search.
Along with the FAQs about News Sitemaps and PageRank in the video above, here's additional Q&A to get you started:
Would adding a city name to my paper—for example, changing our name from "The Times" to "The San Francisco Bay Area Times"—help me target my local audience in News Search?
No, this won't help News rankings. We extract geography and location information from the article itself (see video). Changing your name to include relevant keywords or adding a local address in your footer won't help you target a specific audience in our News rankings.What happens if I accidentally include URLs in my News Sitemap that are older than 72 hours?
We want only the most recently added URLs in your News Sitemap, as it directs Googlebot to your breaking information. If you include older URLs, no worries (there's no penalty unless you're perceived as maliciously spamming -- this case would be rare, so again, no worries); we just won't include those URLs in our next News crawl.To get the full scoop, check out the video!
Written by Maile Ohye, Developer Programs Tech Lead
Filmed by Michael Wyszomierski, Search Quality Team