A Complianz banner in the wrong language can come from the site's language, untranslated custom banner text, the multilingual route or cached output. Changing your own WordPress administrator language is not a reliable fix for what visitors see.
Identify which text is wrong
Compare a fresh visit to the same page in each supported language. Record the visible banner text, button labels, linked policy URL and page language. Do not reset real visitors' consent choices just to force a banner for testing; use an isolated test browser profile.
Separate four things: the WordPress interface, the visitor-facing banner, custom text you entered and the generated legal document. A translated policy page does not prove that the banner strings were translated. A translated banner does not prove its buttons link to the correct policy.
Complianz's language configuration guide and WPML translation workflow distinguish site language, multilingual content and custom strings. Follow the workflow for the actual multilingual plugin installed, not a screenshot from a different setup.
Trace one language all the way through
For a hypothetical English and Spanish site, create a small evidence sheet:
| Location |
English route |
Spanish route |
| Page language |
English content |
Spanish content |
| Banner buttons |
Approved English labels |
Approved Spanish labels |
| Custom explanation |
Current English revision |
Matching translated revision |
| Policy destination |
English policy URL |
Spanish policy URL |
If only a custom sentence stays English, inspect the saved custom string and translation status. If the whole banner switches unpredictably, check the language route, cookie behavior and cache variation. If only the administrator sees the difference, compare an ordinary logged-out visitor before changing public configuration.
English route: Approved text and destination. Spanish route: Matching translated revision. Return visit: Language stays intentional. Consent choices: Meaning and behavior preserved. Explanatory checklist, not a customer test result.
Publish the translation and test the cache boundary
Save and complete the translation workflow, then confirm the visitor-facing string actually changed. A draft translation visible in an editor is not the same as published output. Clear only the relevant page or language cache after the saved configuration is correct.
Test the sequence English page, Spanish page, then English again. Repeat in a fresh profile. This distinguishes a route-specific translation problem from a language value that is retained across navigation. Do not solve it by hardcoding one language globally when the site intentionally serves several.
Preserve the meaning of the choices
Have an appropriate reviewer approve consent wording and button meanings. This is a technical translation workflow, not legal advice about which consent rules apply. Confirm accept, reject and preference-saving behavior remains consistent with the site's approved setup. A translated label must not reverse the underlying action.
If the banner language is correct but the tag-manager integration is missing, use the Complianz GTM field guide. Keep that integration task separate from translation edits.
For help with a multilingual banner problem, provide the affected language URLs and redacted test observations. The useful deliverable is correct visitor text and behavior on each route, not simply a translated administration screen.
References reviewed October 14, 2026. Examples are explanatory, not customer test results.