One-line definition
Translation (翻译本地化) is the process of converting a website's pages, product listings, and marketing content from your source language into the language of a target market — accurately enough that customers there can read, understand, and buy without friction.
Real-life analogy
Think of translation as changing the currency and the plug shape when you move a product into a new country. The product itself stays the same, but the way it meets the customer has to change, or nothing works. A UK plug is perfectly functional — it just won't fit a US socket.
Language works the same way. Your English product page is not "broken" in Germany. It's just plugged into the wrong socket. Translation adapts the language so the same offer actually connects with a local buyer.
Core formula
A useful way to think about it:
Translation value = (Language accuracy × Coverage of touchpoints) ÷ Friction left for the buyer
- Language accuracy — is the grammar, tone, and terminology correct?
- Coverage of touchpoints — how many places did you translate? Homepage only? Or every product page, email, ad, and checkout flow?
- Friction — anything still in a foreign language, or phrased so oddly that it slows the buyer down.
If friction stays high, accuracy doesn't matter much. A perfectly translated homepage with an English-only checkout still loses the sale.
Comparison with related terms
People often use these words interchangeably. They shouldn't. Here's the practical difference:
| Term | What it changes | Scope | Example |
|---|---|---|---|
| **Translation** | Language | Text only | "Free shipping" → "Kostenloser Versand" |
| **Localization** | Language + format, currency, dates, units, culture | Text + systems | Price shown as €49,99 not $49.99; sizes in EU 42 |
| **Transcreation** | Creative intent | Marketing copy, slogans | Rewriting a tagline so it lands emotionally, not literally |
| **Internationalization (i18n)** | The underlying tech | Site architecture | Building your store so it *can* support 12 languages |
| **Transliteration** | Script only | Names, brands | "Nike" → "ナイキ" (sound, not meaning) |
The key relationship: translation is a subset of localization. Localization is the umbrella; translation is the language layer inside it. Internationalization is what you do *before* either, so both are possible.
Use cases
Where translation shows up in a cross-border store:
1. Product pages. Titles, descriptions, specs, sizing charts. This is usually the highest-volume work. A store with 500 SKUs and 6 fields per product is 3,000 strings before you touch a single ad.
2. Site navigation and UI. Menus, buttons, filters, error messages, checkout labels. Small strings, huge impact — a mistranslated "Place order" button directly costs revenue.
3. Marketing and ads. Meta ad copy, Google Search ads, email flows, SMS. Often needs transcreation rather than literal translation.
4. Customer support. FAQ pages, return policies, shipping terms, live chat macros. Poor translation here creates tickets instead of resolving them.
5. Post-purchase. Order confirmations, shipping notifications, review requests. Easy to forget, and it's exactly where trust is won or lost.
6. SEO metadata. Title tags, meta descriptions, alt text, URL slugs. Translated keywords rarely match what locals actually search — this needs keyword research, not just word swapping.
Misconceptions
"Google Translate is good enough." For a rough internal draft, maybe. For customer-facing commerce, no. Machine translation handles common phrases reasonably but stumbles on product terminology, brand voice, and idiom. A 2023 CSA Research survey found that 76% of consumers prefer to buy from sites in their own language, and 40% will not buy from sites available only in another language. "Good enough" language does not clear that bar.
"Translation is a one-time project." Every new product, every price change, every campaign adds strings. Translation is an ongoing operational process, not a launch task.
"English is fine — everyone speaks it." Roughly 1.5 billion people speak English worldwide, but only about 380 million are native speakers. For most of your non-English-market buyers, English is a second or third language, and reading a full product page in it is work. Buyers avoid work.
"Translation and localization are the same thing." They aren't. Translating your text but leaving prices in USD, dates in MM/DD/YYYY, and sizes in inches is a half-finished job. Localization covers all of it.
"Cheaper is fine for low-stakes pages." Sometimes true — a policy page tolerates more than a landing page. But "low-stakes" is a judgment call you should make deliberately, per page type, not by default.
"One translator can cover every market." A native Spanish translator for Mexico may not produce the right register for Spain or Argentina. Market-level nuance matters, especially in ads and product names.
Related terms
- Localization (本地化) — the full adaptation of a store to a market: language, currency, payment methods, sizing, culture, legal.
- Transcreation — creative rewriting of marketing copy to preserve intent rather than literal meaning.
- Internationalization (i18n) — engineering your site so it can support multiple languages and locales.
- Machine Translation (MT) — automated translation, often used as a first draft before human review.
- Post-editing — human review and correction of machine-translated output.
- Glossary / Termbase — a locked list of brand terms and product names so translations stay consistent across pages and translators.
- Locale — a language + region combination (e.g., pt-BR for Brazilian Portuguese vs. pt-PT for European Portuguese).
- hreflang — the HTML tag that tells search engines which language version to serve to which audience.
Translation is the entry-level, highest-leverage step in cross-border localization. Get the language right, cover every touchpoint, and remove the friction — then everything else you build on top of it actually has a chance to convert.
