Vein
Vein is an AnatomicalStructure subtype (through Vessel) for the blood vessels that carry blood back to the heart. It describes the region drained, the tributaries that feed the vein, and the larger vessel the vein eventually drains into.
Full example of schema.org/Vein json-ld markup
The markup is verified as valid with Rich Results Test from Google.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Vein",
"name": "Inferior vena cava",
"regionDrained": [
{ "@type": "AnatomicalStructure", "name": "Lower limbs" },
{ "@type": "AnatomicalStructure", "name": "Pelvis" },
{ "@type": "AnatomicalStructure", "name": "Abdomen" }
],
"tributary": [
{ "@type": "AnatomicalStructure", "name": "Common iliac veins" },
{ "@type": "AnatomicalStructure", "name": "Renal veins" },
{ "@type": "AnatomicalStructure", "name": "Hepatic veins" }
],
"drainsTo": { "@type": "AnatomicalStructure", "name": "Right atrium of the heart" },
"partOfSystem": { "@type": "AnatomicalSystem", "name": "Cardiovascular system" }
}
</script>Direct properties (3)
tributary: AnatomicalStructure — the smaller veins that feed into this vein.regionDrained: AnatomicalStructure or AnatomicalSystem — the region this vein drains.drainsTo: Vessel — the next vessel downstream (eventually the heart).
Minimal valid version
The smallest markup that still produces a valid Vein entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Vein",
"name": "Inferior vena cava"
}
</script>Google rich results this unlocks
Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.
- Google docsNo dedicated rich result (medical reference markup)
Common Vein mistakes
Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.
- 01
Vein used for an artery
Wrong"@type": "Vein", "name": "Aorta"RightArteries use the Artery type (also a Vessel subtype); Vein is specifically blood-to-heartDirection is load-bearing — veins return, arteries deliver. The two live on sibling Vessel subtypes precisely so the direction isn't lost.
- 02
drainsTo pointing at a capillary bed
WrongVein.drainsTo: capillary networkRightdrainsTo: the larger vein or chamber downstream (next-level vessel toward the heart)The drainage direction is heart-ward. Pointing at capillaries reverses the flow the field is meant to encode.
- 03
Collapsing tributary and regionDrained
WrongSame structures listed in bothRightregionDrained = the organ/body region; tributary = the named veins that feed inRegion is the territory; tributary is the named upstream vessel. A medical reference needs both to answer 'where from' and 'by which named vein'.
Schema properties in this example
About the example data
Inferior vena cava — entry in the Dunmore anatomy primer, the vessel anchoring the cardiovascular case studies Jane Xoo referenced in 1945.
Comments
Loading comments...