Insights from Translating Over 500 Pages with Webflow Localization

Hi everyone,

I wanted to share my experience after converting my website from English to German and Spanish. The native implementation of localization in Webflow was impressively executed.

Webflow allows for the translation of entire web pages, individual texts, and CMS content. This is done by simply clicking the translate button for each element. While a single button for translating everything would be convenient, translating each page or CMS item individually does minimize the need for extensive Q/A later.

Here are some observations and areas for potential improvement:

  1. At times, the translation feature can be inconsistent. For example, sections that have been translated occasionally revert to the original language. This issue particularly affects elements that are ‘components’. I had to revisit and re-save certain sections several times. However, considering that this feature is only a day old, it’s a minor inconvenience.

  2. Webflow creates a duplicate of your site for translation purposes. However, it doesn’t allow editing or translating content within the and before the tags. This can be a drawback for those engaged in advanced SEO strategies. I hope to see improvements in this area soon.

  3. The sitemap.xml file requires enhancements for better recognition by Google. Currently, Webflow lists each translated page as an alternative to the root page, but Google Webmaster Tools doesn’t recognize these new pages despite changes in the URL structure. I suggest Webflow adhere more closely to Google’s best practices, such as listing each newly translated page as a root URL. More details can be found here: Google Developers Guide.

Lastly, let’s discuss pricing. If SEO is a priority, localized URLs are essential and you have to choose the “advanced” plan. However, Webflow charges $35 per month for each localization/language. This can be quite expensive for those looking to translate their website into 3-5 languages, especially if the site already has decent traffic. e.g. 5 languages would cost you $175 per month or $145 if you choose the yearly plan. That’s quite steep and makes me reconsider 3rd party alternatives (curious to know what the best alternative is, feel free to post below)

I hope this was helpful to either users who are planning on using Webflow Localization or the Webflow product team!


@Eddywi I’m planning to start the first project with Webflow localization this week. Thanks for your input!

My biggest concern now is that the client can no longer use the old editor included in the hosting plans, but will have to buy additional Workspace Designer seats to edit their site, this adds a big cost increase on localization on top of the localization functionality.

  • Hosting (CMS) = 23$
  • Localization (Advanced) 1 language = 29$
  • Workspace seat (1 seat) = 19$
    = 71$ /month

Since most clients need more than 1 editor seat, the costs for the client to edit their site will be considerable!

The site I’m planning for a new client now will need 2 extra languages and 3 editor seats. Monthly costs will be a whopping 138$ /month! There is a big chance we have to revert to Weglot.


Thanks for your insights.

At first sights it seems very well worked out and intuitive to use.

Though the pricing looks out of proportion to me.
When you want to add one language in the advanced version: you pay $6/month more then to create another CMS hosted website project which costs $23/month.

From a pricing perspective it is cheaper to have a dedicated url website per language (,, …), than use the localisation feature.

1 Like

I find Webflow becoming extremely greedy. There is no justification for such a bump in pricing from year to year, considering the income of an average freelancer.

If we look into other industries offering more complex solutions and running larger teams, we find products more accessible prices-wise.


Actually, I wonder - this “workspace seat” … here: Localization overview - Webflow University Documentation - ignoring the anchor name, it does say you “You can click the Locale view dropdown and choose a secondary locale from the list to access your site in design mode, edit mode, or preview mode.” Which… I assume means any Editor can acess the translations. BUT, assuming can be dangerous. So far, other than this reference, I cannot find much clear documentation that the edit mode for content editors are supported. And, the “preview” you can try in Designer, doesn’t suppot viewing the translated page with the Editor.