- Webflow Localization lets you run your site in more than one language from one project, with a URL folder per locale, translated content and per locale SEO settings.
- Decide which markets matter first. Translate the pages that sell in those markets, not every page on day one.
- Use machine translation for a first draft, then have a fluent person review headlines, calls to action and anything legal.
- Localize the SEO too: translated titles, descriptions, slugs and alt text, with hreflang tags so search engines show the right version.
- Design for longer text from the start. German and French often run longer than English and can break tight layouts.
Webflow Localization: the short answer
Webflow Localization is Webflow's built in way to run a website in more than one language from a single project. You set a primary locale, add secondary locales, and each one gets its own URL folder, such as /de or /fr. You then translate static pages and CMS content, set localized SEO fields, and Webflow handles the language tags that tell search engines which version to show.
Before Localization, most Webflow teams ran multilingual sites with a third party translation tool or by duplicating pages by hand. Both work, but they add cost, scripts or a lot of manual upkeep. Having localization inside Webflow makes a multilingual site much simpler to run, as long as you plan it well.
This guide covers how it works, what to translate first, how to keep SEO strong in every language and the checks we run before launching a new locale. Webflow updates its features and plans often, so check the current Localization plans for exact limits.
How Webflow Localization works
A few ideas make everything else easier to understand:
- Locales. A locale is a language, and optionally a region, such as English, German or Spanish for Mexico. Your primary locale is the default. Secondary locales are the translations.
- Subdirectories. Each secondary locale lives in its own folder on the same domain, for example
yoursite.com/fr/pricing. This keeps the authority of your main domain shared across languages. - One design, many contents. The layout and classes are shared. Text, images, links and SEO fields can be changed per locale.
- CMS localization. Collection items can have translated field values, so blog posts, case studies and other CMS content can exist in every locale.
- A locale switcher. A language menu lets visitors move between versions of the same page.
Localization is a paid add on on top of your site plan. The number of locales and some features depend on which plan you choose.
Because everything lives in one project, a design change made once applies to every language. That is the biggest practical win over duplicated pages, where every update has to be repeated by hand in each copy.
Decide which markets come first
The biggest mistake with localization is translating everything into five languages at once. It takes a long time, it costs a lot, and half of those pages may never get traffic.
Start with data and sales plans:
- Look at analytics. Which countries already visit, and which of them convert well?
- Talk to sales. Which markets are you actively selling into this year?
- Check search demand. Do people in that market search in their own language for what you sell? In some B2B niches, buyers search in English anyway.
- Count support capacity. If a lead arrives in Spanish, can someone reply in Spanish?
Then pick one or two locales to launch first. A well done German site beats five half translated ones.
Also think about regions, not just languages. Spanish for Spain and Spanish for Mexico use different words and different currencies. If one version covers several countries, write in a neutral style and avoid region specific details. If you sell differently in each region, separate locales may be worth it.
What to translate first
Not every page needs to exist in every language on day one. We usually launch a new locale with the pages that sell:
- Home page
- Main product or service pages
- Pricing
- Contact or demo page, and the form messages
- The case studies most relevant to that market
- Legal pages that apply in that region
Blog posts and deep resources can follow, starting with the ones that match search demand in that language. Do not forget the small things: navigation labels, button text, form placeholders, error and success messages, the 404 page and image alt text. A page with a translated body and an English button feels unfinished.
A translation workflow that keeps quality high
Webflow can create machine translations to give you a quick first draft. That is a big time saver. It is not the end of the job.
A workflow that works for most teams:
- Freeze the source. Finish and approve the English pages first. Translating moving copy wastes money.
- Machine translate a first draft inside Webflow or with your preferred tool.
- Native review. A fluent speaker, ideally someone who knows your industry, reviews headlines, calls to action, product terms and anything legal.
- Keep a glossary. A list of product names and terms with the agreed translation, so everyone says it the same way.
- Review in context. Check translations on the actual page, on desktop and mobile, not just in a spreadsheet.
Some phrases should not be translated literally. A playful English headline may need a different idea in another language. Give reviewers permission to adapt, not just translate.
Plan time for it. Review always takes longer than people expect, especially for legal pages and pricing. Book reviewers before the build ends, not after, so translated pages are not waiting in a queue while the English site is ready.
Localized SEO: titles, slugs and hreflang
A translated page only brings in search traffic if search engines understand it. For each locale, set:
- Title and meta description in the local language, written for local search phrases, not just translated word for word.
- Slugs. Translated URL slugs read better, for example
/de/preiseinstead of/de/pricing. Decide this early, because changing slugs later needs redirects. - Alt text and Open Graph fields in the local language.
- Hreflang tags. These tell search engines which page is the English, German or French version of the same content. Webflow adds them for localized pages, so check them on the live site after you publish.
- Sitemap. Make sure localized pages are included and submit the sitemap in Search Console.
Do local keyword research for your most important pages. People in different countries often use different words for the same thing. Our SEO and AEO work includes this for multilingual sites.
Design for every language
Layouts designed only in English often break in other languages. Plan for it in Figma, before the build:
- Text length. German, French and Spanish often run noticeably longer than English. Buttons, navigation and card titles need room to grow.
- Line breaks. Hand placed line breaks in headings rarely work in another language. Let text wrap naturally.
- Images with text. Avoid words baked into images. If you must, prepare localized versions.
- Fonts. Check that your fonts support every character you need, including accents.
- Right to left languages. Arabic and Hebrew need layout mirroring and careful testing. Treat them as a bigger project.
We test a few key pages with the longest language before building the rest. It catches most layout problems in one go.
Watch dates, numbers and currencies as well. Different countries write dates and decimals differently, and a price shown in dollars may confuse buyers who think in euros. Decide whether to show local currencies, and if you do, keep them in the CMS so they are easy to update.
Localizing the CMS and dynamic content
CMS content is where multilingual sites grow quickly. Plan the collections with translation in mind:
- Decide which collections need to be translated. Blog posts and case studies usually do. Internal reference lists might not.
- Decide whether every item needs a translation. Many teams publish some posts only in English. Plan how listing pages handle that.
- Keep field structures simple. Clear fields for title, summary, body and SEO make translation and review faster.
- Translate option fields and reference names that show on the page, such as categories and tags.
Our Webflow CMS guide covers collection planning in more detail, and our Webflow CMS service sets this up for you.
Forms, integrations and routing
A localized page needs a localized journey after the click:
- Forms. Translate labels, placeholders, consent text and success messages. Pass the locale to your CRM as a hidden field so sales knows which language to reply in.
- Booking. If you use a booking tool, link to a version that shows local time zones and language where possible.
- Emails. Automated follow ups should match the language of the form.
- Analytics. Make sure you can filter reports by locale, so you can see which markets convert.
Be careful with automatic redirects based on location. Forcing a visitor to a language based on their IP address can annoy people and can stop search engines from seeing every version. A clear language switcher, and perhaps a gentle suggestion, works better. See our Webflow integrations page for CRM and form setups.
Running a multilingual site after launch
Launching a new locale is the easy part. Keeping every language accurate as the site changes is where most multilingual sites slip. A few habits keep things in sync:
- Treat the primary locale as the source. Change it first, then update translations. Never let translators edit facts like prices or product names on their own.
- Keep a change log. Each time English copy changes, note the page and section so the translations can be updated in the same week.
- Review prices, legal text and dates first. These cause the most damage when they are out of date in one language.
- Watch each locale in Search Console. Look at clicks and impressions for each language folder, and check that the right version ranks in each country.
- Prune what does not work. If a translated page gets no traffic and no leads after several months, consider whether it is worth keeping up.
New pages need a decision too. When you publish a new English page, decide right away whether it gets translated, and when. Otherwise the gap between languages grows quietly until the secondary sites feel abandoned. A simple rule, like "every product and pricing change ships in all live languages within a week", keeps everyone honest.
Launch checklist for a new locale
- Every page in the launch scope is translated and reviewed by a fluent speaker.
- Navigation, footer, buttons, forms and the 404 page are translated.
- Titles, descriptions, slugs and alt text are set in the local language.
- Hreflang tags appear correctly on the live pages.
- The language switcher goes to the same page in the other language, not to the home page.
- Layouts hold up on mobile with the longest language.
- Forms send the locale to the CRM and show translated messages.
- Localized pages appear in the sitemap and the sitemap is submitted.
- Analytics can report by locale.
Our general website launch checklist covers everything else.
How we launch multilingual Webflow sites
We plan localization at the start of a project, even if the extra languages come later. That means room for longer text in the design, translation friendly CMS fields and a clear slug plan. When you are ready for a new locale, we set it up, run machine translation for the first draft, work with your reviewers, localize SEO and test every page before launch.
A new website of up to 5 pages starts at $2,500, and localization work on an existing site gets a fixed quote after a 20 minute call. Every project includes 30 days of support after launch for safe changes, like copy, image, colour and link updates, and fixes to what we built. See our Webflow development service or tell us which markets you are planning.
Terms used: Webflow, Webflow Localization



