CMS Collection lists and templates
Blog posts, case studies, team pages and any Collection list or template page are translated as they render. New CMS items are picked up when visitors see them, with no extra fields or duplicate Collections.
Make your Webflow site multilingual without rebuilding a single page per locale. SiteTran translates static pages, CMS Collection lists, forms and your store's cart and checkout in the visitor's browser, priced by words instead of per language.
Turn raw data into clear weekly reports, no SQL required.
Driving growth for companies with millions of users
SiteTran runs as a short script on your published Webflow site. You keep designing in Webflow as usual, and SiteTran swaps in each visitor's language.
Sign up free and add your Webflow site. SiteTran gives you your Widget Code, which loads translations and adds the language dropdown.
Add the Widget Code once for the whole site, click Save changes, then publish.
Open your published site and pick a language. SiteTran discovers your text, then you translate it with AI, your own translators, or both, and publish.
<script>var sitetran = { site_id: your_site_id };</script> <script src="//c.sitetran.com/widget/v3.js"></script> <div id="sitetran_translate_element"></div>
SiteTran gives you your own ready-to-paste code, with your site ID already in it. The div marks where the language dropdown appears, so where you paste the code decides where the dropdown shows up.
The Widget Code loads on every page, including CMS templates and your store's checkout pages. The dropdown is added at the end of the page, so pin it to a corner with a few lines of CSS in your dropdown style.
Add a Code Embed element to your navbar component and paste the Widget Code there. The dropdown sits in your navigation on every page that uses that component. This is the method our setup guide walks through.
Use one method, not both, so the Widget Code loads once per page. Both use Webflow custom code, included with paid Site plans and with paid Workspace plans for webflow.io staging sites. See which plans include it.
Webflow sites mix static pages, CMS content, Interactions, forms and sometimes a store. Here's how SiteTran handles each part, so every visitor gets the full experience in their language.
Blog posts, case studies, team pages and any Collection list or template page are translated as they render. New CMS items are picked up when visitors see them, with no extra fields or duplicate Collections.
Tabs, sliders, dropdowns, lightboxes and items added by CMS filter or load-more scripts are translated when they appear. SiteTran keeps watching the page for new content.
Classic and GSAP-powered Interactions keep running, because SiteTran changes text, not your classes or structure. Split-text effects break a heading into separate letters or words, so check those headings in each language.
Labels, placeholders, options, buttons and the success and error messages are translated. Submissions arrive as visitors typed them.
Product pages, the cart, checkout and order confirmation pages are translated when the Widget Code loads on them. Shoppers read product details, shipping options and order totals in their own language, right up to the purchase.
Webflow retired User Accounts on January 29, 2026, so most member sites now use a third-party tool. Login forms, account menus and gated content it adds to your page are translated with the rest of your site.
Alt text is translated with your page. For images with words baked in, translate the image URL and SiteTran shows a different image file for each language.
Nothing is written to your project or CMS. Pages, components, styles and Collection items stay in your original language, and you keep publishing from Webflow as usual.
The SEO and Open Graph titles and descriptions you set in Webflow are translated. Languages share your URL by default; indexable language URLs use our Static Translation API. See the details.
Every translation tool that runs as a script needs Webflow's custom code. Check your plan first, then compare what each extra language adds to your bill.
Custom code, including Code Embed elements, depends on your Site plan or Workspace plan.
| Webflow plan | Custom code |
|---|---|
| Starter Site planFree, webflow.io domain | No Unless your Workspace plan is paid |
| Basic or Premium Site planCustom domain | Yes |
| Ecommerce Site plansStandard, Plus, Advanced | Yes |
| Paid Workspace planCore, Growth and up | Yes On webflow.io staging sites |
Plan names from webflow.com/pricing, checked October 20, 2026. Webflow can change its plans, so confirm in your Webflow dashboard.
Webflow Localize is priced per locale. SiteTran is priced by words and pageviews, with unlimited languages.
Localize prices are $9 (Essential, up to 3 locales) and $29 (Advanced, up to 10 locales) per locale per month, billed yearly, from webflow.com/pricing on October 20, 2026. Localize is added to a paid Site plan, and SiteTran needs a plan with custom code, so your Site plan applies in both cases. SiteTran plans also include 3K to 125K translated pageviews per month; a busy site may need a larger plan than its word count suggests.
There are four common approaches. The right one depends on how many languages you need, whether you sell with Webflow Ecommerce, and how much SEO work you want to take on.
Translations live in your Webflow project: either pages and Collections you duplicate yourself, or locales managed by Webflow Localize. Each language is part of what you design and publish.
A separate service translates the site Webflow publishes, either with a script in the browser, like SiteTran, or through a proxy that your domain or language subdomains point to.
| Duplicate pagesFolders and fields per language | Webflow LocalizeNative add-on, per locale | Translation proxyDNS-based services | SiteTranOne script in custom code | |
|---|---|---|---|---|
| How it works | Copy pages into a folder such as /es/ and add a field or Collection per language. | Add locales, then translate pages, CMS items and components for each locale in Webflow. | Your domain or language subdomains point to the service, which serves translated copies of your pages. | Translates your published site in the visitor's browser. |
| Work in Webflow | Every page, component and Collection change is repeated per language. | Translate and review each locale in Webflow, with per-locale styles and images. | DNS records per language, or for your whole domain. | None after the one-time paste. |
| CMS content | Extra fields or Collections, which count toward CMS limits. | Yes, per-locale content for each Collection item. | Yes, from the published pages. | Yes, translated as it's displayed. |
| Ecommerce | Product fields can be duplicated; cart and checkout exist once. | Not supported for products, categories or Ecommerce pages. | Varies by service. | Product, cart and checkout text on your domain. |
| Machine translation | No. | Yes, with monthly AI word allowances per locale. | Yes. | Yes, with DeepL, Google Translate and OpenAI. |
| Translators | Work in Webflow. | Work in Webflow or through a partner translation app. | Work in the service's dashboard. | Translators and reviewers per language, no Webflow access. |
| Language URLs | Yes. Add hreflang tags yourself. | Subdirectories and hreflang sitemap; translated slugs on Advanced. | Yes, often on higher-priced plans. | Same URL by default; indexable URLs via the Static Translation API. |
| Pricing model | No add-on, but your time for every update. | Per locale, per month, on top of a paid Site plan. | Monthly plans by words and languages. | Free plan, then $3 to $75 a month. Unlimited languages. |
Webflow Localize details from webflow.com/pricing and Webflow's documentation, checked October 20, 2026. Proxy services vary; check each provider's current plans.
Start with machine translation and refine it with your own team. You decide what gets approved and when it goes live on your Webflow site.
Get suggestions for any phrase, or translate new phrases automatically, such as each new blog post. You choose whether they're approved automatically or reviewed first.
Invite your own translators for each language and choose who can approve. They work in SiteTran, so you don't add anyone to your Webflow Workspace. Turn on AI Translation Review for a second opinion.
Lock product names and brand terms in the Glossary, set Translation Rules that AI translation follows, and reuse past work with Similar Phrases.
Choose from three dropdown types, with or without flags, and add your own CSS to match your site's fonts and colors. Visitors are switched to their browser language automatically.
Your titles, descriptions and link previews are translated as soon as you install SiteTran, and you can add indexable language URLs when you're ready to grow search traffic.
SiteTran translates more than visible text. When a visitor switches language, the metadata you set in Webflow's page settings and Collection templates switches with it.
lang attribute, set to the selected languageBy default, every language uses your existing Webflow URL and the visitor's choice is remembered. For a separate, indexable page per language, SiteTran's Static Translation API returns translated HTML for URLs like these:
You serve these pages through a small edge worker or proxy. A language subdomain is often the simplest route, because your main domain keeps pointing at Webflow. We'll help you plan it.
Talk to us about Webflow SEOFollow the integration guide, Translate Webflow with SiteTran, for every click from copying your Widget Code to testing your published site.
Most questions come down to where the code was pasted, publishing the site, or publishing a new translation.
?sitetran=on to your URL.#sitetran_translate_element, for example fixed to the top right.notranslate class to the element, or a custom attribute translate = no in Element settings.notranslate.Every plan includes unlimited languages and teammates. Start free and upgrade when your traffic grows.
For landing pages and testing
For sites with moderate translation needs
For CMS-heavy sites or several smaller ones
For large international sites and stores
Can't find your answer? Our team is happy to help with your Webflow setup.
Email supportnotranslate class to an element, or add a custom attribute named translate with the value no in the element's settings. You can also list selectors in sitetran.ignore_selectors. Use this for author names, addresses and other personal data. For text that changes inside a sentence, such as names, dates and prices, use variables so one translation covers every value.Paste one script, publish, and reach visitors in the language they read best. Start on the Free plan and add as many languages as you like.