←  All terms
W
Webflow

Webflow Localization

Webflow Localization manages language and regional variants of content, URLs, metadata, and page settings.

Webflow Localization provides a centralized way to manage multilingual and region-specific website experiences within a single project. Secondary locales inherit the structure, content, and styling of the primary locale by default, while still allowing targeted overrides for each market. Depending on the plan, teams can adapt translations, assets, visibility, slugs, SEO settings, and locale routing to local requirements.

Read more

Localization

Locale

hreflang

Secondary Locale

FAQ

Webflow Localization

When does Webflow Localization beat separate projects per language?
It pays off when language variants should share the same structure and components. A single project avoids maintaining layouts twice. Separate projects make sense when markets have strongly diverging page structures, teams, or schedules. Availability and scope depend on the plan booked.
How is CMS content translated in Webflow Localization?
All locale variants of a CMS item share the same item ID, and fields are translated per locale or inherited. This keeps relationships stable, such as references between collections. For large volumes of content, a translation process with a status per item pays off, otherwise the overview is lost.
What matters for SEO with Webflow Localization?
Each locale needs its own slugs, titles, and descriptions, plus a clean mapping via hreflang. Primary-language text carried over into metadata weakens performance in the target language. Language variants should be treated as standalone pages with local search intent, not as mere copies.
How does Webflow Localization differ from localization in general?
Localization is the content and cultural adaptation to a market, while Webflow Localization is the technical tool for managing the variants. The tool replaces neither market knowledge nor editorial review. It provides the structure for locales, URLs, and metadata, not the quality of the adaptation.
How does inheritance from the primary locale to secondary locales work?
Secondary locales first take over the field values of the primary locale until they are deliberately overridden. If a translation has not yet been maintained, the primary locale content appears. This speeds up the start but requires a check so that no untranslated remnants go live.