Banner language that does not match the site: a consent validity problem, not a translation nicety

GDPR consent must be informed, and the transparency articles require information to be concise, intelligible, and in clear and plain language. A purposes panel in a language the visitor does not read fails that standard in the most literal way available. It does not matter that the text was present and the button was clicked. The informational precondition of the click was missing for that visitor.

Regulators have not treated this as pedantry. Guidance from several European authorities expects consent information in the language of the service offered to the user, and cross border services are expected to handle the languages they market in. If your storefront actively sells in a language, with prices, terms, and support in it, the consent flow is part of that storefront. Arguing the banner is a separate system gets the shrug it deserves.

Informed means understood, not merely displayed

Banner headlines are easy to translate. The purposes layer is where it breaks: vendor supplied purpose descriptions, written in English legal shorthand, run through machine translation into twenty languages nobody at the company reads. Purposes like functional purposes or user experience measurement come out the other side as fluent nonsense, or worse, fluent statements of a different purpose than the one the tags actually serve.

A misdescribed purpose is not a translation defect, it is a specificity defect. Consent given to purpose A does not cover processing for purpose B, and if your German text describes A while your tags do B, the consent is invalid for B in German. Commission real translation for the purposes and vendor layers once, maintain it like the legal text it is, and freeze the tag behaviour to match what the text says in every language.

Purposes are the text that must be right

Language follows the interface. The consent flow renders in the same locale as the page the visitor is on, driven by the same locale signal as the rest of the site, not by a separate banner tool guess from IP address, which misfires for travellers and minority language users alike. The consent record stores the language and version of the text shown, because your proof of what the visitor agreed to is only meaningful attached to the text they actually saw.

Patterns for multi language sites that hold up

Keep reading: Vendor purpose mapping errors: the tag that fires for a purpose nobody consented to, Consent timestamps and clock skew: when your proof of consent argues with itself.

The settings page is part of the banner

Fallbacks need a rule too. Where a full translation genuinely does not exist yet for a new market, the honest interim is the site language of that market storefront if one exists, plus a plan to close the gap, not a quiet English default on a storefront that otherwise speaks the local language fluently. The gap is a launch defect. Schedule it like one.

Withdrawal must be as easy as giving consent, in every language you took consent in. A settings page that exists only in English, linked from a French banner with an English label, makes withdrawal materially harder for the French visitor, which is the asymmetry regulators look for. Translate the withdrawal path with the same priority as the capture path, labels, purpose toggles, and the confirmation that the change took effect.

Test it as a user journey per language: arrive, read purposes, refuse, reopen settings a week later, withdraw one purpose, confirm the tags obey. If any step changes language mid journey, you have found the defect your next complaint will describe, in whichever language it arrives.

Frequently asked questions

Must the cookie banner be in the same language as the website?

In substance, yes. Consent must be informed and information must be intelligible to its audience, so consent information should be provided in the language in which the service is offered to that visitor. A site actively marketed in a language should carry its banner, purposes, and settings in that language.

Is machine translation acceptable for consent purposes?

It is risky. Purpose descriptions are legal statements defining what consent covers. Machine translation errors can misdescribe a purpose, and consent for a misdescribed purpose does not cover the actual processing. Use reviewed translation for the consent layer and keep tag behaviour matched to the text.

What language should be recorded in the consent log?

The language and the version of the notice and purposes text actually shown to the visitor for that consent event. Without that, you cannot demonstrate what the visitor was told, which is part of demonstrating consent. Store it per event, not as a site level assumption.

Does the consent settings page need translating too?

Yes. Withdrawal must be as easy as giving consent, for every audience you took consent from. A settings and withdrawal path available only in another language makes withdrawal harder for those visitors and creates exactly the asymmetry regulators criticise.