Translate your key pages into language-specific URLs, wire up hreflang properly, and sort your legal text before you launch. That’s the short version. The longer version: get your canonical tags right, build a 30-day price history log before you run any discount, and localise your terms and checkout copy so you’re not caught out by EU consumer rules.
Choosing a URL structure and getting hreflang right
Your URL structure sets the ceiling for how well each language version can rank. Subfolders (yourshop.com/de/) borrow authority from your main domain and are the easiest to manage. Subdomains (de.yourshop.com) separate things cleanly but often need separate SEO effort to build authority. Country-code domains (yourshop.de) send the strongest local signal but cost the most to run and maintain.
Hreflang doesn’t tell Google what language a page is written in. It tells Google which other language or regional versions of that page exist, using BCP-47 codes, and it needs an x-default version as a fallback for everyone else. You can implement it through HTML link tags, HTTP headers or an XML sitemap, but mixing methods makes maintenance a nightmare, so pick one and stick with it.
- Use subfolders unless you have a strong reason not to: lower setup cost, shared domain authority.
- Add hreflang tags to every language variant, pointing to every other variant, including itself.
- Set canonical tags per language page, never collapsing everything back to your source language.
- Check Search Console’s International Targeting report and a hreflang validator before and after launch.
Pro Tip: Run a hreflang audit monthly for the first quarter after launch. Small sitemap errors creep in fast and silently tank your indexing.
What to translate first for SEO and conversions
Not everything needs translating on day one. Here’s the order that protects both your rankings and your sales:
- Product titles, meta titles and meta descriptions, since these are what shows up in search results.
- Category pages and your highest-traffic landing pages, where most organic sessions land.
- Checkout labels, shipping information and payment options, because confusion here kills conversions fast.
- Legal pages: terms and conditions, returns policy and cookie notices, localised to the target market before you accept orders from it.
- Structured data, facet labels and filter names, which carry search intent even when a shopper never reads them directly.
Archive blog posts and older campaign pages can wait. They’re low-impact to start with, but once your core catalogue is live, revisiting them can pick up long-tail traffic you’d otherwise leave on the table. Our guide on translating product descriptions covers why this particular content earns priority treatment.
Technical SEO checklist: sitemaps, canonicals and indexing
Hand this list to your developer or use it to check whatever platform you’re on:
- Build a per-language sitemap, or clearly separated language sections within one index sitemap.
- Submit each language or region sitemap to Search Console individually.
- Canonicalise each language page to itself, not back to your original-language version.
- Noindex draft or unfinished translations; only expose languages you’ve actually launched.
- Keep structured data (price, currency, availability) in sync with what’s visibly on the page in each language.
- Watch for schema and visible content disagreeing. That mismatch confuses search engines and can trigger manual review.
Shopify Markets automates a good chunk of this, generating hreflang tags and handling canonical logic for you, though your URL structure choice still shapes how much authority and complexity you’re dealing with.
Pro Tip: Pull your server logs occasionally. If Googlebot isn’t crawling a language section at all, no amount of on-page fixing will help.
Pricing, currencies and legal compliance before you launch a language
Here’s where a lot of e-shops trip up, and it’s not really an SEO problem, it’s a legal one that can tank your credibility fast. Slovak and EU consumer rules now require that the reference price shown next to any discount must be the lowest price the product was sold at during the previous 30 days. Miss that, and you’re not just risking a fine, you’re risking a watchdog complaint.
Enforcement checks in 2026 found that roughly 30% of examined traders were breaching discount transparency rules. That’s not a small slice, so treat your price history logging as non-negotiable, not a nice-to-have.
- Log daily prices automatically so you can always show a lawful “was” price.
- Display local currency clearly, with VAT and duties shown where the market expects it.
- Check OSS VAT thresholds if you’re selling cross-border within the EU.
- If paid placement affects product order or ranking on your site, disclose the criteria to shoppers.
Cross-border selling within the EU means complying with the target country’s consumer law and Omnibus transparency rules, not just your home market’s. Our guide to content localisation for e-commerce breaks down what that looks like in practice.
Building a QA workflow: glossaries, TM and human review
Scaling translation without losing quality comes down to process, not heroics. Start with a glossary, locking product names, facet labels and brand terms so three translators don’t invent three different phrases for the same thing. Translation memory then reuses approved phrasing across thousands of product pages, cutting cost and keeping tone consistent.
An AI first draft plus human post-edit works well for volume, but product titles, meta descriptions and anything legal need native linguistic review before they go live. No exceptions there.
- Lock key terms in a glossary before translation starts, not after.
- Use translation memory to keep metadata consistent across the catalogue.
- Run native QA specifically on titles, legal text and checkout copy.
- Check title length, keyword placement and template consistency before publishing.
Pro Tip: Build your acceptance checklist once, then reuse it for every language launch. Consistency here saves far more time than it costs to set up.
Picking your languages and rolling out in stages
Don’t translate your whole catalogue on day one. Pick languages based on traffic potential, proximity, margin and how complex logistics get in that market.
- Pilot with a small, high-margin product set in your top one or two target languages.
- Measure organic traffic, conversion rate and any legal complaints before scaling further.
- Track indexed pages and returns alongside sales, since a spike in complaints often signals a translation or legal gap.
- Localise legal documents and customer support for your phase-one markets from day one, not as an afterthought.
Platform notes: Shopify and other CMS quirks
Shopify’s Translate & Adapt app and Shopify Markets handle a fair amount automatically, including hreflang generation, but your URL structure choice still affects long-term authority. Other CMS platforms vary wildly: facets and filters often create duplicate content, and plugin-generated hreflang is sometimes incomplete or badly formatted.
- A translation app plus a solid translation memory is usually enough for a small catalogue.
- Large catalogues, custom sitemaps or complicated pricing rules usually need developer involvement.
- Always check how your platform handles URL parameters before assuming hreflang is working correctly.
What usually goes wrong (and what we’d tell a friend)
Pilot first. Full-catalogue launches without testing are how small translation gaps turn into big SEO messes. Don’t skip legal text localisation or native QA on titles, that’s where most of the risk actually lives.
Starter checklist: pick your URL structure, build a glossary, translate your top 100 product pages, and start logging 30-day prices today.
— glocco®
How glocco® can help with your e-shop translation and SEO
We handle exactly this kind of project daily: glossaries, translation memory, AI-assisted drafts with human post-edit through HumanAI, and native legal review through HumanLegal for your terms and checkout pages. A typical engagement starts small, a pilot catalogue and a couple of markets, then scales once the numbers prove out.
Fancy a second opinion on your rollout plan before you commit a developer’s time to it? Get in touch and we’ll talk through what a pilot could look like for your store.
This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.
FAQ
Should I use subfolders, subdomains or a country domain?
Subfolders are the easiest route for most e-shops because they share your existing domain authority and need less setup work. Subdomains or country-code domains can send stronger local signals but take more effort to rank independently, so they suit larger, well-resourced rollouts better.
What is hreflang and do I really need it?
Hreflang tells search engines which language or regional versions of a page exist, so the right version shows up for the right searcher. Google explains that hreflang doesn’t detect page language; it needs explicit tags, headers or sitemap entries, and an x-default fallback for everyone else.
How do I handle discounts legally across EU markets?
Slovak and EU rules require that any discount reference price be the lowest price charged in the previous 30 days. Log your prices daily so you can always demonstrate the correct reference figure if challenged.
What should I translate first on a limited budget?
Start with product titles, meta descriptions, category pages and checkout copy, since these affect both rankings and conversions directly. Legal pages come next, before you actively target a new market, and archive content can wait until your core catalogue is stable.
Can an app like Shopify’s Translate & Adapt handle everything?
For a small catalogue, a translation app paired with a solid translation memory is often sufficient, since Shopify Markets automates hreflang and canonical handling. Larger catalogues, custom sitemaps or complex pricing rules usually need developer work on top of the app.
Sources
- Google Search Central — localized versions and hreflang
- Slovakia preparing new consumer protection act — what you should know
- Cezhraničný predaj v EÚ – legal overview and practical steps
- Shopify — International SEO for markets
