Skip to content
Web Development19 min read

Multi-Language Ecommerce Website: Architecture and SEO Considerations

How to build a multi-language store: localized URLs, hreflang, translated metadata and product data, workflows, navigation, search, structured data and QA.

01

Quick answer

A multi-language ecommerce website needs one URL per language version, hreflang connecting the versions, self-referencing canonicals, and fully translated content including metadata, navigation, filters, product data, structured data text, checkout and emails. Manage translations with structured fields, glossaries and a review workflow; give each language its own search configuration; suggest a language without forcing redirects; and QA with native speakers and crawls of each version. Platforms such as Shopify handle much of the URL and hreflang work once languages are assigned to markets.

02

Languages vs Markets

A language version is not the same as a market. A market sets currency, prices and delivery; a language sets text. Some markets need several languages (Canada, Switzerland, Belgium); some languages serve several markets (English, Spanish). Decide both dimensions before designing URLs. For the full international architecture, see ecommerce internationalization.

This guide covers the four areas to get right: URLs, content, discovery and QA.

03

URL Structure for Languages

Google recommends using different URLs for each language version rather than cookies or browser settings, and compares country domains, subdomains and subdirectories as options; it doesn't recommend URL parameters. For most stores, language subdirectories are the simplest to run. Keep the structure consistent so every page has an equivalent in each language.

StructureExampleNotes
Subdirectoryexample.com/fr/Simple, shares domain authority
Subdomainfr.example.comSeparate hosting possible
Country domainexample.frStrong country signal; country-specific, not language-specific
Parameterexample.com?lang=frNot recommended by Google
04

Hreflang and Canonicals

Hreflang annotations tell search engines which URLs are language or regional alternates of each other. Each version lists itself and all alternates, the annotations must be reciprocal, language codes follow ISO 639-1 with optional ISO 3166-1 region codes (for example fr, fr-CA), and x-default can point to a language selector or default version. Annotations can be placed in HTML head, HTTP headers or sitemaps. Each version should normally have a self-referencing canonical.

Hreflang in the HTML head of the English product page
<link rel="canonical" href="https://example.com/products/linen-shirt" />
<link rel="alternate" hreflang="en" href="https://example.com/products/linen-shirt" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/products/chemise-en-lin" />
<link rel="alternate" hreflang="de" href="https://example.com/de/products/leinenhemd" />
<link rel="alternate" hreflang="x-default" href="https://example.com/products/linen-shirt" />
05

What to Translate

ContentWhy it matters
Product titles, descriptions, attributesUnderstanding and search
Collections, navigation, filters and valuesBrowsing in the shopper's language
Meta titles and descriptionsSearch result appearance
Image alt textAccessibility and image search
Structured data text fieldsConsistent with visible content
Checkout, account, emails and notificationsTrust at the moment of purchase
Legal and policy pagesRights and obligations, reviewed per market
Error and empty-state messagesRecovery when things go wrong
06

Content Management and Workflow

Store translatable content in structured fields with per-language values, not duplicated pages. Use a translation management workflow: extract new or changed strings, translate (machine translation plus human review for important content, professional translation for checkout and legal), review in context, publish, and track status. Maintain glossaries for product terms and brand vocabulary. Decide fallbacks for missing translations and avoid publishing mostly untranslated pages under a translated URL, which gives users a poor experience and can confuse search engines about the page's language.

Launching your store in more languages?

ZSpace Labs builds multi-language storefronts with clean URL structures, hreflang and translation workflows that scale.

Start a Project
07

Provide a language selector that shows language names in their own language (Deutsch, Français), links to the equivalent page rather than the home page, and remembers the choice. Don't use flags for languages; flags represent countries. Suggest a language based on browser settings, but don't force redirects: Google advises against automatically redirecting users between language versions.

08

Search and Filters per Language

Site search must work in each language: language-specific analyzers for stemming and tokenization, synonyms per language, spelling tolerance and zero-result monitoring. Filters and attribute values should be translated from structured data, not free text, so filter logic stays consistent across languages. See ecommerce site search.

09

Structured Data in Each Language

Product and article structured data should match the visible content of each language version: translated names and descriptions, the correct URL for that version, and prices in the currency shown on that URL. Validate a sample of pages in each language. See product structured data.

10

Platform Notes: Shopify

Shopify stores can publish additional languages, assign domains and languages to markets using subfolders, subdomains or top-level domains, and translate content with the Translate & Adapt app (machine and manual translation, CSV import). Shopify's documentation states that hreflang tags are created automatically for configured international domains and subfolders, with self-referencing canonical URLs and sitemaps that include market URLs. See Shopify Markets.

11

QA Checklist

  • Native-speaker review of key templates, checkout and emails
  • Layouts tested with longer translated strings
  • Crawl of each language: hreflang reciprocity, canonicals, status codes
  • No mixed-language pages from fallback gaps
  • Language selector links to equivalent pages
  • Search tested with common queries in each language
  • Structured data matches visible language and currency
  • Sitemaps include every language version
12

Worked Example: Adding French and German

An illustrative scenario: a UK homeware store adds French and German. It uses /fr/ and /de/ subdirectories, translates product titles and descriptions with machine translation plus review for the top 300 products and professional translation for checkout, emails and legal pages, translates filter values from structured attributes, adds per-language search synonyms, and uses automatic hreflang from its platform. A crawl before launch finds pages with untranslated descriptions under /de/; these are held back until translated. After launch, the team monitors indexing and search queries per language.

13

Common Mistakes

  • One URL switching language by cookie
  • Canonicals pointing translations to the default language
  • Hreflang without return links
  • Untranslated metadata, filters or checkout
  • Flags used as language selectors
  • Forced language redirects
  • One search configuration for all languages

Ready to build a multi-language store?

Talk to ZSpace Labs about multi-language development, Shopify languages and markets and localized UX.

Start a Project
14

Conclusion

A multi-language store needs clean URLs per language, correct hreflang and canonicals, complete translations across every surface, language-aware search and a disciplined workflow. Get those right and each language version can perform on its own. For the SEO strategy across countries, see international ecommerce SEO. For Arabic, English and right-to-left builds in the UAE, see multilingual website development in the UAE. For Hindi, Tamil and other Indian languages, see regional-language pages for Indian customers.

FAQ

Common questions.

Give each language version its own URL, for example with a language subdirectory (/fr/), a subdomain or a country domain. Google recommends separate URLs for each language version rather than switching language with cookies on one URL.

Hreflang helps search engines show the right language or regional version. Each version should reference itself and all alternates, with return links, and an x-default for a fallback page where appropriate.

Translated slugs can help users understand URLs in their language; untranslated slugs are simpler to maintain. Either can work if each version has a unique URL and hreflang connects them.

No. Each language version should normally have a self-referencing canonical; pointing translations to another language tells search engines they're duplicates.

Navigation, UI labels, checkout, emails, metadata (titles and descriptions), image alt text, filters and attribute values, structured data text, legal pages, search synonyms and error messages.

Each language needs its own index or analyzer so stemming, synonyms and spelling tolerance work, plus synonyms and zero-result monitoring per language.

Define fallbacks: show the default language for missing fields, flag gaps for translators, and avoid publishing pages that are mostly untranslated under a translated URL.

Google advises against automatically redirecting users between language versions. Suggest the likely language and let visitors choose, remembering their choice.

Yes. Shopify stores can publish multiple languages, assign them to markets with subfolders, subdomains or domains, translate content with apps such as Translate & Adapt, and add hreflang tags automatically for configured versions.

Review translations with native speakers, check layouts with longer text, crawl each language version for hreflang, canonicals and untranslated content, and test checkout and emails in each language.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.