user interface - What are the best practices for multilanguage sites? -

I want to create a multi-language site, such as all or about all pages will be 2 Or is available in more translations.

For example, I consider these language selection mechanisms:

1. Cookie-based selection of the preferred language.
3. Otherwise (perhaps) based on GeoIP

Is anything

As LANG.example.com/page

In the form for example

with any of the above redirects on example.com/page ? (It seems)

To ensure that all translations are properly indexed?

1. Sitemap + correct content-language header with all pages are sufficient?

Users know that there are other translations, but what is the best way to not distract them?

2. Put the "Select language" selector next to the content

What is the best policy to deal with missing / outdated With translations?

1. Can not the missing pages be displayed at all or any page in a different language be displayed?
2. Display old translations, old translations with alerts or pages in a different language?

What else should I take into account? What should I do and what should I not do? In addition to @QuasnoNi's answer, make sure that you get the standard RFC 4646 language identifier (like N-US,

If the translation of a specific page is not available, then use the language fallback mechanism in neutral language; For example "DE-AT", "DE", "" (neutral, for example "EN").

Recent browsers and the built-in operating system will correctly display all the characters needed by the local selector. If the page is correctly encoded (I recommend all pages with UTF-8 ). Make sure that native and current-language names in the local list allow both original and non-native speakers to see the specified translation, e.g. "German (Germany)" If the current locale is EN- * .

Many sites use a flag icon to show the current site, but it is more relevant to this place and some people may be annoyed if you only show a flagship flag (e.g. Flags for US or UK UK).

This more visible (semi-graphical) locale selector home page If a local cookie has not been submitted, then the default locale option can be determined using a combination of GOIP and Accepta-language.

Semi-related: If your users are located in different time zones, then one area stores the timings value in their local time, with the priority of their account profiles and the timing of the help of UTC.