Shopify multilingual work is not finished after translating a product description. A cross-border store must also handle market URLs, currency, price, tax, image text, specifications, support, returns, legal pages, canonicals, and hreflang. Translation tools improve throughput, but product facts and policy copy need human review; markets may need different products, prices, or delivery promises.
Localisation content model
Maintain language, product name, specs, compatibility, units, price, tax, delivery, returns, and support fields per market. Assign source, update date, translator, and approver to each field. After machine translation review terms, negation, units, sensitive claims, and brand names, especially for hardware, energy, health, and safety products.
| Content | Localisation check | Evidence |
|---|---|---|
| Product | Specs, units, variants | Product page and glossary |
| Transaction | Currency, tax, payment | Target-address checkout |
| Fulfilment | Delivery, returns, warranty | Policy and support |
| SEO | URL, title, canonical, hreflang | Crawl and source |
Market and technical QA
Test language switch, default, fallback, links, forms, search, cart, and checkout per market. Check that a translated page is not canonically pointed at another language, that schema uses the right language, and that text in images is not missed. Do not let automatic translation overwrite approved legal or price copy.
Quality and update workflow
Keep a glossary, do-not-translate list, review queue, and update reminders. Product, promotion, stock, policy, and support changes should map to a market version. Use customer questions and return reasons to review quality; a machine-translation completion rate is not localisation quality.
SEO, GEO, and compliance
Each indexable language page needs its own title, description, visible copy, internal links, and market FAQ. Hreflang communicates a language or regional relationship; it does not guarantee indexing. Add update dates and fact sources so search and AI systems can cite the product and policy accurately.
Avoid false metrics
Do not promise every language, a fixed conversion uplift, or guaranteed indexing. Choose languages using market value, fulfilment, support, and compliance capacity; low-quality automation can create duplicate or thin content.
FAQ
Does Shopify automatically translate every page well?
No. Capability depends on current settings and tools; quality, policy, and product facts still need review.
Should multilingual pages share one canonical?
Normally each language URL uses a self-referencing canonical and hreflang expresses the relationship, subject to the site implementation.
Do price and units need localisation?
Yes. Verify currency, tax, units, and rounding per market rather than replacing text only.
How does multilingual content support GEO?
Answer local questions directly in each language and preserve entities, specs, sources, dates, and market constraints instead of generic machine text.