A bilingual website needs a clear plan for its content and maintenance. Adding a language menu is only useful when visitors can reach complete, reviewed information in the language they choose.
For a candidate or political party publishing in English and Kiswahili, the key decisions concern scope, translation responsibility and how both versions will stay current.
Decide which pages will be bilingual
List the essential pages before commissioning translation. The introduction, biography, published documents and contact instructions are reasonable places to begin.
You may choose to translate every article or maintain a smaller, clearly defined bilingual core. State that scope in the project brief so the team knows what must be supplied and reviewed.
Do not describe the whole site as bilingual if the language switch only changes navigation labels while leaving the main information untranslated.
Translate the complete visitor journey
A page includes more than its main paragraphs. Navigation, image descriptions, form labels, error messages and confirmation text all affect usability.
Prepare these interface details as part of the translation pack. A visitor should not have to switch languages unexpectedly to understand how to submit an enquiry or recover from a form error.
Also check downloadable documents. A translated introduction should identify accurately which language the linked file uses.
Give translations an approval owner
Machine translation can support preparation, but important public information needs a fluent reviewer who understands the original meaning and context.
Provide the translator with approved names, role descriptions and terminology. Keep a short terminology record for words that recur across the site.
Ask the reviewer to check meaning and readability rather than requiring an exact word-for-word structure. Record approval for the version actually uploaded.
Plan separate language addresses
Discuss the language structure with your developer before pages are created. A consistent arrangement might use an English page and a corresponding Kiswahili page under separate addresses.
Google’s guidance recommends different URLs for different language versions and explains how language annotations can identify their relationship. These technical details should be implemented and tested by the developer. See Google’s multilingual website guidance.
The arrangement should remain understandable to editors as well as visitors.
Make language switching predictable
Use clear language names and keep the switch in a consistent location on desktop and mobile.
Where a matching translation exists, the switch should take the reader to that version of the same content. Sending every click back to the homepage can interrupt the task.
If a page has no translation, decide how to communicate that clearly. Avoid pretending that an unrelated destination is the equivalent page.
Publish linked changes together
Create an update record with the original page, translated page, approval status and publication date. When a biography or contact route changes, the record helps the team identify both places that need attention.
Urgent corrections need a defined process too. Decide who can approve the source change and who prepares the corresponding translation.
This becomes especially important when news content is updated by several contributors.
Test with fluent readers
Ask reviewers to complete real tasks in each language: find the biography, open a document and submit a test enquiry.
Check whether the text fits buttons and menus without clipping. Longer translated phrases can expose layout problems that do not appear in the first language.
Read the shared-link preview as well. Its title and description should match the page a visitor will actually open.
Budget for continuing translation work
The initial translation is part of a wider commitment. New pages, updated forms and revised publications may all require additional review.
Include responsibilities and expected turnaround in the support agreement. A smaller set of complete, maintained pages can be easier to manage than a broad bilingual site with outdated sections.
Top Web Design Kenya can help define the page structure and development scope for an English and Kiswahili website. Bring your approved content, available reviewers and expected update frequency when requesting a quote.
Explore our political website design service or request a website quote. Call 0721 985 722 or email mail@topwebdesign.co.ke.