Prefer English?
Prefer English? Switch the website language for a better experience.
Localization is Webflow's native feature that lets you duplicate a site into multiple languages or for multiple markets, all from a single source project. In practice, you create "locales" (a language, a regional variant, or a combination of both), and Webflow automatically generates dedicated URLs, either as subfolders (/fr/, /de/) or as subdomains (fr.yoursite.com).
Before this feature launched in 2023, running a multilingual site on Webflow was a workaround at best: manual page duplication, patchy hreflang management through third-party scripts, CMS collections copied by hand. Localization changed the game on the production side. But it hasn't changed the rules of international SEO themselves: it simply finally gives you the right tools to apply them properly.
Three things genuinely change compared to the old workaround methods, and they have a direct SEO impact.
Webflow generates hreflang tags matching your configured locales, with no external script needed. This is often underestimated: a hreflang mistake (a wrongly declared locale, a missing reciprocal link) can make Google lose all confidence in a page's geographic targeting, causing language versions to get mixed up in the results. On an e-commerce project we recently took over, the old hreflang implementation through a misconfigured Weglot setup was sending the German version into French-speaking Swiss SERPs, a mix-up that was clearly costing qualified traffic.
Each locale gets its own URL, its own sitemap, its own customizable meta title and description. This allows for fine-grained indexation by country or language, unlike client-side dynamic translation solutions that only change the display without changing the content actually being crawled.
Localization lets you translate each CMS field, each rich text block, each SEO attribute differently. So you can adapt a blog post not word-for-word, but culturally, a real advantage when targeting a market with different search behaviors (Germans don't search for the same thing as French speakers on the same topic).
This question comes up systematically during project scoping. Here are the key trade-offs.
| Criterion | Subfolders (/fr/, /de/) | Subdomains (fr.site.com) |
|---|---|---|
| SEO authority transferred | Inherited from the main domain | Must be built independently |
| DNS management simplicity | No extra configuration | Requires a CNAME record per subdomain |
| Analytics/server separation | Weaker | Cleaner, useful for complex multi-country setups |
| Recommended use case | Simple multilingual setup, 2 to 5 markets | Distinct local subsidiaries, separate marketing teams |
At Mazette.co, we recommend subfolders in the vast majority of cases. Domain authority builds faster when it's pooled together, and for a site targeting 3 or 4 European markets, the performance gap rarely justifies the technical complexity of subdomains.
This is the most important point in this article, and the one we repeat most often during client audits: Localization is a structural tool, not a content strategy. Turning on the feature and launching an automatic translation is never enough to rank internationally.
Translating word-for-word content optimized for the French market doesn't give you content optimized for the German market. Search volumes, intent, and query phrasing all differ. On a B2B SaaS project we supported into Spain, the direct translation of the main keyword generated 40 monthly searches: the actual term locally used by Spanish prospects generated over 800. Without local keyword research, Localization changes nothing about this problem.
If two locales point to nearly identical content without real personalization, Google can treat them as duplicate content despite well-configured hreflang tags. Hreflang tags indicate a relationship between language versions, they don't excuse content that isn't sufficiently differentiated.
A site that ranks well in France thanks to years of French backlinks doesn't automatically rank in Germany. Each market needs its own link-building strategy, local mentions, and possibly press partnerships or sector-specific directories in the target country.
A site that's fast in France can be slow in Australia if the CDN and Webflow servers aren't optimally positioned for that audience. Core Web Vitals should be measured market by market, something worth systematically checking in Google Search Console once locales are indexed, by splitting performance reports by country.
On the multi-market projects we run, we always follow the same sequence, in this precise order, never the reverse (translating first and structuring afterward is the most common mistake we fix during audits).
On a recent project for a design furniture brand looking to expand into Belgium and Switzerland alongside France, this method enabled a clean launch: all three locales indexed within two weeks, no geographic mix-up in the SERPs, and Belgian content that naturally incorporated local references (delivery, currency, the specifics of Belgian French) rather than a simple copy of the French site.
Since native Localization arrived, this question comes up legitimately. Our take: Weglot remains relevant in specific cases (large-scale automatic translation for sites with very high content volume, or a need for translation management outsourced to non-technical teams through a dedicated interface). But for a site with a well-controlled structure and a genuine SEO stake per market, native Localization offers finer control over tags, indexation, and URL structure, a decisive advantage as soon as international SEO is a business priority, not just a display convenience for foreign visitors.
{{webflow}}
Have you ever received a machine translation that was grammatically flawless but... just sounded wrong? Too formal for a casual brand, or conversely too casual for a premium B2B site? That's exactly the problem Webflow just tackled with its latest Localize update.
The starting point is simple but often overlooked: not all languages encode formality the same way. English, for instance, barely marks any register distinction in its grammar. French, German, Japanese, or Korean, on the other hand, require it through word choice, verb forms, or honorifics. The result: when you translate from a language that doesn't specify this level, the AI has to guess. And it often guesses wrong, or defaults to something generic.
Tone suffers from a different issue: it does exist in your source content, but translation tends to neutralize it by trying to fit the target language's rules. A brand with a strong voice, a bit edgy, or on the contrary very understated, often sees that personality evaporate during translation.
With this update, you can now independently define, for each target language:
In practice, this means you can set a formal register for your Japanese version, keep a warm and direct tone in French, and go for a more relaxed approach in Spanish, all from a single configuration panel, without having to go through a translation vendor for every adjustment.
This feature is limited to the Advanced Localize add-on or Enterprise plans that include Localize. A logical positioning: this is exactly the kind of fine-grained control that appeals to brands already committed to a serious multilingual strategy, not a single-language showcase site.
| Before this update | With adjustable tone and formality |
|---|---|
| Register guessed automatically, sometimes inconsistent | Fixed, controlled register per language |
| Tone that gets neutralized in translation | Tone preserved, even after translation |
| Manual adjustments language by language | Bulk application across multiple languages |
| Validation after the fact, often post-publication | Preview before publishing |
Webflow just announced an update that looks understated on paper, but clearly sets the stage for something bigger. The Localize feature is moving out of Site Settings to get its own panel, accessible directly from the left toolbar. Locales, Glossary, URL Routing and SEO each now have their own dedicated menu.
In practice, if you have been managing a multilingual site on Webflow so far, you know that localization settings used to be buried inside a general screen designed for technical site configuration, not for real editorial and linguistic work. It was functional, but never comfortable.
The language selector at the top of the interface still works exactly as before. The difference is that it now redirects you to this new structured panel, instead of a tab lost somewhere in the middle of general settings.
Each piece now has its own space. No more jumping between multiple tabs to figure out where a given setting lives.
Webflow spells it out clearly: translation capabilities are in the works, and they will be built directly on top of this panel. In other words, this is not just cosmetic tidying. It is a technical foundation designed to support, likely quite soon, more advanced translation tools, potentially automated or AI-assisted, in line with the platform's recent announcements on this front.
| Before | After |
|---|---|
| Localization settings buried in Site Settings | Dedicated Localize panel in the sidebar |
| Confusing navigation across multiple tabs | Locales, Glossary, Routing and SEO grouped together |
| No clear vision for the multilingual roadmap | Foundation laid for upcoming native translation |
If you are planning to roll out your Webflow site in multiple languages, or if you already manage a multilingual site that is becoming harder to maintain, now is a good time to rethink your localization architecture. A multilingual SEO audit before the new translation features land could save you from having to start over later.
At Mazette.co, we regularly help clients tackle these multilingual structuring challenges, particularly on SEO issues tied to URL routing and per-language indexing. If your site deserves a fresh look before Webflow rolls out its new tools, let's talk.
Localization is a real technical step forward for Webflow: it closes a gap that used to put the platform at a disadvantage compared to more mature multilingual CMS options. But what it really changes is how you build a multi-market site, not how you make it rank. International SEO remains its own discipline: local keyword research, country-by-country link building, cultural content adaptation, differentiated performance tracking. Localization gives you the right tools. It never replaces the strategy.
If you're preparing an international expansion or a migration to Webflow with a multi-market challenge, our SEO and Webflow team can frame the technical structure before you even think about design or content: that's the order in which multilingual projects actually succeed.
Code
Over 180 companies have already stepped out of the shadows with us.
Not systematically. Localization offers better native SEO control over hreflang tags and URL structure, which is preferable for a serious international SEO strategy. Weglot remains useful for large-scale automatic translation managed by non-technical teams.
Subfolders like /fr/ or /de/ are recommended in most cases because they directly inherit the authority of the main domain. Subdomains make sense mainly for distinct local subsidiaries with separate teams and business organization.
No, translation alone is never enough. You need keyword research specific to each market, cultural adaptation of content, and a local link-building strategy, otherwise the site stays poorly ranked despite a correct technical structure.
Impactful titles, polished meta descriptions, sitemaps, Schema.org, Hn structure, and audits: these are the SEO foundations that make your content readable by both Google AND generative AI. We cover both simultaneously.
With over 180 clients, our agency is one of the few in France to hold the Webflow Premium Partner label, supporting you in every area, including custom web design, sophisticated automation, conversion optimization, and SEO and GEO visibility.
We create bespoke web designs focused on performance, user journeys, and conversion. Join over 180 clients who have trusted us to elevate their brand.
