A multilingual corporate website is not about translating Chinese into English: The most easily overlooked localization issue for enterprises when building overseas websites

Translation addresses "what language the text is in", while localization addresses "whether users in this market find it natural, trustworthy and usable". The content, URL, unit, date, layout and SEO all need to be rejudged.

01 First, distinguish three concepts: translation, localization, and internationalization

When enterprises build overseas corporate websites, the most common project plan is: "After the Chinese version is completed, translate another set of English." This can lead to an English page, but it doesn't necessarily result in a website that is truly targeted at overseas customers.

The W3C's definition of Localization is not merely translation, but rather the adaptation of products, applications or content to specific language, culture and market requirements. Internationalization is to eliminate localization obstacles in advance during the design and development stages, enabling the product to support different languages, text orientations, number formats, dates, sorting, and regional rules. In simple terms: Translation is about modifying the text, localization is about improving the experience, and internationalization is about ensuring at the bottom layer that these changes will not damage the product.

02 Word-for-word translation of Chinese marketing copy is often the first problem to occur on English corporate websites

"Twenty years of forging ahead", "Craftsmanship builds quality", and "Empowering industries to create the future together" are quite common in the Chinese business context. However, after direct translation, overseas customers may still not know exactly what the enterprise does.

The homepage of a B2B international website needs to more concretize the core information: what the product is, which industries it is targeted at, which countries it serves, what problems it solves, and why it is worth further contact. Often, the correct approach to localization is not to "find the most elegant English translation", but to rewrite a message that is easier for the target market to understand.

03 The interface must leave space for the length of the translated text

One of the biggest technical pitfalls in multilingual design is to first fit the button, Tab and card sizes exactly according to either Chinese or English. W3C's information on the length of translated text reminds us that short strings may expand significantly between different languages. Some short words may even reach two to three times their original value when translated into European languages.

Therefore, a multilingual corporate website should adopt a scalable layout as much as possible to avoid having buttons with a fixed width, title containers with a fixed height, and text embedded in images. The long compound words in German, the higher line height in Thai, the right-to-left movement in Arabic, and the character width in Japanese and Chinese can all cause components that only look perfect on English drafts to fail.

04 Dates, numbers, currencies, and units are not "casually modified by the translator".

03/04/2026 May be understood as March 4th or April 3rd in different countries. 1,000 and 1.000 May also represent completely different numerical formats in different regions.

Unicode CLDR is currently the regional data foundation used by a large number of operating systems and software, covering local conventions such as dates, times, numbers, currencies, units, and sorting. When developing an corporate website, if there are requirements such as price, size, time, time zone, weight, address or phone number, it is best to use mature locale data and internationalization libraries for processing, rather than writing a bunch of conditions like "Display like this if it is in English" on the page.

05 Product categories and keywords cannot be mechanically translated from the Chinese structure

The product naming within an enterprise may have been in use for ten years, but when overseas purchasers actually search, they may use another set of industry terms. Even if the English grammar is completely correct, if the navigation, page titles and product categories are not the languages actually used in the target market, users still have difficulty finding the content.

Therefore, the information architecture and SEO keywords of overseas websites should be subject to target market research. The most worthwhile question to ask is not "What is this Chinese word in English?", but "What words would local customers use to look for this kind of product?" The same product may even have different common names in the United States, the United Kingdom, Australia, and so on.

06 The fundamental rules of Google's multilingual SEO remain clear in 2026

Google Search Central currently recommends using different URLs for different language versions instead of relying solely on cookies or browser Settings for dynamic switching. If there are multiple language or regional versions of the same page, you can use hreflang to help Google understand the corresponding relationships.

Google also clearly suggests that automatic redirection should not be forced just because the system "guesses" the user's language. Instead, clickable language switching entry points should be retained. The main content and navigation of the page should preferably be in a single language. It is not advisable for the main text to be in English while the navigation and a large amount of template content remain in Chinese. For similar pages in the same language but from different regions, it is also necessary to properly handle the relationship between canonical and hreflang.

07 The Chinese version and the English version do not necessarily have to correspond exactly page by page

Localization projects are often bound by the principle that "pages must correspond one-to-one". In fact, the main promoted products, industry maturity, cases, channels and user issues may vary in different markets. If a key service in the Chinese market has not yet been implemented in North America, there is no need for it to occupy the same position on the English homepage.

Conversely, overseas customers may be more concerned about certification, delivery regions, overseas warehouses, after-sales service, privacy and compliance. These aspects are not the focus in the Chinese version. True localization allows the content structure to change reasonably around the market, rather than maintaining two sets of visually identical websites with inappropriate information priorities.

08 Visual materials also need to be localized, rather than just a few "foreigner photos".

A global perspective does not mean an entire site is filled with image libraries of European and American conference rooms. More important than the skin color of the person is the actual business evidence: local customer cases, project sites, international certifications, regional service teams, logistics networks, and real product application scenarios.

If a company truly doesn't have a large amount of overseas materials, it doesn't have to pretend to be a "global company". A clear and accurate description of the current service scope, support methods and market capabilities is more trustworthy than using international image libraries that have nothing to do with the business.

09 Localization should start from the design and development stage, not from the last week of translation

If multilingual is added at the last step of a project, the team often encounters problems such as text overflow, images with Chinese characters, components not supporting RTL, CMS lacking multilingual fields, chaotic URL structure, and inability to manage SEO tags simultaneously.

A more reasonable approach would be to determine the language/regional strategy in the information architecture stage, test it with long texts and different scripts in the design stage, establish a locale mechanism in the development stage, and then have the translation and rewriting completed by those who truly understand the market in the content stage. In this way, localization is the system's capability, rather than a one-time content replication.

10 Conclusion: When judging whether an English website is good or not, don't just ask "Are there any translation errors?"

The real question that should be tested is: For a target market customer who has never been in contact with the company, when they enter the website for the first time, can they naturally understand who you are, what you sell, where you serve, how to view the prices and specifications, how to contact you, and whether you are trustworthy?

If the answer is affirmative, the website can be said to have made the leap from "multilingual" to "localization". Correct language is only the minimum requirement. A truly mature overseas corporate website should make users feel that it was originally designed for this market.

Frequently Asked Questions

Must a multilingual corporate website use hreflang?

If the same content has multiple language or regional URLs, using hreflang usually helps Google understand the corresponding relationships. The specific implementation still needs to be combined with the URL and the site architecture.

Can the language be automatically switched based on the user's IP?

It is not recommended to use automatic redirection as the sole method. Google also suggests retaining accessible URLs and explicit language switching for different versions to prevent users and search engines from being unable to access other versions.

Can English websites be directly machine-translated?

Machine translation can assist in the first draft, but the core pages of the enterprise, product terms, legal and sales content are best proofread or rewritten by people who are familiar with the industry and the target market.

Must the structures of Chinese and English pages be exactly the same?

Not necessarily. The key products, cases and information demands in different markets can vary, but the expression of the brand and core capabilities should remain consistent.

Why should the length of the text be considered in advance in multilingual design?

The lengths and glyphs of different languages vary significantly. Fixed-width and fixed-height components are prone to overflow after translation, so text expansion and different writing systems should be tested during the design stage.