Customer Impact

Website & Development

Leaving your translation tool without losing SEO: from Weglot and co to your own CMS

Copy for AI

You can leave a translation tool without losing SEO: treat it as a migration.

It isn’t a subscription you cancel. That’s the whole difference.

The verdict: leave your translation tool only after the new language versions are live in your own CMS. Cancel last, never first.

Tools such as Weglot, GTranslate, ConveyThis, Linguise, Localize, Bablic and Transifex Live put your site online in several languages quickly. But the translations live with the vendor, not with you.

Cancel without a plan and your French, English or German pages disappear.

Below: what you own today, what Google sees, the 7-step plan and the route per tool and per CMS.

This guide is about a tool you already have.

Still choosing how to translate (machine, human or hybrid)? First read our guide to website translation.

Proxy or JavaScript versus your CMS’s own multilingual setup

A translation tool puts a layer over your site. A multilingual CMS stores each language as a real page.

You see the difference on three points:

Translation tool (proxy or JavaScript)Multilingual setup in your own CMS
Where do the translations live?With the vendor, in its dashboardIn your own database, next to the source text
What do you own?A subscription and, on some plans, an export fileEvery translated page, slug, title and meta description
What does Google see?With a proxy: translated HTML on its own URL. With JavaScript only: often nothing indexableNormal pages per language with your own hreflang and canonicals

A translation proxy

A proxy translates on the server side. Think of Weglot with subdirectories or subdomains, or the paid plans of several tools.

According to Weglot itself, the translated text then sits in the HTML source code and Google can index the pages.

For Weglot on platforms other than WordPress, this runs through a DNS record that points to Weglot’s servers.

A JavaScript layer

A JavaScript layer translates in the visitor’s browser.

In the same documentation, Weglot writes that such an integration has no SEO benefit. The translation happens client side and isn’t crawlable.

A free translation widget usually works this way. The visitor sees a translation; Google sees your source language.

Your CMS’s own setup

Your CMS’s own multilingual setup is more boring, and that’s exactly why it’s more robust.

A French page is a normal page with its own URL, linked to its Dutch version. No intermediate layer, no word limit, no second dashboard.

Why do companies want to leave their translation tool?

Three reasons come back almost every time: cost, a second system and the fear of stopping.

Costs grow with every page

Costs grow with every new page and every extra language, because the word limit counts per language.

What Weglot charges per plan today is worked out in what Weglot really costs.

A second system to manage

The translations live in a second system.

For example, anyone who wants to change a French CTA works in the tool’s dashboard, not in the CMS.

Wrong keywords per market

Tools translate words, not search behaviour.

Our experience: for a Belgian software client, Weglot translated “time registration” as “tijdsregistratie”, with an s. Belgian searchers type “tijdregistratie”, without one. The page targeted the wrong word.

After we fixed the keyword, a page for “tijdregistratie bouw” went from 0 to 4 clicks. Small numbers, but it shows the mechanism.

We once sent translation corrections to many Belgian companies. Many were happy to receive them.

Stopping feels like losing every language

That fear is justified.

In its article on cancelling, Weglot writes that after cancelling or pausing, the translations are no longer active. The translated pages are gradually removed from search engines such as Google.

It’s the same kind of dependency as a closed CMS, which we covered in avoiding CMS vendor lock-in.

The exit in 7 steps

Leaving a translation tool is a small website migration.

The order matters more than the technology. You only cancel once the new language versions are live and checked:

TRANSLATION TOOL EXIT Seven steps, then cancel 1 Inventory URLs and traffic 2 Export the translations 3 Choose the CMS setup 4 Rebuild language versions 5 URL strategy and 301 map 6 Hreflang and canonicals 7 Switch over and monitor in Search Console Only now: cancel the subscription Reverse the order and your translated pages go offline before the new ones exist.

1. Inventory: what does the tool publish today?

List every URL per language, with:

  • its hreflang and canonical
  • the page title
  • the meta description

Pull from Google Search Console which translated pages earn impressions and clicks. Those are the pages you can’t afford to lose.

Also note whether the tool works with subdirectories (/fr/), subdomains (fr.yoursite.be) or JavaScript only.

Quick check: our free hreflang checker shows your language versions and which translation layer is active, in a minute.

2. Export your translations

Get the translations out of the tool while your subscription is running.

At Weglot, export and import of translations sits in the Advanced plan and higher, according to its own help center. The formats are CSV or XLIFF.

No export in your plan? Fetch the rendered translated pages yourself while they’re still online.

Which route you have at Weglot is covered in exporting your Weglot translations and cancelling.

3. Choose your CMS’s multilingual setup

Decide per CMS how the languages will work:

  • WordPress: a plugin or multisite
  • Drupal and Joomla: the core modules
  • Webflow: Localization

Also choose what the URLs look like.

Easiest exit: the same structure as today. If the tool ran on /fr/, let your CMS use /fr/ too.

4. Rebuild the language versions in your CMS

Import the translations as real pages, linked to their source page.

This is also the moment to improve them:

  • align titles and meta descriptions with what people search in each language
  • have CTAs and forms proofread by a native speaker

Machine translation isn’t an SEO problem in itself, as we explain in SEO for translations. But a proofread version converts better.

5. URL strategy and 301 map

Keep every existing URL wherever your CMS allows it.

If that’s not possible (a different slug, or a subdomain that becomes a subdirectory), every old URL gets a permanent redirect to its new address.

For a site move, Google recommends deciding per old URL where it should go. It advises server-side 301 or 308 redirects, kept for at least a year.

Test your redirect list with our redirect checker. For bigger lists, follow our 301 redirect plan.

6. Hreflang and canonicals

Every language version must list itself and all other versions in hreflang.

Google is strict: if two pages don’t point to each other, the tags are ignored.

Every translated page gets a canonical to itself, not to the Dutch version.

How that works in practice is in our guide to hreflang. Already seeing warnings? Read fixing hreflang errors.

7. Switch over, monitor and only then cancel

Put the new language versions live. Then:

  1. switch off the tool on the site (script, plugin or DNS record)
  2. remove leftover language switchers
  3. submit your new sitemap
  4. monitor indexing, impressions and 404s per language in Search Console

Fluctuations in the first weeks are normal.

Only once the new versions are indexed and the old URLs redirect correctly do you cancel the subscription. The full playbook is in our CMS migration step-by-step plan.

The route per translation tool

The plan is the same everywhere. What differs is how you get your translations out and what happens to the URLs.

Weglot

Export as CSV or XLIFF from Advanced.

On WordPress, the Weglot plugin creates the language folders. On other platforms, the translated version runs through a DNS record at Weglot, which you reset when you stop.

The full playbook is in exporting your Weglot translations and cancelling. Still unsure whether to leave? Read Weglot alternatives compared.

GTranslate

First check which version you run.

The free widget translates in the browser and usually produces no indexed language pages. Then there’s little SEO to lose, and mainly a new language version to build.

Running a paid plan with its own URLs per language? Follow the full 301 map.

ConveyThis and Linguise

Both work with a translation layer and a dashboard at the vendor.

Check whether your plan allows export. If it doesn’t, you’ll need the rendered pages. Pull the list of translated URLs before you change anything.

Localize, Bablic and Transifex Live

These are mainly JavaScript layers.

Check whether your translated versions have their own URLs that Google indexes. If not, you build new language versions in your CMS, and the 301 map is small or unnecessary.

Rule of thumb: no indexed language URLs means little to lose, but also little to keep.

The route per CMS

Every major CMS can handle multiple languages itself. The only question is which setup suits your site.

WordPress

Multilingual support comes through a plugin (WPML, Polylang or TranslatePress) or through multisite with one site per language.

WordPress.org homepage presenting the open source publishing platform, a CMS that handles multiple languages with a plugin or multisite after leaving a translation tool WordPress.org, October 2026. Languages come from a plugin or multisite, not from core.

Translations become normal posts and pages, linked to their source version.

Coming from Weglot? We compare both routes in Weglot vs WPML. Moving hosts at the same time? See our WordPress migration checklist.

Drupal

Multilingual support is in core.

According to the Drupal documentation, it comes down to four core modules:

  • Language
  • Interface Translation
  • Content Translation
  • Configuration Translation

You don’t need an extra plugin.

Webflow

Localization gives you locales with their own, translated slugs.

Webflow homepage presenting its visual website platform, where Localization gives each language its own locale and translated slugs Webflow’s homepage, October 2026. Localization is the built-in route for multiple languages.

According to the Webflow developer documentation, you can manage CMS items in primary and secondary locales through the API.

That makes importing, and later AI translation, easy. Our guide to Webflow SEO covers the rest of the setup.

Joomla

Joomla is multilingual in core: language packs, the language filter plugin and linked translations per article and menu item.

You rebuild the language versions as normal, linked content.

Afterwards: AI translation straight into your CMS

Once your translations live in your CMS, new content no longer has to go through a tool.

How it works

An AI agent does four things:

  1. reads a new page
  2. translates it with your glossary and tone of voice
  3. puts the translation as a draft in the right language field
  4. leaves it for a native speaker to proofread and publish

You no longer pay per translated word to a tool. And hreflang stays correct, because the CMS manages the language link.

Why it’s worth it

That way you publish faster in more languages.

Our experience: AI translation plus local search-term data for the right keyword per language gets you most of the way. A human pass is only needed where it really counts.

Each language also builds its own visibility. Our guide to international SEO explains how.

We do this within our service multilingual website and AI translation.

Frequently asked questions

Will I lose rankings if I cancel my translation tool?

Not if you first put the new language versions live on the same URLs or with a complete 301 map, and only cancel afterwards. If you cancel first, the translated pages gradually drop out of Google, according to Weglot.

Can I take my translations with me?

Usually, but it depends on your plan. At Weglot, export is included from Advanced. Without export you can fetch the rendered pages yourself while they’re online.

Do my URLs have to change?

Not necessarily. If your CMS supports the same structure (for example /fr/), you keep the same URLs. Only what changes gets a 301 redirect.

How long does such a switch take?

That depends on the number of pages, languages and the CMS. The preparation (inventory, export, URL plan) takes the most time; the switch itself is a short intervention.

Need help with your switch?

Leaving Weglot, GTranslate, ConveyThis or another tool without losing search traffic is a job for a plan, not a cancel button.

We map what your tool publishes today and rebuild the language versions in your own CMS. We only cancel once everything is live and checked.

See our translation tool migration or the broader website migration SEO.

Contact us

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.