Consent Banner Language: The Translation That Changes the Opt-In Rate

A visitor lands on your site from Lyon, sees a consent banner in English, and clicks Accept, because the button is the only thing they understand. That click is not consent. Consent has to be informed, and a choice made in a language the visitor does not read is not informed, whatever the CMP recorded. The banner language is not a localization nice-to-have. It is the difference between a valid consent record and a record that falls apart the first time anyone looks at it.

The banner has to speak the visitor's language

GDPR Article 4(11) defines consent as freely given, specific, informed, and unambiguous, and the EDPB's Guidelines 05/2020 spell out what informed means: the visitor has to understand what they are agreeing to, which purposes, which vendors, and what happens if they refuse. A banner in English shown to a visitor who reads French fails that test on its face. The purposes are listed in a language they cannot read, the vendor list is in a language they cannot read, and the refuse button is labelled in a language they cannot read. The CMP will record an accept and the record will look clean. The record is clean the way a signed contract in a language the signer does not speak is clean: it holds up until someone asks.

The fix is not a language selector on the banner. It is detecting the visitor's language from the browser and showing the banner in it, the same way the site already shows its content in the visitor's language. Most CMPs support this and most sites never turn it on, because the banner was configured once, in English, and nobody revisited it. The CNIL's guidance is explicit that the information has to be clear and intelligible, and a banner that is clear in English and opaque in French is not clear to the French visitor. The cost of turning on language detection is an afternoon. The cost of a consent record that is not informed is the record itself.

Translation is not just the buttons

Translating Accept and Reject is the easy part and the part most sites do. The hard part is the purposes, the vendor list, and the second layer, where the actual information lives. A banner with translated buttons and an untranslated purpose list is a banner that lets the visitor accept what they cannot read, which is the same failure with better buttons. Translate the whole banner, including the second layer, or do not claim the consent is informed. The reject-all button has the same shape of failure: a rule that killed the buried refuse link, because a choice the visitor cannot find is not a choice. TCF Purpose 1 has the same problem in a different form: legitimate interest does not work for storage, and a purpose description the visitor cannot read does not inform them either way.

Test it from the visitor's browser

Set your browser language to French, clear the consent cookie, and load your site. Read the banner. If it is in English, the language detection is off. If it is in French but the second layer is in English, the translation is incomplete. If the refuse button is in French and the purposes are in English, the consent is not informed. The test takes three minutes and it is the test every non-English visitor runs on your site without telling you the result. Run it for each language your site serves, and run it again after every CMP update, because updates reset language settings more often than anyone admits.

Keep a record of the languages the banner supports and the date each translation was last reviewed. A translation that was right two years ago and has not been checked since is a translation that has drifted, and a drifted translation is a banner that no longer says what you think it says.

Frequently asked questions

Does my consent banner need to be in the visitor's language?

Yes. GDPR consent has to be informed, and a visitor cannot be informed by a banner in a language they do not read. The EDPB's Guidelines 05/2020 require the visitor to understand the purposes, the vendors, and what refusal means. Show the banner in the browser's language.

Is translating the Accept and Reject buttons enough?

No. The buttons are the easy part. The purposes, the vendor list, and the second layer are where the information lives, and those have to be translated too. A banner with translated buttons and an untranslated purpose list lets the visitor accept what they cannot read.

How do I test my banner language?

Set your browser language to one your site serves, clear the consent cookie, and load the site. If the banner is in the wrong language, or the second layer is untranslated, the language detection or the translation is incomplete. Test each language after every CMP update.

What happens if the consent was not informed?

The consent record is not valid, and the processing it authorized has no legal basis. The record looks clean in the CMP, but it falls apart when anyone checks whether the visitor understood what they agreed to. Language is the first thing a regulator checks, because it is the easiest to verify.