Your Banner Speaks One Language. Your Shoppers Read Five.
A consent banner a visitor cannot read produces clicks, not consent. Auditing banner language coverage against your actual traffic, and why machine translated legal text creates its own risk.
Consent is supposed to be informed, and informed has a language requirement nobody wrote into the banner vendor's default settings. A store drawing a fifth of its traffic from Spanish, German, and French speakers shows every one of them a legal choice written in English, records their click on the button they could locate by shape, and files it as consent.
The problem is easy to measure and slightly harder to fix well, because legal text punishes casual translation. This post sets out how to audit the gap between your traffic's languages and your banner's, what regulators expect, and a practical order for closing it without translating your entire privacy operation overnight.
Measuring the gap
Pull three months of traffic by browser language, not by country, because a German speaker in Ohio still reads German and an English speaker in Berlin reads English. Browser language is the honest denominator. Then list the languages your consent platform is actually configured to serve, with the trigger rule for each: many banners switch on store language or visitor geography, which mismatches exactly the visitors most likely to need the translation.
On most international stores the audit finds the same shape: two or three languages covering four fifths of traffic are missing or machine served with errors, while the vendor dashboard shows language support as a green tick because the feature exists in the account, unconfigured.
What good coverage looks like
The banner and the preference centre need the translation, not just the accept button. A visitor who can read 'Accept all' but cannot read the toggles describing advertising, analytics, and sharing has been given the appearance of a choice with the substance removed, which is precisely the imbalance dark pattern guidance criticises. Purpose descriptions, the do not sell page, and the privacy notice summary belong in the same language set, in the same quality tier.
Quality tier is a real decision. Consent text is short, a few hundred words per language, which makes professional translation cheap relative to its legal weight. Machine translation of the banner buttons is common and mostly harmless; machine translation of purpose descriptions and rights language produces sentences that are fluent, confident, and subtly wrong about what the visitor agreed to.
Sequencing the fix
Translate in traffic order, top language first, banner plus preference centre plus do not sell page as one bundle per language. Set the trigger to browser language with a visible manual switcher, because auto detection will guess wrong for bilingual users and the switcher is their remedy. Then add the language set to your consent record: logging which language version a visitor saw is part of proving what they were told.
Related reading: A Practical Audit Checklist for Consent Mode Signals, Consent for Email Capture Popups: Keeping the Ask and the Record Honest, Consent for Embedded Video and Marketing Pixels.
Frequently asked questions
Is a banner in the wrong language legally valid consent?
It is vulnerable. Consent standards require information to be intelligible to the person giving it, and a choice presented in a language the visitor cannot read undermines the informed element, particularly where the same store markets and sells in that visitor's language elsewhere on the site.
Which language should trigger the banner translation?
The visitor's browser language setting is the most accurate signal, better than geography or store locale. Always pair it with a visible language switcher on the banner itself, because browser settings are sometimes inherited from a device or employer and the visitor needs a way to correct the guess.
Can we machine translate the consent text?
For button labels, the risk is low. For purpose descriptions, rights statements, and the do not sell flow, use professional translation: the text is short, so the cost is small, and machine output can be fluent while misstating what a toggle controls, which is the sentence the whole record depends on.
What should the consent record store about language?
The language version presented, alongside the usual timestamp, policy version, and choices made. If a consent is ever questioned, being able to show the visitor was informed in a language they read is a material part of the answer.