

Now that we have settled the strategic differences between a multilingual site, “translated into several languages”, and a multi-country one, “designed to address different countries or regions”, we come to the technical and structural differences. As we said, a multilingual site, in other words a simply translated one, could have a simpler structure, both to develop and to manage, than a multi-country site. However, a multilingual site could also be the initial step towards a multi-country one, so the strategy to adopt needs to be assessed carefully, so as not to rule out any future path.
The most obvious case in which to use a multilingual site is that of a multilingual market: Switzerland, where German, French and Italian are spoken, or Canada, which has both English- and French-speaking users, but also some Italian border regions, where German and French are spoken as well as Italian. In all these examples, using a multilingual site is correct, but this does not mean that the website will be able to rank on search engines outside its own region. A multilingual site, in fact, is a site “replicated, translated” into several languages, customised to make the user experience complete, intuitive and pleasant, according to Google’s guidelines on optimising sites for user experience.
A multilingual site can be structured with a single domain name, e.g. example.com, and several subfolders containing the translations by language:
This type of site structure needs the “lang” attribute to be clearly stated in the source code, in order to correctly deliver the language code of each page to the web browser. It is also always better to add the “hreflang” tag, both in the site and in the XML sitemaps (this is in fact Google’s advice too), to suggest to the search engine that a given page has a version translated into another language.
For example, on my Italian page I will add this tag:
in this way I will tell the search engine that the page has a version translated into French; in this case hreflang="fr" indicates the language only (with no regional indication, as in the case of multi-country websites).
Note: in the examples we talked about folders (/en/, /fr/, /de/), not third-level domains (example: fr.example.com), but only because they are practically the same at a technical SEO level, and for Google today using one or the other makes no difference.
Practically the same: first of all, unlike a third-level domain, the translation’s subfolder “inherits” a number of characteristics, such as ranking and authority, from the starting site. Moreover, it is not certain that the folder is the best solution, or at least, that it will remain so in the future: if the site is and will remain multilingual, the folder structure is the best solution. If, on the other hand, the whole business could be internationalised in the future, then third-level domains (subdomains) could be the right compromise (again taking French as an example, fr.example.com). In this way, we will rank the site on foreign search engines and our products will compete with those of other local producers: this, however, is more of a multi-country solution.
One last important piece of advice in managing a multilingual site is not to automatically redirect users to the page that, according to cookies or browser language data, should correspond to their language. It is better, as Google’s guidelines also suggest, to give users the option of selecting their own language, and to allow them and search engines to view all versions of the site.
For any website needs, and to determine the right internationalisation strategy, remember that you can always ask for a consultation with the SEO experts at Aletur.it!