Translate articles into other languages

1. Add the languages you want to write in

Before you can translate anything, the knowledge base has to know which languages you intend to use.

1. Go to Brand → Knowledge and click your knowledge base to open it. (New to that menu? See what a brand is in Yaplet.)
2. Open Settings and add the languages you want under Other Languages.
3. Save.

Skip this and the translation action refuses with "No additional languages configured" and a button that takes you straight to this page.

2. Add a translation to an article

1. Open the category the article sits in.
2. On the article's row, choose Add other language.
3. Yaplet creates the translated version and opens it in the editor.

There is no language picker: Yaplet takes the first language from your Other Languages list that this article does not already have. Only the title is carried over — the body starts empty, so you are writing rather than editing over machine output. Once an article has translations, its row gains an Other languages dropdown listing each one with a Published or Not Published badge.

3. Translate the content

The translated article has its own Title, Description and body. Nothing is synced with the original, which means:

• You can adapt the phrasing instead of translating word for word.
• When you change the original later, you have to update the translation yourself — Yaplet will not flag it as out of date.

The editor is the same in every language, and images, code blocks and links all behave identically.

4. Publish each language on its own

Every language version has its own Published switch, so you can put the English article live while the Hungarian one is still half-written. Publishing a translation also adds it to your AI's knowledge, exactly as it does for the original.

Ratings are counted per version too — a visitor rating the Hungarian article does not move the English article's score.

How visitors get the right language

• On your public web address, a language selector appears in the header as soon as the knowledge base has more than one language. Visitors switch languages there, and each language has its own set of addresses.
• In the chat widget's Help tab, visitors browse the articles written in the knowledge base's own language — the one shown in the Language column on Brand → Knowledge. Translations are served on the public web address.

The knowledge base's Language setting is a different thing

These are easy to confuse, so it is worth naming them separately. Translations decide what a visitor reads. The knowledge base's own Language — the inline picker in the Language column on Brand → Knowledge, which saves the moment you change it — decides how your AI searches that text. As the tooltip on that column puts it: "The language this is written in. It decides how your AI searches the text — it does not translate anything."

A brand can hold knowledge bases in different languages, and your AI searches up to three of them at once, each in its own language — so adding a second-language knowledge base does not cost you search accuracy in the first. Anything without a language of its own falls back to the brand's language, set at Brand settings → General. This is all separate from the language the AI replies in, which follows the visitor automatically.