MedicalCondition Schema

Element Code: RI-026

What MedicalCondition schema actually is

MedicalCondition is a type in the schema.org health-lifesci extension. It is built to describe a specific disease, disorder, injury, or syndrome in a machine-readable way: what it is called, what part of the body it affects, what causes it, what signs and symptoms show up, how it is diagnosed, and how it is treated. Per schema.org, it sits alongside related types like MedicalSignOrSymptom, MedicalTherapy, and MedicalRiskFactor, all part of the same medical vocabulary originally built with Health on Schema.org (a joint effort involving Google, Mayo Clinic, and others).

This is not a cosmetic tag. It is a structured summary of the same information a doctor would want on an intake form: name, cause, associated anatomy, symptoms, treatment options, risk factors, and standardized medical codes. When you mark a page up correctly, you are telling crawlers and language models, in a format they can parse without guessing, "this page is specifically about condition X, and here is the clinical shape of it."

Why it matters for SEO, crawling, and AI visibility

Health content is squarely YMYL: Your Money or Your Life. Per Google's Search Quality Rater Guidelines, YMYL pages get evaluated against a stricter E-E-A-T bar (Experience, Expertise, Authoritativeness, Trustworthiness) because bad medical information can cause real harm. Structured data does not replace E-E-A-T, and it will not fix a page with no clinical review or no named author. What it does is act as a trust and clarity signal layered on top of good content: it tells search systems the page is organized the way a legitimate reference source organizes disease information, not the way a thin affiliate page throws words at a topic.

There is no dedicated Google rich result snippet type for a bare MedicalCondition block the way there is for Recipe or FAQ. What it does influence:

• Knowledge panel eligibility. Google has historically pulled MedicalCondition-style data (symptoms, related conditions) into health knowledge panels for well-established, high-authority sources.
• AI Overview and answer engine citation. Generative answer systems favor pages where facts are already segmented (symptom vs. cause vs. treatment) because it reduces the model's own extraction risk. A page with clean MedicalCondition JSON-LD gives an LLM a pre-parsed answer key instead of a wall of prose to interpret.
• Entity disambiguation. If a condition has a common name and several clinical synonyms, alternateName and code (ICD-10, UMLS, etc.) help search engines tie your page to the correct medical entity instead of a loosely related one.
• Crawl efficiency and content classification. Structured data gives Googlebot a fast, unambiguous read on topical intent, which matters when a domain publishes a large volume of condition pages that could otherwise look templated or thin.

None of this means "add the schema and rankings go up." It means: on a page that already has solid, reviewed medical content, this markup removes ambiguity for the systems deciding whether to trust and surface it.

How to detect whether a page has or needs this schema

Do not guess. Check directly:

• View-source / Inspect Element: search the raw HTML for application/ld+json and "@type": "MedicalCondition". If it is only in the rendered DOM and not the source, confirm it is not stripped by server-side rendering issues.
• Google's Rich Results Test: paste the URL in and check what structured data Google's parser actually extracts. This tells you if the JSON-LD is valid and readable, not just present.
• Schema Markup Validator (validator.schema.org): the vendor-neutral schema.org validator. Useful for checking full property coverage against the spec, since Google's tool only flags what it currently supports for rich results.
• Search Console: check the Enhancements section and any structured data reports for parsing errors across the site, plus Page Indexing to confirm the page is actually being crawled and indexed in the first place.
• Screaming Frog: run a crawl with structured data extraction enabled (Configuration > Spider > Extraction > Structured Data) to pull every page's JSON-LD types in bulk. This is the fastest way to audit a site with hundreds of condition pages and find which ones are missing MedicalCondition markup, have malformed JSON, or have duplicate/conflicting schema blocks.

If a page is clearly "about" a single medical condition (has a name in the H1, describes symptoms, causes, or treatment), and none of the above tools find a MedicalCondition block, that is a real gap, not a nice-to-have.

MedicalCondition property map

Below is a diagram of how the core properties relate to the condition entity. It mirrors how you should structure the JSON-LD: one root condition object, with arrays or nested objects for anatomy, symptoms, treatments, and risk factors.

{
  "@context": "https://schema.org",
  "@type": "MedicalCondition",
  "name": "Type 2 Diabetes",
  "alternateName": ["T2D", "Adult-onset diabetes"],
  "associatedAnatomy": {
    "@type": "AnatomicalStructure",
    "name": "Pancreas"
  },
  "cause": {
    "@type": "MedicalCause",
    "name": "Insulin resistance combined with reduced insulin secretion"
  },
  "riskFactor": [
    { "@type": "MedicalRiskFactor", "name": "Obesity" },
    { "@type": "MedicalRiskFactor", "name": "Family history of diabetes" },
    { "@type": "MedicalRiskFactor", "name": "Sedentary lifestyle" }
  ],
  "signOrSymptom": [
    { "@type": "MedicalSignOrSymptom", "name": "Increased thirst" },
    { "@type": "MedicalSignOrSymptom", "name": "Frequent urination" },
    { "@type": "MedicalSignOrSymptom", "name": "Fatigue" }
  ],
  "possibleTreatment": [
    { "@type": "MedicalTherapy", "name": "Metformin" },
    { "@type": "MedicalTherapy", "name": "Lifestyle and dietary modification" }
  ],
  "epidemiology": "Accounts for the large majority of diagnosed diabetes cases worldwide, per World Health Organization data.",
  "code": {
    "@type": "MedicalCode",
    "codingSystem": "ICD-10",
    "codeValue": "E11"
  }
}