Moving from Weglot to StoreLingo: a step-by-step plan

Changing translation tools on a working store is worth doing slowly. This plan covers what changes when you move from Weglot to StoreLingo, how to bring your existing translations along, and what to check before you switch over. It does not promise any particular search result; any change of page addresses is a change search engines have to process.

What changes

StoreLingo works differently from a service that delivers translated pages itself. It writes translated copies of your products and CMS items into your own Webflow site. That means:

• New addresses. Each translated product gets its own page with a slug such as de-blue-mug (the language prefix plus the source name; the slug is not translated). Your current translated pages are very likely at different addresses.
• Less is translated. StoreLingo translates product and CMS item fields. It does not translate static page text, labels in page templates (such as "Add to cart"), navigation, cart and checkout pages, emails Webflow sends, Ecommerce categories or slugs. Compare that with what your current setup covers before you start.
• Variants. A translated product gets every variant of the source, with translated option names and values. Each variant takes the source variant's price, compare-at price, SKU code and images.
• Routing is yours. StoreLingo does not route visitors, switch languages or add hreflang tags. You build per-language listing pages in Webflow and filter them by the Locale field StoreLingo sets.

Step 1: record where you are now

• List the languages you serve and the address pattern of your translated pages.
• Note your most-visited translated pages, so you can check each of them after the switch.
• Export your translations from Weglot as a CSV. Weglot's own documentation describes where the export is and what it contains.

Step 2: connect StoreLingo

StoreLingo is a Webflow app that connects to your site and opens in its own browser tab. When you connect, Webflow asks you to grant these permissions: authorized_user:read, sites:read, sites:write, cms:read, cms:write, ecommerce:read and ecommerce:write. There is no custom code permission. You confirm your source language, then StoreLingo syncs your products and CMS items.

Step 3: add languages and choose fields

Add your target languages. StoreLingo supports DeepL's target languages; anything else is refused when you add it. Then check in Settings which fields are translated: by default every text field that has text on your products and CMS items, and image alt text. Untick any you want to keep in the source language.

If there are brand or product names that must stay as written, add them to the glossary (a do-not-translate list) before you run any AI translation.

Step 4: import your Weglot translations

Use Import from Weglot in the app and choose your CSV. What the import does:

• It matches each row to your synced product fields and variant names by the source text (compared after tidying up spaces), for the target language in that row. The language must already be added in StoreLingo.
• A match replaces the translation already there for that field and language, so import before you edit translations in StoreLingo. Rows in your source language are skipped.
• Rows that do not match are reported, with examples, and are not guessed.
• Imported translations are marked Edited, so you can review them before publishing.
• It covers product fields. For CMS items, use StoreLingo's general CSV import, which takes a file in the same layout as StoreLingo's CSV export.

Expect some rows to be unmatched: text that has changed since the export, or text that was never part of a product field. Translate the gaps with AI translate (it fills empty fields) or by hand.

Step 5: review and publish one language

Review the translations, then publish one language. StoreLingo writes the copies straight to your live site and does not publish your whole Webflow site, so unpublished changes you made in the Designer stay unpublished.

Publishing creates one translated copy per product (with every variant) and per CMS item, adds a Locale field to the collections it publishes, and sets it on every copy. The copies count toward your Webflow plan's product and CMS item limits.

Step 6: set up how visitors reach each language

Duplicate your listing pages for each language and filter each Collection List by the Locale field. Your source items are not tagged, so the source-language list shows the items where Locale is not set. The app shows a routing guide after the first publish.

Step 7: check before you switch

Open a few translated products and items, including the most-visited ones from step 1, and check:

• the translated text is there and reads correctly;
• the prices are right (each variant takes its source variant's price when you publish);
• every variant is there, with translated option names and values;
• the per-language listing pages show the right items.

Step 8: switch over

• Redirects. If your old translated pages have visitors or links, add 301 redirects from the old addresses to the new ones in Webflow's redirect settings, one per page. Plan the list from step 1.
• Turn off Weglot following Weglot's own documentation, so two tools are not serving the same language at the same time.
• Hreflang. StoreLingo does not add hreflang tags. If your current setup provides them, they go away when you turn it off. Decide beforehand whether and how you want them; the hreflang post explains the options in plain terms.
• Publish the site so the redirects go live, then open a few old addresses and check that they land on the new pages.

Step 9: keep an eye on it

Watch your analytics and search console for the translated pages over the following weeks, and fix any old address that is missing a redirect. Keep your Weglot export file even after you cancel.

Going back

Before you switch over, going back is simple: the translated copies sit unused in Webflow, and you can delete or archive them. After you switch, turn your previous setup back on and remove the redirects. To remove the translated copies and the Locale fields StoreLingo created, run Remove translations from Webflow in StoreLingo before you uninstall; uninstalling does not remove them, and after an uninstall StoreLingo cannot reach your site, so you would delete them in Webflow yourself.

Questions about a migration go to hello@storelingo.com; we reply within one business day (Monday to Friday, CET).