One site, many languages: how Convor picks what visitors see

A visitor who opens chat on the French version of your site should not land in an English support flow just because their browser happens to be set differently. Convor starts with the locale supplied by the site or widget, then compares it with the content languages enabled for that site. That choice becomes the widget's current content language.

Start with the languages your site supports

For each site in Convor, you choose which content languages are enabled and which one is the default. The default language must stay enabled. It is the safe destination when none of the visitor's locale candidates match a language you have configured.

How the widget learns the visitor's locale

The widget checks four sources, from most explicit to least explicit:

• a locale set directly through the widget SDK
• the data-locale value on the embed script
• the lang value declared by the page's html element
• the visitor's browser language

If your application already has a language switcher, the most reliable option is to pass that selection to the widget. On a conventional multilingual website, a correct page language declaration is usually enough. Browser language is only the fallback when the widget and page have not supplied a locale.

Exact match, parent language, then default

Convor first tries the full locale. If Canadian French is requested and that exact variant is enabled, it wins. If it is not available, Convor tries the parent language, French in this example. When neither variant is enabled, the site's default content language is used. The same rule also applies when a locale is invalid or no usable locale reaches the resolver.

Content language and widget interface are different

The resolved content locale is used for visitor-facing material that your team can localize, including greetings, offline and consent text, pre-chat fields, department names, automation or chatbot copy, and Knowledge Base content. On surfaces with publish states, Convor resolves among published variants and can fall back through the requested language chain before using the site's default.

Convor's own widget controls are separate. The built-in interface currently has Polish and English catalogs. A Polish content locale uses the Polish interface; other locales use the English interface while your localized customer content can still remain in its resolved language. This keeps product UI translation separate from the content you manage.

Language detection does not translate your content

Convor selects from variants that already exist; it does not generate a missing translation while choosing a locale. If you want a visitor to receive a German greeting or a German Knowledge Base article, publish that German variant. Locale detection decides which version to request, not what the translation should say.

Keep the page locale accurate and enable the content languages you actually maintain. Then choose a default you are comfortable showing when nothing else matches. The support flow can follow the language context your site has already established instead of asking the visitor again.