How to plan a multilingual website strategy that prioritises markets and languages for maximum export impact.
A Vietnamese footwear exporter wanted to translate their website into every language they could think of — English, French, German, Spanish, Japanese, Korean, Arabic, and Russian. They spent US$12,000 on translations and ended up with seven language versions, each containing errors because they had tried to do too much at once. Worse, the Arabic version had layout issues that made it unreadable, and the Korean version had mistranslated product specifications. Buyers in their primary market — Japan — noticed the mistakes across other language versions and questioned the exporter's attention to detail.
A multilingual strategy is not about translating everything into as many languages as possible. It is about making strategic decisions about which languages to offer, how deeply to localise each one, and how to manage the complexity of multiple language versions without sacrificing quality. A well-planned multilingual approach with three languages done well outperforms a poorly executed approach with ten languages.
Start with data, not assumptions. Analyse your current website traffic by country — if you are already getting visitors from Germany, you have demonstrated demand for a German version. Review your export targets — which markets have the highest revenue potential? Consider buyer behaviour — buyers in some markets (Japan, China, France) strongly prefer purchasing in their native language and will leave sites that are not available in their language. In other markets (Netherlands, Scandinavia, Singapore), English proficiency is high enough that translation offers less ROI.
Create a language priority matrix. Tier 1 languages are those where the market size, buyer preference for local language, and revenue potential justify a fully localised version with translated content and cultural adaptation. Tier 2 languages are those where a translated version of key pages — product pages, about page, contact page — is valuable but full localisation is not yet justified. Tier 3 languages are those where English-only is acceptable for now, monitored for future demand.
For most exporters, the right approach is: start with English as your default, add one Tier 1 language for your highest-priority market, prove the approach works, then expand to additional languages one at a time. Each language you add multiplies your content management workload — do not commit to more languages than you can maintain well.
Translation converts your content from one language to another while preserving the original meaning. Localisation adapts your content to the cultural context of the target market — adjusting examples, references, images, colours, and even product offerings to suit local preferences. Translation is faster and cheaper. Localisation is more effective but requires deeper investment.
For Tier 1 languages, invest in localisation: adapt your value proposition for the market, use local examples and case studies, adjust imagery to reflect the local context, and review colour choices and design elements for cultural appropriateness. For Tier 2 languages, professional translation with minor cultural adjustments (currency, units of measurement, date formats) is usually sufficient. For Tier 3 languages, machine translation with human review can be acceptable for basic content — but never for product specifications, pricing, or legal terms.
Decide how your language versions will be structured technically. The most common approaches: subdomain (de.yoursite.com), subdirectory (yoursite.com/de/), or separate domain (yoursite.de). Subdirectories are generally preferred for SEO because they consolidate domain authority and are easier to manage. Separate domains are useful if you are targeting countries with strong local domain preferences (Germany, Japan, China) but require more technical setup.
Regardless of structure, implement hreflang tags so Google knows which language version to show in each market. Implement a language switcher that is easy to find — top right corner of the header is standard. Respect the user's choice: if a buyer selects French, show them French on every visit, not the English version based on their IP address. Offer the option to switch languages on every page, not just the homepage.
Three to five languages is the practical maximum for most exporters. One default language (English) plus two to four target market languages. Each additional language requires translation, design review, SEO setup (hreflang tags, sitemaps), ongoing content updates, and quality assurance. The cost of maintaining a language version is ongoing, not one-time — so only add languages you can maintain for the long term. A focused set of well-maintained language versions outperforms a broad set of neglected ones.
Machine translation (Google Translate, DeepL) can be useful for understanding content but should not be your primary translation method for a professional export website. Automated translations frequently miss technical terms, brand-specific language, and cultural nuances that affect buyer trust. Use machine translation for internal understanding or as a starting point, but always have a native-speaking human reviewer finalise the content. For product specifications, legal terms, and pricing, never rely solely on machine translation.
No. A subdirectory structure (yoursite.com/de/) is the recommended approach for most exporters. It consolidates SEO authority under a single domain, is simpler to manage, and avoids the complexity of maintaining multiple domain registrations and SSL certificates. Use separate domains only if you have strong market-specific reasons: a .de domain may improve click-through rates in Germany, and a .cn domain is required for ICP-licensed hosting in China. For all other cases, subdirectories are the better choice.