To see this in motion, let\u2019s have a look at an example. The website instance.com has content material that ambitions users around the globe as follows:<\/p>\n
![\"Map](\"http:\/\/2.bp.blogspot.com\/-0HF8bizWvKs\/UWR4VUvb-dI\/AAAAAAAAAFc\/LBkTiir9CJU\/s1600\/map-us-gb-au-flattened.png\")
<\/div>\n- \n
- http:\/\/example.com\/en-gb<\/a>: For English-talking users in the UK<\/li>\n
- http:\/\/instance.com\/en-us<\/a>: For English-conversing users in the US<\/li>\n
- http:\/\/example.com\/en-au<\/a>: For English-speaking customers in Australia<\/li>\n
- http:\/\/instance.com\/<\/a>: The homepage shows customers a country selector and is the default web page for customers international<\/li>\n<\/ul>\n
On this case, the webmaster can annotate this cluster of pages the use of rel-alternate-hreflang<\/a> using Sitemaps<\/a> or the use of HTML hyperlink tags like this:<\/p>\n
<link rel="alternate" href="http:\/\/instance.com\/en-gb" hreflang="en-gb" \/>
<link rel="alternate" href="http:\/\/instance.com\/en-us" hreflang="en-us" \/>
<hyperlink rel="alternate" href="http:\/\/example.com\/en-au" hreflang="en-au" \/>
<link rel="alternate" href="http:\/\/instance.com\/" hreflang="x-default" \/>
<\/code>
<\/pre>\nThe new x-default hreflang attribute worth<\/strong> signals to our algorithms that this page doesn\u2019t goal any particular language or locale and is the default web page when no different web page is healthier desirable. For example, it will be the page our algorithms attempt to express French-speaking searchers international or English-conversing searchers on google.ca.<\/p>\n
The same annotation applies for homepages that dynamically alter their contents according to a user\u2019s perceived geolocation or the Accept-Language headers. The x-default hreflang value alerts to our algorithms that this sort of page doesn\u2019t target a selected language or locale.<\/p>\n
As all the time, if you have any questions or feedback, please tell us in the Internationalization Webmaster Assist Forum<\/a>.<\/p>\n
Posted by way of Pierre Far<\/a>, Webmaster Developments Analyst<\/span><\/p>\n
\n<\/img><\/a>\n<\/div>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Webmaster Level: All<\/p>\n
The homepages of multinational and multilingual websites are sometimes configured to point visitors to localized pages, either via redirects or by changing the content to reflect the user’s language. Today we’ll introduce a new rel-alternate-hreflang annotation that the webmaster can use to specify such homepages that is supported by both Google and Yandex<\/a>.<\/p>\n
To see this in action, let’s look at an example. The website example.com has content that targets users around the world as follows:<\/p>\n
<\/div>\n- \n
- \nhttp:\/\/example.com\/en-gb<\/a>: For English-speaking users in the UK<\/li>\n
- \nhttp:\/\/example.com\/en-us<\/a>: For English-speaking users in the USA<\/li>\n
- \nhttp:\/\/example.com\/en-au<\/a>: For English-speaking users in Australia<\/li>\n
- \nhttp:\/\/example.com\/<\/a>: The homepage shows users a country selector and is the default page for users worldwide<\/li>\n<\/ul>\n
In this case, the webmaster can annotate this cluster of pages using rel-alternate-hreflang<\/a> using Sitemaps<\/a> or using HTML link tags like this:<\/p>\n
<link rel=\"alternate\" href=\"http:\/\/example.com\/en-gb\" hreflang=\"en-gb\" \/>
<link rel=\"alternate\" href=\"http:\/\/example.com\/en-us\" hreflang=\"en-us\" \/>
<link rel=\"alternate\" href=\"http:\/\/example.com\/en-au\" hreflang=\"en-au\" \/>
<link rel=\"alternate\" href=\"http:\/\/example.com\/\" hreflang=\"x-default\" \/>
<\/code>
<\/pre>\nThe new x-default hreflang attribute value<\/strong> signals to our algorithms that this page doesn’t target any specific language or locale and is the default page when no other page is better suited. For example, it would be the page our algorithms try to show French-speaking searchers worldwide or English-speaking searchers on google.ca.<\/p>\n
The same annotation applies for homepages that dynamically alter their contents based on a user’s perceived geolocation or the Accept-Language headers. The x-default hreflang value signals to our algorithms that such a page doesn’t target a specific language or locale.<\/p>\n
As always, if you have any questions or feedback, please tell us in the Internationalization Webmaster Help Forum<\/a>.<\/p>\n
Posted by Pierre Far<\/a>, Webmaster Trends Analyst<\/span><\/p>\n
- \nhttp:\/\/example.com\/en-us<\/a>: For English-speaking users in the USA<\/li>\n
- http:\/\/instance.com\/en-us<\/a>: For English-conversing users in the US<\/li>\n