Prompt
How do I build a multilingual ecommerce site?
Latest observation
Building a multilingual ecommerce site is mostly about combining internationalization (i18n), localization (l10n), and market-specific commerce rules in a way that scales.
1) Decide what “multilingual” means for your business
You’ll want to define:
- Languages you support
- Countries/regions you sell to
- Whether you need:
- Different currencies
- Different tax rules
- Different shipping methods
- Different product catalogs by region
- Different legal content (privacy, returns, terms)
A site for Spanish speakers in the US is very different from a site for Spain, Mexico, and Colombia.
2) Choose your architecture
There are 3 common approaches:
A. Single codebase, multiple locales
Best for most teams.
- One frontend/backend
- Locale-specific content and routing
- Easier maintenance
B. Headless commerce + localization layer
Good if you want flexibility.
- Commerce engine: Shopify, CommerceTools, BigCommerce, Magento, etc.
- Frontend: Next.js, Nuxt, Remix, etc.
- Translation/content system on top
C. Separate sites per country/language
Best for large enterprises with different teams and rules.
- More control
- More operational overhead
3) Plan your URL structure
Use one of these patterns:
example.com/en/example.com/es/en.example.comexample.com/us/en/
Most SEO-friendly and common: subdirectories
- Easier to manage
- Consolidates domain authority
- Clear for search engines
For country-specific commerce, you may need:
/en-us//en-gb//fr-fr/
4) Localize more than just text
A good multilingual ecommerce site must localize:
Content
- Navigation
- Product descriptions
- Category pages
- Blog/marketing content
- Emails and notifications
- Error messages
- Checkout labels
Commerce elements
- Currency display
- Price formatting
- Taxes/VAT/GST
- Shipping estimates
- Payment methods
- Address formats
- Units of measurement
- Date/time formats
Trust/legal content
- Terms and conditions
- Privacy policy
- Cookie consent
- Returns/refunds policy
- Regional compliance notices
5) Use a translation management workflow
Avoid hardcoding translated strings in random files if the site is large.
Common setup:
- Store UI strings in translation files (
en.json,fr.json, etc.) - Use a translation management system (TMS) like:
- Lokalise
- Phrase
- Transifex
- Crowdin
For product/catalog content:
- Keep translatable fields in your CMS or product database
- Have a workflow for human translation and review
- Support fallback language if a translation is missing
6) Handle product data carefully
Product pages are usually the hardest part.
You may need translated versions of:
- Product title
- Short/long description
- Attributes
- SEO title/meta description
- Slugs/URLs
- Image alt text
Also consider:
- Variant names
- Size charts
- Ingredient lists
- Warnings/disclaimers
Tip: keep structured fields separate from free text so translation is easier.
7) Build locale-aware checkout
Checkout is where multilingual sites often fail.
Make sure you support:
- Local languages
- Local currencies
- Correct address fields by country
- Country-specific phone number validation
- Local payment methods:
- PayPal
- Apple Pay / Google Pay
- Klarna, iDEAL, Bancontact, etc.
- Tax calculation
- Shipping options and delivery estimates
- Locale-specific order confirmation emails
8) Implement language detection, but let users override
Good practice:
- Detect browser language on first visit
- Suggest the closest locale
- Let users manually choose language/country
- Save preference in cookie/account profile
Avoid forcing redirects too aggressively; it can hurt SEO and UX.
9) Make it SEO-friendly
For multilingual ecommerce SEO:
- Use
hreflangtags - Create unique localized metadata
- Translate slugs if appropriate
- Use canonical tags properly
- Avoid duplicate content across locales
- Submit locale-specific sitemaps
Example:
- English product page and Spanish product page should each point to one another via
hreflang
10) Support formatting and accessibility properly
Use locale-aware libraries for:
- Dates
- Numbers
- Currency
- Pluralization
- Gendered language where relevant
Also ensure:
- Fonts support all scripts
- Layout works for longer translated text
- RTL languages like Arabic or Hebrew are supported if needed
- Accessibility labels are translated too
11) Use a CMS/headless commerce stack if possible
A strong modern stack might look like:
- Frontend: Next.js / Nuxt / Remix
- Commerce backend: Shopify / CommerceTools / Medusa / Saleor
- CMS: Contentful / Sanity / Strapi
- Translation platform: Lokalise / Phrase / Crowdin
- Search: Algolia / Meilisearch
- Payments: Stripe + local payment providers
This gives you:
- Flexible content
- Locale-specific pages
- Easier translation workflows
- Better scalability
12) Test each locale end-to-end
Test:
- Language switching
- Currency display
- Checkout flow
- Email templates
- Search/filter behavior
- SEO metadata
- Mobile layout
- Right-to-left rendering if applicable
- Missing translations/fallbacks
Have native speakers review important customer-facing content.
13) Common mistakes to avoid
- Translating only UI and ignoring product content
- Hardcoding currency or date formats
- Auto-translating legal text without review
- Forgetting
hreflang - Creating separate pages with duplicate content
- Not adapting checkout to local markets
- Using machine translation for marketing copy without proofreading
14) Recommended implementation approach
If you’re starting from scratch, a practical path is:
- Choose your target markets and locales
- Pick one codebase with locale-based routing
- Add i18n framework for UI strings
- Connect product/content translation sources
- Localize checkout, currency, taxes, and shipping
- Add SEO and
hreflang - Set up translation workflow and QA
- Launch one market first, then expand
If you want, I can also give you:
- a recommended tech stack
- a database schema for multilingual products
- a Next.js example
- or a step-by-step launch plan for your specific ecommerce business.