Visitors can ask website-chat questions in different languages. Answer quality depends on the question, the retrieved source material, and the model's ability to interpret and express that material. Test the languages important to your audience rather than assuming identical quality everywhere.
There is no per-language guarantee established by the chat installation settings. The embed's label and greeting are site-authored text; changing them is separate from translating your website or validating the generated answers.
Prepare trustworthy source content#
Publish accurate content for the tasks visitors need to complete. When you maintain localized pages, keep service names, eligibility, prices, contact details, and limitations consistent across versions. A precise translated source page is easier to review than an answer improvised from incomplete facts.
Link localized pages deliberately and preserve their canonical URLs. Avoid duplicating conflicting policies in multiple languages without an owner and review process. If information is available in only one language, make that limitation clear in the content and test how chat handles questions in another.
Build a language test set#
For each important language, prepare the same small group of tasks:
- A basic factual question with a direct published answer.
- A question requiring an exception or qualification.
- A follow-up to the first answer.
- A question whose answer is absent from the site.
- A question containing a real product name, address format, or specialist term.
Have a fluent reviewer assess the answers against the source facts. Look for altered numbers, incorrect negation, mistranslated terms, missing restrictions, and an unjustified confident answer to an unsupported question.
Check the interface and references#
Test the launcher, greeting, composer, and error states for your intended audience. Set the site's own label and greeting through hosted configuration or the external embed.
Verify that references reach the intended public page and language version. A response written in the visitor's language can still cite a source written in another language; evaluate whether that is useful for the actual audience.
On narrow screens, check long labels, wrapping, non-Latin text, and writing direction where relevant. Preserve keyboard access and a reachable send control. Do not describe a language as verified based only on one short greeting.
Improve and repeat#
If a response loses a critical qualification, improve the source wording and retest the same question. Record the language, expected fact, actual issue, and source page without retaining private visitor details. Review again when the underlying product or source content changes.
See answer-quality testing, content maintenance, and appearance.