MedicalConditionStage
MedicalConditionStage is a MedicalIntangible used on MedicalCondition.stage. Properties: stageAsNumber (Number — 1, 2, 3, 4) and subStageSuffix (Text — "A", "B", "IIIc"). Inherits name and description for prose detail.
Full example of schema.org/MedicalConditionStage 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": "MedicalConditionStage",
"name": "Stage IIB (TNM: T2N1M0)",
"stageAsNumber": 2,
"subStageSuffix": "B"
}
</script>Minimal valid version
The smallest markup that still produces a valid MedicalConditionStage 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": "MedicalConditionStage",
"stageAsNumber": 2,
"subStageSuffix": "B"
}
</script>Google rich results this unlocks
MedicalConditionStage 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). MedicalConditionStage becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.
Common MedicalConditionStage 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
stage as a string 'IIB'
Wrong"stage": "IIB"RightMedicalConditionStage node with stageAsNumber + subStageSuffixThe structured form lets staging-aware consumers sort and compare; free text is opaque.
Schema properties in this example
About the example data
Stage IIB TNM for the Dunmore Archive's oncology case studies.
Comments
Loading comments...