Translating Your Reviews for International Shoppers

Short answer: Translate a review for the visitor reading it, but never replace what the customer actually wrote — store the translation next to the original, label it clearly as a translation, and keep your structured data and any product feed pointing at the words the customer typed.

You run a store that gets visitors in more than one language. Reviews arrive in whatever language the reviewer used, and a shopper reading in their own language trusts what they read a little more. So you translate. The part that's easy to get wrong is what happens to the original once you do.

Why you can't just overwrite the review text

A review is a named person's words about your business. The moment a translation tool replaces that text in your database, the review stops being what that person wrote and becomes what a model guessed they meant. If a customer wrote "the fit was a little tight" and the tool renders it as "runs small," you've changed the claim, not just the language.

That matters past the wording. If your structured data reads straight from that field, it now carries words the customer never wrote, attributed to their name — the kind of mismatch that costs you when that markup is what decides whether stars actually show in a search result.

Keep the original, add the translation beside it

The fix is structural, not stylistic: store the translation as its own thing, separate from the review itself. Kudo stores machine translations beside the original review, never instead of it — the customer's own words stay on the page, in your structured data, and in any Google feed you publish. The translation is something the widget adds on top, not something that replaces the record.

That also means a visitor can flip back. The widget renders both the translation and the original, marks the translated version "Translated," and switching to "show original" is instant — a toggle, not another request to a server. If you're setting up a reviews widget on your own site for the first time, this is one of the settings worth checking before you turn translation on.

Which languages are actually worth translating into

Translating into more languages is not free, in either sense — every language is a model call per review, and a language nobody on your site reads is wasted work with no upside. Start from your own analytics: what language does your traffic actually read in? A shop that sees mostly English and Spanish visitors gains nothing from a Japanese translation and a real amount from a Spanish one.

Kudo caps a page at five translation languages, on purpose. Past that, most of the languages on the list are getting little to no traffic while each one keeps costing something on every review you collect from then on. Pick the languages your traffic is actually in, not the longest list you can turn on.

What translation should never touch

Not everything on your review page is the customer's writing. If you ask shoppers extra questions beyond the star rating — runs small or runs large, would you buy again — the question and its label are yours, not the customer's. Kudo never machine-translates those merchant-written labels; only what the customer actually wrote gets translated. Translating your own question into a language you didn't write it in would put words in your mouth the same way overwriting a review puts words in a customer's.

Editing a review and what happens to its translation

A review changes sometimes — a customer edits a typo, or you correct a name. When that happens, the old translation is now translating text that no longer exists on the page, which is worse than no translation at all: a shopper could be reading a mistranslation of a sentence you already fixed. Kudo deletes a review's translations the moment its text is edited, so nothing stale survives the edit. The next request regenerates it against the corrected text.

Say a customer misspells your product name in their review and you fix it so the page reads correctly. If the Turkish translation sitting next to it doesn't know that correction happened, it's now describing something else entirely to every Turkish-reading visitor who scrolls past it — a small mistake in the original turning into a bigger, invisible one in the version most of your visitors actually read.

The Two-Minute Version

Kudo stores a review's translation next to the original rather than over it, labels it "Translated" with an instant toggle back to the original, and caps a page at five languages so translating stays worth what it costs. Your structured data and Google feed always carry what the customer actually wrote.

Start free at getkudo.co.

Frequently Asked Questions

Does translating a review change what shows up in Google's rich results?
No. Structured data reads the original review text, not the translation, so what Google indexes is what the customer actually wrote.

Can a visitor tell a review has been translated?
Yes — a translated review carries a visible "Translated" label, and switching back to the original text is instant.

How many languages can one page translate into?
Up to five. Past that, most of the languages on the list are getting little to no traffic, for an ongoing cost on every new review.

Are the extra questions I ask reviewers translated too?
No. Question labels and scales you write yourself stay in the language you wrote them in — only the customer's own review text is translated.

What happens to a translation if the review gets edited?
It's deleted along with the edit, so nobody reads a translation of a sentence that no longer exists on the page.