You have no notifications.
Is it possible to have a domino's alias for a specific language in my channel, similar to what was available in xperience 13? So the default url language would be e.g. domain.com, but to display the French language it would be domain.fr?
No, Xperience by Kentico only supports language path prefix localization and there is no built-in way to limit requests to pages in specific languages for specific channels (except by not publishing those URLs).
You could use multiple website channels (one subdomain for each language) but you would still need the path prefix in the URL for each subdomain to retrieve the correct language culture.
That's a shame ... that seems really limiting if you're a global company with multiple languages/territories to cater for. Is this sometbing thst will be looked at in the future, as it prevents my company from moving onto XBK.
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:
~/pagefor English~/fr-fr/pagefor 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...
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.
Hi Sean,
If I could, I would like to extend onto this question as it seems relevant.
We are at the start of migrating a site from Kentico11 to Xperience by Kentico and in Kentico11 our URLs looked like this:
/name-of-venue (for nl-NL - Dutch. Our default culture. Served / enforced over www.our-domain.nl)
/en/name-of-venue-in-english (for en-GB - English. Our second culture. Served / enforced over www.our-domain.com)
/de/name-of-venue-in-german (for de-DE - German. Our second culture. Served / enforced over www.our-domain.de)
We placed these in the DocumentUrlPath part of the page.
While reading this entry on the roadmap from 2022 I would assume our scenario is supported:
'and configure their URLs to use human codes instead of just ..'. I would imagine I can set my 'human codes' to e.g. 'en' and that would pre-fix the slugs for my English pages with /en/. Alas.. I can't seem to find this feature.
Am I missing something perhaps? Or would we achieve this functionality? We don't want separate channels, we're serving 'the same site' simply translated into various languages, served over multiple domains.
Really looking forward to your reply, and thank you for any insights.
I think all the information you are looking for is in the documentation. I had difficulty typing the right terms in the search to get the result I knew was in the docs, but I then asked the AI chatbot which gave me the answer immediately 😉.
- For pages in a non-primary language, the language’s Code name is inserted into the URL path after the site’s root (‘/’).
- For example, if English is set as the primary language of the website channel, the URLs of pages in Spanish will be in the
~/es/pageformat.- Vanity URLs of pages in a non-primary language DO NOT include the language’s Code name.
To response this discussion, you have to login first.
