Agree on the message before the wording
A bilingual page should begin with an agreed account of what the reader needs to understand and do. Write that intention in plain language before polishing either version. This is especially useful when one language favours a compact phrase while the other needs a more explicit explanation. The two texts can then be judged against the same purpose without requiring identical sentence structures. A shared message brief also helps reviewers distinguish a meaningful difference from a harmless stylistic choice, keeping the discussion focused on the reader’s understanding rather than a word-by-word contest between versions.
Build terminology around real use
A terminology list becomes useful when it includes context. Record the preferred term, its meaning in this project, an example sentence and any alternative that would create confusion. Some technical expressions need a stable translation; some brand phrases need an explanation of the idea they are intended to carry. Ask subject specialists and editors to review the same examples. This reveals cases where a technically familiar term is unclear to the intended audience, and cases where an elegant phrase blurs a distinction that matters. The list should support decisions during production, not merely document them afterwards.
Design the page with both texts present
Text length changes the pace of a page. A headline that sits comfortably on two lines in one language may occupy four in another, shifting the relationship between image and copy. Review layouts with actual bilingual text early enough to adjust hierarchy and spacing. Avoid solving every difference by shrinking type or shortening a sentence until its meaning disappears. Sometimes the better response is a different line break, a more flexible content area or a revised headline in both languages. Treat the visual and editorial decisions as one conversation, with readability as the common standard.
Review the reader’s journey twice
A translation can be accurate sentence by sentence while the page feels unnatural as a whole. Read each language continuously, including navigation, captions, buttons and short supporting labels. Check whether the argument develops in a sensible order and whether the next action is clear. Then compare the versions for material differences in claims, scope and emphasis. These are distinct review passes with different purposes. Keeping them separate gives each language a coherent voice while preserving the shared editorial intention, rather than accepting a page that is formally equivalent but difficult for either audience to read.
Keep updates paired and accountable
Bilingual consistency often weakens after launch, when small changes are made in only one language. Define how an edit is signalled to the owner of the other version and how its significance is assessed. A corrected date may need a direct update; a changed product description may require a fresh editorial review. Keep the relationship between corresponding content items visible so that a redesign does not break it. The ongoing process should make it easy to see which version has changed and what remains to be reconciled, without relying on somebody remembering to send a message later.
Editorial draft prepared for the BGX concept preview. This is not a regulatory announcement or evidence of a deployed client project.
