Leave Your Translation Tool Without Losing SEO

Leaving a translation tool without losing SEO is possible, provided you treat it as a migration and not as cancelling a subscription. 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. Cancel without a plan and your French, English or German pages disappear. In this guide you will read what you actually 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. If you still need to choose how to translate (machine, human or hybrid), first read our guide to website translation.

Proxy or JavaScript versus your CMS’s own multilingual setup

There are two ways to make a site multilingual. A translation tool puts a layer over your site. Making your CMS itself multilingual puts every language version in your own system 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 dashboard	In your own database, next to the source text
What do you own?	A subscription and, on some plans, an export file	Every 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 indexable	Normal pages per language with your own hreflang and canonicals

A proxy (Weglot with subdirectories or subdomains, the paid plans of several tools) translates on the server side. 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 translates in the visitor’s browser. In the same documentation Weglot writes that such an integration has no SEO benefit, because the translation happens client side and is not crawlable. A free translation widget usually works this way: the visitor sees a translation, Google sees your source language.

Your CMS’s own multilingual setup is more boring and that is exactly why it is 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 companies want to leave their translation tool

The reasons are almost always the same. 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. On top of that, the translations live in a second system: anyone who wants to change a French CTA works in the tool’s dashboard, not in the CMS. And stopping feels like losing all your other languages.

That last point is true. In its article on cancelling, Weglot writes that after cancelling or pausing, the translations are no longer active and the translated pages are gradually removed from search engines such as Google. It is the same kind of dependency as with a closed CMS, which we wrote about 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.

1. Inventory: what does the tool publish today?

List every URL per language, with its hreflang and canonical, the page title and the meta description. Pull from Search Console which translated pages earn impressions and clicks: those are the pages you cannot afford to lose. Also note whether the tool works with subdirectories (/fr/), subdomains (fr.yoursite.be) or JavaScript only. 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, as CSV or XLIFF. If export is not in your plan, you can fetch the rendered translated pages yourself while they are 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: a plugin or multisite on WordPress, the core modules of Drupal or Joomla, Localization on Webflow. Also choose what the URLs look like. The easiest exit is 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 actually search for in each language, and have CTAs and forms proofread by a native speaker. Machine translation is not 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 is not possible (different slug, subdomain becomes 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, using server-side 301 or 308 redirects and preferably keeping those redirects for at least a year. Test your redirect list with our redirect checker.

6. Hreflang and canonicals

Every language version must list itself and all other versions in hreflang. Google is strict about this: if two pages do not 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 explained in our guide to hreflang.

7. Switch over, monitor and only then cancel

Put the new language versions live, switch off the tool on the site (script, plugin or DNS record) and remove leftover language switchers. Submit your new sitemap and monitor indexing, impressions and any 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 for migrations 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 is little SEO to lose and mainly a new language version to build. If you run 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 in your plan whether export of translations is possible and 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.

The route per CMS

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

WordPress. Multilingual support comes through a plugin (WPML, Polylang or TranslatePress) or through multisite with one site per language. Translations become normal posts and pages, linked to their source version. Coming from Weglot? We compare both routes in Weglot vs WPML.
Drupal. Multilingual support is in core. According to the Drupal documentation it comes down to four core modules: Language, Interface Translation, Content Translation and Configuration Translation. No extra plugin is needed.
Webflow. Localization gives you locales with their own, translated slugs. According to the Webflow developer documentation you can manage CMS items in the primary and secondary locales through the API, which makes importing and later AI translation easy.
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. An AI agent can read a new page, translate it with your glossary and your tone of voice, and put the translation as a draft in the right language field of your CMS. A native speaker proofreads and publishes. You no longer pay per translated word to a tool, and hreflang stays correct because the CMS manages the language link. That way you publish faster in more languages. 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 are 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?

Want to leave Weglot, GTranslate, ConveyThis or another tool without losing search traffic? We map what your tool publishes today, rebuild the language versions in your own CMS and only cancel once everything is live and checked. See our translation tool migration or the broader website migration SEO.