If you’re a publisher based outside of the US, and you’ve been waiting to put +1 buttons on your site, now’s a good time to get started. Visit the +1 button tool on Google Webmaster Central where the +1 button is already available in 44 languages.

Adding the +1 button could help your site to stand out by putting personal recommendations right at the moment of decision, on Google search. So if you have users who are fans of your content, encourage them to add their voice with +1!

Host: www.example.com
(...rest of HTTP request headers...)
HTTP/1.1 200 OK
Content-Type: application/pdf
Link: <http://www.example.com/white-paper.html>; rel="canonical"
Content-Length: 785710
(... rest of HTTP response headers...)
Another common situation in which rel="canonical" HTTP headers may help is when a website serves the same file from multiple URLs (for example when using a content distribution network) and the webmaster wishes to signal to Google the preferred URL.
We currently support these link header elements for web search only. As we see how webmasters are using these elements, we're hoping to add support for them in our other properties. For more information, please see our Help Center articles about canonicalization and the rel="canonical" element. If you have any questions, please ask in our Webmaster Help Forum.
Share on Twitter Share on Facebook

Share on Twitter Share on Facebook



At Google we're obsessed with speed. We've seen time and time again how an increase in apparent speed leads to a direct increase in user happiness and engagement. Instant Pages helps visitors arrive at your site faster. When we trigger Instant Pages for your site, users can start interacting with your site almost immediately, without having to wait for text and images to load. We'll only trigger Instant Pages when we have very high confidence that your site is the exact result users are looking for. Search traffic will be measured in Webmaster Tools just like before this feature, with only results the user visited counted. We'll take the time this summer before the feature launches in stable versions of Chrome to collect your feedback.

The vast majority of sites will automatically work correctly when prerendered in Chrome. Check out the prerendering post on the Chromium blog if you want to learn more about how prerendering works in Chrome or how you can detect that your site is being prerendered.

Share on Twitter Share on Facebook

Share on Twitter Share on Facebook


To enable these Search Engine Optimization reports, you should sign up for the pilot and you must be both a Webmaster Tools verified site owner and a Google Analytics administrator. Each additional user who would like to view them also needs to individually sign up for the pilot.

Share on Twitter Share on Facebook


Adoption by the webmaster community has grown rapidly, and today we’re able to show rich snippets in search results more than ten times as often as when we started two years ago.

We want to continue making the open web richer and more useful. We know that it takes time and effort to add this markup to your pages, and adding markup is much harder if every search engine asks for data in a different way. That’s why we’ve come together with other search engines to support a common set of schemas, just as we came together to support a common standard for Sitemaps in 2006. With schema.org, site owners can improve how their sites appear in search results not only on Google, but on Bing, Yahoo! and potentially other search engines as well in the future.

Now let’s discuss some of the details of schema.org relevant to you as a webmaster:

1) Schema.org contains a lot of new markup types.
We’ve added more than 100 new types as well as ported over all of the existing rich snippets types. If you’ve looked at adding rich snippets markup before but none of the existing types were relevant for your site, it’s worth taking another look. Here are a few popular types:
Or, view a full list of all schema.org types. The new markup types may be used for future rich snippets formats as well as other types of improvements to help people find your content more easily when searching.

2) Schema.org uses microdata.
Historically, we’ve supported three different standards for structured data markup: microdata, microformats, and RDFa. We’ve decided to focus on just one format for schema.org to create a simpler story for webmasters and to improve consistency across search engines relying on the data. There are arguments to be made for preferring any of the existing standards, but we’ve found that microdata strikes a balance between the extensibility of RDFa and the simplicity of microformats, so this is the format that we’ve gone with.

To get an overview of microdata as well as the conventions followed by schema.org, take a look at the schema.org Getting Started guide.

3) We’ll continue to support our existing rich snippets markup formats.
If you’ve already done markup on your pages using microformats or RDFa, we’ll continue to support it. One caveat to watch out for: while it’s OK to use the new schema.org markup or continue to use existing microformats or RDFa markup, you should avoid mixing the formats together on the same web page, as this can confuse our parsers.

4) Test your markup using the rich snippets testing tool.
It’s very useful to test your web pages with markup to make sure we’re able to parse the data correctly. As with previous rich snippets markup formats, you should use the rich snippets testing tool for this purpose. Note that while the testing tool will show the marked up information that was parsed from the page, rich snippets previews are not yet shown for schema.org markup. We’ll be adding this functionality soon.

The schema.org website and the rich snippets testing tool are in English. However, Google shows rich snippets in search results globally, so there’s no need to wait to start marking up your pages.

To learn more about rich snippets and how they relate to schema.org, check out the Rich snippets schema.org FAQ.

Share on Twitter Share on Facebook


You'll also start to see +1 buttons on other Google properties such as Android Market, Blogger, Product Search and YouTube.

Adding +1 buttons to your pages is a great way to help your content stand out in Google search. By giving your visitors more chances to +1 your pages, your search results and search ads could show up with +1 annotations more often, helping users see when your pages are most likely to be useful.


To get started, visit the +1 button tool on Google Webmaster Central. You’ll be able to configure a small snippet of JavaScript and add it to the pages where you want +1 buttons to appear. You can pick from a few different button sizes and styles, so choose the +1 button that best matches your site’s layout.


In the common case, a press of the button +1’s the URL of the page it’s on. We recommend some easy ways to ensure this maps as often as possible to the pages appearing in Google search results.

If your site primarily caters to users outside of the US and Canada, you can install the +1 button code now; the +1 button is already supported in 44 languages. However, keep in mind that +1 annotations currently only appear for English search results on Google.com. We’re working on releasing +1 to searchers worldwide in the future.

If you have users who love your content (and we bet you do), encourage them to spread the word! Add the +1 button to help your site stand out with a personal recommendation right at the moment of decision, on Google search.

To stay current on updates to the +1 button large and small, please subscribe to the Google Publisher Buttons Announce Group. For advanced tips and tricks, check our Google Code site. Finally, if you have any questions about using the +1 button on your websites, feel free to drop by the Webmaster Help Forum.

Share on Twitter Share on Facebook