Weglot on Shopify: an honest evaluation

Weglot works with Shopify, installs in minutes, supports 110+ languages, and serves translated pages that search engines index normally. All of that is true and none of it is the useful question. The useful question is what Weglot adds to a Shopify store, because Shopify already publishes each language on its own URL, adds hreflang automatically, includes every published language in your sitemaps, and ships checkout in 33 professionally translated languages. Some of what gets marketed as the reason to buy is already sitting in your admin.

So this evaluation runs backwards from every other one. First what you already have, then what Weglot genuinely adds on top, then what that delta is worth, and finally the question the delta does not answer.

Does Weglot work with Shopify?

Yes. Weglot is a hosted translation service with a Shopify integration that installs without code, detects your content automatically, applies a first machine-translation pass and gives you a visual editor to refine it. It carries roughly 1,500 App Store reviews at 4.6 stars, supports 110+ languages and dialects, and states compatibility with all Shopify themes including custom builds, as well as named third-party apps such as Pagefly, Klaviyo, Yotpo and GemPages.

That last point is a real strength and worth stating plainly, because third-party app content is exactly where Shopify's own free tool stops. If your storefront leans on a page builder, a reviews widget and an email tool, coverage of those is not a marketing detail.

What does Shopify already do without any app?

Before evaluating any translation app, establish the baseline you already own. A Shopify store publishes language-specific URLs as subfolders, so publishing French and German changes your store URLs to example.com/fr and example.com/de. Shopify automatically adds hreflang tags and includes all published languages in sitemaps. Checkout and theme content arrive professionally pre-translated in 33 languages. And every plan except Lite lets you sell in up to 20 languages from one store.

This matters because multilingual SEO is the headline benefit in most translation-app marketing, and on Shopify a substantial part of it is platform behaviour rather than app behaviour. You are not buying hreflang. You may well be buying other things worth paying for, but the comparison only becomes honest once the free baseline is on the table.

So what does Weglot actually add?

Weglot's genuine additions on Shopify are coverage, speed and workflow rather than SEO plumbing. It translates content that lives outside Shopify's own translatable resource types, including third-party app output, which is the gap Shopify's free tool leaves open. It applies a first machine-translation pass across the whole storefront immediately rather than two languages at a time. It provides a visual editor with live preview, and the option to order professional translation from inside the dashboard. It offers 110+ languages, though the practical ceiling remains Shopify's 20 per store.

Two additions are plan-dependent and worth checking against the tier you are actually buying. Weglot states that URL translation is available on Pro plans and above, and its language subdomain or subdirectory handling is configured rather than automatic. Neither is hidden, but both are easy to assume you have.

Does Weglot translate the Shopify checkout?

Weglot states that it "translates the full buyer's journey on Shopify, from products to checkout". That is not wrong, but it is incomplete in a way that matters for the decision. Shopify's checkout is Shopify's own system, professionally pre-translated in 33 languages and following the shopper's browsing language. No third-party app replaces that translation; what an app can do is cover the content around and adjacent to it.

The practical consequence is that checkout coverage is not a reason to choose between translation apps on Shopify, because it is not really theirs to differentiate on. If a comparison presents checkout as an app-level feature, it is describing the platform.

Will Weglot's translated pages get indexed?

Yes. Weglot serves translated pages server-side on dedicated URLs with hreflang tags and localised sitemaps, so search engines crawl and index them normally. This needs saying plainly because the category routinely gets it wrong, and because being wrong about it is the fastest way to lose a reader who checks.

The failure mode that does exist is narrower and worth understanding: tools that switch language only in the visitor's browser leave a single crawlable page, and some free tiers across the category are configured that way. That is a real distinction, and it is not a description of Weglot's paid product. The question to ask any vendor is whether your French page is a server-rendered URL with hreflang on the specific plan you are buying.

Indexability is also not the same as demand. Whether those indexed pages earn traffic depends on local keyword demand, and a literal translation of your English keyword set is not what anyone types in Munich. That is a separate commercial problem from the one a translation app solves.

What does it cost as the catalogue grows?

Weglot's pricing scales with translated words multiplied by the number of languages, which means the bill tracks two things that both grow when a store succeeds. The free plan covers 2,000 words in one language, which is a trial rather than an operating tier. Paid plans start from about €15 per month billed annually and step up unevenly, so adding one language or growing the catalogue can move you a tier regardless of the other dimension.

The tier-by-tier arithmetic and where the steps land is a bigger subject than this page should carry; our breakdown of what Weglot actually costs to scale works through it properly. The point to hold here is structural: on a word-times-language model, a growing catalogue in many markets is the expensive case, and that is precisely the case an ambitious store is trying to become.

Who runs it after launch?

You do. This is not a criticism of Weglot; it is what a self-serve tool is. Somebody on your team owns the glossary, reviews strings, checks that new products came through, decides whether the machine output for the new collection sounds right, and notices when a page is half-translated. At two languages and a stable catalogue that is a light load. At six languages and weekly drops it is a standing job that nobody was hired to do.

The alternative model moves that work rather than the tooling: you add a product on your source store and it is live in every language without anyone touching it, with quality handled by AI translation refined by models specialised per language and reviewed by human proofreaders. Whether that is worth it depends entirely on how much your catalogue moves. For a store that publishes twice a year, it is not. For one that publishes weekly in six languages, the operating cost is usually larger than the licence cost and it never appears on the invoice.

For scale on what a properly running translated store is worth: in live 50/50 A/B tests across more than 40 merchants and 50 site and country combinations, translated stores lifted conversion by an average of 40% at launch, with individual results ranging from 15% to 100%. That is a launch measurement against an untranslated experience in the same market rather than a permanent multiplier, and the width of the range is the honest part of it.

When is Weglot the right choice?

Weglot is the right choice when you want indexable multilingual pages quickly, across content Shopify's own tool cannot reach, and you have in-house bandwidth to own quality. A small team with modest language ambitions, a contained catalogue and someone who can read the target languages is well served by it, and would be paying for something they do not need in a managed model.

It is the wrong choice when the language count and the rate of change together create more operating work than your team can absorb, or when brand voice in each market is a commercial requirement rather than a preference. At that point you are not choosing a translation tool, you are choosing who does the work. The guide to ecommerce translation sets the four routes side by side, and if the answer is that the work should leave your team, that is what managed ecommerce localisation is for.

Frequently asked questions