XooCode(){

Muscle

Muscle is an AnatomicalStructure subtype for contractile tissue. It carries the anatomy-primer fields a medical reference page needs: where the muscle attaches, what it does, which nerve drives it, which vessel feeds it.

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

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

Highlight legend:Required by GoogleRecommendedOptional
schema.org/Muscle
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Muscle",
  "name": "Biceps brachii",
  "muscleAction": "Flexion of the forearm at the elbow and supination of the forearm.",
  "insertion": { "@type": "AnatomicalStructure", "name": "Radial tuberosity and bicipital aponeurosis" },
  "antagonist": { "@type": "Muscle", "name": "Triceps brachii" },
  "nerve": { "@type": "Nerve", "name": "Musculocutaneous nerve" },
  "bloodSupply": { "@type": "AnatomicalStructure", "name": "Brachial artery" },
  "partOfSystem": { "@type": "AnatomicalSystem", "name": "Musculoskeletal system" }
}
</script>

Direct properties (5)

  • insertion: AnatomicalStructure — the distal attachment point (the moving end).
  • muscleAction: Text — the movement performed ("Flexion of the forearm at the elbow").
  • antagonist: Muscle — the muscle that opposes the action.
  • nerve: Nerve — the motor supply.
  • bloodSupply: Vessel — the artery that feeds the muscle.

Inherited from AnatomicalStructure: connectedTo, partOfSystem, subStructure. Use partOfSystem to point at the musculoskeletal AnatomicalSystem. Origin attaches via inherited subStructure / partOfSystem or — more commonly in clinical notes — as free text inside description.

Minimal valid version

The smallest markup that still produces a valid Muscle 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/Muscle (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Muscle",
  "name": "Biceps brachii",
  "muscleAction": "Flexion of the forearm at the elbow."
}
</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 Muscle 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

    muscleAction as a one-word verb

    Wrong
    "muscleAction": "Flex"
    Right
    Full clause: "Flexion of the forearm at the elbow and supination of the forearm"

    A single verb is ambiguous — flex what, where? Anatomy references spell out the movement, joint, and any secondary action.

  2. 02

    nerve as a string

    Wrong
    "nerve": "Musculocutaneous"
    Right
    Nerve node with name

    Typed Nerve nodes let knowledge graphs join muscles to their innervation; a bare string is dead text.

  3. 03

    insertion and origin swapped

    Wrong
    Insertion on the proximal attachment, origin on the distal
    Right
    Origin = proximal / fixed; insertion = distal / moving

    Reversing them inverts the biomechanics — the whole point of the muscle fields in a teaching reference is clear direction of pull.

Schema properties in this example

MuscleAnatomicalStructurenamemuscleActioninsertionantagonistnerveNervebloodSupplypartOfSystemAnatomicalSystem

Also mentioned in 1 other example

Muscle also appears in Nerve. See the full Muscle schema page for every reference.

About the example data

Biceps brachii as rendered in the Dunmore 1945 anatomy primer — the teaching reference Jane Xoo paired with her paediatric physical-exam workbook.

Comments

Loading comments...

Leave a comment