{"id":8191,"date":"2026-07-10T09:00:00","date_gmt":"2026-07-10T07:00:00","guid":{"rendered":"https:\/\/inspace.io\/?post_type=insight&p=8191"},"modified":"2026-07-24T15:21:07","modified_gmt":"2026-07-24T13:21:07","slug":"everything-shopify-store-owners-get-wrong-with-translate-adapt-en-ie","status":"publish","type":"insight","link":"https:\/\/inspace.io\/en-ie\/insights\/everything-shopify-store-owners-get-wrong-with-translate-adapt-en-ie","title":{"rendered":"Everything Shopify store owners get wrong with Translate & Adapt (and the one important thing they don’t)"},"content":{"rendered":"

Let’s start with the one thing Translate & Adapt genuinely gets right, because it’s the reason to use it at all. It serves multiple languages from a single domain<\/strong>. No fragmented .be<\/em>, .nl<\/em> and .de<\/em> TLDs each fighting for their own authority, no duplicate stores to keep in sync. One domain, subfolders per market, all the link equity pooling in one place.<\/p>\n

Shopify sets the rules, you play inside them<\/h2>\n

That is the correct architecture for the overwhelming majority of stores, and Shopify makes it the default. The catch is that Shopify also decides how<\/em> that architecture behaves, and you only get to play inside those rules. Most of the problems I’m called in to fix start when someone assumes installing the app was the same as finishing the job.<\/p>\n

The failures I actually see<\/h2>\n

When a multilingual Shopify store underperforms, it’s almost never the engine. It’s the configuration sitting on top of it. Three issues account for nearly everything:<\/p>\n

Untranslated URL handles.<\/strong> The visible copy is translated, but the URL slug is still English, or worse, still a random Shopify handle. To a search engine the page reads as half-localised, and the market it’s meant to serve never fully trusts it.<\/p>\n

Too many language variants.<\/strong> This is the big one, and it deserves its own section below. Stores add every plausible locale “to be safe”, and quietly cannibalise themselves.<\/p>\n

Broken hreflang pointers.<\/strong> Variants reference each other incorrectly, or point at pages that no longer exist. Google can’t build a clean cluster, so it picks a winner for you, and it rarely picks the one you wanted.<\/p>\n

Fixing the handles: it’s in there, but it wasn’t always<\/h2>\n

Here’s the one thing most people don’t know: handle translation exists<\/em> in Translate & Adapt. You can localise the slug per market. The reason so many stores never do it is timing, not capability.<\/p>\n

Stores set up before early 2023 predate the feature being obvious, so the habit never formed. The English handle became the permanent handle, and nobody went back. If that’s you, the fix isn’t manual page-by-page editing. Export your content, translate the handles in bulk, and re-import with a CSV<\/strong>. It’s the difference between an afternoon and a quarter.<\/p>\n

\n

The tool isn’t the thing that breaks. The assumption that installing it finished the work is.<\/p>\n<\/blockquote>\n

The language trap, specifically<\/h2>\n

Now the expensive mistake. Faced with a Dutch-speaking audience across the Netherlands, Belgium and the wider EU, the instinct is to create a variant for each: nl<\/em>, nl-BE<\/em>, nl-EU<\/em>. It feels thorough. It’s actually three near-identical pages competing for the same queries, splitting signals and confusing Google about which one to rank.<\/p>\n

Add a variant only when it earns its place with genuinely differentiated content, pricing or shipping. Otherwise you’re not covering more ground, you’re diluting the ground you already own.<\/p>\n\n\n\n\n\n\n\n
Variant<\/th>\nDifferentiated?<\/th>\nVerdict<\/th>\n<\/tr>\n<\/thead>\n
nl<\/td>\nCore market, full catalogue<\/td>\nKeep<\/td>\n<\/tr>\n
nl-BE<\/td>\nOwn pricing, shipping, BTW<\/td>\nKeep, if real<\/td>\n<\/tr>\n
nl-EU<\/td>\nDuplicate of nl<\/td>\nDrop<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n

One good variant beats three anxious ones. Every time.<\/p>\n<\/blockquote>\n

Where the app itself hits a ceiling<\/h2>\n

To be fair to the tool, there’s a point where the problem stops being your configuration and starts being the app’s limits. Translate & Adapt handles core content well, but it thins out around the edges: third-party app content<\/strong>, collection filters<\/strong>, and image metadata<\/strong> often slip through untranslated.<\/p>\n

If you’re hitting those walls, that’s not failure. It usually means you’ve outgrown a plug-in and into a real localisation workflow, with proper translation memory and coverage of everything the app can’t reach.<\/p>\n

So, keep it or leave it?<\/h2>\n

Keep it, for almost everyone. For a store that wants many languages on one domain without running a localisation stack, Translate & Adapt is the right default and does the hard part well. Just treat installing it as the start<\/em> of the work: translate your handles, be ruthless about variants, and check your hreflang cluster is actually clean.<\/p>\n

Leave it only when you’ve genuinely outgrown it, when third-party content, filters and metadata matter enough that the ceiling is costing you real revenue. Reaching that point isn’t a failure of the tool. It’s a sign you’re winning.<\/p>\n","protected":false},"excerpt":{"rendered":"

The app’s real strength is one domain, many languages. Most broken multilingual stores don’t fail because of the tool. They fail on the assumptions it quietly lets you keep.<\/p>\n","protected":false},"featured_media":8170,"template":"","insight_category":[545,546],"class_list":["post-8191","insight","type-insight","status-publish","has-post-thumbnail","hentry","insight_category-ecommerce","insight_category-multilingual"],"meta_all":{"rank_math_internal_links_processed":"1","insight_dek":"The app's real strength is one domain, many languages. Most broken multilingual stores don't fail because of the tool. They fail on the assumptions it quietly lets you keep.","insight_tldr":"The app does one thing brilliantly: many languages on a single domain, instead of fragmented country TLDs.\nMost failures are configuration, not the tool: untranslated handles, too many language variants, broken hreflang.\nHandle translation exists, but stores set up before 2023 never noticed it. Fix it in bulk with a CSV import.\nOutgrowing the app is a good sign. Know where its ceiling is before you hit it.","insight_read_min":"8","insight_author_name":"Simon Verwaal","insight_author_role":"Strategist \u00b7 InSpace","insight_author_bio":"Simon untangles multilingual and international SEO for InSpace's ecommerce clients, and has fixed more broken hreflang clusters than he'd care to count.","insight_author_photo":""},"meta_all_flat":{"rank_math_internal_links_processed":"1","insight_dek":"The app's real strength is one domain, many languages. Most broken multilingual stores don't fail because of the tool. They fail on the assumptions it quietly lets you keep.","insight_tldr":"The app does one thing brilliantly: many languages on a single domain, instead of fragmented country TLDs.\nMost failures are configuration, not the tool: untranslated handles, too many language variants, broken hreflang.\nHandle translation exists, but stores set up before 2023 never noticed it. Fix it in bulk with a CSV import.\nOutgrowing the app is a good sign. Know where its ceiling is before you hit it.","insight_read_min":"8","insight_author_name":"Simon Verwaal","insight_author_role":"Strategist \u00b7 InSpace","insight_author_bio":"Simon untangles multilingual and international SEO for InSpace's ecommerce clients, and has fixed more broken hreflang clusters than he'd care to count.","insight_author_photo":false},"acf":[],"_links":{"self":[{"href":"https:\/\/inspace.io\/en-ie\/wp-json\/wp\/v2\/insight\/8191","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/inspace.io\/en-ie\/wp-json\/wp\/v2\/insight"}],"about":[{"href":"https:\/\/inspace.io\/en-ie\/wp-json\/wp\/v2\/types\/insight"}],"version-history":[{"count":1,"href":"https:\/\/inspace.io\/en-ie\/wp-json\/wp\/v2\/insight\/8191\/revisions"}],"predecessor-version":[{"id":8192,"href":"https:\/\/inspace.io\/en-ie\/wp-json\/wp\/v2\/insight\/8191\/revisions\/8192"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/inspace.io\/en-ie\/wp-json\/wp\/v2\/media\/8170"}],"wp:attachment":[{"href":"https:\/\/inspace.io\/en-ie\/wp-json\/wp\/v2\/media?parent=8191"}],"wp:term":[{"taxonomy":"insight_category","embeddable":true,"href":"https:\/\/inspace.io\/en-ie\/wp-json\/wp\/v2\/insight_category?post=8191"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}