To translate a cookie banner, detect each visitor's language first. Translate every string: the message, the buttons, and the preference center. Localize the linked cookie policy too, then match the consent model to the visitor's region. Test each language before publishing. This matters because consent is only valid if the visitor actually understands what they are agreeing to.
This guide covers detection, translation, region matching, and testing, in six steps, plus the mistakes that quietly break a translated banner.
Why Does a Cookie Banner Have to Be in the Visitor's Language?
Consent is only valid when it is informed and given in plain language. A banner the visitor cannot read cannot produce valid consent. The UK's ICO states the basic rule plainly.
Tell people the cookies are there. Explain what the cookies are doing and why. Get the person's consent.
A visitor who cannot read the banner cannot meet that standard.
The EU's ePrivacy and GDPR framework backs this with the same principle.
Provide accurate and specific information about the data each cookie tracks and its purpose in plain language before consent is received.
That is gdpr.eu's own instruction to site owners. The ICO adds that valid consent must be "freely given, specific and informed." It requires "some form of unambiguous positive action" from the visitor.
Neither regulator names a hard "native language" mandate word for word. But the informed-consent requirement functions as one in practice. A banner in a language the visitor does not read cannot be informed. It therefore cannot produce valid consent.
For the full set of rules your banner must meet, see the GDPR cookie consent requirements guide. Translation is one piece of how to comply with cookie laws overall, not the whole task.
Translating the Text vs Changing the Consent Model (They Are Not the Same)
Translating the banner's text and changing its consent model are two separate jobs. Confusing them is the single most common translation mistake. The text is what the banner says. The consent model is what the banner must do, and the model is set by the visitor's region, not their language.
A German-speaking visitor in Germany needs the banner in German. They also need an opt-in model, so no cookies load until they click accept. A California visitor typically needs the banner in English. They need an opt-out model instead. Cookies can load by default, but a clear "Do Not Sell or Share My Personal Information" link must be present. Translating the text without adjusting the model leaves a banner that reads correctly and still fails the law that actually governs that visitor.
| Visitor region | Language need | Required consent model |
|---|---|---|
| EU / UK / EEA | Local language | Opt-in (no cookies before explicit accept) |
| US (CCPA/CPRA states) | Usually English | Opt-out (cookies can load by default, with a decline option) |
| Other opt-out regions (Canada, Brazil, South Korea, Japan) | Local language | Opt-out, with a visible way to object |
A consent platform with automatic geotargeting handles the model side of this automatically. It detects the visitor's region and switches between opt-in and opt-out on its own. The translation work and the compliance work do not have to be solved by hand at the same time.
What You Need Before You Start
Translating a cookie banner correctly requires three things. You need a consent tool that supports multiple languages and a real list of the languages your visitors use. You also need a proofreader for machine-translated legal text. Skipping the proofreading step is the prerequisite most people overlook.
You need:
- A cookie consent tool (or banner) that supports multiple languages, not just English. If you have not installed a banner yet, start with how to add a cookie banner before you translate it.
- A list of target languages driven by where your visitors actually are. Check your analytics by country rather than guessing.
- The full set of banner strings and your cookie policy, ready to translate together.
- A native speaker or professional translator to review any machine-translated output before it goes live.
- Roughly 30 to 60 minutes for a first pass across a handful of languages, more if you are translating a policy from scratch.
Step 1: Detect Each Visitor's Language Automatically
The banner should detect and match each visitor's language automatically. It should never show one fixed language to everyone. Three signals work well: the page's HTML lang attribute, the visitor's browser language setting, or the URL path (for sites with per-language URLs like /de/ or /fr/). When none of these match a supported language, the banner falls back to a default.
Consently detects the visitor's language from your site's HTML lang attribute. It falls back to your configured default language when there is no match, so you do not hand-code detection per page. This removes a common failure mode. Some consent tools ship English by default and never check the page's own language signal. A Reddit thread on consent-tool defaults confirms this pattern is common.
i18n-agnostic, ships English by default.
If you run a translation plugin (WPML, Polylang, or similar) alongside your consent tool, confirm it is not overriding the banner's own detection. A WooCommerce translation forum thread describes exactly this problem.
It just won't translate into German. There's no option to change the language from the plugin independently from the site.
The top-voted fix was simple: check whether the plugin is interfering with or overriding the banner output. This kind of plugin conflict is one of the gaps covered in making a WordPress site GDPR compliant.
Step 2: Decide Which Banner Strings to Translate
Every visible banner string needs translation, not just the headline message. Most help docs stop at "translate the banner text." That misses the preference center, the button labels, and the linked policy.
Translate all of these:
- The main banner message.
- Every button: Accept, Reject, and Manage (or Preferences).
- The preference center, including each cookie category's name and description.
- The linked cookie policy and privacy policy.
Consently's Language Manager covers the banner and preference center content together. Its policy generators output 10+ languages, so the linked policy does not stay in English while the banner is translated. Leaving the policy untranslated breaks the "informed" chain even when the banner itself reads perfectly. The banner links to the policy, and the informed-consent requirement covers what the policy explains, not just what the banner says.
Step 3: Translate the Strings (Auto-Translate, Then Proofread)
Auto-translation gets a first draft in place fast. But every string that shapes a legal choice needs a native-speaker proofread before it goes live. A machine mistranslation of "reject" or "consent" can flip the visitor's actual choice. That undermines the consent itself, not just the reading experience.
Consently gives you side-by-side editing, showing the default-language and translated content together. This works for both the banner and the preference center, across 35 languages. Editing default and translation in the same view removes a common friction point: juggling separate export files per language.
Proofread these first, in order of legal weight:
- The Accept, Reject, and Manage button labels.
- The category names and descriptions in the preference center.
- The main banner message.
- The linked policy text.
Step 4: Match the Consent Model to the Visitor's Region
Once the text is translated, the consent model still has to match the visitor's region. That means opt-in for the EU and UK, and opt-out for US states with privacy laws. A perfectly translated banner running the wrong model is still non-compliant. Translation and legal model are governed by two different variables: language and location.
Consently's automatic geotargeting serves an opt-in banner to EU and UK visitors and an opt-out model to US visitors. It can also load scripts by country code, so tracking scripts do not fire before consent where consent is required. This applies at the region level. It does not yet offer granular country-by-country show-or-hide rules beyond the opt-in/opt-out split. You do not need to maintain separate banner configurations per country to get the right legal behavior in each region.
Step 5: Handle Locale, Right-to-Left Languages, and Formatting
Some languages need visual adjustments beyond text swaps. Longer text needs more room, right-to-left languages need a mirrored layout, and dates need locale-correct formatting. German and Finnish translations commonly run noticeably longer than the English equivalent. That extra length can push buttons onto two lines if the banner's layout is not flexible. Right-to-left languages, such as Arabic and Hebrew, need the entire banner mirrored, not just the text direction. Buttons and close icons must land on the expected side. Dates in consent logs and policy documents should follow the visitor's locale format, not one hardcoded pattern.
A banner platform with custom CSS support lets you adjust spacing and layout for longer strings when the default controls are not enough. This is a general styling capability, not an automatic right-to-left layout feature. Verify RTL rendering visually rather than assuming it is handled for you.
Step 6: Test Every Language and Re-Check After Changes
Every translated language needs a live test, not just a preview in the dashboard. Preview each language first. Then load the actual site in that language by switching the browser or HTML lang setting, or by visiting the language-specific URL path. Confirm no English text leaks through anywhere in the banner or preference center.
Consently's live preview lets you check each language before publishing. This catches a missing or partial translation before a real visitor sees it. Test the live page too, not just the preview. A consent cookie can cache the banner in the first language it showed and skip re-detection on reload. A WooCommerce translation forum describes the fix. Open the site in a private or incognito window "to test fresh" whenever the banner still shows in English.
Re-run this full test whenever you add a new cookie category, change a button label, or add a new supported language. A single missed string is enough to break the pattern for that one language.
Common Cookie Banner Translation Mistakes to Avoid
The single most damaging mistake is translating the banner's visible text while leaving the consent model or the linked policy in the wrong state. That leaves a banner that looks correct and still fails the underlying legal requirement.
- Relying on the platform's native banner, which is often English-only. Shopify's own cookie banner tool is a documented example. A Shopify Community thread states plainly, "the Cookie Banner is only available in English. There is no option to localise it from the admin." Non-English visitors get an unreadable banner. The fix is to use a consent tool built to support multiple languages, rather than the storefront platform's built-in banner. See making a Shopify store GDPR compliant for the rest of that platform's compliance gaps.
- Translating the banner but not the linked cookie or privacy policy. The "informed" requirement covers the whole disclosure chain, and it breaks at the policy if that stays in English. The fix is to localize the policy alongside the banner, not as an afterthought.
- A missed or hardcoded string that still shows in English. One untranslated label makes the whole banner look broken and weakens the consent it produces. The fix is to translate every string, including button labels and category descriptions, then test.
- The consent cookie caching the wrong language. The banner fires once in the first language a visitor's browser or device suggested, then skips language detection on reload. The fix is to clear the consent cookie and test each language in a private or incognito window.
- Trusting raw machine translation for legal-facing text. A mistranslated "reject" or "consent" changes what the visitor actually agreed to. The fix is to have a native speaker proofread every button label and category description before publishing.
- Translating the text but not changing the opt-in or opt-out model by region. The banner reads correctly and is still non-compliant, because the model is set by region, not language. The fix is to geotarget the consent model, not just the visible text.
How Consently Serves Your Banner in Every Visitor's Language
Consently handles the full translation task end to end. It detects each visitor's language from your site's HTML lang attribute. It shows the banner and preference center in 35 languages with side-by-side editing of the default and translated content. It localizes the linked cookie policy in 10+ languages through its policy generator. It matches the consent model to the visitor's region through automatic geotargeting.
That combination covers the steps above in one place. There is no need to stitch together separate tools for translation, policy generation, and geotargeting:
- HTML
langdetection with a configurable default/fallback language. - Language Manager plus side-by-side editing across 35 banner languages.
- Policy generator output in 10+ languages, so the linked policy stays in sync with the banner.
- Automatic geotargeting for opt-in (EU/UK) vs opt-out (US) consent models, with country-code script loading.
- Live preview per language before you publish.
FAQs
Does a cookie banner legally have to be in the visitor's language?
Consent must be informed and given in plain language. A banner the visitor cannot read cannot produce informed consent. No single statute names a specific language requirement word for word. But the informed-consent standard from GDPR and the ICO functions as one in practice, so translate the banner to the language your visitors actually understand.
Can I just use Google Translate on my cookie banner?
Machine translation can draft a first version quickly. But legal-facing consent text needs a native-speaker proofread before it goes live. A mistranslated "reject" or "consent" button changes what the visitor actually agreed to, which undermines the choice rather than just reading awkwardly.
Does a cookie that only saves the visitor's language need consent?
A cookie that only remembers a visitor's language choice is generally functional and strictly necessary. It typically does not need consent. The UK ICO's guidance cites the Article 29 Working Party opinion that language-preference cookies fall within the strictly-necessary exemption. Disclose it in your cookie policy anyway, even without a consent prompt.
My platform's built-in cookie banner is English-only. What can I do?
Many native platform banners, including Shopify's, cannot localize from the admin panel. Install a consent tool built to support multiple languages over the platform's built-in banner. Confirm it detects visitor language automatically, rather than defaulting to one language for everyone.
Do I have to translate the cookie policy too, or just the banner?
Both. The banner links to the cookie or privacy policy. The informed-consent requirement covers what that policy explains, not only what the banner itself says. A banner translated into German that links to an English-only policy still breaks the informed-consent chain for a German visitor.
Why does my cookie banner still show in the wrong language?
Three causes are the most common. A translation plugin may override the consent tool's own language detection. A string may be missed or hardcoded in one language. Or a consent cookie cached the banner in the first language it showed. Clear the consent cookie, then test each language in a private or incognito browser window to confirm it is fixed.
How many languages should my cookie banner support?
Support the languages your visitors actually use. Your analytics can show this broken down by country. Do not support every language a consent tool offers by default. A site with visitors concentrated in three or four countries gains little from supporting 35 languages if 90% of traffic reads only two of them. Having more languages available still matters as your audience grows.
Ready to stop juggling a separate translation tool for your banner and your policy? Consently detects each visitor's language from your site's HTML lang attribute. It shows your banner and preference center in 35 languages with side-by-side editing, and keeps your linked cookie policy in sync across 10+ languages. Automatic geotargeting serves the right opt-in or opt-out model by region at the same time. See how it fits your setup on the multi-language cookie banner page, or try Consently free and translate your first banner today.
