Why Multilingual Is a Governance Decision, Not Just a Technical One

Adding a second language to a nonprofit website is rarely just a translation task. It's a commitment to maintaining two versions of every page — keeping them in sync when content changes, ensuring translated content is accurate and appropriate, and deciding who in the organisation is responsible for reviewing and approving translations before they go live.

Before choosing a technical approach, the more important question is: what is the governance model for managing translated content? If there's no clear answer — no named person responsible for French translations, no review process, no plan for updating translated pages when English content changes — then the translation infrastructure you build will deteriorate quickly regardless of which platform you use.

This post covers the three main technical approaches for Webflow nonprofit sites, their trade-offs on cost and SEO, and what each approach demands in terms of ongoing editorial maintenance.

The Three Approaches

Webflow Native Localisation

Webflow has a built-in localisation feature that allows you to create additional language versions of your site within the Webflow Designer. Each locale lives on its own subdirectory — for example, yourcharity.org.uk/fr for French, yourcharity.org.uk/es for Spanish. The primary (default) language lives at the root.

How it works:

You set up a primary locale (your default language) and add secondary locales for each additional language. In the Webflow Designer, you can switch between locales and edit content directly — text, images, links, and other content elements can be customised per locale. Webflow also offers AI-powered auto-translation to generate a first draft of translated content, which can then be reviewed and edited.

Each locale's pages are indexed separately by search engines under their own subdirectory URLs. This matters for SEO.

The SEO case for subdirectory localisation:

When your French content lives at yourcharity.org.uk/fr, Google indexes those pages as distinct URLs that can rank for French-language search queries. Over time, each locale builds its own search authority. This is the architecturally correct approach for organisations that want multilingual SEO performance — reaching French-speaking beneficiaries or donors through organic search, not just serving existing visitors who happen to prefer French.

Webflow also handles the hreflang attribute automatically for each locale. This tells search engines which language version of a page to show to users in different regions — preventing duplicate content issues and ensuring French speakers are shown the French version in search results.

Cost:

Webflow's localisation feature is available on the CMS and higher hosting plans, with localisation add-ons priced per locale. Pricing changes — verify current costs on Webflow's pricing page before budgeting. The cost scales with the number of locales you add.

AI auto-translation cost warning:

Webflow's AI auto-translation charges per word translated. For a nonprofit with a modest static site, this is manageable. For a site with an active blog or large resources section — dozens or hundreds of pages — auto-translating everything can accumulate significant costs quickly. The AI translation produces a usable first draft, but it still requires human review before publishing. If you have a large content library, translate static pages (homepage, about, programmes, contact) and handle the blog separately, either manually or by keeping it English-only for secondary locales.

Best for: Organisations that want multilingual SEO — reaching new audiences through organic search in other languages — and have a team member who can review and approve AI-generated translations before publishing.

Weglot

Weglot is a third-party translation layer that sits on top of your existing Webflow site. It intercepts page content, translates it, and serves the translated version at a subdomain or subdirectory URL depending on your configuration.

How it works:

You install Weglot via a script added to your Webflow site's custom code — similar to how GTM is installed. Weglot scans your site's content and translates it automatically using machine translation (primarily DeepL and Google Translate as sources). The translated content is stored and managed in Weglot's own dashboard, where you can review, edit, and override any translation.

A language switcher widget appears on the site, allowing visitors to switch between languages. The switcher is customisable in appearance.

Weglot's URL structure:

By default, Weglot serves translated content on a subdomain — for example, fr.yourcharity.org.uk. Subdomains are treated by search engines as separate sites, which means French content on a subdomain doesn't inherit the domain authority of your main site as effectively as subdirectory content does. Weglot does offer subdirectory configuration, which is better for SEO — check whether your plan supports this and configure it if so.

Weglot handles hreflang tags automatically, which is important for multilingual SEO regardless of whether you use subdomain or subdirectory structure.

From my own experience:

I've used Weglot on a small project. The installation is quick — once the script is in the Webflow custom code and the site is published, Weglot picks up the content and translates it almost immediately. The translation dashboard is straightforward to use, and the ability to override specific translations without touching the Webflow site is useful — the client's team can correct translations directly in Weglot without needing Designer access.

For small sites with modest content volumes, Weglot works well and the setup time is minimal compared to configuring Webflow native localisation.

Cost:

Weglot charges based on the number of words translated and the number of languages. The pricing tier that covers most small nonprofit sites starts at a reasonable monthly rate, but costs increase with content volume and additional languages. As with Webflow's AI translation, costs can escalate quickly if your site has a large blog or content library — Weglot translates every page it can access, including blog posts, which adds to your word count.

If cost is a concern, Weglot allows you to exclude specific pages or URL patterns from translation — useful for keeping blog posts in the primary language only while translating core pages.

Best for: Organisations that want a fast setup, want translated content to be editable by non-technical team members, have a small-to-medium content volume, and don't need to optimise multilingual SEO aggressively.

Google Translate Widget

Google Translate offers a free widget — a small JavaScript snippet — that can be added to any website to provide on-the-fly browser-based translation. The visitor selects a language from a dropdown, and Google Translate renders the page content in their chosen language in the browser.

How it works:

Add a script from Google Translate to your Webflow site's custom code. A language selector widget appears on the page. The translation happens in the visitor's browser using Google's translation engine — no separate translated version of the page is created or stored.

The critical limitation — no SEO value:

Because the translated content is rendered in the browser rather than hosted at a distinct URL, search engines don't index it. There are no French or Spanish versions of your pages for Google to crawl and rank. A French-speaking beneficiary searching for your services in French will not find your site through organic search as a result of the Google Translate widget — only visitors who arrive at your site through another route and then switch language will benefit.

For organisations whose primary goal is serving existing visitors who prefer a different language — not reaching new audiences through multilingual search — this limitation may be acceptable.

Cost:

The Google Translate widget itself is free. This is its main advantage. For very small organisations or those testing whether multilingual support is needed before investing in a proper solution, it provides immediate translation capability at zero cost.

Quality:

Google Translate's quality varies significantly by language pair and content type. For common European languages, quality is generally usable. For less common language pairs, or for content with sector-specific terminology (safeguarding, grant-making, charitable objects), machine translation errors are more likely. There is no editorial review or correction mechanism in the widget — what Google Translate produces is what visitors see.

Best for: Organisations that need an immediate, zero-cost solution to serve existing visitors in other languages, with no SEO requirement and acceptance of variable translation quality. Not recommended as a long-term solution for organisations with significant multilingual audiences.

Comparing the Three Approaches

<div class="s-table-wrap"><table class="s-table"><thead><tr><th></th><th>Webflow Native</th><th>Weglot</th><th>Google Translate</th></tr></thead><tbody><tr><td><strong>SEO benefit</strong></td><td>Strong (subdirectory, hreflang)</td><td>Good (subdirectory preferred, hreflang)</td><td>None</td></tr><tr><td><strong>Setup complexity</strong></td><td>Medium (Designer config per locale)</td><td>Low (script install + dashboard)</td><td>Very low (script only)</td></tr><tr><td><strong>Translation editing</strong></td><td>In Webflow Designer</td><td>In Weglot dashboard</td><td>Not available</td></tr><tr><td><strong>Non-technical editing</strong></td><td>Limited (requires Designer access)</td><td>Yes (Weglot dashboard)</td><td>Not applicable</td></tr><tr><td><strong>AI auto-translation</strong></td><td>Yes (per-word cost)</td><td>Yes (included in plan)</td><td>Yes (free, no control)</td></tr><tr><td><strong>Cost for small site</strong></td><td>Medium (locale add-on)</td><td>Medium (monthly subscription)</td><td>Free</td></tr><tr><td><strong>Cost for large content library</strong></td><td>High (per-word AI translation)</td><td>High (word count tiers)</td><td>Free</td></tr><tr><td><strong>Editorial review possible</strong></td><td>Yes</td><td>Yes</td><td>No</td></tr></tbody></table></div>

The Content Volume Problem

Both Webflow native localisation and Weglot become expensive when applied to sites with large content libraries — primarily blog-heavy sites. AI translation charges per word, and a single long blog post can cost more to translate than you'd expect.

The practical solution for most nonprofits is selective translation: translate the pages that matter most for the multilingual audience and leave the rest in the primary language.

Core pages to translate in most cases: homepage, about, programmes or services, contact, and any page specifically relevant to the language audience (for example, a French-language programme serving French-speaking communities). Blog posts and resources can remain in English unless a specific case exists for translating them.

Both Webflow native localisation and Weglot support this — you can translate a subset of pages and leave others in the primary language. Plan this before starting translation to avoid unexpected word count costs.

My Recommendation by Scenario

If multilingual SEO is a goal — reaching new audiences through search in another language: Use Webflow native localisation. The subdirectory structure and automatic hreflang handling give you the strongest SEO foundation, and the translation is managed within the Webflow ecosystem you're already using.

If speed of setup and non-technical editorial control are priorities: Use Weglot. The dashboard allows your Communications team to correct and manage translations without Designer access, and the installation is faster than setting up Webflow locales. Configure subdirectory URLs rather than subdomain if your plan allows.

If budget is the only constraint and SEO isn't a requirement: The Google Translate widget provides immediate multilingual access at zero cost. Understand the quality limitations and the absence of editorial control. Revisit the decision when budget allows.

If you're unsure whether your audience actually needs multilingual support: Before investing in any solution, check your current analytics. What languages are your visitors' browsers set to? Are there specific countries in your traffic data that suggest a language need? A Blueprint Audit that includes a stakeholder needs assessment will surface whether multilingual is a genuine requirement or an assumed one.

Further Reading

• How to Set Up Weglot on a Webflow Nonprofit Website
• SEO Fundamentals for Nonprofit Websites
• How to Prepare Your Nonprofit Website to Go Live

‍