Multi-language sites (overview)

An introduction to Webflow Localize — how multi-language websites work in Webflow and what's involved in setting one up.

If your business serves customers in multiple languages or regions, Webflow Localize lets you create language-specific versions of your site without needing a separate website for each language.

Quick summary

Webflow Localize (a paid add-on) lets you publish translated versions of your site's content for different languages and regions. Chykalophia sets up the structure; the translations can come from Webflow's built-in AI translation, from you, or from your translators. Visitors can switch languages with a language switcher, and Webflow tells search engines about each language version.

What is Webflow Localize?

Webflow Localize is Webflow's built-in feature for running multiple language versions of your site within a single Webflow site.

Each language version (called a locale) has its own:

Translated text content
Translated meta titles and descriptions (for SEO)
Optional: different images for each locale (on the Localize Advanced and Enterprise plans)
Its own URL subdirectory (e.g., /fr/ for French, /de/ for German)

Your main language (usually English) remains the primary locale. All other languages are created as secondary locales.

How localization works in Webflow

Chykalophia sets up the locales in Webflow's Localize panel — adding each language you need and setting its URL subdirectory — and builds a language switcher for visitors.

The primary language content exists already — your current site is the starting point.

Translation is added for each secondary locale. Webflow can translate page text and CMS items automatically with AI, or you (or a translator) can enter translations by hand. With the Content editor role, you pick the locale from the locale switcher at the top of the screen, select a text element, and click the globe icon to translate it.

Publish to make the translated versions live. Each secondary locale goes live in its own subdirectory once publishing is turned on for that locale.

What you need to provide

If you're commissioning a multi-language site, you'll need to provide:

Translated text for every page and CMS item you want translated (or a review of Webflow's automatic translations)
Translated SEO titles and meta descriptions for each page
Optionally: locale-specific images (e.g., a photo with English text replaced by a French version)

Machine translation (including Webflow's built-in AI translation, Google Translate or DeepL) can be used as a starting point, but professional human translation is recommended for anything customer-facing.

Webflow Localize plan requirements

Webflow Localize is a paid add-on. It comes in two self-serve tiers: Localize Essential (up to 3 extra locales on top of your primary one) and Localize Advanced (up to 10), plus a custom Enterprise option. Webflow's Team plan includes 2 locales. On the pricing page, Localize is listed as an optional add-on for paid Site plans, not for the free Starter plan.

You can try basic Localize features for free, whatever plan you're on. Publishing a translated version needs the add-on, and Webflow's help articles say adding more than one extra locale does too.

Localize doesn't support Webflow Ecommerce features: on a site with both, products, categories, and store pages can't be translated.

Check with Chykalophia about the right option for your site, or check webflow.com/pricing.

URL structure for locales

Webflow serves each locale from a subdirectory of your domain:

Approach	Example	When to use
Subdirectory	`yoursite.com/fr/about`	Webflow's standard setup — same domain

By default, the subdirectory is the language code (e.g., /fr), or the language and country code if you set a country (e.g., /en-us). Webflow's help articles say you can change it, but its pricing page lists custom locale slugs only on Localize Advanced and Enterprise, so ask us what your plan allows. On Localize Advanced and Enterprise, URL slugs can be translated too, so yoursite.com/careers could become yoursite.com/es/empleos.

SEO benefits

Each locale gets its own SEO title and description, and its own Open Graph (social sharing) settings. Webflow says localized SEO can improve your site's visibility in new markets.

Webflow also adds hreflang tags automatically, both on each page and in your auto-generated sitemap. These tell search engines which language versions of a page exist and how they relate to each other.

Common questions

Can we set up automatic translation in Webflow?

Yes. Webflow Localize includes AI-powered automatic translation for page text and CMS items, with a monthly word allowance that depends on your Localize plan. You can also translate by hand, or use a translation app (Webflow mentions Lokalise as an example). Ask Chykalophia about the right approach for your project.

Can editors update content in each language separately?

Yes — with the Content editor role, you can switch between locales using the locale switcher and update content for each one separately. Changes you make in a secondary locale affect only that locale. Anything in a secondary locale that hasn't been translated or changed still follows the primary locale.

Does localization affect my current site's design?

Not unless you want it to. Every secondary locale starts with the same content, layout, and styles as your primary locale. Styles (and, on higher Localize plans, images) can then be changed for a particular locale.

Do I need a separate domain for each language?

No. Webflow serves each language from a subdirectory of your main domain (e.g., yoursite.com/fr/), so one domain covers every language.

Need a hand?

If you're stuck, email support@chykalophia.com and we'll help. Include your website address and a screenshot if you can.