For a Pan-African NGO, a website is often expected to serve audiences across multiple countries, cultures and language communities.
An organisation may have its headquarters in Nairobi, programmes in Kenya, Uganda and Tanzania, partnerships in Francophone West Africa, donors in Europe, and beneficiaries or community partners who communicate primarily in local languages.
A website designed only around English can therefore create an unnecessary barrier between the organisation and some of the people it is trying to reach.
Multilingual website design is more than translating an English website into French or another language. A genuinely multilingual NGO website needs to account for content management, user experience, search engine optimisation, accessibility, translation workflows, cultural context, different writing systems and, in some cases, right-to-left languages such as Arabic.
For Pan-African NGOs, these considerations should be addressed from the beginning of the website project rather than added as an afterthought.
A multilingual NGO website provides substantially the same organisation, programmes, services and resources in two or more languages.
For example, a Pan-African NGO might offer:
The appropriate combination depends on the organisation’s geographic footprint and audiences.
A multilingual website may allow users to switch between languages using a language selector. Each language can have its own translated pages, navigation, forms, resources and calls to action.
However, multilingualism does not necessarily mean that every piece of content must be translated immediately.
An NGO could launch with English and French, for example, while creating a content architecture that allows Kiswahili or Portuguese to be added later without rebuilding the website.
This is an important distinction.
A multilingual website should be designed for multiple languages even if all of those languages are not launched on day one.
Africa is linguistically diverse. An NGO working across several countries may encounter very different linguistic environments from one programme location to another.
Language therefore affects more than communication. It can influence:
The United Nations treats multilingualism as an important component of its communications and digital presence, and its web guidance specifically recommends considering multilingualism from the beginning of a website project rather than treating it simply as a translation exercise.
For a Pan-African NGO, the same principle is highly relevant.
If a significant portion of an organisation’s audience speaks French, for example, having an English-only website can limit the organisation’s ability to communicate effectively with Francophone partners, institutions and communities.
One of the biggest mistakes NGOs make is treating multilingual website development as a simple translation project.
Translation asks:
How do we convert this English content into French?
Multilingual website design asks a much broader question:
How should this digital experience work for people using different languages and cultural contexts?
The second question affects the entire website.
It can influence:
The W3C describes internationalisation, or i18n, as designing and developing websites and digital products so they can be adapted to different languages, cultures and regions. This extends beyond translating words to considerations such as writing systems, text direction, dates, names and cultural conventions.
That distinction should influence how an NGO approaches its website project.
The first question should not be:
“Which languages can we translate the website into?”
Instead, ask:
“Which audiences need to use our website, and what languages do those audiences actually use?”
Start with the countries where the organisation:
Then identify the dominant languages relevant to each audience.
For example:
| Region | Potential Priority Languages |
|---|---|
| East Africa | English, Kiswahili |
| Francophone West Africa | French |
| Lusophone Africa | Portuguese |
| North Africa | Arabic, French |
| Southern Africa | English, Portuguese and local languages depending on programme |
| Central Africa | French, Portuguese and local languages depending on country |
This is only a starting point. Language priorities should be based on the actual audiences and programmes of the organisation.
An NGO may have different language requirements for different audiences.
For example:
This does not necessarily mean the entire website needs to exist in every language.
Instead, the organisation can prioritise languages according to user needs.
If the NGO already has a website, analytics can provide useful evidence.
Review:
If a substantial number of visitors come from Francophone countries but the website is English-only, that may be evidence for prioritising French.
For many Pan-African organisations working across Anglophone and Francophone Africa, English and French are logical languages to consider.
This can be particularly relevant to organisations operating across regions such as:
However, adding French should not simply mean placing machine-translated English content on a second set of pages.
The French version should be professionally reviewed for:
The same principle applies to any other language.
Not necessarily.
A useful multilingual content strategy can divide website content into tiers.
These pages should usually be available in all primary website languages.
Examples include:
Translate content that is directly relevant to the audiences using a particular language.
Examples:
Not every publication necessarily needs to be translated.
Depending on the NGO’s strategy, it may make sense to translate:
News can require a more flexible approach.
An NGO publishing several articles per week may not have the resources to translate everything immediately.
Instead, it could establish rules such as:
The important thing is to establish a publishing policy rather than creating an expectation that every piece of content will always be available everywhere.
Translated text does not always occupy the same amount of space.
A heading that is short in English may become significantly longer in French or another language.
This can create problems with:
For example, a button designed to fit a short English phrase may wrap awkwardly when translated.
A multilingual website should therefore avoid layouts that assume every translation will have the same length.
Designers should test realistic translated content during the design process.
This is especially important for NGOs.
If a graphic contains English text embedded directly into the image, translating the website does not automatically translate the graphic.
Instead of creating one image containing text, consider:
This also improves accessibility and makes content easier to maintain.
The UN’s multilingual web standards similarly recommend avoiding design approaches that depend heavily on letters or language-specific text as graphical elements because they can become difficult to adapt between languages.
Arabic introduces an additional design consideration.
English, French, Portuguese and Kiswahili generally use left-to-right writing systems.
Arabic uses a right-to-left writing direction.
A website that supports Arabic therefore needs more than Arabic translations.
The interface itself may need to change direction.
This can affect:
The W3C specifically identifies text direction as an internationalisation consideration, while UN web guidance highlights the need to account for switching between left-to-right and right-to-left versions of a multilingual website.
This is one reason multilingual requirements should be established before the website’s visual system is finalised.
Typography is often overlooked in multilingual projects.
A font that looks excellent in English may have poor support for another script or language.
When selecting typography, verify:
The website should also handle Unicode correctly.
For organisations expecting to add languages in the future, font selection should be based on the anticipated language set rather than only the initial English website.
Multilingual websites also have technical requirements.
The HTML document should identify the language being used. Where content switches to another language within a page, the relevant language should also be identified.
For example, an English page should identify English as its primary language, while the French version should identify French.
W3C guidance recommends declaring the default language on the HTML element and using appropriate language tags based on established language standards.
This helps browsers, assistive technologies and other software interpret content correctly.
A multilingual website should generally give each language version a stable, indexable URL.
Common approaches include:
example.org/en/example.org/fr/example.org/sw/Another approach is language-specific subdomains, such as:
en.example.orgfr.example.orgFor most NGOs, language directories are often easier to manage within a single website architecture.
The important thing is consistency.
Each language should have its own predictable URL structure rather than relying entirely on cookies, browser settings or JavaScript to change the language.
Translation can also create significant SEO opportunities.
Instead of competing only for English searches, an NGO can potentially attract users searching in:
However, simply translating keywords word-for-word is not enough.
Search behaviour differs between languages.
A phrase that users search for in English may not have the same literal search equivalent in French or Kiswahili.
For each major language, research:
Each language version should have appropriate:
Do not simply copy English metadata into the French version.
Multilingual websites should also implement appropriate international SEO architecture.
Where relevant, hreflang annotations can help search engines understand the relationship between different language or regional versions of pages.
For example:
This needs to be implemented consistently. Incorrect language annotations can create indexing problems rather than solving them.
AI translation tools can be useful for accelerating workflows, but NGOs should be careful about publishing machine-generated translations without human review.
This is especially important for:
The United Nations’ multilingual website guidance explicitly recommends high-quality human translation and cautions against relying on automatic translations or translations produced by people without sufficient language expertise.
A practical approach can be:
AI or machine translation → professional human review → publication
rather than:
English content → automatic translation → immediate publication
The website should have a defined process for publishing multilingual content.
For example:
This is particularly important for NGOs that publish frequently.
Without a workflow, the website can quickly become inconsistent.
One language may have current programme information while another has outdated content.
A multilingual CMS should have a clear relationship between translations.
For example:
English page
If the English version changes, the CMS or editorial workflow should make it clear that the translated versions may now be outdated.
The website can display statuses such as:
This becomes increasingly important as the number of languages and content editors increases.
The content management system is central to multilingual NGO websites.
The CMS should allow editors to manage multiple language versions without creating unnecessary duplication.
Important capabilities include:
For a large NGO, multilingual capability should be evaluated before choosing a CMS.
It is much easier to build multilingual functionality into the architecture than to retrofit it after hundreds of pages have been published.
Forms are frequently forgotten during translation.
A French version of the website should not send French-speaking users to an English-only application form unless there is a clear reason.
Consider translating:
The confirmation messages should also be localised.
For example:
Thank you. Your application has been received.
should not suddenly be followed by an English-only confirmation page on a French website.
For NGOs fundraising across Africa, language is only one part of the donation experience.
The donation journey may need to account for:
A French-speaking donor should ideally be able to discover the donation page, understand the appeal, complete the form and receive confirmation without unexpectedly switching back to English.
The same principle applies to other calls to action.
Multilingualism and accessibility overlap significantly.
A website should remain accessible regardless of the language selected.
Consider:
W3C’s accessibility and internationalisation guidance makes clear that language handling is part of building an inclusive web experience.
Accessibility should therefore be tested in each major language rather than only in English.
A Pan-African NGO should also consider cultural context.
Localisation can involve:
The same photograph may not communicate the same message to every audience.
Similarly, a programme description written for an international donor may need to be framed differently for a community audience.
The goal is not to create contradictory versions of the organisation’s message.
The goal is to make the same message meaningful to the people receiving it.
NGOs often have specialised terminology.
For example:
These terms should be translated consistently.
A terminology database or glossary can help.
Create a central glossary containing:
| English Term | French | Kiswahili | Notes |
|---|---|---|---|
| Beneficiary | Approved translation | Approved translation | Use consistently |
| Programme | Approved translation | Approved translation | Organisation-specific |
| Safeguarding | Approved translation | Approved translation | Legal/programme context |
This becomes particularly valuable when multiple translators work on the same website.
As an NGO grows, multilingual content becomes a governance issue.
Someone should be responsible for answering questions such as:
Without ownership, multilingual content tends to deteriorate over time.
The design is completed in English and translation is requested at the end.
This often creates:
The homepage is translated, but forms, resources and programme pages remain in English.
This creates a fragmented user experience.
This can introduce grammatical errors, incorrect terminology and potentially serious misunderstandings.
Translated pages exist but have:
Arabic cannot simply be inserted into an English layout without considering text direction.
This makes localisation more difficult and can create accessibility problems.
An organisation launches with three languages but only updates one.
After a year, the site effectively becomes a single-language website with outdated translations.
Country-level targeting does not automatically tell you which language every user prefers.
Programme and audience research should inform language decisions.
A Pan-African NGO could structure its website approximately as follows:
example.org/
│
├── en/
│ ├── about/
│ ├── programmes/
│ ├── resources/
│ └── contact/
│
├── fr/
│ ├── about/
│ ├── programmes/
│ ├── resources/
│ └── contact/
│
└── sw/
├── about/
├── programmes/
├── resources/
└── contact/
The exact architecture will depend on the CMS, SEO strategy and organisational requirements.
The important principle is that language should be part of the information architecture rather than something added through a superficial translation widget.
Automatic translation widgets can be useful for some situations, particularly where an organisation needs broad access to a large volume of content.
However, they should not automatically be considered a replacement for a properly multilingual website.
A translation widget may:
For critical NGO communications, professionally managed language versions are usually preferable.
There is no single price because multilingual functionality affects several components of the project.
Costs can include:
Adding one language to a well-structured website is generally much easier than retrofitting five languages onto a website that was originally built without internationalisation in mind.
For this reason, NGOs should communicate their expected language requirements during the initial website procurement process.
A project that requires English, French and Arabic should be scoped differently from a website that only requires English.
If your organisation is procuring a multilingual website, the RFP or ToR should clearly state the requirements.
Include:
Specify:
Specify:
Specify requirements for:
Specify:
Require accessibility testing across supported languages.
Specify how ongoing translations will be handled after launch.
These requirements can significantly reduce misunderstandings between an NGO and its web development partner.
A practical project can follow these stages.
Identify:
Design the website structure with multilingual content in mind.
Create layouts that can accommodate:
Implement:
Prepare and review the content.
Test each language independently.
Check:
Monitor:
Before hiring an agency to build a multilingual NGO website, ask:
These questions help distinguish between an agency that can translate pages and one that understands multilingual digital product design.
The strongest multilingual NGO websites are not simply English websites with additional translations.
They are designed around the reality that users across Africa may have different:
For Pan-African organisations, this makes multilingualism part of digital strategy rather than merely a content-management feature.
The website should be designed so that language is integrated into its information architecture, UX, technology, SEO, accessibility and content governance from the beginning.
Zedafrica helps organisations design and develop digital experiences that combine strategy, UX research, interface design and technical development.
For Pan-African NGOs, a multilingual website project can be approached as a complete digital experience rather than simply a translation exercise.
This can include:
If your organisation operates across multiple African markets and needs a website that can communicate effectively across languages, the right time to address multilingualism is before the website is designed and developed.
