Each page and CMS entry is translatable. When creating fields for a Collection, mark whether that field is translatable (some fields won't need translation, like references to other collections, price fields, etc).
An option for Links should be added to choose a language (in addition to external links, pages within the site, etc).
We recognize that multi-language functionality is very important and will allow everyone to create inclusive language experiences on their sites. It’s definitely something we plan to build the right way within Webflow.
Please continue to give us feedback. We're listening to how such a feature could enable you build multi-language sites.
It's hard to imagine the way of multi-language on Webflow.
There are 3 common ways:
Weglot / Transifex?
TranslatePress on WordPress
Drupal's Multi-language / WPML on WordPress
I think the way how TranslatePress works on WordPress is the best experience and best suitable for WordPress.
( However, machine translation function is not very necessary in my point of view. )
Need this!
We are on the Business plan with a Global CDN. However, without multilanguages the global CDN is not entirely useful.
This should be the next development with priority 1. The issue was raised in 2017 and still nothing but a comment from admin.
Weblfow, could you give us a quick update on multilanguage functionality?
This should really be the next thing webflow prioritizes after logic and membership is out of beta. I cannot believe that webflow sends E-Mails with content like; do not write "see more" on a button - since that could exclude blind people, but they think it's absolutely ok to exclude not only millions - but billions of people by not offering multi-language.
I'm wondering, can the announced 'Logic' help us with this.
Can someone from Webflow comment on this?
When is this coming? This is urgently needed!
How is it going?
Any updates?
Webflow team, any updates on if/when localization support will be built inside the platform? Many drawbacks of 3rd party plugins, including: (1) expensive when you need to support many languages, (2) can't customize entire blocks of the page, (3) extra load time to serve localizations, (4) makes workflow more difficult to need to use a different platform.
I wish that the Webflow avoids 3 annoying drawbacks from Weglot:
If you edit 1 word in the source language, you lose your manual translations in all languages. And then you're good to enter them again, which is a huge waste of time.
Weglot generates hundreds of deprecated translations. Though they are inactive, they increase your word count. You have to delete them regularly not to be obliged to upgrade your plan - just another way to waste your time.
As mentioned by other users, slug translations are not included unless you subscribe a very expensive plan.
Though Weglot support team is responsive and helpful, the inconvenience of their solution make me look forward to Webflow's native multi-language feature.
We recently took Weglot in use and it seems to work quite well. They have a beta version available for subfolder structure (in addition to subdomain support) – that was important to us to keep the domain look clean.
One drawback is that the slug translation is only included in their Advanced tier that is very expensive for this single feature we'd need. It would be great if they'd offer this in the lower tiers as well.
We're a global company evaluating several CMS options for migrating our site. Webflow checks every box except native localization support, which will likely be a dealbreaker for us. Main problems with the 3rd party proxy solutions that we've seen so far:
Lack of control over localized SEO
Can't add/remove entire content blocks for specific locales
Noticeable delay when serving localized content (seeing around 1-2 seconds)
Significant cost for a high traffic site like ours
Chiming in from Belgium. My country has 3 official languages (Dutch, French and German), with English also being very important (us being the host country of the EU and NATO headquarters, amongst other international institutions). Multilanguage features are very important for us, and it would mean the world if Webflow supported this natively.
Weglot is an excellent solution technically, but it is too expensive for small businesses that need a relatively simple website that supports 3-4 languages. If Webflow supported this natively it would be so much easier for us to sell Webflow projects to our clients!
It for sure should be a CMS native feature. It a huge dealbreaker.
I was really excited to try webflow but I think this is going to be much more of a challenge than worth trying unless a multilingual option is native to webflow. Bring this functionality soon or webflow will keep losing all multinational companies.
I am amazed in an international world that this is not a thing that is included from the beginning. Coming from the games industry where it is required to support multiple languages the solutions where very simple and very effective. This feature will not be ready for my current projects, but I really enjoy Webflow and want it to succeed. Please support the option to add translated text.
Webflow is awesome on many aspects, but not supporting multi-language is so crucial, that I cannot even consider using it for future projects.