Webflow Multilingual After a Year | Localization Cost and SEO Results

I’m Kurita, Representative Director of Webharu Inc. I have been using Webflow since 2021 and explain how to use it for free. It has been about a year since Webflow’s multilingual feature launched and I started using it.

The pair I translate is Japanese → Korean.

In this article I share, for free, what I learned from running the multilingual feature for a year. I publish the SEO results and also cover an overview of Webflow Localization: how to set it up, how to use it, and what it costs.

Let’s get started.

Key takeaways

Webflow Localization — what it means

Webflow Localization is the multilingual feature built into Webflow as standard with the update at the end of 2023. It is available for an extra $9 per month per language and supports changing styles per language.

Contents

For going multilingual in Webflow, Localization is the only choice

Before 2023, going multilingual in Webflow meant depending on an external tool called Weglot. But the update at the end of 2023 made a multilingual feature standard in Webflow.

The 2024 update then made it possible to change styles per language, which widened the range of expression for multilingual sites considerably. So if you are adding multilingual support in Webflow, Webflow Localization is the only real choice. (As of November 2024)

What people worry about, though, is the cost and time to set it up, the SEO effect, and concerns about machine translation. I cover each of these concretely below.

What Webflow Localization costs

Going multilingual costs an extra $9 per month per language. Translating into 3 languages adds $27 per month. Over the long run, that can feel expensive.

(Added October 2026: after the pricing change in May 2026, Webflow’s official pricing page lists “Localize Essential” at $9 per month per language billed yearly, or $12 per month billed monthly, for up to 3 additional languages. 4 or more languages require “Localize Advanced” ($29 per month per language billed yearly, $35 per month billed monthly). Checked on October 5, 2026.)

Localizing everything by hand takes quite a lot of time, so as a trial I decided to localize into Korean, planning to keep running it beyond the first year if it worked. I judge whether it “worked” by SEO traffic, inquiries, and Webflow affiliate revenue.

I currently use Webflow’s multilingual feature for Korean, but even if a web production inquiry came in, I could not handle it in Korean, so for now I only track SEO traffic. (The traffic is strong enough that someone who speaks both Korean and Japanese could probably turn a profit running a Korean division. Details below.)

How long Webflow Localization takes to set up

Setup time: 30 minutes

It is so quick you will want to look for something else to do, and honestly there is very little to it. If you care about the details, adjust the design for each language. In particular, going from Japanese to English shifts where lines break, which can make the site harder to read.

The concrete steps are explained in the next section, “How to set up Webflow Localization.”

How to set up Webflow Localization

Setting up Webflow’s multilingual feature takes about 30 minutes, including payment. Here are the steps in order.

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

Where to pay for Webflow Localization

Open Webflow settings and go to the PLAN page. Then open the Add-ons tab and scroll down to find it.

Among the options there, choose Localization, select the number of languages to unlock, and pay. There are two plans, but the benefits of the more expensive one looked thin, so I started with the cheaper plan only.

Setup steps (with screenshots)

Open the Webflow Designer and click the gear icon at the bottom left of the screen.

From there, add two languages.

One is JA, the language code for Japanese.

The other is the target language and its code. Fill in the remaining fields as described below.

• Locale: The language and region setting, which lets the site support different locales (combinations of language and region). Here, Japanese (ja) is set as the primary locale and Korean (South Korea - ko-KR) is added as a secondary locale.
• Display name: A field for the language or region name shown in places such as lists. In this screenshot it does not appear to be filled in yet.
• Display image: An option to set an image associated with the language or locale. Flags are a common choice.
• Subdirectory for this locale: A field that specifies the site’s subdirectory. Here, Korean pages are set to publish under the “/ko” subdirectory (e.g. www.non-haru.com/ko).
• Enable publishing to the subdirectory: Turning this switch on lets you publish content to the specified subdirectory. Here it is set so that Korean content can be published under the /ko subdirectory.

Next, translate every page. Choose the language from the globe icon at the top left of the screen, then open each page, right-click, and run the translation, repeating for every page.

After that, add a language switcher, translate the CMS, swap images where needed, and every page is translated.

The SEO effect of Webflow Localization, and my honest results after a year

Here are the honest results of running Webflow’s multilingual feature, Japanese → Korean, for just over a year.

• SEO traffic grew. Page views from Korea really did increase
• Webflow affiliate sales came to only a few
• Zero inquiries. It did not lead to any revenue

In short, “the traffic came, but as a business it was a dud.” I think there are several reasons.

• In Korea, NAVER is stronger than Google, so the pool of Google searches is small to begin with. SEO aimed only at Google may have had limited reach
• Webflow Localization’s machine translation was not very accurate, leaving parts that read unnaturally in Korean
• Even if a Korean inquiry had come in, I had no setup to handle it

If I go multilingual again, I will pick a language other than Korean. And I will change the translation method itself.

[2026 verdict] If you go multilingual now, have AI translate and run it yourself

The biggest lesson from this year was cost. I was paying just under ¥100,000 a year for my Webflow subscription including Localization alone. After I switched the site itself to AI-built production, my running cost dropped to just the ¥1,500 a year domain fee.

Today’s AI also translates well, so rather than “paying a monthly fee for a tool,” the realistic approach to going multilingual is to have AI translate every page and run your own translated version yourself. Honestly, there is no longer a reason to be tied to a translation tool’s monthly fee.

One caution. No matter how much you translate with AI, without someone who knows that language you cannot do a final check that the translation is correct. If you are serious about that market, budget for some outsourced native-speaker review.

In fact, this very site was fully rebuilt with AI (Claude Code). I document the entire production process in this article. If you are unsure whether to go multilingual in Webflow or switch to an AI-built site, I will assess which suits you and send a report for free, so feel free to use our free consultation. Here are the details of our AI Website Production.

Selected work

JTB Americas

A full renewal of the North America site, with the operations team able to update it themselves

Hosted by Nippon TV

High-fidelity Figma-to-Webflow conversion, with load speed and responsiveness optimized

PonTech Lab Inc.

Built with AI (Claude Code) on Next.js and Cloudflare, with the build process published

FAQ

How much does Webflow Localization cost?

It is an extra $9 per month per language (billed yearly), or an extra $27 per month for 3 languages. Billed monthly, it is an extra $12 per month per language (as of October 2026, checked on Webflow’s official pricing page). I was paying just under ¥100,000 a year for a Webflow subscription including Localization, but after switching to running an AI-built site, I now pay only the ¥1,500 a year domain fee.

Did the Korean translation have an SEO effect?

Traffic grew and page views from Korea increased, but there were zero inquiries and only a few Webflow affiliate sales, so it did not lead to revenue.

Why didn’t the Korean translation work out?

In Korea NAVER is stronger than Google, so the pool of Google searches is small; the machine translation was not very accurate and left parts that read unnaturally in Korean; and I had no setup to handle inquiries in Korean.

What do you recommend if I go multilingual now?

The realistic approach is to have AI translate every page and run your own translated version yourself. Do budget for a native-speaker check by someone who knows that language. If you want to keep everything inside Webflow, Localization is the only choice.