English, Kiswahili or Both? Planning a Bilingual Website for Your Customers

c
ceofounder
11 min read 44 views
English, Kiswahili or Both? Planning a Bilingual Website for Your Customers
EN SW

English, Kiswahili or Both? Planning a Bilingual Website for Your Customers

A language switch is a tool — not a magic solution. Here's how to make a bilingual site genuinely useful to the people you serve.

Adding Kiswahili to a website can be valuable when customers genuinely need it, but a language switch is not a magic solution. Poor translations, missing pages or different prices across language versions can damage confidence. Before commissioning a bilingual site, decide who needs which information, how translations will be approved and how both versions will stay current.

Start with audience tasks

Identify the actions visitors must complete:

  • Understand a service
  • Compare options
  • Apply for membership
  • Register for a course
  • Contact the organisation

Review customer questions and feedback to learn where English creates friction and where Kiswahili would make the explanation clearer.

A bilingual website should respond to a real communication need, not a vague assumption about what looks local.

Translate meaning, not word order

A literal translation can sound unnatural or change the meaning of a promise. Use a person who understands the subject and audience to review important wording. Keep prices, eligibility, operating hours, service conditions and other factual details aligned across versions. For technical or regulated material, a fluent reviewer should be able to flag ambiguous wording before publication.

✗ Word-for-word

Word order carried across — sounds unnatural, and the promise may shift.

✓ Meaning-first

Reviewed by someone who understands the subject and the audience.

Choose which pages need both languages

A small business may start with the homepage, key service pages, enquiry process and essential policies in both languages, then expand based on demand.

Do not provide a language switch that sends visitors from a complete English page to an empty Kiswahili homepage. Where a page is not yet translated, be transparent and provide a useful route back to available information.

Plan navigation and search

Make the language selector easy to find and label it clearly. Keep visitors on the equivalent page when they switch languages, where a translation exists. A developer should implement language URLs and search metadata consistently, then check that search engines can discover the intended versions.

Read Google's guidance on international and multilingual sites before finalising the technical structure.

Assign ownership for updates

If a price changes or a service is discontinued, both language versions need to change. Assign responsibility for translation review, define an approval process and keep a list of pages that require parity.

If resources are limited, a smaller, maintained bilingual site is better than many outdated pages in two languages.

Build a shared terminology list

Before translating many pages, agree how the organisation will render important service names, roles, eligibility terms and technical concepts. Some English terms may be familiar to the audience; others need a plain-language explanation rather than a direct equivalent. A shared glossary reduces inconsistency when different people write or review pages and makes future updates less expensive.

Why a glossary helps

One agreed rendering per term means every page — and every reviewer — stays consistent.

Service name→ one approved form
Roles & eligibility→ explained, not assumed
Technical concepts→ plain language where needed

Keep the language versions discoverable

The language switch should be visible without dominating the page. Where the other language version exists, send visitors to the equivalent page rather than dropping them at the other language's homepage. Ensure titles, descriptions and navigation make the language of each page clear. Ask the developer to test canonical and alternate-language signals as appropriate for the chosen URL structure.

Budget for review, not only translation

A translation estimate should include proofreading, subject-matter review, page layout checks and the work needed when the English source changes. Text lengths can differ between languages and may affect headings, buttons or mobile layouts.

For a small organisation, begin with a smaller set of high-value pages that can be maintained reliably rather than translating the full site and leaving half of it outdated.

Measure whether language choice helps

Look for useful signals — not simply how often people click the language selector:

  • Completed enquiries
  • Successful application starts
  • Support questions
  • Feedback from visitors

Use these observations to decide which pages to translate next and where explanations remain unclear. Avoid collecting more personal information than needed for this review, and interpret the results in light of traffic volume and audience differences.

A low-risk way to introduce a second language

1

Review customer questions and identify the pages where language has the greatest effect on understanding or action. Agree which audience each translated page is intended to help.

2

Write or review a terminology list for service names, processes and common questions. Translate a small set of important pages, then ask fluent reviewers who understand the subject to check meaning, tone and consistency. Test the page layout because longer phrases may change the design.

3

Assign an owner to update both versions whenever the underlying facts change. Track whether visitors complete the intended task and collect feedback about unclear wording. Expand the translated content only when the organisation has the capacity to maintain it accurately.

Example

A community training provider may find that course descriptions and registration instructions are the most useful pages to translate first, while technical reports can remain in English if that is how the audience expects to access them. The decision should follow reader needs and the team's ability to maintain both versions.

Frequently asked questions

Should every page be translated?

Translate pages that serve real audience needs and that the organisation can keep current. Expand based on demand and capacity.

Can machine translation be used?

It may help with an initial draft, but important service, legal or policy wording should be reviewed by a competent human.

Action checklist

  • The audience and purpose for each language are clear.
  • Key pages have accurate, reviewed translations.
  • Switching languages preserves the visitor's task where possible.
  • Prices, policies and dates stay consistent.
  • A named owner is responsible for future updates.

Final thought

A bilingual website works when the organisation treats language as an ongoing content responsibility. Start with the journeys that matter, use human review for meaning, and plan maintenance before expanding the page count.

Does your audience need a bilingual online presence?

Discuss the scope with Stonehenge Digital KE through our Portfolio & Organisational Website service — and plan a version you can keep accurate in both languages.

Explore the Portfolio & Organisational Website Service →
Share Written by ceofounder

Interested in Portfolio & Organisational Website?

Let's build this for your business

A professional, mobile-first website that makes your business look credible and gets found on Google.

Leave a Comment

Share Your Thoughts