A Banner Is Only as Good as Its Translation

Consent has to be informed. A visitor who cannot read the banner cannot make an informed choice, and a visitor who sees half the text in their language and half in English is unlikely to trust it. For publishers with international audiences, localisation is not a cosmetic layer on top of a consent setup — it is part of whether the setup works at all.

Use this checklist when you launch a banner in a new language, add a market, or review an existing multilingual setup.

1. Language Selection

• Decide how the language is chosen. The usual order is: the language of the page the user is reading, then the browser language, then a default. Showing the banner in the browser language on a page written in another language is confusing.
• Match the site’s own language switch. If a user changes the site language, the banner and preference centre should follow.
• Avoid geolocation-only rules. Country is not language. Belgium, Switzerland and Canada each have several official languages, and many users read sites in languages other than their country’s main one.
• Define a fallback. When no translation exists for a language, fall back to a language the user is likely to read, not silently to a blank or broken banner.

2. Completeness

• Every layer is translated. The first layer, the preference centre, purpose descriptions, vendor details, the withdrawal link and any confirmation messages.
• Button labels are translated consistently. “Accept all”, “Reject all” and “Manage options” should use the same terms in the banner as in the preference centre.
• Standard texts use official translations. If you use the IAB TCF, the purpose names and descriptions are standardised, and translations are maintained alongside the Global Vendor List. Use those rather than writing your own versions.
• Your cookie policy exists in the same language, or the banner says clearly which language the policy is in.

3. Accuracy and Tone

• Review machine translation. A literal translation of “legitimate interest” or “personalised advertising” can read as nonsense. Have a fluent speaker check at least the first layer.
• Keep the same meaning across languages. Do not soften the description of tracking in one language and leave it plain in another.
• Use the formal or informal register your site uses elsewhere in that language.
• Check legal terminology with local counsel for markets where specific wording is expected.

4. Layout and Script

• Text expansion. Some languages need noticeably more space than English for the same message. Buttons must not truncate or wrap into unreadable shapes.
• Right-to-left languages. Arabic, Hebrew, Persian and Urdu need a mirrored layout: text alignment, button order and toggle direction. Check the preference centre too, not only the first layer.
• Fonts. Confirm that the banner font covers the script, including Cyrillic, Greek, Devanagari, Thai and CJK characters. Missing glyphs show as boxes.
• Equal prominence still applies. A longer reject label must not end up visually smaller than the accept button.
• Mobile widths. Test each language on a narrow screen, where expansion problems show first.

5. Vendor and Purpose Names

• Vendor names stay as they are; vendor descriptions and purposes should be in the user’s language where translations exist.
• Your own purposes, if you declare publisher purposes or non-TCF categories, need translations you maintain yourself. These are the strings most often left in English.
• Retention periods and data categories should be expressed in a format users understand, such as days or months in their own language.

6. Testing

1. Set the browser language to each supported language in turn and load a page in a clean profile.
2. Confirm the banner appears in the expected language and every button works.
3. Open the preference centre and scroll through all purposes and vendors looking for untranslated strings.
4. Change the site language and confirm the banner follows.
5. Test RTL languages on both desktop and mobile.
6. Check that consent given in one language is respected after switching to another, rather than prompting again.

7. Maintenance

• Track text changes. When you edit the English banner, record which translations must be updated.
• Re-review after vendor list updates, because new vendors and descriptions can appear untranslated.
• Watch consent rates by language. A sudden drop in one language often points to a translation or layout problem rather than a change in user attitudes.

How FlexyConsent Handles Languages

The FlexyConsent banner is available in 57 languages, so the first layer and preference centre can be shown in the visitor’s language without maintaining every string yourself. You still need to review the texts you write, such as custom purposes and your cookie policy.

Key Takeaways

• Informed consent requires a banner the visitor can actually read.
• Choose the banner language from the page first, then the browser, then a sensible fallback.
• Translate every layer, and use official TCF translations for standard texts.
• Test text expansion, RTL layouts and font coverage on mobile.
• Monitor consent rates by language to catch localisation problems early.