Customer Impact

Website & Development

Weglot export translations and cancel: uninstall cleanly without losing your URLs

Copy for AI

Export your Weglot translations first, rebuild them in your CMS, and only then cancel.

Cancelling Weglot is a few clicks in your dashboard. The hard part comes before and after.

The verdict: your translations live at Weglot, not in your CMS. Cancel in the wrong order and your French, English or German pages go offline, rankings included.

This guide covers how to export your translations and what happens to your URLs per setup.

Then how to avoid 404s and duplicate language versions, and how to remove Weglot cleanly. A checklist is at the bottom.

It’s the Weglot part of our broader guide to leaving a translation tool without losing SEO.

Still unsure whether Weglot is enough for you? Read our Weglot review first.

What happens when you cancel Weglot?

Your translated pages stop showing and gradually drop out of Google.

Weglot is clear about this. Its article on cancelling or pausing says that after cancelling, your translations are no longer active.

They don’t appear on your site anymore. And your translated pages are gradually removed from search engines such as Google.

Your project gets deleted

Your subscription falls back to the free plan.

According to the same article, your project is automatically deleted after three months of inactivity, unless you delete it earlier yourself.

Why this happens

Weglot translates through its own servers. Your CMS doesn’t contain more than your source language.

So without Weglot, your French or German pages simply no longer exist.

First rule: only cancel once your language versions are live somewhere else.

Here’s the safe order in one picture:

WEGLOT EXIT Cancel last, not first 1 Inventory: setup, translated URLs, traffic, hreflang 2 Export translations (CSV or XLIFF) or crawl the pages 3 Build the language versions in your CMS 4 Same URLs or a 301 per changed URL, hreflang complete 5 Switch over in one go, remove plugin, script and DNS 6 Only then: cancel the subscription

Step 1: know what Weglot publishes today

Make an inventory before you export anything.

You want to know four things.

Which setup you have

On WordPress, Weglot works through the plugin.

On other platforms, you choose in the Weglot dashboard under Setup. The options are a JavaScript integration, or an integration with subdomains or subdirectories.

Every translated URL per language

List each translated URL with its matching source URL.

If you have translated slugs (a Pro feature), note them separately. /fr/services/ is a different URL from /fr/diensten/.

Which translated pages earn traffic

Filter Google Search Console on the language folder or subdomain. Export the pages with impressions and clicks.

After the switch, those pages must stay on the same address or redirect with a 301.

The hreflang and canonicals Weglot generates today

Our free hreflang checker shows which language versions point to each other. It also recognises an active Weglot installation.

Tip: save this inventory as a spreadsheet. It becomes your redirect map in step 4.

Step 2: export your translations

Weglot export translations sit in the Advanced plan and higher.

That’s according to the Weglot help center on import and export. You have three ways:

  1. All translations: in your dashboard under Projects, Translations, Languages, choose Actions and then Export. Pick the file format, the language pairs and which translations you want.
  2. Per URL: under Translations, URLs, select the pages and export only their translations.
  3. Specific translations: per language pair, select sentences and export those.

Look for the Export action in the languages list:

What you get

The file arrives by email and is also listed in your dashboard’s activity feed.

Weglot recommends synchronising your translations with your current content first, so the export is complete.

The formats are CSV and XLIFF.

Watch out: a Weglot export is a list of sentences (source and translation), not ready-made pages. You use it to build the language versions in your CMS, not to import them one to one.

On a lower plan?

According to Weglot, you then edit translations one by one in the translation list, without bulk export. You have two options:

  • Upgrade temporarily to Advanced, just for the export
  • Crawl the translated pages yourself while they’re still online

With the second option, you’ll save the full HTML per translated URL, including title and meta description.

What each plan costs today is in what Weglot really costs.

Step 3: build the language versions in your CMS

Put the translations into your own CMS’s multilingual setup as real pages, linked to their source page.

Your options per CMS

  • WordPress: a multilingual plugin or multisite, compared in Weglot vs WPML
  • Drupal and Joomla: multilingual in core
  • Webflow: Localization

The overview per CMS is in our guide to leaving a translation tool.

Improve the translations while you’re at it

Align titles and meta descriptions with what people search for in each language. Have CTAs and forms proofread.

That’s often the biggest gain of the whole switch.

Our experience: for Suivo, Weglot had translated “time registration” as “tijdsregistratie”, with an s. Belgian searchers use “tijdregistratie”, without one.

A tool translates words, not search behaviour. More on that in website translation vs localization.

What happens to your URLs when the proxy stops?

That depends on your setup, and most exit guides skip this part.

There are four setups to check.

WordPress plugin with subdirectories

The Weglot plugin creates the language folders (/fr/, /de/). WordPress itself doesn’t know those addresses.

Deactivate the plugin and those URLs return a 404, unless your new multilingual setup takes them over.

Good news: with a multilingual plugin on /fr/, you can keep exactly the same URLs.

Do check that the slugs stay the same. Where a slug changes, you add a 301.

Subdomains (fr.yoursite.be)

With a subdomain integration, a CNAME record (for example fr) points to Weglot’s servers.

Stop Weglot without changing that record and nothing useful is left on fr.yoursite.be. You have two choices:

  • Keep the subdomain: point it to your own server or CMS and serve the French version there on the same paths.
  • Move to subdirectories, often simpler in a CMS: point the subdomain to your own server and 301 every old URL, such as fr.yoursite.be/contact/ to yoursite.be/fr/contact/.

Which structure suits you is covered in subdomain vs subdirectory for SEO.

Subdirectories on a non-WordPress site

Here it isn’t as visible.

Weglot’s article on switching from subdomains to subdirectories explains the setup. A subdirectory integration changes an existing DNS record to Weglot’s value; for a domain without www, that’s your A record.

Weglot explicitly adds that you must reset that record to its original value when you stop. It recommends taking a screenshot of your settings beforehand.

Watch out: skip that, and your whole domain still runs through a service you no longer use.

JavaScript integration

If Weglot only works through a script in your header, there aren’t any translated URLs that Google indexes.

No 301 map is needed. You remove the script and build the language versions properly in your CMS for the first time.

Avoiding 404s and duplicate language versions

Two mistakes come back in every Weglot exit, and both are avoidable.

404s on translated URLs

They appear when you switch Weglot off before your new versions are live. Or when slugs change without a redirect.

For a site move, Google recommends deciding per old URL where it should go. Use permanent server-side redirects and keep them for at least a year.

Build that list with our 301 redirect plan, then test it with the redirect checker.

Watch out: avoid redirect chains. Point every old URL straight to its final address.

Duplicate language versions

They appear when Weglot and your new setup are active at the same time.

For example, you then have two French versions of the same page, on a subdomain and in a subdirectory. Or two sets of hreflang tags, or two language switchers.

Rule of thumb: never run Weglot and the new setup live side by side. Work on staging and switch over in one go.

Afterwards, check that every language version lists itself and the other versions correctly. Our guide to hreflang explains how, and fixing hreflang errors covers what to do when it fails.

Step 4: remove Weglot cleanly

Once the new language versions are live and the redirects work, you remove Weglot.

The steps differ per platform.

WordPress

Deactivate and delete the plugin.

Check your menus and widgets for a leftover Weglot language switcher, and remove extra CSS you added for it.

Shopify

Deleting the app doesn’t always remove a manually added language switcher.

In a help article on leftover buttons, Weglot describes removing two lines from theme.liquid: {% render 'weglot_hreftags' %} and {% render 'weglot_switcher' %}.

Then search other theme files for weglot and elements such as <div class="weglot_here"></div>.

Other platforms

Remove the Weglot script from your header.

Reset the DNS records: the CNAME for subdomains, the A record for subdirectories.

Then search your source code

Search every template for “weglot”. Don’t skip the footer and header partials.

Leftover hreflang tags pointing to Weglot URLs are worse than no hreflang.

Step 5: cancel and delete your account

Only now do you cancel. It’s the last step, not the first.

According to Weglot, you go to Billing in your dashboard and choose Cancel current plan. Confirm, and optionally leave feedback.

Deleting the account

On a free plan, you delete your account yourself via your profile.

On a paid plan, according to Weglot’s help article on account deletion, you request it from Weglot by email.

Weglot repeats there that your translated pages gradually drop out of Google after cancelling. That’s no longer a problem, because they now live in your CMS.

Monitor the weeks after

Watch indexing and 404s per language in Search Console. Crawl Stats shows how many requests hit a redirect or a 404:

Google Search Console Crawl Stats report for customerimpact.be with total crawl requests and the breakdown by response, used to monitor 301 redirects and 404s after a Weglot exit Crawl Stats in our own Search Console for customerimpact.be, October 2026. The breakdown by response shows how many requests hit a 301 or a 404.

A rising 404 share after the switch means a translated URL lost its redirect.

Our guide to website indexing helps when new language pages are slow to appear.

Checklist: cancel Weglot without losing SEO

Eleven checks, in this order:

  1. Setup identified: WordPress plugin, subdomains, subdirectories or JavaScript.
  2. List of all translated URLs per language, with hreflang, canonical, title and meta description.
  3. Translated pages with traffic exported from Search Console.
  4. Translations exported (CSV or XLIFF from Advanced) or translated pages crawled.
  5. Language versions built in your CMS’s multilingual setup, proofread where it matters.
  6. Same URLs where possible, a 301 redirect per changed URL, tested.
  7. Hreflang complete and reciprocal, canonical per language version to itself.
  8. Weglot and the new setup never live at the same time: switch over in one go.
  9. Plugin, app, script and DNS records removed or reset; source code searched for “weglot”.
  10. New sitemap submitted, indexing and 404s per language monitored in Search Console.
  11. Only then: subscription cancelled and account deleted if needed.

Frequently asked questions

Can I export my Weglot translations on a cheaper plan?

Not in bulk. According to Weglot, export and import are included from Advanced. On lower plans you can upgrade temporarily for the export, or fetch the translated pages yourself while they are online.

Do my translated pages stay in Google after cancelling?

No. Weglot writes that they gradually drop out of search engines after cancelling. That is why you first put the new versions live on the same URLs or with 301 redirects.

Do I have to move from subdomains to subdirectories?

Not necessarily. It is often the simplest setup in a CMS, though. If you choose subdirectories, redirect every old subdomain URL with a 301 to its new address.

Is there an alternative without CMS work of my own?

Yes, another translation tool, but then you stay in the same model. We compare the options in Weglot alternatives compared.

Need help with your Weglot exit?

Cancel last: export, rebuild, redirect, check, and only then stop paying.

We make the inventory, export your translations and build the language versions in your own CMS. Then we set up the 301 map and the hreflang, and only cancel once everything is live and checked.

See our translation tool migration.

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.