How to Use Weglot: The Complete Guide | Webflow, STUDIO Setup and Exclusions

“I want to make a site built in Webflow multilingual”
“I want a clear explanation of how to use Weglot”
“I don’t know how to fix it when the translation doesn’t appear”

This article solves those problems.

Weglot works not only with Webflow but with many no-code tools such as Wix and Shopify, and it handles everything from translation to SEO in roughly one click. A genuinely useful tool.

This article covers how to use Weglot, and how to put Weglot to work in Webflow. It draws on my own experience of using it, and on what the Weglot support team taught me.

The second half also covers the upsides and downsides of Weglot, and the SEO results I actually got from using it.

Let’s get into it.

Key takeaways

Weglot — what it means: Weglot is a multilingual service that works with many no-code tools, including Webflow, Wix and Shopify. It handles everything from translation to SEO in roughly one click, and integrates with Webflow at the app level.

Contents

What this complete guide covers

These were originally separate articles by topic, merged into this single guide in July 2026. Installation, exclusion settings, what to do when the translation doesn’t appear, and the subdirectory workaround: read from the top and you will be able to use the whole thing.

How to install Weglot on a site built in Webflow

Sign up for Weglot
Set the DNS
Paste the JS into your website
Installation complete

I’ll take them in order.

Step 1: sign up for Weglot

From the linked page, click “Try for free” and start using Weglot with the free trial.

For the first week, Weglot translates up to 10,000 characters for free. After that you move automatically to the free plan, which is downgraded to 2,000 characters, so I recommend learning your way around in that first week and paying after that.

Step 2: follow the order Weglot shows you

From top to bottom, enter

the domain of the site you want to translate
the original language
the languages you want to translate into

in that order.

Step 3: set up the DNS for Weglot

DNS may sound a little intimidating, but it simply means the settings on the domain side. Open the admin screen of the domain you own. I use Google Domains, so I’ll walk through it with Google Domains as the example.

Example of adding Weglot’s DNS records in a domain admin screen

In Google Domains, open the DNS section; you can add DNS entries from Custom records. In my case Webflow’s DNS is already set, so I add Weglot’s DNS alongside it. This creates Weglot’s subdomain. Go back to Weglot, and once the DNS has loaded, move on to the next step.
How to use subdirectories with Weglot (in this article)

Step 4: paste the JS code into your site

Pasting Weglot’s JS code into Webflow’s custom code field

Every no-code tool should have a setting for the <head> tag. In Webflow it is in the custom code field under the site settings. Copy and paste the code Weglot shows you there, and installation is done.

How to exclude pages from translation in Weglot (to save money)

Weglot screen for setting URL rules to exclude from translation

Enter the URLs you want to exclude under Weglot’s “Setting → Translation exclusion” and the exclusion is done.

After setting an exclusion, check under Translation that the URL in question has been excluded (that it has a line through it).

* If you are over Weglot’s character limit or on the free plan, Weglot stops working, so this does not seem to display properly.

After setting an exclusion, also delete the excluded pages from “Translation → URL”.

How to exclude everything except one page from translation in Weglot

Example exclusion setting that keeps only one page translated

Set it up using the image as a reference.

^(?!\/the-url-you-want\/).*

With the setting shown in the image, only the pages under /posts are translated and every other page is excluded.

Put the URL of the page you want translated in place of “the-url-you-want” and every other page is excluded from translation. That keeps the character count down, and the cost with it.

Also, using

^(?!\/posts).*

lets you run the exclusion including the /posts page itself.

How to count the characters on a whole page

The tool below counts the characters across your whole site. With its filter you can measure only the pages you want, which makes it a great match for Weglot.

wc.ccjk.tech/

‍

“Weglot isn’t translating!” How to fix it

I found the following bugs in Weglot. They may have been fixed in an update since, but I’m writing down the fixes for anyone who runs into them.

The page is not translated
The URL does not change when you open a translated page
A subdirectory cannot be deleted

Here is how to fix each of these bugs.

How to fix Weglot bugs

When the site is not made multilingual or translated

This bug usually happens in one of the following two cases.

You are over the translation character limit
The URL has not been scanned

1. You are over the translation character limit

Weglot appears to stop working once you go over the character limit.

So limit the pages you translate and adjust things so you stay within the character count. How to limit which pages get translated →

2. The URL has not been scanned

Pages can stop being translated after you delete translations or set exclusions. When that happens, scan your site from “Missing a URL? Scan your website.” at the bottom of “Translation → URLs”.

The pages will be translated again.

When the URL does not change on a translated page

This bug usually happens in the following cases.

You are over the translation character limit
You have only just installed it

1. You are over the translation character limit

As noted above, Weglot stops working when you go over the limit, which can cause the bug where the URL does not change.

How to limit which pages get translated →

2. You have only just installed it

Right after installation, the URL sometimes does not change properly. Wait 24 hours and see.

When a subdirectory cannot be deleted

There is a bug where a subdirectory installed on Webflow cannot be deleted.

The message “DNS settings remain” appears, and it keeps appearing even after you have deleted everything. Contact support and have them delete it.

‍

How to use Weglot subdirectories with Webflow [workaround]

First, log in or sign up to Weglot‍
Open Setup and turn subdomains OFF
Open the link [workaround]
A subdirectory option is added
Follow the steps to configure it

That is the overall flow. Let’s go through it in detail.

1. Sign up for Weglot

From the linked page, click “Try for free” and start using Weglot with the free trial.

2. Open Setup and turn subdomains OFF

Go to the Weglot dashboard and disable subdomains from Setup.

Disabling subdomains under Weglot’s Setup

3. Open the link [workaround]

The Setup screen you configured at the very start of Weglot then appears. At that point, open the dedicated subdirectory URL.

4. A subdirectory option is added

A new box appears and subdirectories become selectable.

Weglot screen with the subdirectory option added

5. Follow the steps to configure it

Set the DNS as instructed and the subdirectory setup is complete. With subdirectories there are two DNS settings.

You also need to set up “www” for SSL. However, if you use Webflow you will already have set “www” in Webflow, and only one of the two can be set. Weglot support said they would like the Weglot “www” to take priority.

Personally I would rather have kept the Webflow one, but I switched to the Weglot one. (Webflow shows an error on its side.)

How to add Weglot to STUDIO (the official steps)

I have not tried Weglot on a STUDIO site. This section only covers what I could confirm in the official Weglot and STUDIO help pages (checked October 5, 2026). STUDIO is a Japanese no-code website builder.

What you need on the STUDIO side

Custom code can only be added on a paid plan.
There are two fields for code: “end of <head>” and “end of <body>”. Code placed in the site settings tab applies to the whole site.
Code you add does not run in the design editor or the live preview. Check that it works on the published site.
STUDIO notes that how third-party code behaves may fall outside the scope of its chat support.

The official steps

Create a Weglot account (dashboard.weglot.com/register).
Choose the original language and the languages you want to translate into.
Enter your domain name. Use your own custom domain, not the URL STUDIO issues.
For the subdomain method, add a CNAME record for each language you translate into, in the screen where your domain’s DNS is managed. Go back to Weglot and press “Check DNS”; once a green check appears, move on.
Copy the JavaScript code shown.
In STUDIO’s design editor, click the gray margin outside the screen. In the [Site] tab of the right panel, paste the code into the “end of <head>” custom code field, then update and publish the site.
It may take a few minutes before the language switcher appears.

If you want to appear in search, don’t pick the JavaScript-only method

There is also a “JavaScript only” method that lets you start without touching DNS. However, Weglot states that with this method the translation is rendered in the browser, so search engines don’t read it and there is no SEO benefit. If you want translated pages to appear in search, choose the subdomain or subdirectory method, which gives each language its own URL and adds hreflang automatically.

Sources (checked October 5, 2026): Weglot Help Center “General Integration - Integration / Setup” / Weglot Help Center “How does Weglot manage your website's SEO” / Studio Help “Adding custom code to a site or page” (Japanese)

If you are torn between building with STUDIO or Webflow, I’ve written up my view in Webflow vs STUDIO.

Weglot’s upsides and downsides, summed up

Upsides of Weglot

• Easy to install

• Lets you reach audiences in languages you don’t speak

• Solid SEO handling too

Downsides of Weglot

• It’s expensive

• Google Translate stops working across the whole site

What happened when I actually used Weglot

How does Weglot rank in SEO overseas?
Does traffic from overseas grow with translation as-is?

First, here is my account from 2022 of adding Weglot to a Webflow site, as it was written at the time.

I made a no-code site built in Webflow multilingual with Weglot

Image representing multilingual sites with Weglot

Installing Weglot | done in three minutes

Installing Weglot is surprisingly easy; it really takes three minutes. I explain it in detail in “How to install Weglot on a site built in Webflow”. Here is a quick version.

How to install Weglot

Sign up for Weglot
Copy and paste the API
Check the translation
Buy a plan that fits your character count

It is so easy it barely needs explaining. No need to worry about “What’s an API?”. Follow Weglot’s screens and the translation is done without any trouble.

Weglot’s translation quality rivals a professional translator

I was worried about the translation quality and checked it, but the text read smoothly with no particular problems.

Because of its accuracy, a translation and interpreting company I know also uses it, and they told me it is excellent: one click gets you URLs and SEO handling.

Plenty of errors and bugs, in my impression

In actual use, things like “I changed it, so why isn’t it reflected??” and “after deleting part of a translation I couldn’t restore it (no idea how)” happened. A little research answered most of it, but where I just couldn’t figure it out I emailed support.

Changing the design of the Weglot button seems best done mainly on the site side, in the HTML and so on. How to make the Weglot button look better.

What was good and bad about using Weglot

Installing Weglot | what was good

Here is what I felt was good about installing Weglot.

Going multilingual broadened my view to overseas audiences.
Support teaches you anything you don’t know. (It was good practice for business email in English.)
If traffic grows, I can expect more income. (2026 update: this was back in my personal-blog days. The later multilingual operation ended with 0 inquiries in about two years.)
I could trial whether my site would work overseas.

Installing Weglot | what was bad

Here is what I felt was bad about installing Weglot.

It felt expensive (thanks to the weak yen). * Payment is in euros, by the way.
Until I got used to it, I didn’t really understand how to use it.
Sometimes I couldn’t tell whether it was a bug or my own lack of knowledge.

Is it fine to leave Weglot on machine translation? [first-hand]

Image representing a review of machine-translation quality

Weglot is apparently not fully AI; part of the translation is done by people, which is how it avoids being excluded by Googlebot. Supposedly that means a Weglot translation can carry your SEO rankings straight over into an English version without any changes. That said, the keywords that rank well differ by language, and you will need at least some knowledge of international SEO.

Still, for things like shop products, or articles like mine that introduce Webflow, which has many users overseas, I think translation as-is can bring in a certain amount of traffic.

Weglot lets you choose subdomains or subdirectories

If you don’t want to affect your existing site, use subdomains. If you want to carry over as much ranking as possible, use subdirectories.

That said, Google has stated that neither makes much difference for SEO, so you may as well pick whichever you prefer. I built mine with subdirectories. The reason is ease of management: with subdirectories you can keep using your existing Google Search Console as is, which is very convenient.

How to choose subdirectories in Webflow

Subdirectories in Webflow are still in BETA, so they don’t seem to be openly selectable, but following a method the support team taught me made them selectable. It’s described in the Weglot how-to section, so please check there.

(2026 update: Webflow’s native Localization feature now supports subdirectories, so you can go multilingual without an external tool. I have published the measured results of running it for a year in my Webflow Localization article.)

I predict Weglot and Google will keep wrestling

Image representing the tug-of-war between Weglot and Google

Google basically does not like machine translation. The reason is that machine translation is hard for users to read, and information varies by region. In “language”, a field where wording matters because of religion, weather, safety and so on, Weglot, which promises translations Google won’t ban, will be wrestling with Google for a long time to come.

Even so, simply leading the pack with cutting-edge technology can earn you a fair amount of money. Just as Webflow has done.

While you hold back thinking “it might be a bit expensive”, you could miss a big opportunity. If it feels right, please give Weglot a try.

What happened after, and my conclusion as of 2026

To start with the conclusion: traffic from overseas really did grow. I began running this site in multiple languages with Weglot, then moved to Webflow’s native Localization and kept running it in Japanese → Korean. Page views from Korea grew, and a few Webflow affiliate sales came in. My sense is that for a topic with many users overseas, like Webflow, translation as-is can bring in a certain amount of traffic.

As for business results, though, to be honest, about two years of operation produced 0 inquiries or orders for web production. I think the causes were that NAVER is stronger than Google in Korea so the search volume was small, that the machine-translated Korean still had unnatural parts, and that I had no setup to handle inquiries in Korean in the first place. “Traffic came, but it didn’t turn into revenue” is what I measured.

The cost can’t be ignored either. At the time I was paying just under ¥100,000 a year for the Webflow subscription with Localization alone. After I later switched the site itself to AI production, the running cost is now just the domain fee of ¥1,500 a year.

My conclusion as of 2026 is that for going multilingual, having AI translate every page and running it yourself is more realistic than paying a translation tool every month. Weglot’s appeal is that it installs in three minutes, and it is still an option for anyone who wants to leave everything to a tool, but be sure to check the monthly cost and the accuracy of the machine translation before you install it.

For the specific numbers that led me to pull out and what I decided after, see my measured results from Korean localization.

Selected work

FAQ

Is Weglot free to use?

The first week is a free trial that translates up to 10,000 characters. After that you move automatically to the free plan (up to 2,000 characters). I recommend learning your way around in that first week and then paying.

What should I check when Weglot doesn’t translate?

First check whether you are over your plan’s character limit, then whether the URL has been scanned. Scanning from “Missing a URL? Scan your website.” at the bottom of Translation → URLs gets the translation working again.

How do I translate only certain pages (to keep the cost down)?

Enter the URLs you want excluded under Setting → Translation exclusion. The regex ^(?!\/the-url-you-want\/).* excludes everything except the page you name in one go, which keeps both the character count and the cost down.

Can I use Weglot on a STUDIO site?

According to the official steps, yes. On a STUDIO paid plan, paste Weglot’s JavaScript into the “end of ” custom code field and update the site. If you want translated pages to appear in search, choose the subdomain or subdirectory method rather than the JavaScript-only method (checked October 5, 2026).

What if a Weglot subdirectory cannot be deleted?

There is a bug where the message “DNS settings remain” appears even after you have deleted every DNS record. You cannot remove it yourself in that case, so contact Weglot support and have them delete it.