What a localisation style guide does that the house style cannot
The editorial style guide is the rulebook for the source language: spellings, how the product is named, how numbers and dates are written, heading and link rules, the words to avoid. Much of it cannot be carried into another language. Spelling rules, punctuation habits, capitalisation, word order and the ways a language marks politeness or gender all work differently, and a translator who applies the source rules literally produces copy that reads as foreign. An edition that already reads as several voices is diagnosed on the page about translated marketing copy that reads wrong, where the missing style guide is one of six causes.
The translation and transcreation guide names three documents that keep a brand consistent across languages: the termbase, the style guide and the brief. It describes the style guide in a paragraph: formal or informal address, directness, sentence length, punctuation and capitalisation, dates, numbers, currency and units, inclusive language where the language marks gender, and local sensitivities. This tutorial builds that document, one language at a time.
The localisation style guide is the language layer of content governance. It does not replace the house style; it inherits from it and records only what changes. It also does not replace the brand guidelines: the brand identity and voice guide still defines what the brand sounds like, and the language guide explains how that sound is achieved in another language.
Before you start
- Have the house style and the voice description. The editorial style guide and the brand's brand voiceThe consistent personality a brand expresses in its words across channels, with tone adjusting to the situation and the audience. description are the source the language guide adapts.
- Name the in-country reviewer. A native speaker who knows the market and the category, with time agreed with their manager, as the translation guide advises. They will write most of the language decisions.
- Collect real copy. Gather source pages, emails and ads, plus any localised copy already published or delivered in the target language, with the reviewer's corrections if they exist.
- Have the termbase started. Terms are kept in the termbase, not in the style guide; the guide links to it.
- Know the market's scope. The localisation brief template records the market, the language and its variant, the audience and the assets. The guide is written for that language and variant.
The steps
Start from the house style and the voice
Open the editorial style guide and the voice description and mark every rule as one of three kinds: applies in every language (for example, the rule that claims need evidence, or that headings describe the content), adapts per language (the rule exists everywhere but the answer differs, such as how dates are written), or source language only (spelling variant, punctuation habits). Only the second kind needs a decision in the new guide, and the first kind is simply referenced. This keeps the language guide short and stops it drifting away from the house style.
Name the language owner and the reviewer
Write on the first page who owns the guide for this language and who reviews changes. Usually the in-country reviewer or a senior linguist owns the language decisions, while the localisation owner at head office owns the brand decisions. Record how to reach both and how quickly a translator's question is answered, so translators ask rather than guess.
Decide address and register for the market
Many languages force a choice the source language may not: a formal or informal way of addressing the reader, and a level of formality in vocabulary and sentence shape. The reviewer recommends the choice for this market and this audience, and the guide records it with the reason, the exceptions (legal pages, complaints replies, business customers) and an example of each. This single decision changes almost every sentence, so it is made once, here, rather than by each translator.
Translate the voice, not the adjectives
Voice descriptions such as "plain-spoken" or "warm" do not translate as words; they translate as habits. For each trait in the voice description, ask the reviewer what that trait sounds like in their language: sentence length, how direct a recommendation can be, whether humour or understatement lands, how much enthusiasm reads as sincere. Write each trait as a short rule with an approved example and a rejected one. Where a line depends on wordplay, mark it for transcreationRewriting marketing copy for another language or market from the original brief, so the intended effect survives even when the words change. rather than asking the guide to solve it.
Set local formats for dates, numbers, money and units
Record how this market writes dates, times, numbers, decimal and thousands separators, currency symbols or codes and their position, measurement units, phone numbers and addresses. The localising websites and campaigns guide explains why these details decide whether a page looks local; the style guide makes them consistent across pages, emails and ads. Where the house style already sets a rule for the source language, the language guide states the local equivalent beside it.
List what stays in the source language
Google Search Central's guidance on managing multi-regional and multilingual sites, as the international SEO section explains, is that each version of a page should be in one language, navigation and content alike. So the default is to translate everything, and the guide lists the exceptions: brand names, product line names and feature names the brand has decided never to translate, which the tutorial on naming a product or brand checks with native speakers before they are chosen. Record how those names behave in a sentence, such as whether they take local grammar, and keep the list in step with the termbase's do-not-translate entries.
Record sensitivities and cultural-check findings
The reviewer and the market team know which topics, images, comparisons and expressions to avoid or handle with care. Write them down with the reason, and add the findings of every cultural check on a localised asset, as the localising guide asks, so the lesson is learned once. Record how the language handles gender-inclusive wording where the language marks gender, and what the brand's choice is.
Add reviewed examples under every rule
A rule without an example is interpreted differently by every translator. Under each rule, put one approved example from real copy and, where useful, one rejected version with the reviewer's reason. Take the examples from assets the reviewer has already corrected, because those are the mistakes translators actually make. Keep examples short and show them in the target language with an English gloss for head office.
Publish it beside the termbase and the brief
Put the guide where translators, transcreation writers and reviewers already work, and link it from every localisation brief, which has a "Tone and style" row for exactly that purpose. Send it with every job, together with the termbase. A guide that lives in someone's inbox is not a guide. Record a version date on the first page so everyone can tell which edition they are following.
Feed every reviewer correction back
When the reviewer corrects the same kind of thing twice, it becomes a rule in the guide, with the example. When a rule causes awkward copy, the owner changes it and records the change. The translation guide makes the same point about the termbase: fix the source of the error, not only the asset. Review the guide at each market gate and when the house style or the voice changes, because a language guide that falls behind the source drifts quietly.
What each language's guide holds: a contents table
| Section | What it records | Who decides |
|---|---|---|
| Scope | Language and variant, market, audience, version date | Localisation owner |
| Owners | Language owner, reviewer, how to ask a question | Localisation owner |
| Inherited rules | House-style rules that apply in every language, by reference | Localisation owner |
| Address and register | Formal or informal address, formality, exceptions by content type | In-country reviewer |
| Voice in this language | Each voice trait as a habit, with approved and rejected examples | Reviewer with the brand owner |
| Formats | Dates, times, numbers, separators, currency, units, phone numbers, addresses | Reviewer |
| Source-language names | Brand, product and feature names never translated, and how they behave in a sentence | Brand owner, checked by the reviewer |
| Sensitivities | Topics, images, comparisons and expressions to avoid, with reasons; cultural-check findings | Reviewer and market team |
| Inclusive language | The approach where the language marks gender | Reviewer with the brand owner |
| Links | Termbase, localisation brief, house style, keyword list | Localisation owner |
| Change log | Each change, the reason and the date | Language owner |
The searched-for words are not style decisions. They come from keyword research for a new market and go into the termbase and the brief, and the style guide simply links to them. Once pages are published, each one still has to sit in the right hreflangAnnotation for language/region versions. set, which the localisation checklist covers rather than the style guide.
A brand's distinctive brand assets belong in the guide only as constraints: the name, the logo lock-up, a recurring line kept in the source language. Those are the elements every market keeps, so the guide says what must not be translated or redrawn, and leaves everything else to the language decisions above.
A cycle repair kit maker writes its first language guide (illustrative)
Spekkora Cycle Kits writes a style guide for Market A
Spekkora Cycle Kits, an invented maker of puncture-repair and maintenance kits sold online, prepares to launch an edition for Market A. Its house style runs to 14 pages; the marketing lead and the in-country reviewer, a cycling mechanic who writes in Market A's language, go through it in two 90-minute sessions and mark 31 rules as applying everywhere, 22 as adapting per language and 9 as source language only.
The reviewer recommends the informal form of address for product pages and emails, because the brand's customers are riders who maintain their own bikes, and the formal form for the terms page and complaint replies. The voice trait "plain-spoken" becomes three rules: short sentences, instructions in the imperative, and no exclamation marks in product copy. The 6 kit names stay in the source language, and the guide records that they take no local plural ending. Formats for prices, decimal separators and tyre-size units are set from the market's conventions.
The first batch of 40 pages comes back with 57 reviewer corrections. Eighteen of them are the same three problems: a formal form slipping into product pages, a literal translation of a tagline that the brief had labelled for transcreation, and units written the source-market way. Each becomes a rule with an example. The second batch of 35 pages comes back with 12 corrections, none of them repeats.
Common mistakes
- Translating the house style. Source-language spelling and punctuation rules do not carry over. Mark which rules apply everywhere, which adapt and which stay at home, and write only the adapting ones.
- Leaving address and register to each translator. It changes almost every sentence. Decide it once, with the reviewer, and record the exceptions.
- Describing the voice in adjectives. "Warm" means nothing to a translator. Write each trait as a habit with an approved example.
- Putting terms in the style guide. Individual terms belong in the termbase; the guide links to it.
- Rules without examples. Every rule needs an approved example from real copy, or it will be read differently by every writer.
- Writing it at head office alone. Only a native speaker who knows the market can judge what sounds natural. The in-country reviewer writes the language decisions.
- Corrections that never reach the guide. A repeated correction is a missing rule. Add it, with the example, and record the change.
The marketing localisation hub shows where the style guide sits between the language workflow and the asset work.
