Domain alias for language site

1. You can create separate website channels and use completely different domains for these channels. If you need to share content between them you can do this through the Content Hub. So, you aren't blocked as this is still an option.

   This might be the best approach if the content is completely different between the different localized sites.

   Just to clarify, if you want you can specify a different primary language for each website channel. This means your URLs would not need to be prefixed for each separate website channel catering a different language. But if English was the "default" (fallback) for all website channels for unlocalized content then you would have the language prefix for localized content across all of them.

   From the docs:

   • Primary language – a language configured in the Languages application. In multilingual content, the primary language is not displayed in URLs, as opposed to other languages. For example: If the primary language is set to English, and content is also in French, the URLs are in the format:
     • ~/page for English
     • ~/fr-fr/page for French

   So, if you had a subscription with 4 website channels you could use a separate domain (or subdomain) for each and configure a different primary language for each. There would still be a single default language for all non-channel (Content Hub) content, but you could get the experience you wanted out of your website channels.
   This does require that each website channel manages its own pages/tree/etc...

2. It's an SEO best practice to use paths to separate language variants of the same content for a website vs separate domains.

When considering how to design localization in Xperience by Kentico we received feedback from a large number of customers and partners. Their feedback led us to the solution we're using, so it's used effectively by global companies with multiple languages and territories.