Webflow Localization for multi-market sites: a practical guide

Webflow Localization is usually the simplest way to run a multi-market marketing site on Webflow. You keep one site, add a locale for each language or region, and each locale gets its own subdirectory such as /de/, with its own text, SEO settings and CMS content. Webflow also generates hreflang annotations so search engines can match each page to its translations.

The tool is the easy part. What decides whether a multi-market site works is planning: which locales you really need, what gets adapted rather than translated, and how visitors and search engines reach each version. This guide covers both, with Google's current guidance on international sites (updated in September 2026) at the time of writing (November 2026).

How Webflow Localization works

Every localised site has one primary locale and one or more secondary locales. Each locale has a display name for the language switcher, a subdirectory (taken from the locale code by default, but editable) and its own publishing status. Inside that structure:

• Static pages: text, form labels, SEO titles, descriptions and Open Graph settings can be set per locale.
• Components: you can localise the main component, which changes every instance in that locale, or a single instance.
• CMS: Collections and fields are shared across locales, but items are localised individually. A secondary locale inherits the primary value until you edit it, and each localised item can be published or left as a draft on its own. An item can also exist in one locale only.
• Assets, styles and visibility: images, alt text and styles can be changed per locale, and elements can be hidden in a locale. Right-to-left languages such as Arabic are supported.

If you plan to manage translations through the API or an AI agent, note what Webflow's developer documentation says: primary locale page content must be edited in the Designer, and styles and classes cannot be localised through the Data API.

Choose your locales before you build

Every locale adds pages to translate, review and keep up to date, so add one only when the content will genuinely differ. Google's hreflang rules also shape what you can use as a locale code:

• Language codes use ISO 639-1 (de) with an optional ISO 3166-1 region (de-CH). A region on its own is not valid.
• Codes such as es-419 (Latin American Spanish) are not supported, and reserved codes such as UK have no effect. Use en-GB for the United Kingdom.
• If you have regional versions of one language, also provide a generic version (such as en) for everyone else. It can be one of the regional pages.

Subdirectories, which Webflow uses, are one of the options Google lists for multi-regional sites. They are simple to set up and keep everything on one domain. Separate country domains give a stronger country signal but cost more to run, and are rarely worth it for a small or mid-sized business.

Get hreflang and sitemaps right

According to Webflow's help centre, Webflow adds the list of localised variants to the head of each page and includes hreflang annotations in its auto-generated sitemap. Only locales with publishing enabled appear in the sitemap. If you use a custom sitemap, you have to add hreflang yourself.

Automatic does not mean you can skip checks. After publishing, view the source of a few pages and the sitemap, and confirm that:

1. 1 Every version lists itself and every other version. Google ignores hreflang when pages do not point back to each other.
2. 2 URLs are absolute and use your live domain, not a staging or webflow.io address.
3. 3 Canonical tags on each locale point to that locale's own URL, not to the primary language page.
4. 4 SEO titles and meta descriptions are translated, not left in the primary language.
5. 5 Locales still in progress are not published, so half-translated pages stay out of search.

Our Webflow SEO guide covers the rest of the on-page set-up.

Be careful with automatic redirects

Webflow can route visitors to a locale based on their browser language on some plans. Use it with care. Google advises against redirecting people to a language version based on assumptions, because it can stop users and search engines reaching every version. Googlebot usually crawls from the USA without a language preference, so it may never see pages that only appear after a redirect.

The safer pattern is a visible language switcher on every page, with links to each locale. If you do use routing, make sure anyone can still switch versions manually and that each locale URL loads directly without being redirected away.

Translate for the market, not word for word

Webflow includes machine translation, and its newer agentic translation can work through a whole site (we covered it in our Webflow Conf 2026 roundup). That gets you a fast first draft. Before a locale goes live, make sure a fluent reviewer checks:

• Headlines, calls to action and form messages, where tone matters most.
• Prices, currencies, phone numbers, addresses and date formats.
• Case studies, testimonials and trust signals that make sense to that market.
• Legal pages such as privacy and cookie notices, which may need local advice rather than translation.
• A glossary of product names and terms that should never be translated.

Google detects a page's language from its visible content, so keep each page in one language. Translating only the navigation and footer while leaving the main content untranslated creates near-duplicate pages that serve nobody well.

Plans and costs

Localization is sold as an add-on to site plans, with tiers that differ in how many locales you can add and in features such as translated URL slugs, asset localisation and visitor routing. Webflow's new Team plan, launched in May 2026, includes Localization, according to Webflow's plan announcement. Some AI translation features also use AI credits. Locale limits and prices have changed more than once, so check the pricing page for current figures before you scope a project.

Frequently asked questions

Can I localise only some pages?

Yes. CMS items can exist in one locale only, items publish per locale, and elements can be hidden in a locale. Avoid linking to pages that do not exist in the visitor's language.

Should I use a third-party translation tool instead?

Third-party services still work with Webflow and may suit you if you already use them elsewhere. Native Localization keeps translated content, SEO settings and publishing inside Webflow, which is usually easier for one team to manage.

Will localising my site improve rankings in other countries?

It can help you appear for searches in other languages, but results depend on content quality, competition and links in each market. Treat each locale as its own content project.

Need help with a multi-market Webflow site?

We plan and build localised Webflow sites, from locale structure and translation workflow to hreflang checks after launch. See our Webflow development services, our Webflow website for a productivity SaaS company, or read when Webflow is the right choice. When you are ready, tell us about your markets.

Sources: Google Search Central: Managing multi-regional and multilingual sites, Google Search Central: Localized versions of your pages, Webflow Developers: Working with localization, Webflow Help: Localized SEO and locale routing, Webflow Community: Updates to Webflow plans and pricing