How to Leave Weglot and Keep Your Multilingual Website (Every Platform)

Last updated: October 22, 2026 · By the LATW team

Quick answer: To leave Weglot without losing your multilingual site, export your translations, then rebuild each language natively in your own platform: WPML, Polylang or TranslatePress on WordPress, Shopify’s built-in languages, Wix Multilingual, Webflow Localization, or the language systems in Drupal and PrestaShop. Translate in bulk with LATW Cloud, add 301 redirects, check hreflang, and cancel Weglot last.

Weglot is quick to switch on. Switching it off is where people get nervous, and for good reason. Your word count grows with every product and blog post, the bill grows with every new language, and all those translations sit on Weglot’s servers, not yours.

This guide walks you through leaving Weglot step by step, with a section for each platform. At the end, your site is still multilingual, the translations are stored in your own platform, and your traffic from Google stays where it is.

Disclosure: LATW makes LATW Cloud, the translation engine we recommend in this guide. The steps work with any native setup, and there’s a section on when staying with Weglot makes more sense.

In this guide:

• What happens when you cancel Weglot
• The 15-minute Weglot exit checklist
• How to leave Weglot in 6 steps
• Weglot vs native translations
• Platform by platform: WordPress, Shopify, Wix, Webflow, Drupal, PrestaShop
• How to keep your Google rankings
• How much it costs
• FAQ

What happens when you cancel Weglot

When you cancel Weglot, your translated pages stop working, because Weglot stores and serves the translations from its own servers. Your site only ever held the original language.

In practice, that means:

• Translated pages disappear. Depending on your setup, language URLs either fall back to the original language or return a 404 error. On sites that used subdomains (fr.example.com), the subdomain points to Weglot, so it simply stops loading.
• Indexed pages lose their content. Google keeps sending visitors to your French or German URLs for a while. If those pages are empty or broken, rankings and traffic from those markets drop.
• Uninstalling isn’t cancelling. Removing the Weglot plugin or app doesn’t stop billing. Weglot has confirmed this in its replies to Shopify App Store reviews: you need to cancel separately in your Weglot account’s billing settings.

Proxy translation vs native translation

Proxy translation (Weglot’s model) means a third-party service stores your translations and serves them on top of your site. Native translation means each translated page is a real record in your own CMS, edited in your usual editor and backed up with the rest of your site. Leaving Weglot is really a move from the first model to the second.

The 15-minute Weglot exit checklist

Do these six things before you change anything on your site:

1. Write down your languages and URL format. Subdomains (fr.example.com) or subfolders (example.com/fr/)? This decides whether you’ll need redirects.
2. Export your indexed URLs per language. Use your sitemap and the Pages report in Google Search Console. This is your redirect and QA list.
3. Export your translations from Weglot. Use the import/export option in the Weglot dashboard. If your plan doesn’t include it, ask Weglot support before you cancel.
4. Save your glossary and translation rules. Brand names, product terms and words you never translate. You’ll reuse them in the new setup.
5. Note your renewal date. Plan to finish the migration before Weglot renews.
6. Back up your site. Standard practice before any structural change.

How to leave Weglot in 6 steps

The process is the same on every platform. Only the tools change, and you’ll find them in the platform section below.

Step 1: Turn on your platform’s native multilingual feature

Native multilingual means your platform itself knows about languages: it stores a translated version of every page, product and menu, and it generates language URLs, hreflang tags and sitemaps. Shopify, Wix, Webflow, Drupal and PrestaShop have this built in. On WordPress you add it with a plugin such as WPML, Polylang, TranslatePress or LATW Multilingual.

Add the same languages you had in Weglot, but don’t publish them yet.

Step 2: Match your URL structure, or plan redirects

The safest migration keeps the exact same URL pattern. If Weglot used example.com/fr/, set up your native languages with /fr/ too, and most URLs won’t change at all.

If Weglot used subdomains and your platform uses subfolders, that’s fine. You’ll redirect each old URL to its new address with a 301 redirect (see how to keep your Google rankings).

Step 3: Translate your content into the new setup

Your Weglot export is a backup, not something you can paste back in. The fastest way to fill your native languages is to translate the site again, straight into your platform.

That’s what LATW Cloud does. It’s a hosted AI translation engine that writes translations natively into your platform:

1. Install the free LATW connector for your platform and click Connect with LATW.
2. Choose your languages and a quality class: Economy (GPT-6 Luna, good for blog posts), Standard (GPT-6 Sol, good for landing pages) or Premium (GPT-6 Astra, good for legal pages).
3. Add the terms from your Weglot glossary to your LATW glossary, or import them as a CSV file. Add a prompt preset for your brand voice, for example “friendly, informal tone”.
4. Check the cost estimate and start the job. It runs on LATW’s servers in the background, so you can close the tab.

LATW Cloud doesn’t import Weglot export files today. Check latw.ai/cloud or the LATW docs to see if the option has been added since. Keep your Weglot export anyway: it’s useful for comparing terminology on your key pages.

Step 4: Review the pages that make you money

You don’t need to read every page. Check the homepage, your top landing pages, your best-selling products and your legal pages. Look at terminology, prices and units, buttons and calls to action, and SEO titles. If a term keeps coming out wrong, add it to your glossary and run that content again rather than fixing it page by page.

Step 5: Set up redirects, hreflang and sitemaps

Add 301 redirects for every URL that changed. Then check that each language version has hreflang tags pointing to all the others, and that the translated pages appear in your sitemap. Your native platform generates these. Your job is to confirm they’re right (common hreflang problems).

Step 6: Switch Weglot off, cancel, then monitor

Do it in this order:

1. Publish your native languages.
2. Disable and uninstall Weglot (and remove its subdomain DNS records, if you used them, once your redirects are ready).
3. Cancel the subscription in your Weglot account’s billing settings.
4. Resubmit your sitemaps in Google Search Console and monitor for four to six weeks.

Zero-downtime switch: build and review your native translations while Weglot is still live. Your visitors keep seeing Weglot’s pages until the moment you publish the native ones, so there’s no gap where your French or German site is missing.

Weglot vs native translations

	Weglot	Native platform + LATW Cloud
Where translations live	Weglot’s servers	Your own platform (CMS database)
If you stop paying	Translations disappear from your site	Translations stay on your site
Translated URLs, hreflang, sitemaps	Handled by Weglot	Handled by your platform
How you pay	Subscription by translated words and languages	Per word, no subscription required
Where you edit translations	Weglot dashboard or visual editor	Your usual editor
Backups	Depend on Weglot’s export	Part of your normal site backup

For a full feature comparison, see LATW Cloud vs Weglot.

Your native replacement for Weglot, platform by platform

Platform	Native multilingual feature	What LATW Cloud does	Do URLs change?
WordPress	WPML, Polylang, TranslatePress or LATW Multilingual	Translates and saves into your multilingual plugin	Usually not (Weglot on WordPress also uses /fr/)
Shopify	Built-in store languages (Shopify Markets)	Translates all store content into Shopify’s native translations	Only if Weglot used subdomains
Wix	Wix Multilingual	Translates into Wix Multilingual	Only if Weglot used subdomains
Webflow	Webflow Localization	Translates into your Webflow locales	Only if Weglot used subdomains
Drupal	Core Language and Content Translation modules	Works as a TMGMT translation provider	Only if Weglot used subdomains
PrestaShop	Built-in languages	Translates into PrestaShop’s language fields	Only if Weglot used subdomains

How to leave Weglot on WordPress

To remove Weglot from WordPress, install a native multilingual plugin, translate your content into it with LATW Cloud, then deactivate the Weglot plugin.

Native replacement: pick the framework that fits your site.

• LATW Multilingual: free and lightweight, with a language switcher, language URLs and hreflang. A good fit if Weglot was your only multilingual tool.
• Polylang: flexible and developer-friendly.
• WPML: the full framework for complex sites and WooCommerce stores.
• TranslatePress: translate visually on the live page.

Steps:

1. Install your framework and add your languages with the same /fr/-style URLs Weglot used.
2. Install the matching free LATW connector (LATW for WPML, LATW for Polylang, LATW Multilingual Pro or the TranslatePress connector) and connect it to LATW Cloud.
3. Translate pages, posts, products, menus, strings and SEO titles in one background job.
4. Review, publish, then deactivate and delete the Weglot plugin.

SEO trap: don’t delete Weglot before the new framework is live. The /fr/ URLs would return 404 errors in the meantime. Also note that translating WooCommerce products needs a LATW Pro licence.

More: LATW Multilingual vs Weglot and how to migrate between WPML, Polylang, TranslatePress and Weglot.

How to remove Weglot from Shopify

To remove Weglot from Shopify, add your languages in Shopify’s own settings, translate your store with LATW Cloud, publish the languages, then uninstall the Weglot app and cancel the plan.

Native replacement: Shopify supports multiple languages out of the box. You add languages in Settings → Languages and assign them to your markets, and Shopify serves them on subfolders such as yourstore.com/fr/.

Steps:

1. Add your languages in Shopify, but leave them unpublished.
2. Install the LATW Cloud app and connect your store.
3. Translate the whole store into Shopify’s native translations: products and variants, collections, pages, blog posts, navigation menus, metafields, theme text, SEO titles, meta descriptions and URL handles.
4. Review your top products and collections, publish the languages, then uninstall Weglot.
5. Cancel the Weglot plan in your Weglot account. Uninstalling the app doesn’t do it.

SEO trap: if Weglot served your languages on subdomains (fr.yourstore.com), Shopify’s URL redirect tool can’t redirect them, because they never pointed to Shopify. Set up a redirect rule at your DNS provider (for example Cloudflare) that sends fr.yourstore.com/ to yourstore.com/fr/.

How to replace Weglot on Wix

To replace Weglot on Wix, turn on Wix Multilingual, translate your site into it with LATW Cloud, then remove Weglot.

Native replacement: Wix Multilingual is built into Wix. It adds a language switcher and serves each language on its own URL.

Steps:

1. Turn on Wix Multilingual in your dashboard and add your languages, keeping them hidden from visitors.
2. Install the LATW Cloud app and connect your site.
3. Translate your pages, menus, blog posts, store products and SEO settings.
4. Review, make the languages visible, then remove Weglot and its code from your site.

SEO trap: Weglot on Wix usually runs on subdomains. Choose the URL format in Wix Multilingual before you launch, and redirect the old subdomains at DNS level if the format changes.

How to move from Weglot to Webflow Localization

To move from Weglot to Webflow Localization, add locales in Webflow, translate your static pages and CMS items with LATW Cloud, then remove the Weglot script.

Native replacement: Webflow Localization stores a translated version of each page and CMS item and serves locales on subfolders such as example.com/fr/. It’s a paid add-on, so include it in your costs.

Steps:

1. Enable Localization and add your locales (unpublished).
2. Install the LATW Cloud app and connect your site.
3. Translate static pages, CMS collections, SEO titles and meta descriptions.
4. Review, publish the locales, then remove the Weglot script and its DNS records.

SEO trap: a common question on the Webflow forum is how to move content out of Weglot into Localization. You don’t have to move it: translate directly into your locales, then add 301 redirects in Webflow (or at your DNS provider for old subdomains).

How to leave Weglot on Drupal

To leave Weglot on Drupal, enable Drupal’s core language modules, add the TMGMT LATW Cloud provider, and translate your content into native translations.

Native replacement: Drupal core has the Language, Content Translation, Interface Translation and Configuration Translation modules. TMGMT (Translation Management Tool) adds translation jobs on top.

Steps:

1. Enable the core language modules and set language detection to URL prefixes (/fr).
2. Install TMGMT and the TMGMT LATW Cloud module, then connect it to LATW Cloud.
3. Create translation jobs for your content and let them run in the background.
4. Review, remove Weglot, and add redirects with the Redirect module where URLs changed.

How to leave Weglot on PrestaShop

To leave Weglot on PrestaShop, add your languages in the back office, translate your catalogue with the LATW Cloud module, then remove Weglot.

Native replacement: PrestaShop stores every product, category and CMS page in all your installed languages, with friendly URLs such as /fr/.

Steps:

1. Add your languages under International → Localization → Languages.
2. Install the LATW Cloud module and connect your shop.
3. Translate products, categories, CMS pages and SEO fields. Large catalogues run in the background, for example overnight.
4. Review your bestsellers, then remove Weglot.

SEO trap: check that your theme or SEO module outputs hreflang tags for every language, and redirect old Weglot subdomains at DNS level.

How to keep your Google rankings when you leave Weglot

A Weglot migration doesn’t have to cost you rankings. Google cares that every old URL still leads to the same content in the same language. Four things make that happen.

Map old URLs to new URLs

Use the URL list from your checklist and add a 301 redirect for every address that changes:

Old Weglot URL	New native URL
fr.example.com/	example.com/fr/
fr.example.com/a-propos/	example.com/fr/a-propos/
de.example.com/produkte/tasche/	example.com/de/produkte/tasche/

If your URL format stays the same, you only need redirects for slugs that changed.

Keep translated slugs consistent

If Weglot translated your slugs (for example /fr/a-propos/ instead of /fr/about/), keep the same translated slugs in your new setup, or redirect the old ones. LATW Cloud translates URLs, so your new slugs will be translated too. Compare them with your old list.

Check hreflang, canonical tags and sitemaps

Every language version should list all the others in hreflang tags, carry a self-referencing canonical tag and appear in your sitemap. Your platform generates these. Spot-check a few pages per language with a crawler or by viewing the page source.

Watch Search Console for six weeks

Track three things: indexed pages per language, 404 errors, and clicks by country. Short ranking swings after a URL change are normal when redirects are in place. A steady drop in one language usually means missing redirects or broken hreflang.

How much does it cost to leave Weglot?

With a native setup, you pay once to translate your site and then only for new or changed content, instead of paying Weglot every year for the same words.

Here’s an example: a 40,000-word site in 3 languages. Weglot and LATW Cloud both count words per target language, so that’s 120,000 translated words.

	Cost	What you get
Weglot Pro	€79/month or €790/year	Up to 200,000 words and 5 languages, every year. Business (€29/month) caps at 50,000 words.
LATW Cloud, Economy	about $2.81, one-off	120,000 words at $0.0234 per 1,000 words
LATW Cloud, Standard	about $56.16, one-off	120,000 words at $0.468 per 1,000 words

Most sites mix quality classes: blog posts in Economy, landing pages in Standard and legal pages in Premium ($2.34 per 1,000 words). After the first run, you only pay to translate what you add or change.

A few more details:

• No subscription required. Connecting your site is free. You top up LATW Credits from $5, pay from $23.40 per 1 million words, and Credits never expire. Unused Credits are refundable within 14 days.
• You see the price first. The estimate appears before each job, and Credits charge exactly what it shows. Retries and failed items aren’t billed.
• Bigger sites and agencies can choose Solo ($9/month), Startup ($25/month) or Agency ($79/month). These add your own AI key (BYOK), Batch mode at half the cost with results within 24 hours, and 20%, 30% or 40% off Credits.
• Platform costs. Shopify’s languages and Wix Multilingual are included in those platforms. Webflow Localization and WPML are paid. On WordPress, translating WooCommerce products needs a LATW Pro licence.

Prices checked on October 22, 2026. Weglot prices are in EUR, excluding VAT. LATW prices are in USD, excluding VAT.

When staying on Weglot makes sense

Leaving isn’t always worth it. Stay with Weglot if:

• the site is temporary, such as a campaign that ends in a few weeks;
• you can’t access your CMS or your site runs on a custom or headless stack that LATW Cloud doesn’t connect to;
• your content is small and stable, so you never get near your plan’s word limit and the bill doesn’t bother you;
• your team wants zero setup and is happy to edit translations only in Weglot’s visual editor.

If none of these applies, a native setup will usually cost less over time and leave you owning your translations.

FAQ

Will I lose my translations if I cancel Weglot?

Yes, they disappear from your site. Weglot stores and serves translations from its own servers, so your translated pages stop working when the subscription ends. Export your translations before you cancel, and set up native languages in your own platform first so visitors and search engines never hit empty pages.

Can I export my translations from Weglot?

Yes. Use the import/export option in your Weglot dashboard, or ask Weglot support if your plan doesn’t include it. Do it before you cancel. LATW Cloud doesn’t import Weglot export files today, so check latw.ai/cloud to see if the option has been added. Retranslating with LATW Cloud is usually faster anyway.

Does uninstalling Weglot cancel my subscription?

No. Removing the Weglot plugin or app doesn’t stop billing. You need to cancel the subscription separately in your Weglot account’s billing settings. Uninstall only after your native languages are live, and cancel right after, before your next renewal date.

Will leaving Weglot hurt my SEO?

Not if you keep every old URL working. Publish your native languages before you switch Weglot off, add 301 redirects for any URL that changes, check hreflang and sitemaps, and monitor Google Search Console for four to six weeks. Short ranking swings are normal. Lasting drops usually mean missing redirects.

What’s the cheapest way to keep a multilingual site after Weglot?

On WordPress, use a free multilingual plugin such as LATW Multilingual or Polylang and translate with LATW Cloud. Connecting your site is free, there’s no subscription, and Economy translation costs $0.0234 per 1,000 words. On Shopify and Wix, the native multilingual features are included in your plan.

Do I need to change my URLs when I leave Weglot?

Only if your new platform uses a different format. If Weglot used subfolders like /fr/, keep the same pattern and most URLs stay the same. If it used subdomains like fr.example.com, move to subfolders and add 301 redirects from each old address, usually at your DNS provider.

How long does a Weglot migration take?

Connecting LATW Cloud takes a few minutes, and a small site can be translated and live in under an hour. Large catalogues run in the background on LATW’s servers, often overnight. Plan extra time for reviewing your key pages and setting up redirects, especially if you’re moving from subdomains to subfolders.

Does LATW Cloud work on Shopify, Wix and Webflow?

Yes. LATW Cloud connects to Shopify, Wix, Webflow, WordPress (WPML, Polylang, TranslatePress and LATW Multilingual), Drupal and PrestaShop. On each platform it writes translations into the native multilingual system, so translations stay on your site even if you stop using LATW Cloud.

Is my content safe during translation?

LATW Cloud processes content on EU-hosted servers, and a data processing agreement (DPA) is available. Submitted text is deleted 7 days after the translation job finishes. The finished translations live in your own platform, not on LATW’s servers.

The bottom line

Leaving Weglot comes down to the order you do things in. Export first, build your languages natively while Weglot is still running, redirect anything that changed, and cancel last. Do it that way and your visitors never see a broken page.

LATW Cloud handles the translation step on every major platform and writes the result into your own site, so you own your translations from day one. Connect your site for free and top up from $5, no subscription needed.

Translate my website →

Need platform-specific setup steps? See the LATW docs. Still comparing options? Read the best Weglot alternatives compared.