Browse Herbs by Plant Part
The plant species is only part of the identity. Browse released herbal ingredients by the exact material used—and see why root, leaf, flower, fruit, seed, bark and other parts should not be treated as interchangeable.
A plant name alone does not always tell you which herbal material is being discussed. SanYuan Herbs records the material as precisely as the source supports.
Direct Answer
Plant part matters because different parts of one species may differ in traditional material name, composition, processing, safety and product use. Same species does not automatically mean the same ingredient.
Plant-Part Registry
Search and filter the current released entity records. Counts and cards appear only when verified public data is loaded.
Browse All Plant-Part Categories
The browse UI may group related categories for convenience, while the underlying material record stays exact.
Roots
Verified root materials only. Do not classify every underground structure as a root.
Dynamic public count onlyRhizomes
Underground stems. They may browse near roots, but remain botanically distinct.
Dynamic public count onlyLeaves & Aerial Parts
Leaf-only, whole aerial material and flowering aerial parts should not be merged without source support.
Source definition controlsFlowers & Buds
Flower and flower bud can represent different materia-medica identities.
Exact stage retainedFruits
Fruit material remains separate from the seed unless the authoritative material standard says otherwise.
Fruit ≠ seedSeeds
A seed from the same plant may have a distinct name, safety context and use.
Separate material identityBark / Twigs / Stems
Bark, twig and stem are not interchangeable fields. Store the exact source-defined material.
Bark ≠ woodWood
Wood is a distinct material category and should not be collapsed into bark.
Exact source requiredResins & Exudates
Resin is better treated as a plant-derived material/exudate rather than simple anatomy.
Material type mattersFungi & Other
Fungi are not plants. Broader ingredient libraries should classify them separately instead of forcing them into plant anatomy.
Do not force taxonomyWhy the Exact Part Changes the Record
Plant part is not decorative metadata. It can determine which ingredient concept the user is actually reading about.
Root vs Rhizome
Rhizomes are underground stems, not roots. A browse interface can place them nearby, but the canonical ingredient record should keep them separate.
Fruit vs Seed
A single species can have a fruit material and a seed material with different traditional names, use contexts or safety considerations.
Leaf vs Aerial Parts
“Aerial parts” may include more than leaves. The source standard should define exactly what above-ground material is included.
Bark vs Wood
These are different tissues/materials. A product or ingredient profile should not collapse them simply because both come from the same plant.
Processing Can Change the Material Record
Species + part may still be insufficient when a material has a meaningful processed form.
Species
Accepted scientific identity and source-backed taxon.
Plant Part
Root, rhizome, leaf, flower, fruit, seed, bark, wood or other exact material.
Processed Form
When processing changes the recognized material identity, record it instead of silently merging.
Entity Decision
One canonical entity for one resolved ingredient concept; ambiguous cases stay unresolved rather than forced.
How to Browse Without Creating Thin SEO Pages
P077 is the indexable hub. Filters are utility states unless they later earn distinct editorial and entity depth.
Current Hub
/ingredients/plant-parts/→ index, follow- search and part filters stay on this page
- released entity cards link to unique canonical ingredient profiles
Automatic Filters
?part=root→ utility state?part=leaf→ utility state- default noindex / canonical to the hub
Safety & Identification
Part identity supports safer interpretation, but P077 does not replace the ingredient’s own safety profile or the exact product label.
Confirm the Material
English name, Chinese/Pinyin names, scientific identity and exact part should point to one resolved entity where possible.
Use the Safety Owner
Ingredient-specific risk belongs on the canonical ingredient profile. Cross-herb safety principles belong to Herb Safety & Interactions.
Part ≠ Product Form
A root may appear in tea, food, extract or another format. Finished-product format belongs to P078.
Frequently Asked Questions
Short answers keep taxonomy, identity, efficacy and crawl policy separate.
Why does plant part matter?
Because it can change the medicinal-material identity.
Can root and leaf be different ingredients?
Yes. They should not be treated as interchangeable unless the authoritative material standard says they are equivalent.
Are roots and rhizomes the same?
No. Rhizomes are underground stems, even if the browse interface groups them near roots.
Are fruit and seed the same?
No. Fruit and seed can represent different material identities.
Is resin a plant part?
It is better treated as a plant-derived material or exudate rather than a simple anatomical plant part.
Are fungi plant parts?
No. Fungi are not plants and should use a separate material type.
Does plant part prove a health benefit?
No. Plant part is an identity and browsing field.
Can parts be substituted?
Not automatically. Identity, formula and safety evidence must support substitution.
Can I browse by product type?
Yes—use the Browse Herbs by Product Format hub.
Why are filter pages noindex?
Because filters are utility states unless they independently earn unique content, enough verified entities and distinct user value.