How to Build a Multilingual Site: English + Minor Languages + hreflang

True multilingual expansion is localization โ€” using the language, habits, and expressions of your target markets so that customers in each market feel "this was made for us." This article explains the right way to build a multilingual site.

02.3 Cui Lishu Cui Lishu
V1.0Current version
1revisions
BeginnerReading difficulty
2026.09.10Updated
Cui LishuLast modified
A multilingual site isn’t just “translating Chinese into English.” If you get it wrong, Google may flag your site as duplicate content.
True multilingual expansion means Localizationโ€”Using the language, habits, and expressions of the target market, so customers in each market feel like “this was made just for us.” This article explains the right approach to multilingual sites.

Many companies build multilingual sites by simply machine-translating Chinese content into English and launching. But truly effective multilingual expansion is about Localizationโ€” Not only must the language be correct, but it must also align with the culture, habits, and search behavior of the target market.

1. Multilingual โ‰  Translation

  • Language Localization: Use the natural expressions of your target market, not literal translations. Avoid “Chinglish.”
  • Content localization: Units (imperial/metric), currency, case studies, certifications, etc., all need to be adapted to the target market.
  • Search localization: Users in different markets have different search habits; keywords need separate research rather than translating Chinese keywords.

2. hreflang: Tell Google about the relationship between language versions

hreflang It’s a technical tag that marks the relationship between multilingual pages. Its purpose is to tell search engines: these pages are different language versions of the same content, so please show the version in the corresponding language to users in the corresponding region. Using hreflang correctly prevents your pages from being flagged as duplicate content and ensures each language version gets the right search exposure.

There are three common multilingual site structures: subdirectory (example.com/en/), subdomain (en.example.com), and separate domain. For most B2B companies going global,Subdirectory structure(example.com/en/, example.com/de/) is the most cost-effective choice โ€” domain authority is consolidated and management is simple.

3. The Order for Building a Multilingual Site

  • Step one: Build the English site first (as your primary version).
  • Step two: Based on your target markets, gradually add high-value niche languages (German, Spanish, French, Japanese, etc.).
  • Step three: Each language version should be locally optimized, not just translated.
Key reminder: Incorrect hreflang configuration (such as mismatched annotations or missing return annotations) is worse than no configuration at all, and may cause search engines to display the wrong language version in the wrong region. When launching a multilingual site, it’s advisable to use professional tools to verify hreflang accuracy.
One-sentence conclusion ยท TL;DR

The core of a multilingual site is localization, not translationโ€”language, content, and search keywords must all be adapted to the target market. Use hreflang to correctly mark the relationships between language versions and avoid duplicate content misjudgments; prioritize building the English main site first, then gradually expand to high-value niche languages.

Common Questions
Start with English first, or go multilingual right away?

We recommend building a solid English site as your primary focus first, then expanding gradually once it’s running smoothly. Launching multiple languages simultaneously significantly increases content production and maintenance costs, while English alone can cover most of the overseas B2B market. It’s more efficient to concentrate on doing English well first, then expand into high-value languages in a targeted way.

Subdirectory, subdomain, or separate domain โ€” which should you choose?

For most B2B companies going global, a subdirectory (example.com/en/) is recommended: domain authority stays concentrated and SEO management is simpler. Subdomains and standalone domains suit large enterprises with dedicated teams that need to operate specific markets completely independently, but they dilute authority and increase maintenance costs.

Is machine translation plus human proofreading enough for minor languages?

It’s acceptable as a starting approach, but machine-translated drafts must go through human proofreading and localization polishing by native speakers of the target market. Key pages (homepage, product pages, inquiry pages) are best written directly by professional native speakers, because these pages directly affect conversion and trust.

Further reading
Revision History
v1.0 2026.09.10 Initial publish Cui Lishu
Tags for this entry