Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
SEO

MedicalCondition Markup for Patient Education: Signs, Risk Factors, Treatments

Model a condition page as a connected graph: MedicalCondition, reviewed MedicalWebPage, symptoms, tests and treatments, linked by @id to procedure and doctor pages in the same cluster.

MedicalCondition Markup for Patient Education: Signs, Risk Factors, Treatments

This post is for marketing and content teams at hospitals and specialty clinics who run a patient-education library: pages on diabetes, kidney stones, endometriosis, cataracts and the like. It is also for the developer who has been asked to "add schema" to those pages and wants a model more considered than one blob of JSON-LD per article.

The question it answers is how to describe a condition page as a small graph. The condition is a node. Its signs, risk factors, tests and treatments are linked nodes. The page is a node that is about the condition and was reviewed by a named clinician. The condition then connects to the procedure and doctor pages in the same cluster, so the site describes a coherent subject and not a pile of articles.

The syntax of JSON-LD is covered in our implementation guide, the complete guide and the advanced markup article. Here we focus on the model, which is where most condition markup goes wrong.

Set expectations before you build

Google's structured data gallery has no feature for medical conditions. Google's general guidelines also say structured data is not guaranteed to produce any display. So this markup is a structured statement of what the page says, not a ticket to a rich result.

Two rules still apply. Mark up only what readers can see, and treat the clinical content as needing review by the provider's clinicians before publication. Health pages are the kind Google's quality guidance calls YMYL, and the visible reviewer and review date are part of earning trust. The markup should repeat them, not create them.

What a MedicalCondition can say

MedicalCondition sits under MedicalEntity. Its own properties include the following, with the expected types as defined by schema.org.

PropertyExpected typePage section it should mirror
signOrSymptomMedicalSignOrSymptom"Signs and symptoms"
riskFactorMedicalRiskFactor"Who is at risk"
causeMedicalCause"Causes"
typicalTestMedicalTest"How it is diagnosed"
possibleTreatmentDrug, DrugClass, LifestyleModification or MedicalTherapy"Treatment options"
primaryPreventionMedicalTherapy"Prevention"
secondaryPreventionDrug, DrugClass, LifestyleModification or MedicalTherapy"Preventing recurrence"
possibleComplicationText"Complications"
associatedAnatomyAnatomicalStructure, AnatomicalSystem or SuperficialAnatomyWhere in the body
stageMedicalConditionStageStaging, if the page uses it
differentialDiagnosisDDxElementRarely needed on a patient page
expectedPrognosis, naturalProgression, pathophysiology, epidemiologyTextUsually leave out

The last row is deliberate. Prognosis language drifts into outcome promises, and pathophysiology is clinician-level content. A patient page that does not discuss them should not emit them.

From MedicalEntity the node also gets code (a MedicalCode, for an identifier from a recognised coding system if your clinical team supplies one), relevantSpecialty and guideline.

Respect the expected types

Here is a trap. possibleTreatment expects Drug, DrugClass, LifestyleModification or MedicalTherapy. A MedicalTherapy is a subtype of TherapeuticProcedure, which is a subtype of MedicalProcedure. The reverse does not hold. A surgical operation is a SurgicalProcedure, a sibling branch, not a MedicalTherapy.

Put differently, you cannot honestly list "knee replacement" under possibleTreatment if it is typed as a surgical procedure. You can list physiotherapy or radiotherapy there, because those are therapy subtypes, along with drugs and lifestyle changes. Whether a validator complains is a separate matter; the point is that the vocabulary says what it expects, and a model that ignores that makes consumers guess.

For surgical options, link at the page level instead.

  • The condition page mentions the procedure nodes that the page discusses.
  • Or significantLink points to the treatment page that covers it.
  • The treatment page, in turn, is about the procedure.

That keeps the condition's own properties valid and still creates the graph edge.

Model the page as a graph

Use a single @graph per page, with each node identified by a stable @id. The W3C JSON-LD 1.1 specification says a node is identified by @id and that a node object containing only an @id is a reference to a node described elsewhere in the document. That is exactly the tool you need.

A condition page should contain these nodes.

NodeType@id pattern (hypothetical domain)Key links
The pageMedicalWebPagehttps://www.example-hospital.in/conditions/type-2-diabetes/#webpageabout the condition, reviewedBy a clinician, lastReviewed, medicalAudience, mentions procedures
The conditionMedicalCondition.../conditions/type-2-diabetes/#conditionsignOrSymptom, riskFactor, typicalTest, possibleTreatment, relevantSpecialty
The reviewerPhysician.../doctors/dr-example/#physicianhospitalAffiliation, medicalSpecialty
The publisherHospital.../#hospitalReferenced as the publisher of the page

Use MedicalWebPage, which inherits reviewedBy and lastReviewed from WebPage and defines medicalAudience itself. Reference the reviewing doctor by @id so the same doctor node, defined fully on the doctor's profile page, is the one named here.

Build the nodes from the page's structure

A good condition page has headings. Each heading maps to one property, and each list item maps to one small node.

  • Each symptom in the "Signs and symptoms" list becomes a MedicalSignOrSymptom with a name. Keep the name as it appears on the page.
  • Each risk factor becomes a MedicalRiskFactor with a name.
  • Each test in the diagnosis section becomes a MedicalTest with a name.
  • Each therapy, drug class or lifestyle change in the treatment section becomes the right typed node with a name.

If a section is a paragraph, not a list, do not split it into guessed nodes. Either leave the property out or have an editor turn the paragraph into a list first. That is a content improvement for readers too, and it is the same logic as our patient education SEO work.

Do not add a list of symptoms that the page does not show. Do not state that a condition "cures" or that a treatment "works". Descriptions of urgent signs, such as when to seek emergency care, must use wording approved by the clinical team and should be visible on the page before they appear in markup.

Want this applied to your practice? Get a free seo audit.

Book my free audit

Connect the cluster

Think of the cluster as three layers: condition pages, procedure and treatment pages, and doctor pages. The graph edges run as follows.

  1. Condition to procedure. Condition page mentions or significantLinks procedure pages. The procedure page is about its MedicalProcedure node. The hospital's availableService references the same procedure node by @id.
  2. Condition to specialty. Both the condition node and the doctors' nodes use relevantSpecialty and medicalSpecialty with the same MedicalSpecialty value, so a specialty links them.
  3. Condition to doctor. The condition page names its reviewer. Other doctors who treat the condition appear as links in visible text on the page, and each doctor page lists the conditions they manage in visible text. On the doctor node, knowsAbout can point to the condition. It is defined on Organization, so it is available to Physician, and it accepts text, a Thing or a URL.

The result is a set of internal links in the visible page and a matching set of identifier links in the markup. Our condition and treatment SEO page explains the page cluster; the graph follows it.

A worked graph, clearly hypothetical

Imagine a kidney stones page at a mid-sized hospital in Jaipur. The page node is a MedicalWebPage that is about the condition node and reviewedBy the urologist's Physician node. The condition node lists three signs taken from the page's bullet list, two risk factors, and one test, an imaging scan the page names. Under treatments, the page discusses fluids and diet changes, medication, and a surgical option.

The first two are valid under possibleTreatment, as a LifestyleModification and a Drug or DrugClass. The surgical option is not a MedicalTherapy, so the page node mentions the lithotripsy procedure node, whose own page is about it. The hospital node then lists that procedure in availableService. A reader moving through the site follows ordinary links: condition, treatment page, doctor. A machine reading the graph finds the same path through identifiers.

The test of success is simple. Delete the visible prose and read the graph alone: it should still tell a coherent story that matches the page. Then do the reverse and read the page alone. If the two disagree, the page or the markup is wrong.

Maintenance and review

Add three columns to the content register: the condition node @id, the clinician who reviewed the page, and the date of last clinical review. When any of them changes, regenerate the markup. Set a review interval that the clinical team agrees to, so a page is not marked lastReviewed once and left for years.

Check what happens when a doctor leaves. Their profile may be removed while condition pages still name them as reviewer. Decide in advance whether a page needs re-review with a new reviewer or can keep the old name with its original date, and make the template handle a missing reviewer by omitting the property, not by emitting a broken reference.

Failure modes

  • Duplicated nodes with different values. The condition is defined on three pages with three sets of symptoms. Define a node fully in one place, and reference it elsewhere.
  • Reviewer drift. The visible page says "Reviewed by Dr A, March 2026", the markup says "Dr B". Generate both from one field.
  • Symptom stuffing. Adding every long-tail symptom for SEO. A node should match the visible content.
  • Orphaned nodes. A MedicalCondition with no page node that is about it. The graph works only if the nodes are attached.
  • Treatment promises. Using possibleTreatment to imply a cure. The property says a treatment is possible, not that it works.

Where to start

Pick one condition cluster, for example diabetes with its tests, specialists and one procedure or therapy page. Draw the graph on paper first: condition, page, reviewer, related procedures, doctors. Agree the @id convention. Then ask the content team to confirm that each heading in the page is a list that can be turned into nodes. Generate the markup from CMS fields, validate with the Schema Markup Validator and the Rich Results Test, and have the clinical reviewer sign off the visible page, which is what the markup describes. Once one cluster is clean, the schema markup service is a template for the rest.

Filed underMedicalCondition schemacondition page structured dataschema markup patient educationsignOrSymptom schemaMedicalWebPage reviewedByhealthcare content cluster schema

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 15 pages

The Patient Acquisition Blueprint

A 90-day plan from first search to booked appointment.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free seo audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · Healthcare websites

Work relevant to medicalcondition markup for patient education signs risk factors.

Explore client work →