Multi-language sites and CMS fields

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).

  • Brent Cartier
  • Jan 18 2017
  • Reviewed
  • Aug 28, 2021

    Admin response

    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.

  • Val commented
    18 Sep 01:35pm

    Please bear SEO in mind! Because having the same URL with only content traslated it's pretty useless if not harmful for your website, (Weglot it's definitely not a solution). With my agency as soon as we have a multi-linguage project we directly develop on WordPress.

  • Guillaume Langlois commented
    16 Sep 10:47pm

    The only possible (and intelligent!) workaround to systematic localization was clever usage of CMS multi-references and nesting. However, I discovered this is limited to 5 multi-refs and a single nested collection per page! Why would such a limitation be imposed on us loyal customers is beyond me.

  • Thomas Lynch commented
    2 Sep 03:07pm

    @Mark Joncheff

    I use,, its really cheap and we have tested it in a few languages with native speaking like Russian, French and Spanish and it seems to work really well.

    ConveyThis doesn't follow a single SEO optimization. It got my content penalized and removed from google because of duplicate content, amongst a list of other problems I had. When reporting this to the company they returned my money, proving they have no real solution.

  • Marco Ceruti commented
    29 Aug 04:57pm

    We want an ETD!

    It was in the roadmap and then it was removed. Now you say "is very important and will allow everyone to create inclusive language experiences on their sites", but when?

    It's incredible that such a big company, after such a big round of investemnt, doesn't take seriously the concept of "global market"!

    We are also willing to pay more for multilanguage hosting, but this issue is driving me crazy. Every other platform on the web includes this simple feature! Squarespace, Wix, EditorX... even Tilda!

    You have to fix this because that's the biggest problem you have right now!

  • Kyle F commented
    28 Aug 12:54am

    @Mark Joncheff. Conveythis is not cheap. $15 is the same price as the entire Webflow basic hosting/platform, just for translations.

    Please stop using this thread to advertise workarounds like Weglot and Conveythis. The purpose of this thread is to get a NATIVE CMS solution from Webflow. We are not interested in workarounds. Thanks!

  • Mark Joncheff commented
    27 Aug 12:52am

    I use,, its really cheap and we have tested it in a few languages with native speaking like Russian, French and Spanish and it seems to work really well.

  • Javier Rodriguez commented
    26 Aug 10:27am

    With Weglot you have

    • your SEO broken,

    • your Analytics meaningless,

    • and no control of content according to language.

    So, I have no chance to bring this CMS to customers in Europe.

    Sad, because the Designer is as yet one of the best in the market.

  • Kyle F commented
    19 Aug 06:31pm

    This has been pending since 2017. Multi language MUST be a PRIORITY. Just heard Vlad saying in the stream that basically there's no concrete plan for this. So disappointing!

  • Ben Smith commented
    12 Aug 04:22pm


  • mBusiness GmbH commented
    20 Jul 08:59pm

    Really sad how ignorant Webflow deals with this top voted requirement.

  • Gregory Zagkos commented
    17 Jul 10:51am

    Weglot is way too expensive. Not helping at all. Here in Europe pretty much every second business needs more than 1 language. Especially here in Switzerland, we have 4 native languages.

  • Jeroen van der Elst commented
    16 Jul 12:43pm

    Weglot only provides subdomain support, no subdirectory support. Being able to use subdirectories is a must for SEO. When your current site uses subdirectories for example .com/en or .com/de and you swap to and the penalty for SEO is HUGE.

  • Simon Wachtler commented
    11 Jul 10:33am

    This is absolutly neccessary!!!

  • Daan Steegmans commented
    7 Jul 09:05am

    This really needs to get done. We have built a big corporate website and using Weglot does not work at all for us and I believe a lot of others developers agree on this..

    Get this done Webflow..

  • Urs Odermatt commented
    25 Jun 07:21am

    DO THIS WITH PRIORITY. it is a base funicionality.

  • Tomas Ferezou commented
    9 Jun 06:33am

    How can this not be a priority? Webflow says there is Weglot out there (there are actually numerous other options) but it is so expensive that it hurts our business case (and Webflow's). And even if you don't look at the price, it is just not maintanable for larger websites, where every comma changed in the original language changes the end translation. How can you even pretend this is a solution? It's preposterous and arrogant from Webflow.

  • Christoffer Furnes commented
    27 May 11:43am

    Have been using Weglot on several projects lately. It's just not good enough for enterprise solutions. The UX experience for the client is terrible and there is a lot of issues with SEO, handling language versions of files and links, URL translations and much more. Weglot is an impressive hack, but it's exactly that; a hack, NOT a viable solution.

  • Ana Labudovic commented
    25 May 12:13pm

    come on webflow! you will lose me over this one..

  • Simon Hausdorf commented
    18 May 06:51pm

    wow, this is from 2017, is ranked second in popular and webflow keeps recommanding 3rd party solutions?

  • Javier Rodriguez commented
    17 May 10:11am

    I don't mind paying something for automatic translation. However, I would like to have both the functionality and hosting of my pages in one place; Webflow. That is also the reason why I am not on WordPress.

    In my eyes it is a wrong decision not to prioritize this fundamental function of a CMS.

  • Load older comments
  • +6333