How Should the Terminology and Translation Quality of a Changzhou Manufacturer's English/Multilingual Website Be Accepted?

Direct answer: Accepting an English or multilingual website is not a check for "does an English page exist." It should verify the terminology base (products, models, processes, standards, regulations, units), the translation process (translation—revision—review—proofreading), the scope of machine-translation post-editing, the split between native-language review and subject-matter review, how model numbers, units, and standard numbers are handled, hreflang and language switching, and whether the English version stays in sync when the Chinese source changes. Otherwise the page "reads like English," but model numbers were rewritten, units converted incorrectly, and standard numbers translated—making overseas buyers and procurement less confident, not more.

This guide is for export, marketing, engineering, quality, legal, IT, and website vendors at manufacturers in Changzhou and nearby industrial areas. It explains how to accept the terminology and translation quality of an English (or multilingual) website. Information is current to 2026-11-01. It is a review of public standards and project practice, not translation-service certification, legal, or compliance advice; specific terminology, standards, official translations, and quality requirements depend on the applicable standards, official terms, customer requirements, and contract.

How does translation quality relate to the multilingual decision, translation pricing, and English SEO?

The multilingual decision answers which markets and languages to invest in; translation pricing answers cost by volume, language, and deadline; English SEO answers titles, keywords, hreflang, and indexing; translation-quality acceptance answers whether the text is usable, terminology is consistent, and updates are synchronized. They are separate decisions, but quality is the precondition for the other three.

Manufacturers often go to one of two extremes: machine-translating the whole site so it reads like a manual, or paying for "premium translation" without a terminology base—model numbers rewritten, and the English frozen two years behind the Chinese. The website is the first material an overseas buyer uses to judge professionalism; stable terminology and facts matter more than elegant prose.

This split is editorial; process and competence requirements are in GB/T 19363.1-2022 (identical to ISO 17100:2015).

What should the English terminology base contain?

At minimum: Chinese term, English term, abbreviation/full form, definition or usage context, prohibited renderings, source (Termonline, national standard, industry practice, customer-specified), owner, version, and update date. Cover product names, model numbers, processes, materials, standards, regulations, units, job titles, and departments.

A term base is not a dictionary; it is a shared agreement between the company and external translators. One "assembly" becomes assembly in one place and unit in another; heat treatment becomes "thermal processing" elsewhere; model "LY-200A" gets "translated" into "LY-200A type." A term base fixes these so translators, reviewers, sales, and customers stay on the same page.

These fields are editorial; specific terms follow Termonline, applicable standards, and customer agreements.

How should model numbers, units, standard numbers, and regulation names be handled?

Model, part, and drawing numbers, trademarks, standard numbers, and regulation identifiers should not be translated, rewritten, or reformatted; units should be consistent and conversions stated (mm/inch, kg/lb, °C/°F); standard numbers stay as written (GB/T, ISO, DIN, ASTM); regulation names use official translations or the original with a translation. Any change needs a rule in the term base.

This is where English sites most often "translate an accident": model numbers get spaces, standard numbers get transliterated, units are converted with wrong rounding, and regulation names are paraphrased into English names that do not exist. Overseas buyers, test labs, and procurement use these details to check certificates and quotes; one wrong character can break the match.

These rules are editorial; standard numbers, regulation names, and unit conversions follow the original standards, official translations, and customer requirements.

How should the translation process (TEP) be accepted?

Accept against a basic "translate—revision—review—proofread" process: a translator produces the draft, a second translator or reviser checks it against the source line by line, a subject-matter expert reviews technical content, and a final proofread/format check follows; each step needs a record, owner, and version. GB/T 19363.1-2022, identical to ISO 17100:2015, sets requirements for the process, resources, and competences of translation services.

GB/T 19363.1-2022, Translation services — Part 1: Requirements for translation services, was published on 2022-12-30 and took effect on 2023-07-01; it is current, identical to ISO 17100:2015, and replaces GB/T 19363.1-2008. ISO 17100:2015 focuses on translation-service process requirements, including translation, revision, review, and proofreading, plus competences for translators, revisers, reviewers, and project managers. For the buyer, acceptance means checking whether these steps were done, by whom, and with what records—not just hearing that the vendor has a "multilingual team."

Process requirements are in GB/T 19363.1-2022 (identical to ISO 17100:2015); specific steps and roles follow the vendor's process and the contract.

How should machine-translation post-editing (MTPE) be accepted?

Machine translation is only a first draft; define whether it is full or light post-editing, have it handled by post-editors with language and domain competence, and require review. Terms, model numbers, units, negation, numbers, and regulation names must be checked item by item. ISO 18587:2017 sets requirements for post-editing machine-translation output.

ISO 18587:2017, Translation services — Post-editing of machine translation output — Requirements, distinguishes full post-editing from light post-editing and sets requirements for post-editor competence, process, and quality control. The most common failure is treating machine output as final and fixing only obvious words: negation flipped, digits and units misplaced, terminology inconsistent. Acceptance should sample paragraphs against the source and focus on these high-risk points, not just "does it read smoothly."

Post-editing requirements are in ISO 18587:2017; specific levels, tools, and thresholds follow the vendor's process and the contract.

How should native-language review and subject-matter review be split?

Native-language review handles "does it sound like the target language, is it natural, is the tone right"; subject-matter review handles "are the technical facts, terms, standards, and regulations accurate." They cannot replace each other: a native reviewer may not know the process, and a subject expert may not write idiomatic English. Ideally the native reviewer fixes language first, the expert checks facts, and the final approval freezes the version.

Much of the "translationese" on English sites is not grammar errors but literal renderings of Chinese parallelism, four-character phrases, and slogans that read awkwardly to overseas buyers. Conversely, a native reviewer may change "quenching" to "hardening" or "tolerance" correctly, but without process knowledge may render "tempering" inaccurately. Both lines are needed, with records.

This split is editorial; actual staffing follows the company, vendor capability, and contract.

How should errors be graded and sampled?

Grade by impact: critical (fact/safety/regulatory errors, wrong model or standard, reversed meaning), major (inconsistent terminology, wrong numbers/units, missing key information), minor (grammar, spelling, tone). Sampling should cover home, product, capability, contact, and downloadable files; critical errors must be zero, major errors cleared before launch, minor errors scheduled.

Acceptance cannot sample one paragraph that "reads fine." Sample by page type and risk: product parameter pages for numbers/units/models, capability pages for process and capacity claims, certification pages for standard numbers and claim boundaries, contact pages for address and time zone. A critical error means the whole batch goes back—do not "launch first, fix later," because once customers or search engines see the English page, fixing it still leaves a trace.

Grading and thresholds are editorial; specific quality gates follow customer requirements, the vendor contract, and industry practice.

How should hreflang, language switching, and content sync be accepted?

Each language version should declare hreflang for all versions (including itself) and set x-default; the language switcher should go to the corresponding page, not the home page; when the Chinese page changes, the English page should update content and date; bilingual sitemap lastmod, canonical, and RSS should align. Do not fake hreflang for pages without a full English version.

Google's localized-versions documentation asks each language version to list hreflang links for all versions (including itself) in the page head, with x-default available to point to the default or language-selector page, and return links must correspond. Common errors: the English page points only to Chinese, the switcher always goes home, the Chinese page changes but English and lastmod do not. The details look small but directly affect indexing and user experience.

hreflang rules are in Google Search Central's localized-versions documentation; implementation follows the site structure and search-engine docs.

What should the page say, and how should it link?

Include the term base (downloadable/searchable), the translation and review process, the MTPE statement, error grading and feedback channel, language switching and hreflang notes, and an update log; link to the multilingual decision page, translation-cost page, English product pages, and contact page. Do not make the term base an internal-only Excel, and do not hide "machine translated" in the footer.

Make "translation quality" a page useful to both customers and staff: customers see how terminology and facts are kept consistent, and staff follow one process. The English page can add "terminology follows our term base; corrections welcome" with a feedback mailbox—more credible than "professional translation team."

These modules are editorial; specific terms, process, and disclosure follow the company and the vendor contract.

Go-live acceptance checklist

Ten checks: term base, models/units/standards, process records, MTPE level, native review, subject-matter review, error grading, hreflang/switching, content sync, and feedback channel. Each needs an owner, evidence, and review date.

Export, marketing, engineering, quality, legal, IT, and the website vendor can share this list. The pass condition is not "the English page opens"; it is consistent terminology, unchanged facts, correct units, untouched standard numbers, natural reading, English updated with Chinese, and someone handling customer corrections.

This checklist is editorial; specific quality gates, process, and disclosure follow applicable standards, customer requirements, and the vendor contract.

Who should read this, who should not, and what decisions does it support?

It suits manufacturers in Changzhou and nearby areas that already have or plan an English/multilingual website, attend overseas exhibitions, run export sites, or send English materials to customers. It does not suit teams with no English content needs, or those who want machine translation to "hang an English shell" first.

Read it if you are in export, marketing, engineering, quality, legal, IT, or a website vendor; you are accepting an English site, translation service, term base, MTPE, or hreflang; or you need to decide how terms are set, how the process is verified, whether MT is acceptable, who does native review, and how updates are synchronized. Skip it if you have no English content capability but promise "all languages"; you treat machine output as final; or you want one page to replace the translation contract, standards, or legal advice. It supports self-review of the term base, models/units/standards, TEP process, MTPE, native review, error grading, hreflang, and content sync.

Lingyi Information is a website development and enterprise AI project provider, not a translation-service certification body, standards body, or law firm. This article is not a substitute for the translation contract, conformity certification, or legal advice. Changzhou projects are delivered remotely or on site as confirmed per project; Lingyi is one candidate, does not claim a local office or team, and does not promise translation certification, indexing, rankings, or inquiries.

FAQ

Can machine translation be used directly on a website?

Not recommended. Machine translation can be a first draft, but it needs post-editing and review, especially for models, units, numbers, negation, standards, and regulation names. ISO 18587:2017 sets requirements for post-editing machine-translation output; with a limited budget, at least fully post-edit and native-review the high-risk pages.

Should the term base be public?

A searchable public version helps customers, translators, and dealers use the same terms; keep customer-specific, undisclosed-process, or trade-secret terms in an internal version. A public term base also reduces "customer asks A, sales answers B."

Is native review mandatory for English pages?

Depends on the market and content risk. For product, capability, and certification pages aimed at European or North American buyers, at least native review is advisable; internal or temporary materials can be lighter. Native review handles natural language, subject experts handle factual accuracy—they cannot replace each other.

What happens if the Chinese page updates but English does not?

Customers see two sets of facts: Chinese shows a new line or capacity, English shows the old one; Chinese updates a certification scope, English still lists the old certificate. That hurts trust more than having no English page and affects freshness signals. Keep a ZH-EN version comparison table with update dates.

What if hreflang is wrong?

Search engines may pick the wrong language version, create duplicate-content or indexing issues, and the language switcher may send users to the home page instead of the corresponding page. At minimum, ensure reciprocity, self-reference, correct x-default, and page-level switching.

How can translation quality be measured?

Use error grading plus sampling: critical errors must be zero, major errors cleared before launch, minor errors scheduled; sampling covers home, product parameter, capability, certification, and contact pages. Do not rely only on a subjective "reads fine."

One-sentence takeaway

Accepting a Changzhou manufacturer's English/multilingual website is not about whether an English page exists; it is about a term base, a TEP process, MTPE, native and subject-matter review, model/unit/standard handling, hreflang, and content sync—documented and recorded—so terms are consistent, facts unchanged, and the text reads naturally.

Method and limitations

This is a review of public standards and project practice, not certification or legal advice on any company, translation, translation service, or website. No undisclosed customer translations, term bases, or contracts were used. Term-base fields, process roles, error grading, and the acceptance checklist are editorial suggestions, not translation-quality certification or an evaluation of any vendor. Specific terminology, standards, official translations, process, and quality gates depend on applicable standards, official terms, customer requirements, and the vendor contract.

Sources and scope

Information is current to 2026-11-01. The following are public official/primary pages; their scope, version, and wording control.

1. GB/T 19363.1-2022, Translation services — Part 1: Requirements for translation services (published 2022-12-30, effective 2023-07-01, current; identical to ISO 17100:2015): National Standards Information Public Service Platform.
2. ISO 17100:2015, Translation services — Requirements for translation services: International Organization for Standardization. Translation, revision, review, and proofreading process and competence requirements.
3. ISO 18587:2017, Translation services — Post-editing of machine translation output — Requirements: International Organization for Standardization. Full/light post-editing and quality control.
4. Google Search Central, Localized versions of your pages: Google Developers. hreflang, x-default, and reciprocity.
5. Termonline (China National Committee for Terms in Sciences and Technologies): Termonline. Standard terminology lookup.