GTranslate SEO comes down to one question: are your translated pages actually indexable, or are they just painted on in the browser? The free GTranslate widget translates client-side with JavaScript, which means Google usually indexes only your original-language pages and never sees the translated versions as separate, rankable URLs. That single distinction decides whether your Shopify store earns international organic traffic or just looks translated to visitors who are already there.
This guide breaks down how GTranslate’s tiers affect indexing, where hreflang goes wrong, the SEO risk of hosting translations on a proxy, and a practical checklist you can run before you commit.
Does GTranslate help or hurt Shopify SEO?
The free GTranslate widget helps usability but does not, on its own, build multilingual SEO, because client-side JavaScript translation does not create separate indexable URLs for search engines. It can hurt if you assume it does, launch languages, and then wonder why none of them rank.
Here is the mechanism. The free tier ($0, machine/widget translation, as of July 2026 per the GTranslate site) swaps text in the browser after the page loads. A shopper sees Spanish; Googlebot fetches the page and, in most crawl passes, sees your source language at a single URL. Google can render JavaScript, but it does so on a separate, slower rendering queue, and content injected purely client-side is not treated the same as server-delivered HTML at a distinct URL. Google Search Central is explicit that JavaScript content can be delayed or missed in rendering, which is exactly the fragility you do not want under your entire international catalog. (See Google’s guidance on JavaScript SEO basics.)
So the free widget is a translation experience, not a translation index. For real multilingual search visibility you need one page per language at its own crawlable URL, and that is where GTranslate’s paid structure comes in.
To be clear about what the free tier does well: it is genuinely useful for reducing bounce among visitors who already found you and simply want to read in their own language. That improves engagement metrics and can indirectly support SEO. But indirect signals are not a substitute for the direct one that matters most, which is having a distinct, indexable page that ranks for native-language queries in the first place. If the goal is being found by non-English searchers rather than understood by ones who already arrived, the free widget is the wrong tool, and no amount of on-page tuning fixes an architecture that never produces crawlable translated URLs.
When indexable URLs require GTranslate’s paid tiers
Indexable translated URLs on GTranslate require the paid neural tiers, and specifically the Business plan for URL translation, so the SEO-relevant capability is not part of the free product. Here is the tier map, as of July 2026 (per the GTranslate site):
| Plan | Price | What you get for SEO |
|---|---|---|
| Free | $0 | Client-side widget only; no separate indexable URLs |
| Bilingual Startup | $12/mo | Neural translation, limited scope |
| Startup | $25/mo | Neural translation, all languages |
| Business | $35/mo | Adds URL translation / indexable translated URLs |
| Enterprise | $50/mo | Neural delivery at scale |
The takeaway: the plan that unlocks the SEO feature you actually care about (translated, crawlable URLs) is the Business tier at $35/mo, not the free widget most merchants try first. And the neural tiers deliver translations through a hosted layer GTranslate calls a Translation Delivery Network, which brings us to the ownership question.
Free widget ≠ free SEO
If you launched GTranslate on the free plan expecting international traffic, check Google Search Console coverage. If only your source-language URLs are indexed, the widget is doing its job for visitors but nothing for search.
The proxy risk: who owns your translated URLs?
GTranslate’s neural tiers serve translations through a hosted Translation Delivery Network, which means your indexable translated URLs are delivered by a proxy layer rather than living natively in your own store, and that has direct SEO consequences. Proxy and subdomain hosting can absolutely rank; the issue is ownership and portability.
When translated pages live on a delivery network or a vendor subdomain:
- You inherit a dependency. Your ranking translated URLs exist because the proxy renders them. Change vendors, and those URLs and their accumulated authority can vanish.
- Migration is a rankings event. Moving off a proxy means redirecting or rebuilding every indexed language URL, a project that risks the international traffic you spent months earning.
- hreflang correctness sits partly outside your control. How the proxy emits alternate-language tags determines whether Google connects your versions correctly.
Contrast that with Shopify-native translation, where the translated content is written into Shopify itself and served from your own domain. Your language URLs are yours; if you switch translation apps, the pages and their indexing stay put. We break down the proxy-versus-native tradeoff further in our Weglot vs LocaleFlow comparison, since the same architecture question applies to any proxy-based translation tool.
None of this means proxy delivery cannot work in the short term. Plenty of stores rank on subdomain or delivery-network setups today. The point is that you are borrowing indexing infrastructure rather than owning it, and the cost of that arrangement is invisible until the day you want to leave. At that moment the difference between “my translated pages are Shopify URLs I control” and “my translated pages exist because a vendor renders them” becomes the difference between a clean app swap and a full international-SEO migration. Weighing that portability question before you launch languages is far cheaper than discovering it after your translated pages have accumulated a year of rankings.
Getting hreflang right (or watching rankings scatter)
hreflang is the set of tags that tell Google which language and region each page version serves, and getting it wrong is one of the fastest ways to sabotage multilingual SEO regardless of which app you use. Google uses hreflang to serve the right language to the right searcher and to avoid treating your language versions as duplicate content.
Common hreflang failures that quietly cost rankings:
- Missing self-reference. Each page must list itself in its own hreflang set. Omit it and Google may ignore the whole cluster.
- Non-return tags. If page A points to B but B does not point back to A, Google discards the pairing.
- Wrong or invented codes.
en-UKis not valid (it isen-GB); bad codes are dropped. - Pointing at non-indexable URLs. hreflang that references JavaScript-only or noindex pages sends Google nowhere useful.
That last point loops back to the free-widget problem: if your translations are not indexable URLs, there is nothing valid to declare in hreflang. Google’s own hreflang documentation is the authoritative reference here, and it is worth reading before you launch any multilingual setup. For the full playbook, see our multilingual SEO guide.
A practical GTranslate SEO checklist for merchants
Before you rely on any translation app for search traffic, verify these seven things, because most GTranslate SEO disappointment comes from skipping the indexing check.
- Confirm indexable URLs exist. View source (not the rendered DOM) on a translated page. If the translated text is not in the served HTML at a unique URL, it is not reliably indexable.
- Check Google Search Console coverage. Are translated URLs being indexed, or only your source language? This is the single most important signal.
- Validate hreflang. Every language version self-references and points to all others, with correct language-region codes.
- Verify the plan tier. On GTranslate, translated URLs need the Business plan ($35/mo, as of July 2026); the free widget will not deliver them.
- Map the hosting model. Are translated pages on your own domain, a subdomain, or a proxy delivery network? Note the migration risk.
- Test crawlability. Use Search Console’s URL Inspection tool to confirm Google renders and would index each translated URL.
- Plan your exit. If you left the app tomorrow, would your translated URLs survive? If the answer is no, factor that into the decision.
If most of these feel like work you would rather not repeat every time you add a language, that is the argument for native translation.
How LocaleFlow keeps SEO ownership on your side
LocaleFlow writes translations directly into Shopify’s native multilingual system, so your translated URLs live on your own domain, Shopify emits native hreflang automatically, and there is no proxy layer between your store and search engines. That removes the indexing guesswork and the vendor-dependency risk in one move.
Concretely, LocaleFlow ($150/mo flat, as of July 2026) includes AI translation, unlimited languages and words, auto-sync when content changes, and full metafield and metaobject support, all served through Shopify’s own storefront rather than a delivery network. Because the translations are native, your language pages are real, crawlable Shopify URLs from day one, and they stay indexed with you even if you change apps later.
The business case behind all of this is unchanged: CSA Research found that 76% of shoppers prefer buying in their native language and 40% will not buy at all without it. Multilingual SEO is how those shoppers find you in the first place, so the indexability of your translated pages is not a technical footnote, it is the top of your international funnel. If you want to weigh options side by side, our comparison hub lays out the tradeoffs across the major Shopify translation apps.
Conclusion
GTranslate’s free widget is a fine way to let existing visitors read your store in another language, but it does not build multilingual SEO on its own, because client-side JavaScript translations are not reliably indexed as separate URLs. Indexable translated URLs require the paid Business tier, and those pages are delivered through a hosted proxy layer you do not fully own. Add hreflang complexity and migration risk, and the SEO math starts favoring native translation.
LocaleFlow keeps your translated URLs on your own domain with native hreflang and no proxy, so your international rankings belong to you.
Install LocaleFlow from the Shopify App Store and start translating today.
