Chinese Herbal Ingredient Library
Search Chinese botanical and material ingredients by English name, Chinese name, Pinyin, scientific name, plant part or product format.
SanYuan Herbs uses one canonical page for each ingredient/material entity and connects it to the products, guides, safety information and evidence that actually relate to it.
Short Answer
What is the Ingredient Library? It is SanYuan Herbs’ structured reference for Chinese herbs, food botanicals, incense woods, moxa materials, fungi and other product-related ingredients. A complete profile can resolve names and identity, show the part and material type, separate traditional context from modern research, surface safety and sourcing evidence, and connect only the SanYuan products that actually use the ingredient.
Featured Ingredients
The hub should feature useful public entities—not empty name-only records. The list below is a starter view and can be replaced by the current public entity dataset.
Goji Berry / Wolfberry
Fruit-based ingredient entity used across tea, paste and food contexts.
Explore Goji →Jujube / Red Date
Fruit entity with alias, species, part, sensory, sourcing and product relationships.
Explore Jujube →Chrysanthemum
Flower-based ingredient entity connected to tea and related product formats.
Explore Chrysanthemum →Mugwort / Ai Ye
Material entity that can connect foot soak, topical and moxa contexts without collapsing them into one product claim.
Explore Mugwort →Browse A–Z & by Chinese Name / Pinyin
Alphabet and language browsing help users discover the same canonical entities. They do not create multiple versions of an ingredient page.
Browse A–Z
Use one A–Z page with anchors. Do not create thin `/ingredients/a/`, `/ingredients/b/`, `/ingredients/c/` pages.
Browse by Chinese Name & Pinyin
Useful when a user knows a Chinese or romanized name but not the English canonical term.
Gou Qi Zi · 枸杞子
→ `/ingredients/goji-wolfberry/`
Jujube / Red Date
Da Zao · 大枣
→ `/ingredients/jujube-red-date/`
Browse by Plant Part
Root, leaf, flower, fruit, bark, seed, wood or resin can have different product forms, traditional contexts, safety considerations and search intent.
Browse by Product Format
This view answers “which ingredients appear in this kind of product?” It can hand off to Shop, but should not copy transactional category copy.
Tea / Drink
Ingredients used in tea bags, loose blends, botanical drinks or related beverage forms.
Paste / Food
Food-form botanical relationships and edible ingredient contexts.
Topical / Foot Soak
Material relationships for external-use product formats.
Incense / Moxa
Woods, botanicals and other materials used in aroma or moxa-related products.
Oil
Botanical oil or oil-based product relationships where the exact formula supports them.
Bracelet / Aroma Material
Wearable or non-burning aroma-material contexts.
Not every item is a plant
Fungi, wood, resin and other materials should use the correct MATERIAL_TYPE.
Explore Products by Ingredient
Product cards must come from current BOM/formula relationships, not from name guessing.
How Ingredient Names Are Standardized
Common names vary by region, trade and translation. The library stores aliases for discovery while maintaining one canonical entity.
ING003
A stable internal identifier connects content, products and evidence.
Jujube / Red Date
The main consumer-facing entity name.
大枣 / Da Zao
Stored as aliases and structured identity fields.
Verified scientific identity + Fruit
Scientific name is shown only after verification; plant/material part is explicit.
/ingredients/jujube-red-date/
Aliases search-match or redirect here instead of creating four indexable pages.
What an Ingredient Profile Contains
The library is not a template that repeats “benefits / uses / dosage” 100 times. Each entity page should resolve identity, part, context, evidence and real relationships.
Identity
- canonical English
- Chinese / Pinyin
- scientific name
- family / part / material type
At a Glance
- neutral definition
- appearance
- taste / aroma
- common product forms
Traditional Context
Historical and cultural context with sources, visually separated from modern claims.
Modern Research
Human, review, observational, preclinical or limited/mixed evidence with studied material identified.
Safety & Interactions
Interactions, allergy, pregnancy, children, surgery and product-form differences.
Sourcing & Quality
Origin, processing, authenticity, lot/batch records and first-party evidence.
Products Containing It
Generated from current BOM/formula relationships.
Related Guides / Ingredients
Meaningful relationships with a reason—never random bulk linking.
Sources & Review
Author, reviewers, review date and change log.
Traditional Context vs Modern Research vs Product Facts
SanYuan Herbs separates historical description, contemporary research and current SKU facts so a traditional statement does not silently become a product efficacy claim.
Traditional Context
What historical sources, Chinese materia medica, tea culture or everyday practices describe.
- cultural language
- historical use
- traditional naming
Modern Research
What current studies investigate, which material was studied and what evidence level exists.
- human / clinical
- reviews
- observational
- preclinical
- limited / mixed
Product Facts
What a current SanYuan SKU actually contains, how it is labeled, how it is used and which market/formula version applies.
- BOM / formula
- label facts
- format
- market
Safety & Interactions
Natural ingredients are not automatically risk-free. A complete Ingredient profile should make safety status visible and source/reviewer driven.
Medication Context
Potential interactions belong to reviewed ingredient-specific evidence, not generic “natural = safe” language.
Allergy / Sensitivity
Ingredient and product-form context should be clear.
Pregnancy / Lactation
Do not infer blanket safety from traditional use or food familiarity.
Age / Children
Age-related cautions require appropriate sources and product context.
Surgery / Procedures
Relevant cautions should be reviewed rather than copied between ingredients.
Product-Form Differences
Beverage, extract, topical, incense and other formats may have different exposure and safety questions.
Sourcing & First-Party Evidence
Definitions and history already exist in generic encyclopedias. SanYuan’s differentiation should come from real material, supplier, batch, BOM and first-party observation records.
How Ingredients Connect to Products
Product relationships should flow through the current ingredient ID, BOM and formula version. A marketing product name is not enough to prove the relationship.
Review & Update Method
An Ingredient page can change when taxonomy, alias mapping, safety evidence, product formula, supplier/material source or first-party evidence changes.
Taxonomy & Name Review
Canonical English, Chinese/Pinyin, species/material identity, part and material type.
Safety Review
Interactions, allergies, pregnancy, children, surgery and form-specific cautions.
BOM / Product Verification
Formula version, SKU, product format, market and ingredient relationship.
Last / Next Review
Review dates, change note and evidence updates should be recorded rather than silently overwritten.
Frequently Asked Questions
The library is designed to resolve identity and relationships, not to create duplicate URLs for every spelling or filter.
Why do some Chinese herbs have several English names?
Common names can vary by region, translation and trade. SanYuan Herbs keeps those terms as aliases while selecting one canonical entity page.
Is Pinyin a different ingredient?
No. Pinyin usually represents the romanized Chinese name. It should map to the same ingredient unless the term actually refers to a different material or preparation.
Why is scientific name important?
Common and trade names can be ambiguous. Scientific identity helps clarify which taxon is meant, but it still needs the correct material and part information.
Are all items in the library plants?
No. The library may include fungi, woods, resins and other materials with an explicit material-type field.
Does every ingredient have a SanYuan product?
No. Product modules only show current SKU relationships supported by BOM/product data.
Why are some processed forms not separate pages?
A processed form can remain a section of the main entity until it has enough independent search, safety and product value to justify its own canonical page.
Can I search by Chinese characters?
Yes, when the search index contains verified Chinese aliases. Search results still point to the canonical ingredient entity.
Are filter pages separate SEO pages?
No. Filters are discovery tools, not automatically independent indexable content.
Library Coverage & Entity Status
The library can grow early under the current index-leniency policy, but unverified facts stay hidden and empty name-only pages are not published.
20–30 high-priority entities
Focus on identity, disambiguation, real product/guide relationships and core safety/evidence fields.
50–70 entities
Add stronger Chinese/Pinyin browse, plant-part discovery and product-format relationships.
100+ entities
Expand first-party evidence, expert media, batch/source records and the product relationship graph.