A Multilingual Website Chatbot Without Translating Your Whole Site

Yes, you can answer visitors in Spanish, German or Japanese without translating your site. A modern AI chatbot reads your English pages, finds the passage that answers the question, and writes the reply in whatever language the visitor used. What it can't do is make your site rank in those languages, or turn a paraphrase into your official terms. For those you still need translated pages.

I build ChatBento, an AI support chatbot for websites. Here's how answering in other languages works, where it's reliable, where to be careful, and a test plan for each language you care about.

Why answer in the visitor's language at all?

Because people buy in their own language. In a 2020 survey of 8,709 consumers in 29 countries, CSA Research found that 76% of online shoppers prefer to buy products with information in their native language, and 40% will never buy from websites in other languages. It's a shopping survey from a firm that studies translation markets, so read it as a direction, not a forecast for your site. A chatbot doesn't fix the whole problem. It fixes the moment someone has a question and can't read the answer.

How does a chatbot answer in another language from English content?

Two steps, both of which have to work across languages:

1. Finding the answer. Your content is split into passages, and each visitor question is matched to the passages most likely to answer it. This is retrieval. ChatBento uses a multilingual embedding model (bge-m3) for the matching, so a question in Portuguese can find a passage written in English.
2. Writing the reply. The matched passages go to the language model, Anthropic's Claude, which writes the answer. One of the bot's built-in rules is to reply in the language the visitor writes in.

Anthropic's multilingual documentation says "Performance varies by language, with particularly strong capabilities in widely spoken languages", and advises testing the languages relevant to you. That holds for any model: test the languages your visitors use instead of trusting a list.

What works well

• Factual questions with a clear answer on your site. Opening hours, delivery times, what's included in a plan, how to book, whether a product fits a use.
• Steps. "How do I reset my password?" answered as a short list in the visitor's language.
• Visitors who switch languages. Someone who starts in English and switches to French should get French from that point. It's one of the tests below.

One thing to expect: the source links under answers point to your pages, which are still in English. The answer helps, but the page they click through to won't be in their language.

What to watch

Legal and policy wording

A chatbot's answer about your refund policy in German is a paraphrase made on the fly, not your German refund policy. For anything binding, the bot should summarize briefly and point to the official page. You can say so in your chatbot's own instructions:

For refund, warranty, privacy or legal questions, give a short summary and link the official policy page. Say that the English version of our policies is the official one.

If you need official terms in another language for a market you sell into, that's a translated page reviewed by someone qualified, not a chat answer.

Prices, currencies and units

The bot's rules say never to invent prices, so it shouldn't convert your $30 into euros on its own. Make that easy for it:

• Write the currency explicitly in your content: "$30 USD per month", not "30/mo".
• If you sell abroad, put the units your buyers use on the page: centimetres next to inches, kilograms next to pounds. Don't rely on the bot doing the arithmetic.
• Write dates in words. "03/04" means March 4 in the US and April 3 in most of Europe. "April 3" means April 3.

Names that must not be translated

Product names, plan names, brand terms and place names can get translated or adapted when a model writes in another language. If yours must stay exact, say so in your instructions:

Never translate these names: Hobby plan, Standard plan, Moonlight Blend.

Tone and regional variants

German and French have formal and informal "you". Portuguese differs between Brazil and Portugal, and Chinese between Simplified and Traditional script. If it matters to your customers, add an instruction such as "In German, use the formal Sie." The instructions generator can help you phrase these.

The parts you write yourself

The greeting, the header title, the input placeholder and the suggested questions are text you write, and they don't change per visitor. In ChatBento, a few built-in labels, such as the contact form's fields and the "Talk to a human" button, are in English. Two practical fixes:

• Make the greeting say it out loud: "Hi! Ask me anything. You can write in English, Español or Français."
• Keep suggested questions short and simple, so a visitor with basic English understands them.

Replying to leads in another language

When the bot can't answer or a visitor asks for a person, the chat shows a contact form and the message is emailed to you, in whatever language the visitor wrote. Decide in advance how you'll reply. If your team only replies in English, add an instruction like "If the visitor writes in another language, mention that our team replies by email in English." More on handoffs in the human handoff use case.

When do you still need translated pages?

A chatbot answers people who are already on your site. It does nothing to bring people searching in other languages to it. Google is explicit about how it decides a page's language: in its guide to managing multilingual sites, it says "Google uses the visible content of your page to determine its language." Chat replies aren't part of your page, so to show up in Spanish searches, you need Spanish pages.

If you do translate, follow Google's guidance:

• Give each language its own URL. Google "recommends using different URLs for each language version of a page", rather than switching language with cookies or browser settings.
• Connect the versions with hreflang. Google's localized versions guide explains the three ways to do it (HTML tags, HTTP headers or a sitemap). Each version must list itself and all the others, and if two pages don't point to each other, the tags are ignored.
• Don't redirect automatically by language. Google advises against it, because it can stop people and search engines from reaching every version. Link to the other languages instead and let visitors choose.
• Review machine translation. Google's spam policies give, as an example of scaled content abuse, generating many pages from other content "including through automated transformations like synonymizing, translating", where little value is provided to users. A reviewed translation of the pages that matter is a different thing from auto-translating hundreds of pages.

Here's how I'd decide, page by page:

The practical order: switch the chatbot on, then read your conversations for a couple of months to see which languages actually appear and what those visitors ask. That tells you which language to translate first and which pages to start with. I describe a monthly routine for this in your chatbot's conversations are a content plan.

A test plan for each language

Run this before you announce support for a language, and again after big content changes. Allow about an hour per language.

Who writes the questions: a native speaker if you can find one (a customer, a friend, a freelancer for an hour). Don't write them with the same AI you're testing; you'll test the model against itself.

Fourteen questions per language:

1. Your five most common questions, written the way a native speaker would type them, with typos and missing accents in at least one.
2. A price question, plus "how much is that in [their currency]?" A pass gives the price as written on your site and doesn't invent a conversion.
3. A refund or cancellation question. A pass summarizes your policy without adding promises, and links the official page if you've asked it to.
4. A question that uses a product or plan name. A pass keeps the name exactly as you wrote it.
5. A size, unit or date question. A pass matches your page exactly.
6. A question your site doesn't answer. A pass says, in that language, that it doesn't have the information and offers the contact form.
7. "Can I talk to a person?" A pass shows the contact form.
8. An off-topic question. A pass declines politely, in that language.
9. A conversation that starts in English and switches. A pass follows the switch.

Score each answer on four things: facts correct, right language throughout, names and prices intact, natural enough that a native speaker wouldn't wince. The last one needs a native reader. If you don't have one, a back-translation through a different tool is a rough check for meaning, not for tone.

Fix in this order:

• Wrong facts: fix the content. The answer is usually wrong in English too, so check that first.
• Mangled names or terms: add them to your instructions as "never translate".
• Wrong tone or variant: add a short instruction for that language.
• Gaps: add a Q&A. It can be in English; the bot can answer from it in other languages. Then run the failed question again.

Conversations you start from the dashboard preview are marked "Test" in the conversations list, so your test runs won't get mixed up with real visitors.

The checklist

• Languages chosen from real visitors, not guesses
• Prices written with currency, units and dates written unambiguously
• Instructions for policy questions, untranslatable names, tone and reply language
• Greeting says visitors can write in their own language
• Fourteen-question test passed in each language, reviewed by a native speaker
• Decision made, page by page, on what still needs real translation
• Retest after major content changes

If your visitors speak more than one language, the multilingual visitors page shows how ChatBento handles it, and the 14-day trial (200 messages, no card) or the free plan is enough to run the test plan above on your own site.