Google は各ページについて主となる言語を判断しようとします。言語を認識されやすくするには、ページごとに使用する言語を統一し、原文と訳文を一緒に表示することは避けるようにしてください。1 ページで複数の言語を認識することもできますが、ページ内のすべての要素(ヘッダー、サイドバー、メニューなど)には同じ言語を使用することをおすすめします。
Google は「lang」属性からドキュメント タイプ定義(DTD)まで、コードレベルの言語情報をすべて無視します。一部のウェブ編集プログラムではこれらの属性が自動的に作成されるため、ウェブページの言語を判断する際にこうした情報はあまり信頼できません。
自身の言語を使って Google で検索を行うユーザーは、ローカライズされた検索結果が表示されることを期待しています。そのためウェブマスターは、ローカライズを行う場合、それが検索結果に表示されるようにする必要があります。以下にそのためのヒントをいくつか紹介します。
[[["わかりやすい","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"]],[],[[["\u003cp\u003eMultilingual websites cater to audiences speaking different languages, increasing reach and engagement.\u003c/p\u003e\n"],["\u003cp\u003eGoogle encourages using one language per page for easier language recognition, aiding in localized search results.\u003c/p\u003e\n"],["\u003cp\u003eStructure URLs to indicate language for user clarity and efficient indexing of multilingual content.\u003c/p\u003e\n"],["\u003cp\u003eEnsure all language versions are easily crawlable by Googlebot through cross-linking between corresponding pages.\u003c/p\u003e\n"],["\u003cp\u003eUse UTF-8 encoding for website content and maintain consistency to avoid conflicting character encoding information.\u003c/p\u003e\n"]]],["Multilingual websites should have one language per page, avoiding side-by-side translations. URL structures should indicate the language (e.g., /en/, /fr/) using UTF-8 encoding for non-English characters. Cross-linking between language versions of pages is recommended, and automated translations should be avoided. Prevent automatic user language redirections and maintain separate URLs for each language's content, not using cookies for translations. Finally, utilize UTF-8 character encoding across your website.\n"],null,["# Working with multilingual websites\n\n| It'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). Check out our [current documentation on managing multi-lingual sites](/search/docs/specialty/international).\n\nFriday, March 19, 2010\n\n\nA multilingual website is any website that offers content in more than one language. Examples of\nmultilingual websites might include a Canadian business with an English and a French version of\nits site, or a blog on Latin American soccer available in both Spanish and Portuguese.\n\n\n**Usually, it makes sense to have a multilingual website when your target audience consists of\nspeakers of different languages.** If your blog on Latin American soccer aims to reach the\nBrazilian audience, you may choose to publish it only in Portuguese. But if you'd like to reach\nsoccer fans from Argentina also, then providing content in Spanish could help you with that.\n\nGoogle and language recognition\n-------------------------------\n\n\nGoogle tries to determine the main languages of each one of your pages. **You can help to make\nlanguage recognition easier if you stick to only one language per page and avoid side-by-side\ntranslations.** Although Google can recognize a page as being in more than one language, we\nrecommend using the same language for all elements of a page: headers, sidebars, menus, etc.\n\n\nKeep in mind that Google ignores all code-level language information, from \"lang\" attributes to\nDocument Type Definitions (DTD). Some web editing programs create these attributes automatically,\nand therefore they aren't very reliable when trying to determine the language of a webpage.\n\n\nSomeone who comes to Google and does a search in their language expects to find localized search\nresults, and this is where you, as a webmaster, come in: **if you're going to localize, make it\nvisible in the search results** with some of our tips below.\n\nThe anatomy of a multilingual site: URL structure\n-------------------------------------------------\n\n\nThere's no need to create special URLs when developing a multilingual website. Nonetheless, your\nusers might like to identify what section of your website they're on just by glancing at the URL.\nFor example, the following URLs let users know that they're on the English section of this site:\n`https://example.ca`**/en/**`mountain-bikes.html` or\n`https://`**en.**`example.ca/mountain-bikes.html`. While these other URLs let users\nknow that they're viewing the same page in French:\n`https://example.ca/`**fr**`/mountain-bikes.html` or\n`https://`**fr**`.example.ca/mountain-bikes.html`. Additionally, this URL structure\nwill make it easier for you to analyze the indexing of your multilingual content.\n\n\nIf you want to create URLs with non-English characters, make sure to use UTF-8 encoding. UTF-8\nencoded URLs should be properly escaped when linked from within your content. Should you need to\nescape your URLs manually, you can easily find an\n[online URL encoder](https://www.google.com/search?q=url+encoder)\nthat will do this for you. For example, if I wanted to translate the following URL from English to\nFrench, `https://example.ca/fr/`**mountain-bikes**`.html`, it might look something like\nthis: `https://example.ca/fr/`**vélo-de-montagne**`.html`. Since this URL contains one\nnon-English character (é), this is what it would look like properly escaped for use in a link on\nyour pages: `https://example.ca/fr/v`**%C3%A9**`lo-de-montagne.html`.\n\nCrawling and indexing your multilingual website\n-----------------------------------------------\n\n\nWe recommend that you do not allow automated translations to get indexed. Automated translations\ndon't always make sense and they could potentially be viewed as spam. More importantly, the point\nof making a multilingual website is to reach a larger audience by providing valuable content in\nseveral languages. If your users can't understand an automated translation or if it feels\nartificial to them, you should ask yourself whether you really want to present this kind of\ncontent to them.\n\n\nIf you're going to localize, make it easy for Googlebot to crawl all language versions of your\nsite. Consider cross-linking page by page. In other words, you can provide links between pages\nwith the same content in different languages. This can also be very helpful to your users.\nFollowing our previous example, let's suppose that a French speaker happens to land on\n`https://example.ca/en/mountain-bikes.html`; now, with one click they can get to\n`https://example.ca/fr/vélo-de-montagne.html` where they can view the same content in\nFrench.\n\n\nTo make all of your site's content more crawlable, avoid automatic redirections based on the\nuser's perceived language. These redirections could prevent users (and search engines) from\nviewing all the versions of your site.\n\n\nAnd last but not least, keep the content for each language on separate URLs---don't use\ncookies to show translated versions.\n\nWorking with character encodings\n--------------------------------\n\n\nGoogle directly extracts character encodings from HTTP headers, HTML page headers, and content.\nThere isn't much you need to do about character encoding, other than watching out for conflicting\ninformation - for example, between content and headers. While Google can recognize different\ncharacter encodings, we recommend that you use UTF-8 on your website whenever possible.\n\nIf your tongue gets twisted...\n------------------------------\n\n\nNow that you know all of this, your tongue may get twisted when you speak many languages, but your\nwebsite doesn't have to!\n\n\nFor more information, read our\n[post on multi-regional sites](/search/blog/2010/03/working-with-multi-regional-websites)\nand stay tuned for our next post, where we'll delve into special situations that may arise when\nworking with global websites. Until then, don't hesitate to drop by the Help Forum and\n[join the discussion](https://support.google.com/webmasters/community/thread?tid=12a5507889c20461)!\n\nWritten by Xavier deMorales, Google Search Quality"]]