Localisation is more than translation
A translated page answers the question "can people in this market read it?" A localised page answers a harder one: "would people in this market believe it was written for them?" The gap between the two is where most international marketing underperforms. Visitors forgive an occasional awkward phrase; they do not forgive prices in a foreign currency, a checkout that refuses their card, delivery promises that do not apply to them or a headline joke that only works in the source language.
Localisation therefore has two halves that need different people. The language half is specialist work: translators, transcreationRewriting marketing copy for another language or market from the original brief, so the intended effect survives even when the words change. writers, terminology management and reviewers who are native speakers of the target language. The asset half is marketing and product work: deciding the page structure, the local landing pages, the pricing and payment content, the imagery and the paid campaign assets for each market. The two meet in keyword research, because the words people search for in a market are the words the pages and the ads must use.
The scope of localisation is set upstream. The decision in the standardisation vs adaptation comparison fixes which elements are global and which each market may change, and localisation executes that split. If the split was never written down, localisation teams end up arguing strategy one asset at a time, which is slow and produces inconsistent brands.
Language, content, site, campaigns
| Layer | What it covers | Who usually owns it | Guide |
|---|---|---|---|
| Language | Translation, transcreation, termbases, style guides, machine translation with review | Localisation lead with translators and in-country reviewers | Translation and transcreation, Localisation style guide, Termbase and translation memory |
| Content | Which pieces are localised, rewritten or created locally; local examples, proof and references | Content lead with market input | Translation and transcreation, Deciding what to localise first |
| Site | Structure per market, local pages, currency, payment, delivery and legal content | Web and product teams with legal input | Localising websites and campaigns |
| Campaigns | Paid creative, landing pages, offers, tracking and imagery per market | Performance and creative teams with market owners | Localising websites and campaigns, Adapting creative |
The layers are sequential in practice. Language assets (the termbase and the style guide) should exist before content is translated; content should be agreed before the site is built in a language; and the site should be live and tested before paid campaigns send traffic to it. Running them in parallel saves a few weeks and usually costs more in rework.
The core guides
Translation and transcreation for marketing covers the language workflow. It sets out the spectrum from literal translation through localisation to full transcreation, explains which kinds of copy belong where on that spectrum, and shows how termbases, style guides and a proper brief keep a brand's voice consistent across languages. It also covers keyword research in the target language, the place of machine translationTranslation produced by software or a language model, now fluent enough for first drafts but used with human post-editing applied by content type. with human review, and how in-country review and sign-off are organised so that they do not become a bottleneck.
Localising websites and campaigns covers the assets. It summarises the site-structure options, then works through local landing pages and message match, currency, payment, delivery and legal content, imagery and cultural checks, and the localisation of paid campaign assets and their tracking. It ends with a per-market launch checklist that can be reused for each new market.
Together the core guides decide whether a localised page converts. Conversion rate (CVRShare of visits or clicks that convert.) is the honest measure of localisation quality, because a page that reads well but converts poorly against the home edition usually has an asset problem (price, payment, trust) rather than a language one.
Further guides
Further guides turn the language workflow into standing assets and routines, decide what to localise and keep it current, and adapt the creative itself:
- Writing a localisation style guide — a tutorial for one target language: address and register, voice carried across, local formats, untranslated names and a reviewer's examples.
- Building a termbase and translation memory — a tutorial for extracting terms, approving them per language, do-not-translate names, ownership and corrections.
- Reviewing localised copy in a language you do not speak — a tutorial on what a marketer who does not speak the language can check: structure, formats, links, claims by back-translation, reviewer notes and results.
- Choosing and managing translation suppliers — agency, freelance or in-market staff, paid test pieces, briefs, ownership of files and reviews.
- Deciding which content to localise first — a tutorial for a new market's first scope: an inventory, the job of each piece, local demand, cost and upkeep.
- Keeping localised content in step with the source — tracking changes, triage by risk, prices and claims first, retiring pages and drift checks.
- Adapting creative for different markets — a master built for change, imagery and casting, text and video in other languages, claims and testing.
Localisation and international SEO
Localisation produces the pages; international search engine optimisation (SEOImproving visibility in unpaid search results.) decides how search engines find and serve them. The two must be planned together, because the site structure chosen for search (country domains, subdomains or subdirectories) shapes how content is shared or duplicated across markets, and the content decisions in turn decide whether editions in the same language are near-duplicates that need handling.
The international SEO section owns the structural choices and the geotargeting signals, drawing on Google Search Central's documentation on managing multi-regional and multilingual sites. The annotation that tells search engines which language and region each page version serves is hreflangAnnotation for language/region versions., and the hreflang guide covers its codes, placement and the errors that break it. This section does not repeat that material. Its responsibility is upstream and downstream of it: upstream, making sure each localised page is genuinely written for its audience and uses the terms people search for; downstream, making sure that new localised pages are added to the hreflang set when they are published rather than months later.
A practical rule: whoever owns international SEO signs off the structure before the first page is localised, and the localisation checklist includes a line confirming the page has been added to the alternates of every other edition.
Quality: in-country review and a localisation checklist
Quality in localisation is not something a central team can check alone, because the central team cannot read most of the languages. Quality comes from two mechanisms. The first is in-country review: a native speaker who knows the market and the category reads the localised asset in context (on the page, in the ad preview, inside the email) and approves or corrects it. Reviewers should be named per market, briefed on the brand's voice and the termbase, and given a deadline, otherwise review becomes the step that delays every launch. The tutorial on reviewing localised copy in a language you do not speak covers what the central team can still check, and how to read the reviewer's notes.
The second mechanism is a checklist that every localised asset passes before publication. It turns the lessons of past markets into a routine and catches the errors reviewers do not look for because they are not language errors.
Before a localised asset goes live, confirm each of the following:
- Copy reviewed in context by a named in-country reviewer
- Termbase terms used consistently; no untranslated source-language strings
- Prices, currency symbols, dates, numbers and units in local format
- Payment, delivery and returns information correct for the market
- Legal, privacy and cookie content written for the jurisdiction
- Imagery, names and examples checked for local relevance
- Links point to the same-market edition, not the home site
- Page added to the hreflang set of every other edition
- Tracking parameters and conversion events firing for the market
A homeware brand catches its errors before launch
Fernhill Living, a UK homeware retailer, localised 40 product pages and its checkout for the Netherlands. The translations had passed a translator's own quality check. Its Dutch in-country reviewer, working through the checklist on a staging site, found 11 issues in two hours: prices shown with a decimal point instead of a comma, delivery times copied from the UK edition, a returns page still citing UK consumer law, three product names that were unfortunate in Dutch and a footer linking to the UK privacy policy. None was a translation error. After fixes, the Dutch edition launched with a conversion rate of 2.1% in its first month, against 2.4% for the UK site.
Common localisation problems
| Problem | Usual cause | Guide |
|---|---|---|
| Copy is accurate but reads as foreign | Translated literally where it should have been transcreated | Translation and transcreation |
| Brand and product terms vary between pages | No termbase or style guide before translation began | Translation and transcreation, Termbase and translation memory |
| Localised pages get little organic traffic | Keywords translated rather than researched in the target language | Translation and transcreation |
| Every launch waits on review | Reviewers not named, briefed or given deadlines | Translation and transcreation |
| Localised editions lag behind the source | No record of which editions a change touches; changes not triaged by risk | Keeping localised content in step |
| A translation supplier misses deadlines or the tone | Supplier chosen on a portfolio, not a paid test piece; jobs sent without the brief, termbase and style guide | Choosing and managing translation suppliers |
| Ads read as translated | Master creative built for one market; headline translated over a home-market picture | Adapting creative for different markets |
| Good traffic, weak conversion in one market | Currency, payment, delivery or trust content not localised | Localising websites and campaigns |
| Ads in the local language land on home-market pages | Campaign assets localised without local landing pages | Localising websites and campaigns |
| Wrong edition shown in search results | Structure or alternates not set up | International SEO |
The strategic decisions that set the scope of all this work are on the international marketing hub, which shows how localisation sits between market choice and day-to-day operations. When localised copy already reads wrong to the market, or localisation is the late step on every launch, the international marketing troubleshooting section traces the fault to the brief, the termbase, the reviewer or the queue rather than to the translator.
