Manage content languages

Content languages belong to each site. They control the visitor-facing text you write in Convor: widget copy, pre-chat fields, triggers, chatbot content, knowledge-base articles, automation messages, CSAT copy, and other localized content.

They are separate from the language of the Convor dashboard and from Convor's built-in widget interface.

Start with DefaultCopy Anchor Link

A new site starts with one version called Default.

Default has no language attached to it. Write your content normally in whichever language you use. If the site needs only one language, you can leave it this way permanently.

With one content version, editors show normal fields only. There is no language switcher or extra translation workflow.

Add another languageCopy Anchor Link

Open Settings → Languages & localization and choose Add language.

Enlarge

Search by language name or code, then save the settings. If the language is not in the suggested list, enter a valid BCP 47 tag such as es-MX or pt-BR.

Adding a language does not rename or delete Default. For example, you can use:

• Default + Polish
• Default + German
• Default + Spanish (Mexico)

Once more than one active version exists, localized editors show a language selector.

Name your existing Default contentCopy Anchor Link

Sometimes the text already stored under Default is clearly written in one language.

For example, you may have an English-only site today and want to add German. In Settings → Languages & localization, select English and choose Set language for Default.

Convor keeps the existing content and labels that version as English. You can then add German. The result is:

• English
• German

There is no additional empty Default version.

Use Add language instead when you want to keep the neutral Default version and create an additional translation.

Choose the fallbackCopy Anchor Link

After Default has a language and you have multiple active languages, you can choose which one is the default.

The default is used when Convor cannot match the visitor to another configured language.

When several languages are active, you can also choose how visitor language is resolved:

• Detect automatically uses the locale requested by the widget or detected from the page/browser when it matches an enabled content language.
• Always use the default language ignores those signals and keeps the site's default content language.

With only one active content version, this choice is unnecessary and the control stays hidden.

Edit translated contentCopy Anchor Link

You do not need to translate every feature just because you added a language.

Open the feature you want to edit and switch between the active language versions there. Existing versions stay intact when you edit another language.

The default version remains the fallback. Additional translations can be prepared independently and published when the feature supports draft/published states.

Disable a languageCopy Anchor Link

You can disable an additional language without deleting its saved content. Re-enabling it restores the existing version.

The default language and the last active language cannot be disabled. Convor can also prevent disabling a language while active conversations still depend on it.

Widget language and content language are separateCopy Anchor Link

Your content-language list does not install or remove Convor's built-in widget translations.

Convor ships the widget interface catalogs separately. A visitor can still receive your Spanish, German, or other configured content even when the built-in widget controls use a fallback interface catalog.

For multilingual single-page applications, use Convor.setLocale(locale) when the application language changes without a full navigation.

Related guidesCopy Anchor Link

• Customize the widget before you publish
• Build a knowledge base people can use
• Use canned responses consistently
• Widget JavaScript API