[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2011-12-01 UTC。"],[[["\u003cp\u003eGoogle is enhancing its support for multilingual and multi-regional websites to better serve diverse users with appropriate content.\u003c/p\u003e\n"],["\u003cp\u003eWebsite owners can use the \u003ccode\u003erel="alternate" hreflang\u003c/code\u003e link element to specify language and regional variations of their content for better search engine understanding.\u003c/p\u003e\n"],["\u003cp\u003eAnnotations should be implemented on a per-URL basis, indicating specific URLs for each language and region variation.\u003c/p\u003e\n"],["\u003cp\u003eFor additional support and guidance on implementing these features, refer to the Google Help Center article and the Webmaster Help Forum.\u003c/p\u003e\n"]]],["Websites can use the `rel=\"alternate\" hreflang` link element to specify language and regional variations of their content. This allows for targeting users with appropriate versions, whether it's content in different languages or the same language with regional differences, such as pricing. The `hreflang` attribute defines the language and, optionally, the region. Alternate URLs can be on the same site or different domains, allowing for signal consolidation and better search result presentation. Using the mentioned markup is done on a per-URL basis.\n"],null,["# New markup for multilingual content\n\nMonday, December 05, 2011\n\n\nMany websites serve users from around the world. There are different approaches to serving content\nappropriate to your users' language and/or region. Last year, we launched support for\n[explicit annotations](/search/blog/2010/09/unifying-content-under-multilingual)\nfor web pages rendering the same content with different language templates.\n\n\nToday we're going further with our support for multilingual content with improved handling for\nthese two scenarios:\n\n- Multiregional websites using substantially the same content. Example: English webpages for Australia, Canada and USA, differing only in price\n- Multiregional websites using fully translated content, or substantially different monolingual content targeting different regions. Example: a product webpage in German, English and French\n\nSpecifying language and location\n--------------------------------\n\n\nWe've expanded our support of the\n[`rel=\"alternate\" hreflang link` element](/search/docs/specialty/international/localized-versions)\nto handle content that is translated or provided for multiple geographic regions. The\n`hreflang` attribute can specify the language, optionally the country, and URLs of\nequivalent content. By specifying these alternate URLs, our goal is to be able to consolidate\nsignals for these pages, and to serve the appropriate URL to users in search. Alternative URLs\ncan be on the same site or on another domain.\n\nAnnotating pages as substantially similar content\n-------------------------------------------------\n\n\n~~Optionally, for pages that have substantially the same content in the same language and are\ntargeted at multiple countries, you may use the\n[`rel=\"canonical\"` `link` element](/search/docs/crawling-indexing/consolidate-duplicate-urls)\nto specify your preferred version. We'll use that signal to focus on that version in search,\nwhile showing the local URLs to users where appropriate. For example, you could use this if you\nhave the same product page in German, but want to target it separately to users searching on the\nGoogle properties for Germany, Austria, and Switzerland.~~ \n\n**Update:** to simplify implementation, we no longer recommend using\n`rel=\"canonical\"`.\n\nExample usage\n-------------\n\nTo explain how it works, let's look at some example URLs:\n\n- https://www.example.com/ - contains the general home page of a website, in Spanish\n- https://es-es.example.com/ - is the version for users in Spain, in Spanish\n- https://es-mx.example.com/ - is the version for users in Mexico, in Spanish\n- https://en.example.com/ - is the generic English language version\n\n\nOn all of these pages, we could use the following markup to specify language and optionally the\nregion: \n\n```\n\u003clink rel=\"alternate\" hreflang=\"es\" href=\"https://www.example.com/\" /\u003e\n\u003clink rel=\"alternate\" hreflang=\"es-ES\" href=\"https://es-es.example.com/\" /\u003e\n\u003clink rel=\"alternate\" hreflang=\"es-MX\" href=\"https://es-mx.example.com/\" /\u003e\n\u003clink rel=\"alternate\" hreflang=\"en\" href=\"https://en.example.com/\" /\u003e\n```\n\nIf you specify a regional subtag, we'll assume that you want to target that region.\n\n\nKeep in mind that all of these annotations are to be used on a **per-URL basis**. You should\ntake care to use the specific URL, not the home page, for both of these link elements.\n\nMore help\n---------\n\n\nAs always, if you need more help correctly implementing multiregional and multilingual websites,\nplease see our\n[Help Center article](/search/docs/specialty/international/localized-versions)\nabout this topic, or ask in our\n[Webmaster Help Forum](https://support.google.com/webmasters/community).\n\n\nWritten by\n[Christopher Semturs](https://plus.google.com/114874451484944689517/about),\nSoftware Engineer, Search Infrastructure, Google Switzerland"]]
