If you are researching Weglot SEO issues on Shopify, here is the honest short answer: Weglot is not bad at SEO. It actively markets multilingual SEO — hreflang tags, translated meta descriptions, and localized sitemaps — as a core feature, and those features work. The real considerations are structural: how Weglot delivers translated pages, where those URLs live, and what happens to your rankings if you ever leave.
This guide walks through how Weglot’s delivery model works, the concerns merchants genuinely raise, what Weglot does well, practical checks to keep your international pages crawlable, and how a Shopify-native approach keeps translated URLs on your own domain.
How Weglot delivers translated pages
Weglot uses a proxy/subdomain layer. Instead of writing translations directly into your Shopify store’s database, Weglot intercepts your pages, translates the visible content, and serves the localized version through its own infrastructure on a language-specific URL — typically a subdomain (fr.yourstore.com) or a subdirectory (yourstore.com/fr/) routed through Weglot.
This is why setup is fast and works across many platforms: Weglot sits in front of your site rather than rebuilding it. But it also means your translated pages are, technically, delivered by Weglot’s layer rather than served natively by Shopify. That single fact is the root of nearly every SEO question merchants ask.
It helps to picture the two models side by side. In a proxy model, a request for the French page travels through the translation service, which fetches your source page, translates it, and returns the localized version. In a native model, Shopify stores the French translation itself and serves it directly, the same way it serves your default-language page. Both can rank; the difference is who owns the URL and the tags at the end of that request.
Proxy model: Visitor → Weglot layer → your Shopify page → translated response
Native model: Visitor → Shopify (serves stored French translation directly)The SEO concerns merchants actually raise
None of these are “Weglot is broken.” They are trade-offs worth understanding before you commit.
1. Subdomain vs subdirectory
Search engines can index either a subdomain (fr.yourstore.com) or a subdirectory (yourstore.com/fr/). Google has stated both are valid for international sites. In practice, many SEOs prefer subdirectories because they inherit the main domain’s authority more directly, while subdomains are sometimes treated as more separate properties that build authority on their own. Weglot supports both depending on your setup, so the concern is less “Weglot forces a bad structure” and more “make sure the structure you pick matches your strategy.”
The practical advice: pick one structure at the start and never mix. Migrating a live catalog from subdomains to subdirectories later means redirects, re-crawling, and a temporary ranking dip while Google re-consolidates signals. Shopify’s own international setup leans toward subfolders under a single domain, which is one reason a native approach removes this decision entirely.
2. hreflang setup
hreflang tells Google which language and region each page targets. Weglot adds these tags automatically, which is genuinely helpful. Problems, when they happen, come from misconfiguration — missing return tags, incorrect region codes (en-US vs en-GB), or conflicts with tags Shopify or another app also emits. Google’s own guidance on telling Google about localized versions of a page is the reference to validate against.
3. Canonical handling
Each language version should carry a self-referencing canonical so Google knows the French page is the canonical French page, not a duplicate of the English one. Proxy-served setups can occasionally emit canonicals that point back to the source language, which would tell Google to ignore your translated page entirely. This is worth checking manually on a few live translated URLs.
Canonicals and hreflang work together, and getting them consistent is what actually protects translated pages. A correct setup has each language page canonicalize to itself and reference every other language version via hreflang, with matching return tags in both directions. When the two signals disagree — say, the canonical points to English but hreflang says the page is French — Google has to guess, and it often resolves the conflict by dropping the translated page from the index. Any translation app can drift here after a theme change or a Shopify update, so treat this as a recurring check rather than a one-time setup task.
4. Page speed of the translation layer
Because content passes through Weglot’s layer before reaching the visitor, there is an added hop. Weglot invests in caching and CDNs to minimize this, and for most stores the impact is small. Still, Core Web Vitals are a ranking factor, so if speed matters to your market, measure your translated pages with real-world tools rather than assuming parity with your source pages.
5. Dependency and lock-in if you leave
This is the concern with the longest tail. Because Weglot serves your translated URLs, those URLs — and their indexed SEO equity — belong to the Weglot layer. Turn the app off without a migration plan and the translated pages can disappear, taking their rankings with them. This is not unique to Weglot; it is inherent to any proxy translation model. It is simply the item most merchants underestimate.
Check before you commit
Before scaling up, spot-check three live translated URLs: view source and confirm each has a self-referencing canonical, correct hreflang return tags, and a translated meta title. Five minutes now saves a re-indexing headache later.
What Weglot does well for SEO
A fair guide has to say this clearly: Weglot’s SEO feature set is a selling point, not a weakness.
- Automatic hreflang tags across all language versions, so you rarely hand-code them.
- Translated metadata — meta titles and descriptions get localized, not just body copy, which matters for click-through in local search results.
- Localized sitemaps so search engines can discover your translated pages.
- Indexable, server-rendered translated content rather than client-side-only swaps that search engines struggle to read.
Weglot holds a strong 4.5/5 rating from 798 reviews on the Shopify App Store (as of July 2026), and a lot of that goodwill comes from setup speed plus these SEO defaults working out of the box. If your priority is getting multilingual pages indexed quickly across multiple platforms, Weglot earns its reputation.
Practical fixes and checks
Whether you stay on Weglot or evaluate alternatives, run this checklist:
- Validate hreflang with Google Search Console’s international targeting report and confirm every language pair has matching return tags.
- Confirm self-referencing canonicals on a sample of translated URLs (view source, check the
<link rel="canonical">). - Submit and monitor sitemaps for each language and watch indexation counts in Search Console.
- Measure Core Web Vitals on translated pages, not just your default-language pages.
- Decide subdomain vs subdirectory deliberately and keep it consistent — do not mix mid-catalog.
- Document your exit plan before you scale, so leaving never means losing indexed pages.
The Shopify-native alternative: keep URLs on your own domain
Here is where the delivery model matters most. A Shopify-native translation app takes a different route: instead of proxying, it writes translations into Shopify’s own translation system. The result is that your translated URLs live directly on your domain (yourstore.com/fr/), served by Shopify itself, with native hreflang emitted by the platform — no third-party layer in front of your storefront.
LocaleFlow works this way. It writes into Shopify’s native translations, so:
- Translated URLs are served by Shopify on your own domain, not by a proxy.
- hreflang is native to the platform, reducing the misconfiguration surface.
- You own the SEO equity. Change or remove the app and your translated pages and their indexed signals stay put, because they were never hosted elsewhere.
- Pricing is a flat $150/month with unlimited words and languages, AI translation included, auto-sync, and full metafield and metaobject support.
This is not a claim that Weglot loses you rankings — it does not, when configured correctly. It is a structural difference: native delivery keeps your international URLs and their SEO signals under your control by default, which removes the lock-in concern entirely.
The business case for getting any of this right is real. CSA Research found that 76% of shoppers prefer buying in their native language and 40% won’t buy at all without it. Translated pages that rank in local search are how those shoppers find you in the first place.
See it on your own store
LocaleFlow’s demo translates your actual store content into Shopify’s native system, so you can see real translated URLs on your own domain before committing.
Conclusion
Weglot SEO issues, examined fairly, are less about quality and more about architecture. Weglot ships strong multilingual SEO features — hreflang, translated meta, sitemaps — and they work. The genuine considerations are the proxy delivery model, deliberate subdomain-vs-subdirectory choices, careful canonical and hreflang validation, translation-layer speed, and above all the lock-in that comes with any proxy-served setup.
If Weglot’s speed and cross-platform reach fit your needs, configure it carefully with the checklist above and you will be fine. If you are Shopify-focused and want your translated URLs and SEO signals to live natively on your own domain — with flat, predictable pricing and no proxy dependency — a native approach is worth a serious look.
Install LocaleFlow from the Shopify App Store and start translating today. Your translated pages live on your domain, with native hreflang, from day one: Start translating.
