XooCode(){

MedicalEnumeration

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

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

schema.org/MedicalEnumeration
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Drug",
  "name": "Atorvastatin",
  "prescriptionStatus": "https://schema.org/PrescriptionOnly",
  "pregnancyCategory": "https://schema.org/FDAcategoryX"
}
</script>

Minimal valid version

The smallest markup that still produces a valid MedicalEnumeration 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/MedicalEnumeration (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MedicalEnumeration"
}
</script>

Google rich results this unlocks

MedicalEnumeration 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). MedicalEnumeration becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common MedicalEnumeration 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

    Typing an entity as bare MedicalEnumeration

    Wrong
    "@type": "MedicalEnumeration"
    Right
    Use the specific subtype (MedicalSpecialty, MedicalStudyStatus, etc.)

    Like its parent Enumeration, MedicalEnumeration is never the right type on a value — always reach for the specific subtype.

About the example data

Parent type for every clinical enum Jane Xoo's Dunmore Archive entries reference.

Comments

Loading comments...

Leave a comment