I speak Greek and this new feature was the spilling point that finally brought me over to webflow. I’m exited to learn the platform and join the community.
Hi, I have a question about localising Ecommerce items? When I switch the language to edit the text, I see only CMS tab but the E-Commerce tab vanishes. Any suggestions? Thank you! :)
Hi, thanks for this powerful feature! We love it. 😍 What happens to the indexation when we deactivate Weglot for the "localisation webflow native solution"? Are our pages still online or do they appear in 404? Do we have to revise the existing URL to write the same thing as before? What impact will this have on SEO? Many thx.
Is there a way to translate complete CMS on one click instead of translate each CMS item (record)? manually its taking a lot of time and I think we are wasting money by enabling this feature, weglot is much better
Is it possible to make it instead of saying “Languages” it will just have a flag of the currently selected locale and then the dropdown will showcase the flags of the other available locales? If so how would I achieve this?
Great stuff! Only think I disliked was the lack of possibility to edit locale in Editor. My clients know only this mode, and would expect you to add this new functionality there too. Hope you will fix it in the future.
Good question. I'm using Weglot for a customer, but used the javascript version, so it translates the page on the user site. The SEO ratings have dropped because of this, because Google thinks there's just one version. So I'm looking for a way to have subdirectories and Localization provides this. Also, with Localization you can really swap assets, or hide assets, which isn't possible with Weglot. If someone can say more about ways to make subdirectories without Localization, please share!
You now have the ability to bulk localize every field in a single CMS item. Will let the team know you'd like the ability to localize all items in a collection! webflow.com/feature/bulk-field-translation-for-single-cms-items
@@Webflow Sorry, but this is nuts. I just pulled the trigger, and I'm regretting it now. Not only do I have to click on the body tag for every page, under each localization (30 pages x 2 new locales)... I now have to go through each of our 252 items across our 8 collections, and open each 1 by 1? Without essentials like this, I feel like this is a paid beta. Step one after paying for localization, of course I want to auto translate everything everywhere on the site! Is this not obvious? I can't believe this made it out of a beta without something like this requested by any testers on the first day. I mean a PM should have figured this out probably before you did a line a code, much less an alpha. 🧠🔫
Nice demo, however the Webflow page with the pricing says in regards to Localization that it is only paid once the site is published. this isn't clear seeing that i'm already using a paid Basic plan (14$/month). So how much extra in payment is required to publish Localized content?
Anyone can use localization for free while they're exploring in the designer, however if you'd like to add multiple locales (languages) and publish to your live site you'll need to find a plan that fits your needs. The lowest price for localization starts at $9/mo (annually) or $13/mo if you do month to month
What about localisation from the Editor? Currently, it's clunky to switch but does work in Collections - how about static pages? I don't seem to find an option to edit static page translations... any help appreciated!
I already launched a website for client, using the javascript (client side) version of Weglot. But SEO ratings have dropped for English (the secondary and almost equally important locale), because I didn't now Google doesn't recognize the client sided translated page as a different language. Now looking for a way to use subdirectories to crank back up the Google rating. So I could use Localization, but the site has about 500 CMS items with each a couple of paragraphs of texts. Manually translating them is a lot of work, as @Arctic Econoline stated in the live chat because he/she is in a similar position. * Is it possible to automate this, so translating all 500 CMS items automatically? * Is there another way to add subdirectories to the site, this way being able to keep on using Weglot, since we've already paid for the year? * Can editors make translations in the Editor? Didn't fully grasp the answer of Joanna, but guess she said editors have to go to the Designer and translate from there? Hope someone can shine some light on the questions.
What about component property values? If I use a CTA button saved as a component, but then change that CTA copy on different instances. I assume we need to go an manually translate every instance?
Does the webflow website auto detect the locale let's say website has two locales English and Dutch if I access the website in Germany it will show all the content in Dutch or do I have to select the locale for Dutch?
Great session! But I am still wondering whether there’s a way to publish the newly added locale to the staging site, or the plan must be upgraded first?
Does it Geotag based on the visitors location? I.e if I want a UK Version of my site and the visitor is from UK will it auto recognize them from the UK and send them that site?
It depends on your settings, you can adjust based on location or based on preference. So a user can select their preferred language or you can have it auto-detect.
I was really happy until I realized that crucial features are only available in the enterprise plan for an unreasonable price. Hiding a page in one locale? Enterprise. Hiding elements? Enterprise. Styling elements to e.g. keep a headline in 2 lines in both languages? Enterprise… Does that make sense for you guys or do clients stay at Weglot? Or do we go with custom code and workarounds. It’s really sad, that the proper use is limited to the small fraction of enterprise users.
No my question was deleted. Interesting. BTW it's Tina Turner. Thee one and only Tina Turner. ... Interesting that in order to translate CMS content, you have to click in fields to 'magic translate', or do so manually every field you want translated? Imagine you have a collection list with 25 fields, and you have 50 items in that list. Pricing issues, also a fairly large step from $9 to $29 for things like locale specific images, and localized slug. As opposed to what other locale slug? Plus, to try this out, you really can't do anything without paying Webflow. You cannot even put the locale wrapper on a page, and have it show the 2nd locale. What?????
Hey Michael, Thanks for the feedback-to magic (machine) translate CMS items, you do need to go field by field. Only published locales appear in the locale picker which require the right plan-that is correct. We appreciate the feedback here (on the features and pricing), I'll bring that to the team!
Language and localisation should be 2 things. Belgium has 3 languages. And I don't want French speaking Belgians to see my offering ment for the country France.
Hi Johan! They are indeed separate in Webflow. You can select between Belgium French, Canadian French or France French as your locale and this is the case for all locales that have regional variance like French.
![How to create a Multi-Language site in Webflow [2025]](/img/n.gif)
We now have a free course covering everything you need to know to localize your sites in Webflow: university.webflow.com/localize
I speak Greek and this new feature was the spilling point that finally brought me over to webflow.
I’m exited to learn the platform and join the community.
Arron is french-Canadian. that explains so much.
This so cool ! Thank you Webflow! Cheers from Riga!
Hi, I have a question about localising Ecommerce items? When I switch the language to edit the text, I see only CMS tab but the E-Commerce tab vanishes. Any suggestions? Thank you! :)
i have the same problem. it seems tha ecom items aren't supported on localizations.
Ecommerce is NOT support at this moment of time. With kind regards Dominic
Great introduction to this new superpower! Greetings from France 🙂
Salut!
French Canadian! Oui monsieur! 🥳
Hi, thanks for this powerful feature! We love it. 😍
What happens to the indexation when we deactivate Weglot for the "localisation webflow native solution"? Are our pages still online or do they appear in 404? Do we have to revise the existing URL to write the same thing as before? What impact will this have on SEO?
Many thx.
Is there a way to translate complete CMS on one click instead of translate each CMS item (record)?
manually its taking a lot of time and I think we are wasting money by enabling this feature, weglot is much better
AOA
I am unable to modify the text once the localization option is enabled sometimes.
Is it possible to make it instead of saying “Languages” it will just have a flag of the currently selected locale and then the dropdown will showcase the flags of the other available locales?
If so how would I achieve this?
Wondering the same
Great stuff! Only think I disliked was the lack of possibility to edit locale in Editor. My clients know only this mode, and would expect you to add this new functionality there too. Hope you will fix it in the future.
How do i localize text in my custom properties, for example (data words)?
What is the advantage of this over Weglot? Because it is pretty expensive to add locals.
Good question. I'm using Weglot for a customer, but used the javascript version, so it translates the page on the user site. The SEO ratings have dropped because of this, because Google thinks there's just one version. So I'm looking for a way to have subdirectories and Localization provides this. Also, with Localization you can really swap assets, or hide assets, which isn't possible with Weglot.
If someone can say more about ways to make subdirectories without Localization, please share!
Hey, I have 200 blog articles, does it mean I'll have to go and manually localize every elements?
You now have the ability to bulk localize every field in a single CMS item. Will let the team know you'd like the ability to localize all items in a collection! webflow.com/feature/bulk-field-translation-for-single-cms-items
@@Webflow Sorry, but this is nuts. I just pulled the trigger, and I'm regretting it now. Not only do I have to click on the body tag for every page, under each localization (30 pages x 2 new locales)... I now have to go through each of our 252 items across our 8 collections, and open each 1 by 1?
Without essentials like this, I feel like this is a paid beta. Step one after paying for localization, of course I want to auto translate everything everywhere on the site! Is this not obvious? I can't believe this made it out of a beta without something like this requested by any testers on the first day. I mean a PM should have figured this out probably before you did a line a code, much less an alpha. 🧠🔫
Nice demo, however the Webflow page with the pricing says in regards to Localization that it is only paid once the site is published. this isn't clear seeing that i'm already using a paid Basic plan (14$/month). So how much extra in payment is required to publish Localized content?
Anyone can use localization for free while they're exploring in the designer, however if you'd like to add multiple locales (languages) and publish to your live site you'll need to find a plan that fits your needs.
The lowest price for localization starts at $9/mo (annually) or $13/mo if you do month to month
What about localisation from the Editor? Currently, it's clunky to switch but does work in Collections - how about static pages? I don't seem to find an option to edit static page translations... any help appreciated!
Hi Emma! Localization is not supported in the editor.
I already launched a website for client, using the javascript (client side) version of Weglot. But SEO ratings have dropped for English (the secondary and almost equally important locale), because I didn't now Google doesn't recognize the client sided translated page as a different language. Now looking for a way to use subdirectories to crank back up the Google rating. So I could use Localization, but the site has about 500 CMS items with each a couple of paragraphs of texts. Manually translating them is a lot of work, as @Arctic Econoline stated in the live chat because he/she is in a similar position.
* Is it possible to automate this, so translating all 500 CMS items automatically?
* Is there another way to add subdirectories to the site, this way being able to keep on using Weglot, since we've already paid for the year?
* Can editors make translations in the Editor? Didn't fully grasp the answer of Joanna, but guess she said editors have to go to the Designer and translate from there?
Hope someone can shine some light on the questions.
I've experience when I change the from US to FR my div block are gone.
How do you delete local? I am trying to change my local and it is giving me a duplicate error
What about Ecommerce, Forms, and the Editor? Is there a roadmap?
Hey Simon! Forms can be localized, I'll let the team know about your feedback for the rest!
Polish! Greetings from Poland :)
Great question!
What about component property values? If I use a CTA button saved as a component, but then change that CTA copy on different instances. I assume we need to go an manually translate every instance?
Component property need to be manually translated, that is correct!
Does the webflow website auto detect the locale let's say website has two locales English and Dutch if I access the website in Germany it will show all the content in Dutch or do I have to select the locale for Dutch?
Automatic visitor routing is available on the advanced plan, check out all of the options here: webflow.com/localization
Great session! But I am still wondering whether there’s a way to publish the newly added locale to the staging site, or the plan must be upgraded first?
Hey Daryl, to publish you need a localization plan!
I assume you can't export the site, this has to be CMS?
Hi, what about Ecommerce and forms ... especially the email-flow. Is this also part of localisation?
Forms are included but not e-commerce emails, will let the team know your feedback!
Seems like you have to publish the site to actually preview the locales. Is that correct?
Edit: Tried it, indeed this seems to be the case.
In preview mode, it will list all published locales.
Does it Geotag based on the visitors location? I.e if I want a UK Version of my site and the visitor is from UK will it auto recognize them from the UK and send them that site?
It depends on your settings, you can adjust based on location or based on preference. So a user can select their preferred language or you can have it auto-detect.
“Ayubowan” Greeting from Sri Lanka🙂
I was really happy until I realized that crucial features are only available in the enterprise plan for an unreasonable price. Hiding a page in one locale? Enterprise. Hiding elements? Enterprise. Styling elements to e.g. keep a headline in 2 lines in both languages? Enterprise… Does that make sense for you guys or do clients stay at Weglot? Or do we go with custom code and workarounds. It’s really sad, that the proper use is limited to the small fraction of enterprise users.
It’s also not mentioned in your tutorials…
No ideas! Say what means that localization? Here's in British English one word "localisation".
Pls add Uzbek Language Support
Tabarnak !
👀going to act like I've never heard that word before
No my question was deleted. Interesting. BTW it's Tina Turner. Thee one and only Tina Turner. ... Interesting that in order to translate CMS content, you have to click in fields to 'magic translate', or do so manually every field you want translated? Imagine you have a collection list with 25 fields, and you have 50 items in that list. Pricing issues, also a fairly large step from $9 to $29 for things like locale specific images, and localized slug. As opposed to what other locale slug? Plus, to try this out, you really can't do anything without paying Webflow. You cannot even put the locale wrapper on a page, and have it show the 2nd locale. What?????
Saying what for the CMS? It means slug.
@@pilot341 that is correct ✌️
Hey Michael, Thanks for the feedback-to magic (machine) translate CMS items, you do need to go field by field. Only published locales appear in the locale picker which require the right plan-that is correct. We appreciate the feedback here (on the features and pricing), I'll bring that to the team!
Update: you can now translate all fields in an item with one click webflow.com/feature/bulk-field-translation-for-single-cms-items
ofc you need to pay for it
Language and localisation should be 2 things. Belgium has 3 languages. And I don't want French speaking Belgians to see my offering ment for the country France.
Hi Johan! They are indeed separate in Webflow. You can select between Belgium French, Canadian French or France French as your locale and this is the case for all locales that have regional variance like French.
german
Ich ferhstein kein deutsch is all I know in German!