Website Translation vs Localization: What You Need

"Just translate the website" is the brief most agencies get, and it's usually the wrong one. Website translation converts words from one language to another; localization adapts the whole experience, currency, imagery, legal wording, even layout, to a specific market. Confusing the two is why some multilingual sites read fine but still don't sell.

What website translation actually covers

Translation is linguistic conversion: your English homepage becomes a French, German or Japanese homepage with the same structure, the same images, the same functionality. A qualified translator reads the source text and produces an accurate equivalent in the target language. Nothing about the site's logic, currency handling or visual design changes.

This is enough when:

• You're publishing informational content: blog posts, help docs, an about page, where the reader just needs to understand the text.
• Your audience is proficient in the source culture's conventions and doesn't need date formats, payment methods or imagery adjusted.
• You're testing a market before investing in a full local build.

What localization adds on top

Localization starts from translation and goes further. It adjusts everything a native visitor expects to see done "their way":

• Currency and pricing display: €, $, £ shown correctly, not just converted in a tooltip.
• Date, time and number formats: 31/12/2026 vs 12/31/2026 vs 2026年12月31日.
• Payment methods: iDEAL in the Netherlands, Alipay in China, SEPA in the eurozone.
• Legal and compliance text: GDPR notices, tax disclosures, terms that match local regulation. Confirm exact wording requirements with a local counsel where the stakes are high.
• Imagery and color: a stock photo or color choice that reads neutral in one market can read off-brand or worse in another.
• Tone and idiom: literal translation of a slogan often falls flat or means something unintended. This is where transcreation work comes in.

An ecommerce checkout, a SaaS pricing page, or a lead-gen form aimed at converting new-market customers almost always needs localization, not translation alone.

A quick example

Take a SaaS pricing page. Translation alone gives you the plan names, feature list, and FAQ in the target language: accurate, readable, and enough for a visitor to understand what's on offer. Localization goes further. Prices show in the local currency at the actual exchange rate you charge, not a generic conversion; the payment method looks familiar to the visitor; VAT or sales tax is handled the way that market expects to see it; and the "Contact sales" flow routes to someone who can actually respond in that language. The translated version reads fine. The localized version is the one that gets a card entered.

The same split shows up on a support or documentation site, just inverted. A help center rarely needs currency or payment localization, but it does need localized screenshots if the underlying product UI is itself localized, since a French user reading French instructions next to English screenshots loses trust fast.

Where teams get the split wrong

Two mistakes come up constantly:

• Localizing everything, including pages that don't need it. A static "About us" page or a company blog post rarely benefits from currency or payment-method work. Translating it well is enough, and spending localization budget there is money that should have gone to the checkout flow instead.
• Translating the checkout and calling it done. This is the more expensive mistake. A checkout page that reads grammatically correct but shows the wrong currency symbol, an unfamiliar payment button, or a shipping estimate in the wrong date format creates hesitation exactly where you can least afford it, and it's invisible to anyone reviewing the page for language quality alone, because the words are technically right.

How to tell which one your project needs

Ask three questions before you scope the work:

1. Does the page ask for money or personal data? Checkout, signup, and pricing pages need localization: currency, payment methods, and legal text are conversion factors, not nice-to-haves.
2. Is the content purely informational? Blog posts, documentation, and press releases usually only need accurate translation.
3. Are you entering the market long-term, or testing interest? Long-term entry justifies full localization investment; a market test can start with translation and expand later.

Most sites end up mixed: marketing and transactional pages localized, evergreen content pages translated. That's a reasonable way to control cost without cutting corners where it matters.

What this means for budget and timeline

Translation-only work is priced per word and moves fast. There's no design or engineering coordination involved, just source text in and target text out. Localization takes longer and costs more per page, because it involves decisions beyond the linguist's control: which currency to display, which payment methods are actually integrated, what the legal team requires in that jurisdiction. Scoping this upfront, page by page, rather than as one blanket "localize the site" line item, is what keeps a multilingual launch on budget instead of ballooning once someone notices the checkout still shows USD to euro shoppers.

A practical starting point

Send us the URLs or the exported content, tell us which pages take payments or collect data, and we'll scope translation-only versus full localization per section rather than quoting one blanket rate for the whole site. See our localization service page for what's included in a full multilingual site build, including string handling and QA on the translated layout.

Getting started

Whichever route fits, the workflow is the same: instant online estimate, a human-confirmed fixed quote within about two business hours, and payment only after you approve, with no charge upfront. Every project uses 100% native linguists with independent proofreading by a second translator. Request a localization quote and tell us which pages need full adaptation versus straight translation.