0

We have a site that will be made available in different geographical zones and on different languages. We envision making them available in the following URL

+--------+-----------+-------------+------------------+------------------+
| Locale |  Country  |   Region    |     Language     |       URL        |
+--------+-----------+-------------+------------------+------------------+
| nb-NO  | Norway    | Scandinavia | Norwegian Bokmål | company.no/      |
| en-NO  | Norway    | Scandinavia | English, UK      | company.no/no/en |
| lt-LT  | Lithuania | Baltikum    | Lithuanian       | company.no/lt/lt |
| en-LT  | Lithuania | Baltikum    | English, UK      | company.no/lt/en |
| en-SE  | Sweden    | Scandinavia | English, UK      | company.no/se/en |
| en-DK  | Denmark   | Scandinavia | English, UK      | company.no/da/en |
+--------+-----------+-------------+------------------+------------------+

I observe a lot of different approaches, for instance Ikea:

Some companies mix the {location}/{language} with different domains per location. Some again use the whole locale as part of the URL, as HM:

Is there a best practice regarding this?

The question is somewhat related to URL structure for multi-language site but differs on whether to include full locale or not.

nitech
  • 1,822
  • 3
  • 21
  • 35
  • 1
    Combined language and region usually refers to the local variant of the language. For example, `en-GB` means "British English language, any region", not "American English language, UK region". If the language and region are independent variables, it would make sense to use the `/se/sv/`, `/se/en/` approach. – VLL Jun 14 '23 at 12:16

0 Answers0