specialty

specialty · Not mentioned by Google

Appears in

• MedicalWebPage

What is it?

The medical specialty that a web page's content relates to. specialty classifies health pages by clinical domain: cardiology, oncology, dermatology, geriatrics, and so on. This helps search engines understand the medical context of the page and match it to specialty-specific queries.

Why this matters for AEO

When a user asks an AI engine about a condition, the AI benefits from knowing the medical specialty to provide contextually appropriate answers. A query about "atrial fibrillation treatment" should pull from cardiology-classified pages, not general wellness content. specialty gives AI engines a structured classification signal that improves answer relevance for clinical queries.

What the specs say

Schema.org: Specialty. One of the domain specialities to which this web page's content applies. schema.org/specialty

Google: Not mentioned. No dedicated Google structured data page exists for MedicalWebPage.

How to find your value

• Cardiovascular — https://schema.org/Cardiovascular
• Oncology — https://schema.org/Oncologic
• Dermatology — https://schema.org/Dermatology
• Geriatric — https://schema.org/Geriatric
• Psychiatric — https://schema.org/Psychiatric
• Musculoskeletal — https://schema.org/Musculoskeletal

Format and code

Use a URL reference to the schema.org Specialty enumeration value.

{
  "@context": "https://schema.org",
  "@type": "MedicalWebPage",
  "name": "Understanding Beta-Blockers",
  "specialty": "https://schema.org/Cardiovascular",
  "lastReviewed": "2024-01-15"
}

Multiple specialties:

{
  "@context": "https://schema.org",
  "@type": "MedicalWebPage",
  "name": "Diabetes and Heart Disease Connection",
  "specialty": [
    "https://schema.org/Cardiovascular",
    "https://schema.org/Endocrine"
  ]
}

Webflow implementation

Static pages

Add the specialty URL in the JSON-LD block in Page Settings > Custom Code:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MedicalWebPage",
  "name": "Health Topic",
  "specialty": "https://schema.org/Cardiovascular",
  "lastReviewed": "2024-09-15"
}
</script>

CMS template pages

Create a dropdown field with specialty values in your health articles CMS collection. Map it to the specialty property in the JSON-LD embed, prepending https://schema.org/ to the value.

In Schema HQ

Your specialty CMS field to the correct schema.org enumeration URL automatically. is mapped automatically

Real examples

Schema.org official MedicalWebPage example:

{
  "@context": "https://schema.org",
  "@type": "MedicalWebPage",
  "about": {
    "@type": "MedicalCondition",
    "name": "High Blood Pressure"
  },
  "audience": "https://schema.org/Patient",
  "lastReviewed": "2011-09-14",
  "name": "beta-blocker",
  "specialty": "https://schema.org/Cardiovascular"
}

eSEOspace healthcare schema guide:

{
  "@type": "MedicalWebPage",
  "specialty": "https://schema.org/Cardiology",
  "lastReviewed": "2024-01-15"
}

Related fields

• medicalAudience
• lastReviewed
• reviewedBy
• about

FAQ

What specialty values does schema.org define?

Schema.org defines a Specialty enumeration with values including Cardiovascular, Dermatology, Endocrine, Gastroenterologic, Geriatric, Gynecologic, Hematologic, Infectious, Musculoskeletal, Neurologic, Oncologic, Optometric, Otolaryngologic, Psychiatric, Pulmonary, Renal, Rheumatologic, and Toxicologic. Use these as URL values (e.g., https://schema.org/Cardiovascular).

Can a page have multiple specialties?

Yes. Use an array of specialty URLs for pages that span multiple clinical domains. A page about "diabetes complications on the heart" could list both Endocrine and Cardiovascular.

Is specialty only for MedicalWebPage?

specialty is defined on WebPage, not just MedicalWebPage. However, the medical specialty enumeration values are specific to health content. For non-medical specialties, the property has limited practical use.