Webflow localization starts at $9 a month for the Localize Essential add-on, which covers up to three locales and 10,000 AI-translated words a month, according to Webflow's pricing page. The features most B2B sites actually want, translated URL slugs and automatic visitor routing, start one tier up, on Localize Advanced from $29 a month.
This guide covers what each tier buys, the order to set a localised Webflow site up in, and eight jobs the locale switcher leaves to you. The rules come from Webflow's own Localize checklist, developer documentation and Google's guidance on multilingual sites; the worked example is Flöa, a bilingual English and French site we built in Webflow for Web Tonic.
What Webflow localization costs in 2026
Webflow sells localisation as an add-on on top of a paid Site plan. Publishing a secondary locale needs both, and the add-on tier sets how many locales you can add. Prices below are the starting prices shown on Webflow's pricing page on 4 November 2026; both rise with the number of locales you select.
| Tier | Starting price | Locales | AI translation | Adds |
|---|---|---|---|---|
| Localize Essential | $9 a month | 1 to 3 | 10,000 words a month | CMS and static page localisation, localised SEO, style localisation |
| Localize Advanced | $29 a month | 1 to 10 | 50,000 words a month | Everything in Essential, plus asset localisation, localised URLs, automatic visitor routing |
| Localize on Enterprise | Quoted by sales | Custom | Custom | Custom element visibility, draft locale-specific static pages |
| Team Site plan | Included | 2 locales | Not stated | Localize bundled into the plan |
Source: Webflow, Plans and pricing, read 2026-11-04
The word allowance is the number teams misjudge. AI translation draws on it every month, and excluded content does not count against it, so legal text, SKUs and product codes are worth excluding before the first run. At an assumed 300 words a page, a 60-page marketing site holds about 18,000 words, so its first full translation pass would not fit inside one month of Essential's allowance even with a single extra language.
For comparison, Weglot, a third-party translation service that also works on Webflow, prices by total words rather than monthly words: its Starter plan is €15 a month for one language and 10,000 words, Business €29 for three languages and 50,000 words, and Pro €79 for five languages and 200,000 words, with the limit fixed rather than renewing. We build in Webflow, so read our preference for native Localize with that bias in mind: the deciding factor is usually that native locales sit in the same CMS and Designer the marketing team already edits.
A worked example: what a bilingual Webflow site looks like when live
Flöa sells home water filtration in Québec. The site has 60+ pages in English and French, built in Webflow as a Web Tonic project. We read its live sitemap and page source on 4 November 2026 to show what Webflow localization produces, including the parts that need a decision.
| Item | What the live site shows |
|---|---|
| Locales | English primary, French (Canada) in the /fr subdirectory |
| Page pairs in sitemap | 33 pairs, 66 URLs, each with en, fr-CA and x-default hreflang entries |
| Translated slugs | 28 of 33 pairs, for example /about-us and /fr/a-propos |
| Untranslated slugs | 5: the homepage, /faq, two product codes and /financement |
| Collection folders | /blogs/, /systems/ and /categories/ stay the same in French |
| Hreflang in page head | Yes, on every page checked, alongside the sitemap |
| Switcher | A custom EN and FR link pair, not the native Locales list |
| Automatic routing | Off: a French browser request to the root returns the English homepage |
Source: Octo Agency read of drinkfloa.com sitemap and page source, 2026-11-04
Two rows are worth a second look. /financement is a French word sitting in the English URL, the kind of slip that happens when a page is created in the second language first. And the Collection folders keep English names in French URLs, so a French visitor sees /fr/blogs/ followed by a French slug. Neither hurts rankings much, but both are cheaper to decide on before launch than to redirect afterwards.
The setup order that avoids rework
Most localisation rework comes from doing steps in the wrong order. The sequence below follows Webflow's own Localize checklist, with the reason each step sits where it does.
1. Confirm plan and scope. Check you have a paid Site plan and choose the Localize tier by locale count and word volume. If the site sells through Webflow Ecommerce, stop here: Localize does not localise products, categories or Ecommerce pages.
2. Fix the primary locale. It cannot be changed later, and a secondary locale cannot be promoted to primary. Every structural change happens in the primary locale, so it should be the language the build team works in.
3. Name the subdirectories. Each locale gets a subdirectory such as /fr or /es-mx. Avoid one that matches an existing page, folder or Collection slug.
4. Finish structure before translation. Secondary locales inherit from the primary until you override them. Translating before the layout settles means translating twice.
5. Choose the translation mode. Agentic translation can run once or continuously, or you can trigger AI translation, translate by hand, use an app, or connect a translation management system through the Localize APIs. Decide who reviews each language before anything is published.
6. Build the switcher and set routing. Covered in detail below.
7. Localise SEO settings and redirects. Slugs, titles, descriptions, Open Graph and per-page custom code, then separate 301 rules for each localised path.
8. QA on staging, then publish per locale. Turn publishing on only for finished locales. Unfinished ones stay off and out of the switcher.
If the site is also changing CMS structure, settle the model first. Our guide to Webflow CMS limits covers the item and reference caps that a second locale does not raise.
The 8 things the Webflow localization switcher will not do for you
The native switcher is the Locales list element, usually placed inside a Dropdown in the navbar. It lists every published locale and links to the same page in that locale. That is all it does. Everything else is yours.
| Gap | What happens if you skip it | Fix |
|---|---|---|
| 1. Translating its own label | The dropdown text stays in the primary language | Translate the label in every secondary locale |
| 2. Hiding unfinished locales | Any locale with publishing on appears in the list | Keep publishing off until a locale passes QA |
| 3. Fixing hard-coded links | Custom URL links send French visitors to English pages | Use the Page or Collection page link type |
| 4. Routing visitors | Nothing happens on Essential; on Advanced only root-homepage visits route | Show the switcher on every page, routing or not |
| 5. Matching language-only browsers | A browser set to French is not routed to French (Canada) | Add a plain language locale or rely on the switcher |
| 6. Adding redirects | /old-page and /fr/old-page need separate 301 rules | Write one rule per locale path |
| 7. Removing links to drafted pages | A page drafted in one locale still has links pointing to it, so visitors hit a 404 | Check navigation and internal links before publishing |
| 8. Translating forms and images | Form labels, buttons and text inside images stay in the primary language | Translate interface text and swap images per locale |
Sources: Webflow University Localize checklist; Webflow University locale navigation lesson, read 2026-11-04
Gap 3 is the easiest to miss in QA, because the English site looks fine. A link set to a custom URL such as /contact will always open the English contact page, even from /fr. Only Page and Collection page link types follow the visitor's locale.
Flöa's switcher shows another route. Instead of the Locales list, it uses a two-link EN and FR element with a small script that reads the hreflang tags Webflow writes into each page head, so every link lands on the matching translated slug. That works because Webflow emits those tags on static and CMS pages alike. We would only take this route where the design calls for a toggle rather than a dropdown; the native element needs no code.
Translation: AI, manual or a translation system
Webflow offers four ways to fill a locale, and the choice affects who can edit what later.
AI translation. You trigger it, it draws on the monthly word allowance, and you edit the output by hand. Tone and formality can be set per target language.
Agentic translation. One-time mode translates once. Continuous mode keeps translating as the primary locale changes, and the checklist warns that switching to continuous can replace translations your team wrote. If a regional marketer owns the French copy, use one-time mode.
Manual. Switch locale in the Designer or CMS panel and type. Slow, but the only option that guarantees a reviewer has seen every line.
Apps and the API. Translation apps and translation management systems connect through the Localize APIs. The Data API can localise page content, component properties and CMS items, but it cannot localise images, styles or classes, and it can only update page and component content in secondary locales. Primary-locale page copy still has to be edited in the Designer.
One CMS rule catches teams out: deleting an item in the primary locale deletes it from every locale. To hide an item in the primary language only, set it to draft there instead.
SEO for a localised Webflow site
Webflow handles the mechanical part. With Localize on, the auto-generated sitemap includes hreflang entries, and, as Flöa shows, each page head carries alternate links for every locale plus x-default. Google's documentation requires each language version to list itself and all other versions, and that is what Webflow writes.
The decisions are yours. Google advises against automatically redirecting users by what you think their language is, because it can stop users and crawlers from seeing every version, and recommends links that let users switch. Webflow's routing is limited to the root homepage, so it stays within that advice, but it is still worth leaving off until each locale is finished.
Localised titles, descriptions and slugs need writing per locale. A translated page with the primary language's meta title still ranks for the primary language's query. Our Webflow SEO checklist has the full order of settings, and our answer to whether Webflow is good for SEO covers the redirect rule for localised subdirectories in more detail.
Whether a second language is worth it
There is no primary data on what localisation does for B2B website conversion. The closest large survey is consumer data: CSA Research's 2020 study of 8,709 online shoppers in 29 countries found 76% prefer to buy products with information in their own language and 40% will not buy from websites in other languages. Treat that as a proxy. B2B buyers in technical fields read English more readily than consumers, so the effect is probably smaller, but the direction holds in markets such as Québec, where the buying conversation happens in French.
The cost side is predictable. The add-on runs from $9 to $29 a month at the lower locale counts, plus review time for every page you translate. The hidden cost is maintenance: every new page, blog post and CMS item now exists twice.
What this means for a Webflow site going multilingual
Start with the locale count and the word volume, because together they decide the tier. If you need translated slugs or routing, budget for Advanced from day one. Fix the primary locale, finish the structure, then translate. Close the eight switcher gaps on staging, not after launch, and decide who owns each language's copy before turning on continuous translation.
If you are planning a bilingual or multilingual build, our Webflow development service page explains how we scope it.
