Website & Development
Weglot review: what automatic translation gets wrong and when it is enough
Copy for AI
Weglot is a platform that translates your website automatically, one URL per language.
It puts a separate version online for each language, without you rebuilding your CMS.
The verdict: technically, Weglot does a lot right for SEO. But the text stays machine translation, and that’s the weak point for Belgian buyers.
Separate URLs per language, hreflang and translated metadata all work. Yet a French-speaking or Dutch-speaking customer reads the words, not the tags.
In this Weglot review, you’ll see how it works, what it costs, where automatic translation goes wrong and when it’s good enough.
This article goes deeper into one part of our guide to website translation.
Unsure about the SEO side of automatic translation? Also read what Google thinks of machine-translated pages.
How exactly does Weglot work?
Weglot sits between your website and your visitor.
It detects the text on your pages, has a machine translation engine translate it, and shows the translated version to the visitor.
The engine behind it
Weglot’s own features page mentions a reverse proxy and a JavaScript integration.
It names DeepL, Microsoft and Google Translate as its translation providers. New content is picked up and translated automatically.
Here’s the flow in one picture:
Where your translations live
The key detail is in the same place: your translations are stored at Weglot, accessible through the Weglot dashboard. They’re not in your CMS.
That makes installation light, because you aren’t building a second site. But it also makes you dependent on the platform.
More on that below.
Editing, glossary and translators
Weglot gives you three ways to steer the output:
- List view or visual editor: edit translations in a list, or on the page itself
- Glossary: fixed terms, such as brand and product names, always translate the same way
- Professional translators: order them, or add your own, from the dashboard
Weglot also adds a language switcher automatically.
You can see the visual editor on Weglot’s own site:
What does Weglot do well for SEO?
The technical foundation is solid, more so than in some translation plugins.
Weglot’s documentation on SEO for WordPress lists three things the platform does.
Separate URLs, hreflang and metadata
- A separate URL per language. Weglot creates a subfolder for each translated language, for example
/fr/or/nl/. - Hreflang tags. Weglot adds the hreflang annotations to your source code automatically.
- Translated metadata. Meta descriptions and image alt texts are translated in the source code, not only on screen.
Why it matters: Google recommends separate URLs per language version instead of switching language via cookies or browser settings.
Hreflang tells Google which versions belong together. Our guide to hreflang for Belgian sites explains how those tags work.
Because the translation sits in the source code, search engines can read and index the translated pages.
Two caveats
x-default: on WordPress, Weglot doesn’t add the x-default tag by default. The same documentation offers a code filter if you want it.
Translated slugs: /fr/services/ instead of /fr/diensten/ only comes with the Pro plan, according to the pricing page.
A French-language page with a Dutch slug isn’t a disaster. But you miss a signal in the URL and in the search results.
What does Weglot cost?
Weglot charges per plan, with a limit on translated words and on languages.
The word limit counts per language. For example, a 20,000-word site in two extra languages uses 40,000 translated words.
The plan range
According to the Weglot pricing page, checked 5 November 2026, plans run from:
- Free: 2,000 words, 1 language, 0 euros
- Pro: 200,000 words, 5 languages, 79 euros a month
- Extended: 5 million words, 20 languages, 699 euros a month
Starter, Business and Advanced sit in between. Every paid plan comes with a free 14-day trial.
Two thresholds for a Belgian B2B site
Translated URLs: only from Pro.
Export and import: only from Advanced.
If you might ever take your translations elsewhere, factor that in before you start.
All amounts per plan, and what Weglot costs over three years, are in what Weglot really costs.
Where does automatic translation go wrong in practice?
The technology is usually right. The language often isn’t.
A machine translation is correct enough to understand. But a French-speaking or Dutch-speaking customer notices straight away that it wasn’t written for them.
The six mistakes we see most
These show up again and again on automatically translated Belgian sites:
- Tone and form of address. A breezy Flemish “je” becomes “tu” in French, sometimes “vous”, sometimes both on one page.
- Belgian French and jargon. Sector terms, job titles, VAT, the KBO/BCE register or paritair comité come out literally, or in French-from-France.
- CTAs and microcopy. Buttons, form errors and confirmations get translated short and without context.
- Text in images and PDFs. A proxy doesn’t translate an image or a download.
- Legal and technical pages. Terms, privacy policy and specifications need precision an engine doesn’t guarantee.
- Keywords. A translated page targets the translation of your Dutch keyword, not what French speakers type.
Tone: for a French-speaking business audience, mixing “tu” and “vous” sounds sloppy.
CTAs: “Request” can go wrong in five ways. And that’s exactly where the visitor decides whether to enquire.
Jargon: an engine doesn’t know the difference between France and Belgium by default.
Images: your French page then shows a Dutch infographic.
The keyword problem, in one word
The keyword mistake isn’t a Weglot problem but a translation problem. Yet it costs you findability.
Our experience: for Suivo, Weglot translated “time registration” as “tijdsregistratie”. Belgian searchers type “tijdregistratie”, without the s.
Suivo targeted Belgium, not the Netherlands. Read how we approached that market in the Suivo go-to-market case.
We once sent translation corrections to many Belgian companies. Many were happy to receive them.
When is Weglot enough?
When speed matters more than perfection, or when the language isn’t a core market.
Where it works well
Concretely, Weglot does the job for:
- Supporting content, such as a knowledge base, FAQ or large product catalogue
- A quick start in a new language, to test demand before you invest in copy
- Sites without a technical team, where a second language wouldn’t exist otherwise
For supporting content, being available in the customer’s language weighs more than perfect style.
Where it’s only a first draft
Your money pages are a different story:
- homepage and service pages
- pricing information and landing pages
- contact forms
There, machine translation is only a first draft. Your copy deserves a native speaker who rewrites rather than corrects.
Hybrid approach: machine for volume, human for conversion. It works inside Weglot itself: you adjust the translation in the visual editor, and Weglot remembers your version.
How do you get the most out of Weglot?
Six interventions limit the biggest risks.
Before you go live
- Build a glossary for your brand name, product names, sector terms and form of address.
- Rewrite your top 10 pages manually in the visual editor, with a native speaker. Start with the pages that generate leads.
- Switch off automatic language redirects and rely on the language switcher.
The glossary makes Weglot translate fixed terms consistently. Turning off redirects lets Google and visitors reach every version.
After you go live
- Check your hreflang and x-default after installation. Our hreflang checker shows which versions point to each other and whether a translation plugin is active.
- Do keyword research per language and adjust titles, meta descriptions and headings to what French speakers search for. See SEO for translations.
- Keep an eye on your word limit. Every new blog post counts in every language.
Watch out: if the checker shows errors, our guide to fixing hreflang errors walks through the usual causes.
Leaving Weglot: what if you want to stop?
Don’t cancel first: export, rebuild, redirect, and only then cancel.
Your translations live at Weglot, not in your CMS. Weglot’s own article on cancelling says they stop working after you cancel.
Your translated pages are then progressively removed from search engines.
The safe order
- Export your translations.
- Build the language versions in your own CMS’s multilingual setup.
- Keep the same URLs, or redirect every old URL with a 301.
- Check hreflang.
- Only then cancel.
Changed URLs need a mapping. Our 301 redirect plan shows how to build one.
Where to read more
The full playbook, with what happens to your URLs per setup and a checklist, is in exporting your Weglot translations and cancelling.
The route for other tools and per CMS is in our guide to leaving a translation tool without losing SEO.
Want someone to handle the switch? See our translation tool migration.
Weglot or something else?
You have three alternatives to Weglot:
- a translation plugin that stores translations in your own CMS, such as WPML or TranslatePress
- your platform’s built-in multilingual features (Webflow, Shopify and others)
- separate, human-written pages per language
On WordPress, the plugin route keeps every translation in your own database:
WordPress.org, October 2026. Plugins on this CMS store translations in your own site instead of on a platform.
Three questions that decide it
- Where are your translations stored?
- Who writes them?
- How much control do you have over URLs and metadata?
We compare the options in Weglot alternatives compared, and for WordPress in Weglot vs WPML.
Weighing it up for your market? Read our strategy for a multilingual B2B website, or the practical guide to a bilingual NL/FR website.
Frequently asked questions about Weglot
Is Weglot good for SEO?
Technically, yes: Weglot creates a separate URL per language, adds hreflang and translates metadata in the source code. Whether your translated pages also rank depends mainly on the quality of the text and on the keywords you choose per language. Machine translation alone doesn’t help enough there.
Does Google penalise automatically translated pages?
Not because they’re automatically translated. Google targets content created at scale without value for the user, and explicitly names automatic translation as one of the techniques. A proofread, useful translation doesn’t fall under that. The details are in SEO for translations.
What happens to my translations if I stop using Weglot?
The translations are stored at Weglot and not in your CMS. If you stop, you have to offer those translated versions another way, otherwise those pages disappear. According to the pricing page, exporting translations comes with the plans from Advanced upwards, so plan for that in advance. The step-by-step route is in exporting your Weglot translations and cancelling.
Is Weglot suitable for a Belgian NL/FR site?
As a starting point, yes; as the end result, rarely. For a bilingual Belgian site, use Weglot for volume and have the pages that generate leads rewritten by a French-speaking or Dutch-speaking copywriter.
Want your translated site reviewed?
Running Weglot or another translation plugin, and unsure whether the translated versions bring in customers?
We review your language versions, your hreflang and your lead pages. Then we tell you where machine translation is enough, and where it isn’t.
See how our website translation services deliver native NL and FR copy and a correct multilingual SEO setup.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.