{"id":24753,"date":"2013-04-10T00:00:00","date_gmt":"2013-04-10T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/introducing-x-default-hreflang-for-international-landing-pages\/"},"modified":"2013-04-10T00:00:00","modified_gmt":"2013-04-10T00:00:00","slug":"introducing-x-default-hreflang-for-international-landing-pages","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/introducing-x-default-hreflang-for-international-landing-pages\/","title":{"rendered":"Introducing &#8220;x-default hreflang&#8221; for international landing pages"},"content":{"rendered":"<aside class=\"key-point\">It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). Read the up-to-date <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/localized-versions\/\">documentation about localization<\/a>.<\/aside>\n<p class=\"gargardate\">Wednesday, April 10, 2013<\/p>\n<p>\n  The home pages of multinational and multilingual websites are sometimes configured to point visitors<br \/>\n  to localized pages, either via redirects or by changing the content to reflect the user&#8217;s<br \/>\n  language. Today we&#8217;ll introduce a new <code>rel-alternate-hreflang<\/code> annotation that you can<br \/>\n  use to specify such home pages that is supported by both Google and<br \/>\n  <a href=\"https:\/\/webmaster.ya.ru\/replies.xml?item_no=15326\" class=\"external-link\">Yandex<\/a>.\n<\/p>\n<p>\n  To see this in action, let&#8217;s look at an example. The website example.com has content that targets<br \/>\n  users around the world as follows:\n<\/p>\n<div class=\"separator\">\n  <img decoding=\"async\" alt=\"Map of the world illustrating which hreflang code to use for which locale\"\n       src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-d60796d52a20.png\" loading=\"lazy\" \/>\n<\/div>\n<ul>\n<li><code>https:\/\/example.com\/en-gb<\/code>: For English-speaking users in the UK<\/li>\n<li><code>https:\/\/example.com\/en-us<\/code>: For English-speaking users in the USA<\/li>\n<li><code>https:\/\/example.com\/en-au<\/code>: For English-speaking users in Australia<\/li>\n<li>\n    <code>https:\/\/example.com\/<\/code>: The home page shows users a country selector and is the<br \/>\n    default page for users worldwide\n  <\/li>\n<\/ul>\n<p>\n  In this case, you can annotate this cluster of pages using<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/localized-versions\/\"><code>rel-alternate-hreflang<\/code><\/a><br \/>\n  using <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/sitemaps-overview\/\">sitemaps<\/a> or using HTML<br \/>\n  <code>link<\/code> tags like this:\n<\/p>\n<div><\/div>\n<p>\n  The new <strong><code>x-default<\/code> <code>hreflang<\/code> attribute value<\/strong> signals to<br \/>\n  our algorithms that this page doesn&#8217;t target any specific language or locale and is the default<br \/>\n  page when no other page is better suited. For example, it would be the page our algorithms try to<br \/>\n  show French-speaking searchers worldwide or English-speaking searchers on google.ca.\n<\/p>\n<p>\n  The same annotation applies for home pages that dynamically alter their contents based on a user&#8217;s<br \/>\n  perceived geolocation or the <code>Accept-Language<\/code> headers. The <code>x-default<\/code><br \/>\n  <code>hreflang<\/code> value signals to our algorithms that such a page doesn&#8217;t target a specific<br \/>\n  language or locale.\n<\/p>\n<p>\n  As always, if you have any questions or feedback, please tell us in the<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/community\/\" class=\"external-link\">Internationalization Webmaster Help Forum<\/a>.\n<\/p>\n<p class=\"byline-author\">\n  Posted by<br \/>\n  <a href=\"https:\/\/developers.google.com\/search\/blog\/authors\/pierre-far\" class=\"external-link\">Pierre Far<\/a>,<br \/>\n  Webmaster Trends Analyst<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). Read the up-to-date documentation about localization. Wednesday, April 10, 2013 The home pages of multinational and multilingual websites are sometimes configured to point visitors [&hellip;]<\/p>\n","protected":false},"menu_order":84195,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24753","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24753","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24753\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/26981"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24753"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24753"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24753"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}