Website Translation vs Website Localization: What to Buy, Page by Page
Translation converts the words; localization adapts the experience. A page-by-page framework for deciding which content needs which — and the SEO layer most sites skip.
By Ilaria Menchini — Founder & CEO, Verbavox Group
Ask five agencies the difference between website translation and website localization and you will get five answers, most of them designed to sell the more expensive one. Here is the version that is actually useful when you are deciding what to buy.
Quick answer
Website translation converts the text of your existing site into another language, keeping the same structure, content and messaging.
Website localization adapts the site so it works for a specific market: the copy, but also navigation, page structure, search terms, imagery, formats, legal content, payment and contact expectations, and the technical setup that lets search engines serve the right version to the right user.
Translation is a subset of localization. The question is not which is better, but how much adaptation a given market and a given page genuinely need.
Where the difference becomes concrete
Consider a British software company publishing a pricing page in French and Italian.
Translation gives you the same three plans, the same feature names, the same case study from a US customer, the same reassurance about a phone number in London, and the same headline built around a metaphor that works in English.
Localization asks different questions. Do buyers in this market compare on price per user or per site? Is VAT displayed inclusive or exclusive? Does the proof on this page mean anything locally, or should a European reference come first? Is the search term for this product category actually the literal translation of the English one? Does the contact expectation involve a form, a phone number, or an invoice-friendly quote?
The words matter. So does everything around them.
What to localize, page by page
Not every page deserves the same treatment. A pragmatic split:
| Content type | Usual treatment | Reason |
|---|---|---|
| Legal, terms, privacy | Accurate translation, locally reviewed | Meaning must be preserved exactly |
| Technical documentation | Translation with terminology control | Consistency outweighs style |
| Product and category pages | Localization with local keyword research | Search intent differs by market |
| Homepage and campaign pages | Transcreation | The idea has to be rebuilt, not carried across |
| Blog and knowledge content | Selective localization | Some topics have no local demand; some need originals |
| Checkout, forms, error states | Localization | Friction here costs conversions directly |
The mistake is applying one policy to the whole site. Most sites need three: exact translation, adapted localization, and rebuilt creative.
The SEO layer people skip
A translated site with no keyword research is a site optimised for the wrong words — the reasoning is set out in international keyword research. Search volume, phrasing and competitive intensity vary by market, and the literal translation of your best-performing English keyword is frequently not the term local buyers type.
Beyond words, the technical layer decides whether the work is visible at all:
- A clear URL strategy — subdirectories, subdomains or ccTLDs, chosen once and kept
- hreflang annotations that are reciprocal and complete, including an x-default
- Self-referencing canonicals per language version, not a canonical pointing back to English
- Localized titles, meta descriptions and structured data, not translated ones
- Internal links that stay within the language version instead of dumping users back into English
Getting this wrong is the most common reason a well-translated multilingual site underperforms. We cover the discipline in more depth under multilingual SEO.
How to decide what you need
Three questions usually settle it.
What is this page for? Informational and legal content leans towards translation. Anything with a conversion goal leans towards localization.
How competitive is the market? In a market where local competitors publish natively, a translated site reads as a translated site — and buyers notice.
What happens if it is merely correct? For documentation, correct is the goal. For a homepage, correct and forgettable is a failure.
Common mistakes
- Auto-translating the site with a plugin and treating the job as done
- Localizing the marketing pages but leaving forms, error messages and checkout in the source language
- Publishing all languages at once with no plan to maintain them
- Using the same imagery and social proof everywhere regardless of relevance
- Building hreflang tags that point one way only
Expert insight
The pages that reward localization most are rarely the ones clients expect. Homepages get the attention, but the biggest measurable gains usually sit in category pages, comparison pages and support content — pages where users arrive with a specific intent already formed in their own language. If budget is limited, localize the pages that answer a question, not the pages that describe the company.
FAQ
Is machine translation ever enough for a website? For internal or low-risk reference content, machine translation with professional post-editing can be reasonable. For pages that sell, rank or bind you legally, it is not.
Do I need every page in every language? No. Partial localization is normal and perfectly workable, provided navigation and hreflang reflect what actually exists in each language.
Which URL structure is best? Subdirectories (/fr/, /it/) are the pragmatic default for most companies: simpler to maintain and they consolidate domain authority. Country domains make sense when the market operation is genuinely separate.
Next step
If you are scoping a multilingual site, our website localization services cover content, SEO structure and technical implementation together — and for product interfaces the work continues in software localization. Send us the site and we will tell you which pages need translation and which need rebuilding.
Related reading: Website Translation Services and Marketing Localization vs Transcreation.
Translator and interpreter, ISIT and Sorbonne graduate, working between English, Italian and French.
Need a translation that sounds local?
Tell us about your project — we'll get back within one business day.
