VitalSign

VitalSign is a MedicalSign subtype. Vital signs are measures of various physiological functions in order to assess the most basic body functions.

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

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

schema.org/VitalSign

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "VitalSign",
  "name": "Example VitalSign"
}
</script>

Minimal valid version

The smallest markup that still produces a valid VitalSign 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/VitalSign (minimal)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "VitalSign",
  "name": "Example"
}
</script>

Google rich results this unlocks

VitalSign is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). VitalSign becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common VitalSign 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
Using bare MedicalSign instead of the specific VitalSign subtype
Wrong
```
"@type": "MedicalSign"
```
Right
```
"@type": "VitalSign"
```
Specific subtypes carry domain context consumers use; reach for the narrowest applicable type.

Schema properties in this example

VitalSign MedicalSign

About the example data

Reference entry in the Xoo Code schema.org catalogue.

Comments

Loading comments...