Consent Banners on Multilingual Sites: Translation Is a Legal Task
Most multilingual sites translate their marketing copy carefully and their consent banner as an afterthought, sometimes automatically, sometimes by whichever vendor string file shipped first. The banner is the one text on the site whose exact wording carries legal weight in every market at once.
This guide covers how to manage consent language as controlled legal text: translation workflow, version records per language, the button wording traps, and how regional differences should shape one system without becoming five inconsistent ones.
Consent text is not marketing copy
A translated banner that softens a purpose, renames a category to something friendlier, or turns reject into a vaguer phrase has changed what visitors agreed to, and in the strict markets, whether they agreed at all. Treat source wording as controlled text: legal approves the master, professional translators with legal experience render it, and a native reviewer checks that category names and button labels mean the same action in each language. Keep a glossary so the same purpose is named identically across the banner, the preference center, and the cookie policy in every language.
Version the record per language
A consent receipt should capture the notice version and the language it was shown in. When wording updates roll out at different speeds across locales, and they always do, the record is the only way to prove what a specific visitor actually read. Configure the platform so language and version travel with the consent ID, and audit the preference center in each locale after every release. The classic failure is a banner updated in the primary language while three locales quietly serve last year text with categories that no longer exist.
Buttons and equal prominence in every locale
The rule that reject must be as easy as accept survives translation only if someone checks it per language. Long translated labels push buttons off mobile screens, right to left languages flip layouts in ways that break prominence, and polite phrasing in some languages can make the decline option read as agreement. Test the banner in each language on a phone, complete a decline, and confirm the stored state matches the intention. A screenshot set per locale, refreshed at each wording change, is cheap evidence of diligence.
Regional rules beneath shared wording
Markets differ in defaults, in what needs opt in versus opt out, and in which purposes are even permitted. A single global banner text with regional rule sets behind it is the workable architecture: shared structure and glossary, market specific defaults and legal bases configured per region, and wording variants only where the law actually diverges. Resist the opposite patterns, one naive global setting for everyone, or fully independent local banners that drift into contradicting each other about the same processing.
Related reading
These earlier guides cover connected questions in more depth: Consent for Server Side Tagging: The Gateway Changes Nothing and Everything, Consent or Pay: How 'Accept Tracking or Subscribe' Models Work, and Consent in Progressive Web Apps: When the Site Works Offline and the Banner Logic Does Not.
Frequently asked questions
Can we machine translate the banner to launch a new locale fast?
As a draft for professional review, yes; as the live legal text, no. Automated translation mishandles exactly the terms that matter, consent, legitimate interests, and category names. Launching a locale with unreviewed consent text trades a small delay for a large validity question.
Which language governs if translations disagree?
From a regulator or visitor perspective, the language the visitor was shown governs what they agreed to. That is why per language version records matter: the master document in your files is not the text anyone consented to in another market.
Do we need separate consent per language version of the site?
Consent follows the visitor and their choices, not the language toggle. Switching languages should not reset or duplicate consent; the state persists, while the record keeps the language in which the choice was originally made.
How often should translations be rechecked?
At every source wording change, every platform template update, and at least annually. Add a locale spot check to the consent audit: one decline and one partial acceptance per language, verified against stored receipts.