XooCode(){

LymphaticVessel

LymphaticVessel is an AnatomicalStructure subtype (through Vessel) for vessels that carry lymph toward the heart. The three direct properties anchor the vessel in its drainage path: where it starts, what it drains, where it ends.

Full example of schema.org/LymphaticVessel json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional
schema.org/LymphaticVessel
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LymphaticVessel",
  "name": "Thoracic duct",
  "originatesFrom": { "@type": "AnatomicalStructure", "name": "Cisterna chyli (L1–L2)" },
  "regionDrained": [
    { "@type": "AnatomicalStructure", "name": "Lower limbs" },
    { "@type": "AnatomicalStructure", "name": "Abdomen" },
    { "@type": "AnatomicalStructure", "name": "Left thorax" },
    { "@type": "AnatomicalStructure", "name": "Left head and neck" },
    { "@type": "AnatomicalStructure", "name": "Left upper limb" }
  ],
  "runsTo": { "@type": "AnatomicalStructure", "name": "Left venous angle (junction of left subclavian and internal jugular veins)" },
  "partOfSystem": { "@type": "AnatomicalSystem", "name": "Lymphatic system" }
}
</script>

Direct properties (3)

  • originatesFrom: Vessel — the cistern or confluence the vessel begins at.
  • regionDrained: AnatomicalStructure or AnatomicalSystem — the body region drained.
  • runsTo: Vessel — the downstream vessel the lymph enters (typically a venous angle).

Minimal valid version

The smallest markup that still produces a valid LymphaticVessel 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.

schema.org/LymphaticVessel (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LymphaticVessel",
  "name": "Thoracic duct"
}
</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.

  • No dedicated rich result (medical reference markup)
    Google docs

Common LymphaticVessel 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.

  1. 01

    LymphaticVessel for a blood vessel

    Wrong
    "@type": "LymphaticVessel" on an artery or vein
    Right
    Vein or Artery for blood vessels; LymphaticVessel specifically for lymph

    Lymph and blood travel in anatomically separate systems; the types exist to keep that distinction machine-readable.

  2. 02

    runsTo pointing at a lymph node

    Wrong
    runsTo: lymph node
    Right
    runsTo: the downstream vessel or venous angle

    Lymph nodes are way-stations along the path, not the terminus. runsTo is designed for the next-vessel relationship; node relationships belong on other fields (e.g. using subStructure).

  3. 03

    Omitting regionDrained on a large duct

    Wrong
    Thoracic duct with no regionDrained
    Right
    Include the full drainage territory — the pedagogical point of a lymphatic reference is the catchment

    Without regionDrained, the page gives no sense of what the duct actually does. The catchment is the whole reason for documenting a lymphatic vessel in structured data.

Schema properties in this example

LymphaticVesselAnatomicalStructurenameoriginatesFromregionDrainedrunsTopartOfSystemAnatomicalSystem

About the example data

Thoracic duct — the largest lymphatic vessel, cross-referenced in the Dunmore anatomy primer against the 1945 post-war lymphatic-drainage teaching material.

Comments

Loading comments...

Leave a comment