Configure your locales, decide how visitors will navigate between them, and establish your team's localization workflow before translating content.
Confirm that Localize fits your site and plan before you add locales. Publishing a secondary locale requires a paid Site plan and a paid Localize add-on, and the add-on sets how many locales you can add. Localize doesn't support Ecommerce Site plan features, so you can't localize products, categories, or Ecommerce pages.
Where: Webflow dashboard; Localize panel > Locales
↳ Resources
Set your primary locale, which is your site's default language and the foundation for every secondary locale. Then add the languages or regions you'll support, and decide which to launch first.
Caution: You can't change your primary locale later, and you can't promote a secondary locale to primary.
Where: Localize panel > Locales
↳ Resources
Set each locale's language, country (where applicable), display name, display image, and URL subdirectory, such as /es or /es-mx. Avoid subdirectory slugs that match an existing page, folder, or Collection.
Where: Localize panel > Locales
↳ Resources
Build a locale switcher with a Dropdown element and the Locales list element. On Advanced and Enterprise plans, decide whether automatic domain-level routing suits your audience.
Tip: Automatic routing applies only to visitors who land on your root homepage. A browser set to a language only (e.g., French) isn't routed to a country-specific locale (e.g., French (Canada)).
Where: Add panel > Advanced (Dropdown, Locales list); Localize panel
↳ Resources
On eligible Enterprise plans, limit which secondary locales each team member can edit so regional owners don't change other locales. Locale access restricts editing, not publishing.
Where: Site settings > Site access
↳ Resources
Decide how your team will translate and maintain localized content: agentic translation (one-time or continuous), AI translation you trigger yourself, manual translation, a translation app, or a TMS connected through the Localize APIs. Define who translates, reviews, and approves before publishing. AI translation draws on a monthly word allowance.
Caution: Switching to continuous translation can replace existing translations, including ones your team wrote. Use one-time mode if you need to keep editing translations yourself.
Where: Localize panel > Target languages; CMS panel
↳ Resources
Translate and customize your site's content, CMS items, assets, and page settings to create complete experiences for each locale.
Set tone and formality for each target language. On Enterprise sites, consider uploading a custom translation glossary to keep brand and product terms consistent.
Where: Localize panel > Target languages, Glossary
↳ Resources
Before you translate, exclude content that should stay in the primary language, such as SKUs, reference codes, or legal text. Excluded content doesn't use your word allowance.
Where: Localize panel > Exclusion rules
↳ Resources
Translate your static pages for each secondary locale, and review key messaging for clarity and regional relevance rather than relying on direct translation. Secondary locales inherit from the primary locale until you override them.
Where: Locale switcher > Canvas
↳ Resources
Localize Collection item names, fields, and rich text. Decide which items appear in each locale, and whether each Collection list shows the current locale's items or the primary locale's.
Caution: Deleting an item from the primary locale also deletes it from every secondary locale. To hide it in the primary locale only, set it to Draft there.
Where: Locale switcher > CMS panel
↳ Resources
Replace images that contain text, translate alt text, and adapt styles for different text lengths. Review localized components and right-to-left languages where they apply. Structural changes must be made in the primary locale.
Where: Locale switcher > Canvas, Assets panel, Style panel
↳ Resources
Check that internal links reach the right localized pages, and translate form labels, button text, and other interface text. Use the Page or Collection page link type so links route to the matching locale.
Where: Locale switcher > Canvas, Pages panel
↳ Resources
Customize page names, slugs, SEO titles and descriptions, Open Graph settings, and custom code for each locale. Review your hreflang setup and sitemap. Add separate 301 redirect rules for localized paths.
Where: Locale switcher > Pages panel > Page settings; Localize panel > SEO; Site settings > SEO
↳ Resources
Review localized experiences for quality, functionality, and discoverability before publishing each locale.
Review localized pages and CMS content for accuracy, tone, and completeness. Check for untranslated text and unintended fallbacks to the primary locale, and have a reviewer validate each language. Wait for translations to finish processing before you review.
Where: Locale switcher > Canvas, CMS panel
↳ Resources
On your published staging site, test each locale across breakpoints and devices. Check text wrapping, navigation, locale switching from interior pages, forms, and key user journeys.
Where: Published staging site; Breakpoints
↳ Resources
Review URLs, metadata, language codes, and hreflang for each locale. Check for broken links, incorrect redirects, duplicate slugs, and unexpected 404 errors, and confirm your sitemap includes the localized pages you plan to publish.
Where: Published staging site; Localize panel > SEO; Site settings > SEO
↳ Resources
Enable publishing for completed secondary locales and keep unfinished ones off. On Enterprise sites, you can set individual static pages to draft in specific locales.
Caution: Drafting a localized page doesn't remove links to it, so visitors can reach a 404. Review navigation and internal links before you publish.
Where: Localize panel > Locales; Page settings; Publish menu
↳ Resources
Visit each published locale on your production domain. Confirm URLs, navigation, locale switching, forms, and key journeys work, check indexing in Google Search Console, and set a process for reviewing future translation updates.
Where: Published production site; Localize panel; Google Search Console
↳ Resources