Translation moves the words of a page into another language. Localization adapts the page for the people who will read it, which means changing whatever the page assumes about its reader: the currency, the date format, the form fields, the references and sometimes the headline itself. A page can be translated without being localized. The quickest way to see the difference is one page done both ways.
The definitions, briefly#
The W3C's internationalization group describes localization as adapting content "to meet the language, cultural and other requirements of a specific target market (a locale)." It adds that localization is "often thought of only as a synonym for translation" but can involve number and date formats, currency, symbols and colours, legal requirements and address formats.
Translation, in that frame, is the language part. It is the largest part on most websites, and the part software does fastest. The rest of localization is a set of decisions about the market, and each one has to be made by someone who knows it.
One landing page, translated and then localized#
Here is an invented example. A US company sells invoicing software to freelancers and wants a German version of its landing page. The first column is the English source. The second is a faithful translation, the kind a careful translator or a good machine translation produces. The third is the same page localized for Germany.
The translated column is correct German. A German reader would still notice that the page was written for someone else.
What the translation got right#
Every sentence in the second column says what the English says. The grammar is fine and the button is a real button label. If the page only needed to be understood, this would do. This is the column machine translation aims for, and a fluent reviewer can check it quickly.
What localization changed#
The price. A dollar price on a German page asks the reader to convert and guess at fees. The localized page shows a euro price, and choosing it is a business decision: which price, and whether it includes VAT.
The date. 10/31/2026 is month first, as US English writes it. MDN's documentation of the browser's date formatter shows the difference: US English gives 12/19/2012, British English 19/12/2012, and German a long date such as Donnerstag, 20. Dezember 2012. The localized line follows the German form.
The form. A German postal address has no state line, so the State field goes. If it stays and is required, German customers cannot sign up.
The reference. Tax Day is an American deadline. Translated, it becomes an English phrase inside a German sentence that means nothing to the reader. The localized page drops it, or replaces it with a deadline a German freelancer knows, checked by someone who knows German tax rules.
The button. "14 Tage kostenlos testen" (try it free for 14 days) is shorter than the literal version and states the length of the trial, which the English left implicit. The company has to confirm the trial really is 14 days in Germany before that goes live.
Where transcreation starts#
The headline is the one row where the localized version does not translate the source at all. The English line leans on a US reference, the tax filing deadline, and makes a promise about the weekend. The German line keeps the promise and drops the tax framing, because the task a German freelancer dreads may be a different one.
That is transcreation: rewriting a line so it has the same effect on a new audience, even if the words share nothing. It belongs to headlines, slogans, ad copy and calls to action. It needs a copywriter who writes in the target language, and it should be rare on a website. Most pages need translation and a few localized details; only the lines that sell need recreating. Our glossary entry on transcreation has more on where it sits.
How to tell which one a page needs#
Ask what the page assumes about its reader.
A help article, a feature description or a blog post usually assumes little beyond the language. Translation with a review is enough.
A pricing page, a checkout, a signup form or a contact page assumes a currency, an address format, payment habits and sometimes a legal context. Those pages need localization, and the changes often happen in your CMS or store, outside the translated text.
A homepage hero, a campaign landing page or a tagline assumes a cultural reference. Those lines may need transcreation.
Language and region interact here too. A page for French readers in general can be fr; a page that quotes Canadian prices or Canadian law is fr-CA. Our entry on locales explains the tags, and the website localization guide walks through scoping a whole site.
Does search care about the difference?#
Google treats properly translated pages as separate versions, and its documentation says localized versions "are only considered duplicates if the main content of the page remains untranslated." Nothing in that documentation checks whether a page's prices were converted, so that part of localization is for your readers.
How LangRelay handles the two#
LangRelay translates your pages with AI that follows your glossary and, for German, Spanish, French, Italian, Dutch and Turkish, the formality register you set per language. That produces the second column, live by default, with free checks that hold a page with untranslated text, the wrong language or a changed price.
The third column is where a reviewer works. In the Visual editor, they click a line on the rendered page and edit it in a side editor with a live preview: the price wording, the date in the offer line, a rewritten headline. That edit becomes the translation for that text; it is approved, then published, before visitors see it. Your own edits never use words from your plan. Changes that are not text, such as removing a form field or setting a euro price in your store, still happen on your site. Glossary entries for string translation and the article on machine vs human translation cover the review side in more detail. To see the editor on your own pages, book a demo.
Sources
The pages this one cites, with the day each was read.
- 01W3C Internationalization, Localization vs. Internationalizationw3.org, checked 6 October 2026
- 02MDN Web Docs, Intl.DateTimeFormatdeveloper.mozilla.org, checked 6 October 2026
- 03Google Search Central, Tell Google about localized versions of your pagedevelopers.google.com, checked 6 October 2026


