A bilingual website needs paired content, predictable language links and a maintenance process that keeps both versions current.
Pair equivalent pages
Give each language a stable URL and map equivalent pages explicitly. The language switch should open the same topic, not always the homepage. Decide how to handle a page awaiting translation. Do not label an English body as BM merely because its navigation is translated.
Translate meaning and interface text
Review headings, forms, validation errors, buttons and confirmation messages as well as article text. Use a shared terminology list for technical services. Preserve numbers, units and qualifications. Allow for different text lengths in the layout instead of forcing both languages into identical line breaks.
Keep revisions synchronised
Record which language version changed and whether its pair needs review. Test language links and metadata after publication. Assign a reviewer familiar with the subject, not only the language. A practical release checklist includes both contact journeys so one version does not send users to an outdated form.