When people talk about a multilingual trade website, the first thought is usually translation. Get the words right and the site counts as localized. In daily operation, what makes overseas visitors uncomfortable is rarely the wording. It is a set of details that translation never touches. Architecture and language choices were covered in an earlier piece on the four decision points. This one moves past that stage, into five localization details that get missed.

Date, number and unit formats

Flat illustration of a globe at the center with three browser windows in blue, teal and orange connected by dotted lines

One date, three notations. China writes 2026, October 31. The US writes 10/31/2026. Much of Europe writes 31/10/2026. Reuse the Chinese date template in the English version and a client may misread a delivery deadline by a full month.

Units behave the same way. Millimeters alone leave UK and US buyers doing mental math. Give inches alongside. These fixes belong to templates and code, not to copywriting.

Contact details and time zones

Phone numbers need the country code, grouped the way the target market groups them. A German buyer looking at a bare mobile number without an area code reads it as unprofessional.

Beyond the number, state the office hours with an explicit offset. CST is ambiguous, since China, US Central and Cuba all use those letters. Write UTC plus 8 and the ambiguity disappears.

Form fields and input habits

Copying the Chinese form into the English version creates two classic traps. First, translated field labels without reordered logic, so family names and given names swap places. Second, a postal code field limited to six digits, while UK postcodes mix letters and numbers. The visitor cannot complete the field and the form is dead.

The form is the conversion gate of an independent trade website. A platform store borrows trust from the marketplace; a standalone site builds it layer by layer, and field level localization is one of those layers. B2B forms should also reserve inputs for job title and purchasing intent so sales can sort leads.

Text burned into images

Words baked into a picture stay put. A banner carrying a Chinese slogan still shows those characters on the English page, and visitors notice instantly that the site was not really finished.

Decide this at the build stage: text goes into HTML, images carry background only. Images that are already burned need one redraw per language. No shortcut exists.

Legal footer localization

Privacy policy, cookie notice, return terms. Different markets expect different wording. EU visitors look for a GDPR style consent box by default. US buyers care about a different set of disclaimers. Have someone who knows the local rules review this block. Letting the translation vendor sweep it through is the risky option.

Five items, checked one by one before launch. Localization done, the next gate is indexing and ranking, and the pace is laid out in this ninety day Google SEO checklist.

Related Q&A

How many languages should a multilingual trade website have

Follow customer distribution, not language count. Main markets in Europe and the US, start with English plus one major market language. Customers spread across regions, cover the top two inquiry sources first. Each language carries ongoing maintenance, so fewer done well beats many done loosely.

Is machine translation with human review workable

Workable, and it is what most companies do now. Review must go to someone who knows the industry terms, since generic reviewers miss errors in spec sheets and certification names. Product parameters and contract related pages deserve full human review; news pages can run machine translation with spot checks.

Does poor localization hurt Google rankings

Yes. Confused date formats and leftover foreign text inside images stretch visitor decision time, and rising bounce rates drag rankings down. A wrong hreflang target scrambles indexing in that market directly.