Skip to content

Your Guide to Translation

Different routes to serving content in multiple languages

If your charity works with communities who speak different languages, offering translations on your website can make your content more inclusive. But there’s no one-size-fits-all answer—it’s all about budget, quality expectations, and how much ongoing work your team can take on.

Do nothing

Some browsers (especially Google Chrome) automatically offer to translate pages if the visitor’s language doesn’t match the site. This often uses Google Translate behind the scenes.

Google Translate widget

Google still offers a free translation widget to charities. It’s a quick, low-effort way to let users choose a language from a dropdown, with translations handled by Google.

Full multilingual site structure

The heavyweight option—creating separate site trees for each language. Every page, menu, and form is translated, including system text like error messages.

Page-by-page translation

Rather than duplicate the entire site, you duplicate and translate only certain pages—like key service info or campaign landing pages.

Optional: Automated translation integration

Your CMS can integrate with services like DeepL, Google Cloud Translate, or OpenAI. Editors create a page in English, hit “translate,” and the system generates a version in another language. Naturally nothing is good as a human translating meaning and context, but sometimes that's not required to get the key messages across.

How to Choose

A quick rule of thumb:

We can help you work through the options, set up the right approach in Wagtail, and make sure your multilingual site works for everyone who needs it. Get in touch—we’re here to explain and support.