One Year with Webflow Localization: Results, Costs, Verdict

Webflow Localization

Webflow Localization is the multilingual feature built into Webflow in a late-2023 update. It costs an additional $9/month per language and supports per-language style overrides.

Hi, I'm Masato, a Webflow specialist using the platform since 2021. It's been about a year since Webflow's localization feature launched and I started using it.

My translation pair: Japanese → Korean.

This article shares a full year of operating the localization feature — the SEO data, how to set it up, what it costs, and the honest outcome.

For multilingual Webflow, Localization is the only choice

Before 2023, multilingual Webflow meant depending on the external tool Weglot. Then the late-2023 update built localization directly into Webflow.

A 2024 update added per-language style overrides, widening what's expressible. So if you're going multilingual within Webflow, Localization is effectively the only choice.

The real questions are cost, time, SEO results, and machine-translation quality. Let's take them in order.

What Webflow Localization costs

Localization costs +$9/month per language — three languages means +$27/month. Over the long run, that adds up.

But hand-localizing everything takes serious time, so I decided to trial Korean, planning to continue past year one only if it "worked" — judged by SEO traffic, inquiries, and Webflow affiliate revenue.

How long setup takes

Setup time: 30 minutes.

So fast you'll be looking for more to do — there honestly isn't much. If you want to be thorough, adjust the design per language: line breaks shift between languages and can make pages harder to read.

Setting up Webflow Localization

Setup, payment included, takes about 30 minutes:

1. Open billing and choose the plan
2. Add and configure the language
3. Translate every page
4. Adjust CMS and images
5. Done

Where to subscribe

Open Webflow settings → Plans page → Add-ons tab, scroll down, select Localization, choose the number of languages, and pay. Of the two tiers, the pricier one's benefits looked thin, so I started with the cheaper.

Setup steps

Open the Webflow Designer, click the gear at bottom left, and add two locales: your primary language's code, and the target language with its code. Configure the remaining fields:

• Locale: the language/region pair — a primary locale (e.g., Japanese, ja) and a secondary (e.g., Korean, ko-KR).
• Display name: the name shown in language lists.
• Display image: an image for the locale — flags are common.
• Subdirectory for this locale: the URL prefix, e.g. Korean pages publishing under "/ko".
• Enable publishing to the subdirectory: switch this on to publish content to that subdirectory.

Then translate every page: pick the language from the globe icon at top left, open each page, right-click, translate, repeat.

Add a language switcher, translate the CMS, swap images where appropriate — and the full translation is done.

The SEO results — an honest year-one report

The honest outcome of a year-plus running Japanese → Korean localization:

• SEO traffic grew — pageviews from Korea genuinely increased
• Webflow affiliate revenue: a handful of conversions
• Inquiries: zero. No revenue impact

In short: traffic came, business didn't. My read on why:

• In Korea, NAVER dominates over Google, so Google-facing SEO reached a limited audience to begin with
• Webflow's machine translation quality wasn't great — unnatural Korean remained
• Even if a Korean inquiry had arrived, we had no capacity to handle it

Next time I'd pick a different language — and change the translation approach entirely.

[2026 conclusion] Going multilingual today? Have AI translate it and run it yourself

The biggest lesson of the year was cost. My Webflow subscription with localization ran close to ¥100,000/year. After switching the site itself to AI production, operating costs dropped to just the domain: ¥1,500/year.

Today's AI translates well, so the realistic play isn't paying a tool's monthly fee — it's having AI translate every page and operating your own translated version. The reason to be locked into a translation tool's subscription has honestly evaporated.

One caveat: however well AI translates, without someone who reads the language you can't verify the output. If you're serious about a market, budget for at least some native review.

This very site was fully rebuilt with AI (Claude Code). Torn between Webflow localization and switching to an AI-built site? We'll assess which fits you, free, with a written report — book a consultation or see our AI site production service (Japanese).