How to Translate a Webflow Site Into Multiple Languages
Webflow actually has a built-in localization feature. It shipped in late 2023, and it works — you get separate URLs per locale, proper hreflang tags, and Google indexes each language version independently.
So why would you need a third-party translation tool?
Because Webflow's localization costs real money. You pay extra per locale on top of your existing Webflow plan. For a site that needs five or six languages, the locale fees add up fast. And the setup isn't simple — you're duplicating pages, managing translated CMS content, and dealing with Webflow's localization UI, which has a learning curve.
If you need full multilingual SEO with separate URLs and hreflang tags, Webflow's native localization (or a proxy tool like Weglot) is the right call. But if you just need visitors to read your site in their language — a portfolio, a startup landing page, an agency site — there's a much simpler way.
Your options for translating a Webflow site
Webflow's native localization
The official solution. You add locales to your project, Webflow creates translated versions of each page, and you get proper /fr/, /es/ subdirectories. SEO-friendly, Google indexes each version, hreflang tags are automatic.
The downsides: each additional locale costs money on top of your Webflow plan. You have to manually review and edit translations for every page and CMS item. The workflow for managing translations across a large site is time-consuming. And if you're on a lower Webflow plan, locale limits are tight.
For large marketing sites with dedicated content teams doing serious international SEO, this is the right approach.
Proxy tools like Weglot
Weglot sits between your visitors and your Webflow site, translating pages on the fly and serving them through subdirectories. Similar SEO benefits to native localization — separate URLs, hreflang, indexed translations. Weglot has an official Webflow integration and it's well-documented.
Pricing starts at $15/month for one language and 10,000 translated words. It scales up from there. A content-heavy Webflow site with 50,000+ words in five languages will cost $50–200/month on Weglot alone, on top of your Webflow subscription.
Client-side translation widget
The lightweight approach. Paste a script tag into Webflow's custom code settings, and visitors get a language switcher on your published site. They pick a language, text swaps on the page, done. No proxy, no DNS changes, no per-locale Webflow fees.
OwOsy Translate works this way. Translations are generated once, cached on Cloudflare's edge, and served to visitors instantly. Free for one language.
The tradeoff: no SEO benefit. Search engines only see your original language. For sites where multilingual organic search matters, use native localization or Weglot. For everything else, this is simpler, faster, and cheaper.
Step by step: adding translation to your Webflow site
1. Create an account and add your site
Go to app.owosy.com and sign up. Add your Webflow site's published URL — your custom domain or your *.webflow.io staging URL.
2. Pick your languages
Choose your source language and target languages. Free plan gives you one target language. Starter ($9/mo) gets you three, Growth ($19/mo) gets you ten.
Don't go overboard. Start with the languages your actual visitors need. Check your Webflow analytics or Google Analytics for geographic data.
3. Scan and translate
Hit "Scan Site" in the dashboard. OwOsy reads your published Webflow pages and extracts text content — headings, paragraphs, buttons, nav links, CMS content, everything visible.
Click "Translate" and the system processes everything, then caches the results globally on Cloudflare. This is a one-time cost per content version. Visitors get cached translations with zero processing delay.
4. Copy the embed script
Go to Settings in your OwOsy dashboard and copy the script tag:
<script src="https://api.owosy.com/widget.js" data-site="your-site-id"></script>5. Add it to Webflow
You have two options in Webflow:
Option A: Site-wide (recommended)
- In your Webflow project, go to Project Settings → Custom Code
- Paste the script tag in the Head Code section
- Click Save Changes
- Publish your site
Option B: Specific pages only
- Open the page in the Webflow Designer
- Go to the page's settings (gear icon)
- Paste the script in the Inside <head> tag field
- Publish
Option A is simpler and covers every page. Option B is useful if you only want translation on certain pages (like your marketing site but not your blog).
6. Test it
Visit your published Webflow site. The language switcher button should appear. Click it, pick a language, and verify the translations look right. Check a few different pages, especially CMS-driven ones.
Webflow-specific things to know
CMS content: OwOsy scans rendered pages, so CMS collection items get translated if they're visible on a published page. Individual CMS item pages, collection lists, dynamic content — it all gets picked up during the scan.
Interactions and animations: The widget swaps text content in the DOM. Webflow interactions that animate text (typing effects, reveal animations) might briefly show the original language before swapping. Static text translates cleanly. If you have a lot of animated text, test those sections carefully.
Staging vs production: If you add the script to your .webflow.io staging URL for testing, remember to update your site URL in the OwOsy dashboard when you switch to your custom domain. The translations are cached per domain.
Webflow plans: Custom code injection is available on all paid Webflow site plans. The free Webflow plan doesn't support custom code, so you'd need at least the Basic plan ($14/month) to add the widget.
When to use this vs Webflow's native localization
Use native Webflow localization when:
- You need multilingual SEO (separate URLs, hreflang tags, indexed translations)
- You have a content team managing translations
- You're targeting specific foreign markets through organic search
- Budget for per-locale Webflow fees isn't a concern
Use a translation widget when:
- You want visitors to read your site in their language but don't need multilingual SEO
- You're building a portfolio, agency site, startup landing page, or SaaS marketing site
- You want to avoid per-locale fees on top of your Webflow plan
- You need a fast setup without restructuring your Webflow project
- You want one solution that works across Webflow and other platforms
Both approaches are valid. They solve different problems.
Pricing
Free for one language and 2,000 words per month. Paid plans from $9/month. Full breakdown on the Webflow translation page.
FAQ
Does Webflow have built-in translation?
Yes. Webflow launched native localization in late 2023. It creates translated page versions with separate URLs and SEO support. However, it requires per-locale fees on top of your Webflow plan and involves significant content management overhead. A client-side widget is an alternative for sites that don't need multilingual SEO.
Do I need a paid Webflow plan?
Yes. Custom code injection requires a paid Webflow site plan (Basic or above at $14/month). The free Webflow plan doesn't support adding custom code to your site's head.
Does this work with Webflow CMS content?
Yes. The widget translates whatever text is visible on the published page, including CMS-driven content like blog posts, collection items, and dynamic lists. It scans the rendered output, not the CMS database, so it picks up everything a visitor would see.
Can I use this alongside Webflow's native localization?
Technically yes, but there's no reason to. If you've already set up Webflow localization with separate locale URLs, the widget is redundant. Pick one approach.
Bottom line
If multilingual SEO is your priority, use Webflow's native localization or Weglot. If you just want visitors to read your site in their language without the per-locale costs and content management overhead, a translation widget gets you there in five minutes.
Disclosure: This guide is published by the OwOsy team. We build OwOsy Translate, so we have a financial interest in you choosing our product. We've tried to present all options fairly.