How to Migrate from Weglot to GPTranslate (And Own Your Translations)

The Problem With Weglot That Nobody Talks About

Weglot is a well-marketed product. Their Facebook and Google ads are everywhere, and the onboarding is genuinely smooth. But there’s a structural problem that becomes obvious the moment you try to leave: your translations are stored on Weglot’s servers, not in your WordPress database.

Cancel your subscription, and those translations — every French product description, every German page you spent time reviewing — are gone. You don’t get a backup. You don’t get an export unless you manually trigger one before cancellation. This is by design: Weglot’s business model depends on that lock-in.

The other structural issue is technical: Weglot works as a JavaScript overlay. Your WordPress site stays monolingual; Weglot’s CDN injects translated text client-side when a visitor loads the page. That means your translated content doesn’t live in WordPress posts — it lives on Weglot’s infrastructure. Googlebot sometimes renders JS slowly or inconsistently, which is why Weglot users occasionally see translated pages drop from search rankings after a crawl cycle.

GPTranslate works the opposite way: translations are stored as native WordPress post entries, each with its own URL, indexed directly, no JS proxy required. This guide walks you through migrating from Weglot to GPTranslate without losing what you’ve already translated.

Why People Switch Away from Weglot

Beyond the ownership problem, Weglot has three other pressure points that tend to trigger migrations:

• Pricing that scales badly. Weglot charges per word and per language. The Starter plan (€15/month) covers 1 language and 10,000 words. The Business plan (€29/month) covers 3 languages and 50,000 words. For a content-heavy site with 5+ languages, you’re quickly looking at the Pro plan at €79/month — annually, that’s €948 for translation hosting alone. GPTranslate Pro is a one-time purchase per site; you bring your own DeepL or AI API key and pay only for actual usage.
• No native WordPress SEO integration. Because Weglot’s translations aren’t WordPress posts, they don’t interact natively with SEO plugins like SureRank, Yoast, or Rank Math. You can’t set per-language meta titles or descriptions the way you’d expect — you’re working around Weglot’s abstraction layer.
• Translation quality control is limited. Weglot gives you a visual editor, but the translation memory lives on their servers. You can’t use your own glossary natively or switch translation engines per content type without upgrading to their highest tier.

Before You Start: What You Need

Before touching your live site:

1. Export your Weglot translations NOW — before anything else. Go to your Weglot dashboard → Settings → Translations → Export. Download the CSV for every active language. Do this even if you plan to re-translate everything with AI — it’s your safety net.
2. A staging site. Duplicate your live site to a staging environment (WPStaging, Duplicator, or your host’s tool). Run the migration there first.
3. GPTranslate Pro with the WP Export add-on. The add-on handles the Weglot CSV import into WordPress natively.
4. A DeepL Pro API key (optional but recommended for re-translating new content going forward). Get it at deepl.com/pro-api.
5. A full database backup. phpMyAdmin, UpdraftPlus, or your host’s backup tool. Non-negotiable before any multilingual migration.

Step 1: Export Your Translations from Weglot

This is the most time-sensitive step. Export before you change anything on your site.

1. Log into your Weglot dashboard.
2. Go to Settings → Translations.
3. Click Export translations. Select each target language and download the CSV file.
4. Repeat for every language your site has active in Weglot.

The Weglot export gives you a CSV with two columns: the original string (in your source language) and the translated string. For posts and pages with a lot of content, large sections may be split into sentence-level segments. GPTranslate’s import reassembles these into complete post content.

What’s NOT in the Weglot export: translated URLs (slugs), hreflang configuration, and any overrides you made via their visual editor that weren’t synced back to their translation memory. Translated slugs will need to be recreated by GPTranslate (it does this automatically). Visual editor overrides that weren’t in the translation memory may need manual review after import.

Step 2: Install GPTranslate Alongside Weglot

Do not deactivate or uninstall Weglot yet. Install GPTranslate Pro first — they can coexist temporarily while you verify everything is configured correctly.

1. Upload and activate GPTranslate Pro from your JExtensions Store account.
2. Go to GPTranslate → Settings → Languages and add the same language codes you had active in Weglot (ISO 639-1 codes — fr, de, ja, etc.).
3. Under Settings → AI Models, configure your translation engine. If you’re using DeepL Pro, paste your API key here.
4. Under Settings → Routing, confirm GPTranslate uses subdirectory URLs (/fr/, /de/). Weglot also uses subdirectories by default, so your URLs will remain identical after the switch — no 301 redirects needed for the majority of sites.
5. Do NOT enable auto-translation yet. Import your existing Weglot translations first before the AI Crawler runs.

Step 3: Import Your Weglot Translations into GPTranslate

With the WP Export add-on active:

1. Go to GPTranslate → WP Export → Import.
2. Select Weglot CSV as the import format.
3. Upload the CSV file for your first language.
4. Review the import preview. Entries that can’t be matched (orphaned strings from deleted posts, widget text, etc.) are flagged as unmatched — review these separately.
5. Confirm the import. GPTranslate creates native WordPress post entries for each translated page, each with its own URL under the language subdirectory.
6. Repeat for each language.

The key difference from a WPML migration: Weglot exports string-by-string rather than full post content, so the import process does more reassembly work. For most standard WordPress themes, the matching is reliable. For heavily customised Elementor or Divi pages, do a manual spot-check after import to confirm the assembled content is correct.

Step 4: Verify, Then Remove Weglot

Before uninstalling Weglot, confirm the migration is solid:

• Browse 5–10 translated pages in each language. Check that headings, body text, and product descriptions are correctly assembled.
• Check WooCommerce product pages in 2–3 languages. Confirm cart text, checkout strings, and attribute labels are translated.
• Run Google Search Console URL Inspection on 3–4 translated URLs. Confirm HTTP 200, correct canonical, and hreflang tags present.
• Specifically verify that the translated page content is visible in “View source” — with GPTranslate’s native model, you should see the translated text in the raw HTML, not a JS placeholder. This is the key SEO architecture improvement over Weglot.

Once verified: deactivate and delete the Weglot plugin from Plugins → Installed Plugins. At this point, your Weglot subscription can be cancelled — your translations are now stored natively in WordPress and are no longer dependent on Weglot’s infrastructure.

Step 5: Enable GPTranslate’s AI Agent Crawler for New Content

With your existing translations imported, you’re ready to enable automatic translation for new content going forward.

GPTranslate’s AI Agent Crawler™ monitors your site for new or updated posts and translates them automatically using whichever AI model you’ve configured — DeepL Pro, Claude, GPT, or Gemini. You can set different models per language or per content category. For most migration scenarios, DeepL Pro is the best default: it’s fast, reliable, and at ~€5.99/month for the Starter plan on pay-as-you-go billing, it costs a fraction of what Weglot charged just for translation storage.

Enable the crawler under GPTranslate → AI Agent → Enable Crawler, set your translation schedule (immediate on publish, or batched nightly), and publish a test post in your source language to confirm it gets translated across all active languages.

Post-Migration SEO Checklist

The Weglot-to-GPTranslate migration changes your site’s rendering architecture, which has specific SEO implications:

1. Confirm translated content is in raw HTML. View source on any translated page and verify the translated text is in the page source — not injected by JavaScript. This is the most important architectural change from Weglot.
2. Check hreflang tags. View source and search for hreflang. You should see one tag per active language pointing to the correct language-prefixed URL. GPTranslate generates these natively.
3. Submit your GPTranslate sitemap to GSC. The multilingual sitemap is at /wp-json/gptranslate/v1/sitemap.xml. Submit it under Search Console → Sitemaps, replacing any Weglot-era sitemap submissions.
4. Inspect 5–10 translated URLs in GSC. For any URL previously indexed under Weglot, confirm Google still finds it at the same URL and returns HTTP 200 with the correct canonical.
5. Monitor impressions for 4–6 weeks. Because you’re moving from JS injection to native rendering, some pages may see a short-term adjustment as Google re-crawls them. Sites with previously inconsistent JS rendering under Weglot often see ranking improvements within 4–8 weeks.
6. Check for duplicate content warnings if Weglot was configured with subdomains instead of subdirectories. Set up 301 redirects from fr.yoursite.com to yoursite.com/fr/.

Frequently Asked Questions

Will I lose my Weglot translations if I cancel before exporting?

Yes. Weglot does not retain your translations after subscription cancellation — they are stored on Weglot’s servers, not in your WordPress database. Always export via the Weglot dashboard before cancelling or making any changes to the plugin setup.

Will my translated URLs change after switching to GPTranslate?

In most cases, no. Both Weglot and GPTranslate default to subdirectory routing (/fr/page-name/, /de/page-name/). If your Weglot configuration used subdirectories, your URLs remain identical and Google sees an in-place content update. If you used Weglot’s subdomain option (fr.yoursite.com), you’ll need 301 redirects from the subdomains to the subdirectory URLs.

What happens to my SEO rankings during the migration?

Because GPTranslate serves translated content as native HTML rather than JavaScript injection, the migration typically improves long-term indexing reliability. Rankings usually remain stable, and sites with previously inconsistent JS rendering under Weglot often see improvements within 4–8 weeks of the switch.

Is GPTranslate cheaper than Weglot?

For most sites, significantly. Weglot bills monthly by word count and language count — a 5-language site with moderate content volume typically costs €29–€79/month (€348–€948/year). GPTranslate Pro is a one-time licence per site; you pay only for the AI API calls you actually make (typically €2–€15/month in DeepL or OpenAI API charges). The break-even for most sites is within the first 3–4 months.

Do I need to re-translate everything after the migration?

No. The Weglot CSV export captures your existing translations, and GPTranslate’s import brings them into WordPress natively. You only need to re-translate content that wasn’t translated in Weglot, or content where you want to upgrade quality with a new AI model like DeepL Pro or Claude.

👉 Ready to switch? Download GPTranslate Pro — the WP Export add-on for Weglot CSV import is included. Questions about your specific Weglot setup? Use the support form on the JExtensions Store page.