A diagnostics lab website is a catalogue with a booking button. It has hundreds of test pages, a handful of panels, a price for each, a home-collection promise and a stack of preparation instructions. Most of that is exactly what structured data was invented to describe, and most labs mark up almost none of it beyond a generic LocalBusiness block.
This article is for SEO leads and developers at pathology and radiology businesses, and for agencies that build for them. It assumes you already use JSON-LD and have read the general material on healthcare schema markup. What follows is narrower: how to model the test catalogue, prices, panels, home collection and report turnaround, and where to stop so the markup never reads like clinical advice.
A caution up front. Schema.org's medical types are descriptive vocabulary. Google does not offer a rich result for MedicalTest, so this work will not produce a new snippet by itself. What it does is make entities, prices and service areas unambiguous for crawlers and for the AI systems that read pages, and it forces your team to agree one clean version of each fact.
What the vocabulary gives you, and what it does not
The schema.org DiagnosticLab type is a MedicalOrganization with an availableTest property pointing at MedicalTest. MedicalTest itself is a MedicalEntity, a descriptive type with properties such as usedToDiagnose, normalRange, signDetected, usesDevice and affectedBy. Three structural facts shape everything else:
DiagnosticLabdescends fromOrganization, notLocalBusiness. For a lab with a street address and visiting hours, you also want aLocalBusinesssubtype such asMedicalBusiness. Schema.org allows multiple types, and Google's local business documentation shows type arrays, so["MedicalBusiness", "DiagnosticLab"]is a reasonable declaration. Validate it and keep it if your tooling accepts it.MedicalTesthas no price. Price belongs to anOffer, andoffershangs off aServiceorProduct, not off a medical entity.- There is no property for fasting duration, sample type, container colour or report turnaround on
MedicalTest. Schema.org lets you extend withadditionalPropertyon some types, but there is no such property onService, and inventing property names means search engines ignore them.
So the model has two layers. The descriptive layer says what the test is. The commercial layer says what you sell, at what price, through which channel and to whom. Keep them separate and link them.
A graph for one test page
For a single test page, build a small graph with stable @id values rather than nesting everything:
- The page as a
MedicalWebPage(schema.org) withmainEntitypointing at the test,lastReviewedandreviewedByif a pathologist or radiologist actually reviewed it, andmedicalAudience. - The test as a
MedicalTestwithname,alternateNamefor the names patients use, and a description in plain language. - The service as a
ServicewithserviceType,providerpointing at the lab,areaServed,offersandavailableChannel. Link it to the test withisRelatedTo, a property schema.org defines forServiceandProduct. - The lab as the
@idof the organisation defined once in the site-wide graph.
This is more work than a flat block, but it scales. A catalogue of 600 tests becomes 600 small nodes that all reference the same lab node, rather than 600 copies of the lab's address.
Price: the part that is easiest to get wrong
An Offer needs price, priceCurrency (INR) and, where known, availability. Several rules keep the markup honest:
- The price in markup must equal the price on the page. Google's structured data policies require markup to describe content users can see. A price that exists only in JSON-LD is a policy problem as well as a trust one.
- Do not mark up a strike-through "was" price as the current price. If you show a discount, make the discounted price the
priceand describe the offer in visible text. - Home-collection fees are separate. Either model a second
Offerfor the collection fee or state it in visible text beside the test price. Do not fold it into the test price silently. - Price differs by city? Use one page per priced scope, or put
eligibleRegionon eachOffer. Do not publish a single price for a catalogue whose real price depends on where the sample is taken. priceValidUntilonly when a date is real. An expired date on a permanent price creates a stale warning for no benefit.
For panels, use MedicalTestPanel with subTest pointing at each component MedicalTest. The panel gets its own Service and Offer. A hypothetical "basic health check" panel with eight components is one MedicalTestPanel, eight MedicalTest references and one price, not eight prices.
What not to mark up: the clinical-advice line
The clinical properties are the risky ones. normalRange invites you to publish a reference range. Reference ranges depend on the method, the analyser, the patient's age and sex, and often the lab itself. A range copied into markup is a clinical statement made without context, repeated in machine-readable form. Similarly usedToDiagnose and signDetected make claims about what a result means.
A workable policy:
- Do not populate
normalRange,signDetectedoraffectedByunless the lab's pathologist or radiologist has approved the exact wording and the page shows the same content to patients. - Use
usedToDiagnosesparingly, and only with a namedMedicalConditionthe clinical lead approved. "Blood sugar testing" does not need it. - Write test descriptions in terms of what the test measures and how a sample is taken, not what a result means for you.
- Put a line on the page that results must be interpreted by a doctor, and have the clinical lead own that wording.
Google's guidance on creating helpful, reliable content asks who wrote a page and why you should trust it. For YMYL pages, that question is better answered by a visible reviewer line than by deeper schema.




