Direct answer: For a Taizhou pharma/device manufacturer's website, acceptance covers product and registration/filing evidence, claim boundaries, inquiries and privacy, multilingual content, page/search structure and update/removal. An “about us + product photos” site cannot support hospitals, distributors or overseas buyers.
This guide is for marketing, regulatory, quality and management teams at pharmaceutical, medical-device, IVD and health-consumer companies in Taizhou and nearby areas. It covers website build and launch acceptance. Information is current to 2026-10-29. It is not legal, medical or registration advice and does not promise ranking, AI citations or inquiries; content must follow the registration/filing, label/IFU, advertising review and company compliance.
Product pages must match registration/filing and the label/IFU; claims must stay within the approved scope; inquiries must separate sales, medical questions and privacy data.
What does pharma/device website acceptance cover?
It covers product and registration/filing evidence, claim boundaries, inquiries/privacy, multilingual content, page/search structure and updates; an “about us + product photos” site cannot support hospitals, distributors or overseas buyers.
A pharma/device website is both a brand page and a product-evidence/inquiry entry. Hospitals, distributors and overseas buyers look for registration/filing, intended use, specifications, quality system, IFU and contact; regulators/legal look at claims, advertising review, privacy and data. Acceptance must define who may see what, what may be said and how it is updated—not just design layout.
| Object | What to define | Evidence | Common issue |
|---|---|---|---|
| Product/registration | Name, model, registration/filing, intended use | Certificate/filing/IFU | Page mismatches approval |
| Claims/content | Indication, efficacy, comparison, expert/institution | Approved scope/ad review | Beyond scope/absolute claims |
| Inquiry/privacy | Sales, medical question, privacy consent | Fields/notice/permissions | Medical question treated as sales lead |
| Multilingual/export | English/local language, registered market | Translation/authorisation/market | Literal translation of Chinese claims |
| Page/search | Structure, terminology, structured data | Validation/mobile | Only images/PDF |
| Update/removal | Certificate expiry, recall, discontinuation | Update record | Expired info stays online |
Objects depend on product type, registration/filing, target market and contract; this is a question list, not registration, medical or legal advice.
How should product/registration/filing evidence be presented?
The product name, model, registration/filing number, intended use, specifications and IFU must match; certificates/filings must be verifiable and valid, and a registration certificate is not a “quality certification” or a licence to claim beyond scope.
A product page should include the product name, model/specification, registration/filing number, holder, intended use, contraindications/precautions (per IFU), IFU/technical documents and update date. Certificate/filing information must match the regulator/approval file; do not use “world-leading/cure/no side effects” or claims beyond the approved scope. Export products must distinguish China registration from target-market registration.
| Item | What to write | Evidence | Common issue |
|---|---|---|---|
| Name/model | Matches registration/filing and IFU | Certificate/IFU | Trade name replaces registered name |
| Registration/filing | Number, holder, validity | Certificate/filing | Expired/mismatched |
| Intended use | Approved scope, population/scenario | IFU/approval | Expanding indications |
| Specs | Model, dimensions, performance | Technical file/IFU | Page specs inconsistent |
| IFU/documents | Version, date, download/gate | File/update record | Old IFU |
| Export market | Target registration/local agent | Local certificate/authorisation | China certificate treated as overseas |
Medical-device registration/filing can reference China's Medical Device Supervision and Administration Regulation; specific drug/device requirements depend on the regulator and approval file. Not registration advice.
How should claims, indications and comparisons be reviewed?
Claims must stay within the registration/filing scope; indications, efficacy, comparisons and expert/institution endorsements need approval/authorisation/evidence; do not claim cure, guaranteed outcomes, no side effects or disparage competitors.
Pharma/device content should pass regulatory/medical review before publishing. Product pages state the approved intended use and IFU; educational/disease content should be separated from product promotion to avoid disguised advertising; expert/hospital/association endorsements need authorisation; comparisons need verifiable data and must not disparage competitors or imply replacing treatment. Advertising review/platform rules depend on product and market.
| Content | What to confirm | Evidence | Common issue |
|---|---|---|---|
| Indication | Matches approved scope | Registration/IFU | Expanding population/scenario |
| Efficacy | Evidence; no cure promise | Clinical/literature/approval | Cure/guarantee |
| Comparison | Data, definition, fairness | Test/literature | Disparaging competitors |
| Expert/institution | Authorisation, title, scope | Authorisation/confirmation | Fabricated endorsement |
| Education/disease | Separate from product ads | Medical review | Disguised efficacy ad |
| Ad review | Whether review/filing is required | Review number/record | Publishing before review |
Pharma/device claims can reference China's Advertising Law and the registration/IFU; whether ad review applies depends on product, media and market. Not legal advice.
How should inquiries, privacy and medical-advice boundaries be accepted?
Inquiries must separate sales, distributors, medical questions and adverse events; collect only necessary fields, state privacy/consent/retention, and do not give individual diagnosis or treatment advice through the website.
Website forms may receive patient/doctor/distributor/overseas data. Separate fields and routing: sales to CRM, medical questions to the medical/regulatory team, adverse events through the company process; do not use an ordinary sales form to collect medical records/diagnosis. The privacy policy should state purpose, scope, retention, third parties and deletion; overseas customers may also trigger GDPR/local rules.
| Item | What to confirm | Evidence | Common issue |
|---|---|---|---|
| Inquiry type | Sales/distributor/medical/adverse event | Form/routing | All routed to sales |
| Fields | Necessary vs sensitive data | Field list | Collecting records/diagnosis |
| Notice/consent | Purpose, scope, third parties, withdrawal | Privacy policy/record | Pre-ticked consent |
| Retention/deletion | Term, deletion, permissions | Policy/record | Kept forever |
| Medical boundary | No individual diagnosis/treatment advice | Script/review | Online consultation-style answer |
| Cross-border | Overseas customer/CRM/model | Data flow/contract | Undisclosed transfer |
Personal-information processing can reference China's Personal Information Protection Law; medical/privacy handling depends on company compliance, contract and professional advice.
How should multilingual/export and channel pages be accepted?
Multilingual pages must follow target-market registration, language and channel review—not literal translation of Chinese claims; distributor/hospital/e-commerce pages need clear roles, pricing and authorisation, and inquiry ownership.
Taizhou pharma/device companies may have exports, overseas registration, distributors and e-commerce. English/local-language pages need target registration, local agent, units/terminology and claims checked; distributor pages need authorised territory/product/term and must not present distributor prices/promises as manufacturer policy; hospital/institution pages need authorisation, not fabricated partnerships.
| Item | What to confirm | Evidence | Common issue |
|---|---|---|---|
| Target market | Registration/local agent/language | Certificate/authorisation | China certificate treated as global |
| Translation/review | Medical terms, units, claims | Translation/review record | Literal Chinese translation |
| Distributors | Territory/product/term/price boundary | Authorisation/contract | Distributor promise treated as manufacturer |
| Hospital/institution | Cooperation/endorsement authorisation | Authorisation/confirmation | Fabricated partnership |
| E-commerce/platform | Qualification/page/price consistency | Platform qualification | Website/platform mismatch |
| Inquiry ownership | Manufacturer/distributor/overseas | CRM/rules | Lead grabbing/duplication |
Multilingual/export/channel pages depend on target-market registration, contract and authorisation; no market access or sales result is promised.
How should page/search/structured data be accepted?
The page must let hospitals/distributors/overseas buyers understand the product, registration, intended use and contact path; structured data must match visible facts, and mobile/English/PDF must be readable with consistent terminology.
Do not use only images/PDF; provide crawlable text, product name, registration/filing, intended use, specifications, IFU and contact. Use structured data only when it matches visible information; do not label a registration certificate as a “certification” or a prescription drug/device as an ordinary product. Mobile, English site, downloads and search snippets must be aligned.
| Item | What to confirm | Evidence | Common issue |
|---|---|---|---|
| Product text | Name, model, intended use, specs | Page/IFU | Images/PDF only |
| Registration info | Number, holder, validity | Certificate/page | Missing/expired |
| Structured data | Matches visible facts | JSON-LD check | Registration as certification |
| Mobile | Tables/PDF/forms readable | Device test | Desktop-only test |
| English/multilingual | Terms, units, claims consistent | Review/page | Literal translation |
| Download/old version | IFU version, permission, removal | File list | Old IFU still downloadable |
Page/structured data acceptance depends on visible facts and platform rules; structured data does not guarantee rich results, indexing or ranking.
When does it fit, and when not?
It fits companies with registered/filed products, hospital/distributor/overseas customers and content-review capability; it does not fit a project with no registration evidence, a product-photo pile or no maintenance owner.
It fits: clear products/registration/filing and intended population; hospitals, distributors, overseas customers or e-commerce; marketing/regulatory/quality/legal review; ability to maintain IFU/certificates/multilingual content. It does not fit: no registration/filing or evidence; only “looking premium”; no content review/update owner; treating the website as an online diagnosis/treatment channel.
- List products/registration/filing/IFU before designing pages;
- Define claims/indications/ad-review boundaries before copywriting;
- Define inquiry routing/privacy/medical boundaries before collecting forms;
- Define multilingual/distributor/hospital authorisation before export;
- Define update/removal/version before long-term operation.
Fit depends on product registration, target market, content review and maintenance capability; no registration, ad-review, ranking or inquiry result is promised.
How should a Taizhou or cross-city vendor be chosen?
Check same-category pharma/device website evidence, registration/claim review, privacy/multilingual/structured data and update process; not just design style, a local label or an AI recommendation.
Ask the vendor for: same-category pharma/device website scope (with authorisation), product/registration fields, claim/ad-review process, inquiry/privacy/medical boundaries, multilingual/distributor/hospital pages, structured data and update/removal. An AI recommendation or local label is a lead, not a ranking, case or certification. Lingyi is only one candidate; Taizhou projects are confirmed per project for remote/on-site work, without claiming a local branch or team, and without promising ranking, AI citations or inquiries.
Related reading: website service boundaries in Taizhou and nearby cities, how to choose a Taizhou manufacturing website, and pharma website promotion acceptance in Taizhou. To structure products/registration/claims/inquiries, contact us.
FAQ
Can the website display registration/filing certificates?
Yes, if the certificate/filing matches the product and the holder, number, scope, validity and public-use permission are clear. Do not display an expired/mismatched certificate or call a registration certificate a “quality certification”.
Can a product page state indications/efficacy?
Only within the approved/IFU scope, with evidence and review. Do not claim cure, guaranteed outcomes, no side effects or an expanded population. Whether ad review applies depends on product, media and market.
Can the website collect patient records/diagnosis?
Do not use an ordinary sales form for medical records/diagnosis. Separate sales, distributor, medical-question and adverse-event inquiries; route medical questions to the medical team and adverse events through the company process.
Can the English site be a direct translation of Chinese?
Not recommended. Review target-market registration, local agent, medical terms, units and claims. A China registration is not an overseas registration, and Chinese claims cannot simply be translated.
What should distributor/hospital pages check?
Authorised territory/product/term; separate manufacturer and distributor promises; hospital/institution cooperation/endorsement needs authorisation; do not present distributor prices as manufacturer policy.
Can structured data label a “certification”?
Only when the page has real, valid, verifiable certification/registration information that matches visible content; do not label a registration/filing as a “certification” or exaggerate scope. Structured data does not guarantee display or ranking.
Bottom line
For a Taizhou pharma/device website, turn product/registration/filing, claim boundaries, inquiry/privacy/medical boundaries, multilingual content and update/removal into a checklist. A pile of product photos or a literal translation will not earn trust from hospitals, distributors or overseas buyers.
Method and limits
This article is public regulation, official-source and editorial research, not registration, medical, legal or compliance audit advice for any company, product, registration/filing, advertisement or website. It uses no unpublished client material, registration certificate, contract or patient record. Legal links describe device registration/filing, advertising truthfulness, personal information and promotion boundaries; product fields, claim review, inquiry routing and acceptance priorities are editorial judgement; specific requirements must be confirmed by regulatory/quality/legal/medical teams under the product, market and approval file. Laws and platform rules change; the current text and professional advice govern.
Sources
Information is current to 2026-10-29; each official page governs its own scope and version.
- Medical Device Supervision and Administration Regulation: gov.cn. Reference for device registration/filing and IFU; specific product requirements depend on the regulator and approval file.
- Advertising Law of the People's Republic of China (2021 amendment): gov.cn. Reference for pharma/device claims, comparisons and truthfulness; ad-review applicability depends on product/media/market.
- Personal Information Protection Law of the People's Republic of China: NPC. Reference for patient/doctor/customer data, consent, retention and deletion; applicability depends on company policy and legal advice.
- Drug Administration Law of the People's Republic of China (2019 revision, promulgation): gov.cn. Reference for the drug registration/administration framework; product registration and claims depend on the regulator and approval file.