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

Structured Data for Diagnostics Labs: MedicalTest, Price and Home Collection Service

How a diagnostics lab can model tests, panels, prices and home collection in schema.org, and which clinical properties to leave out so markup never reads as medical advice.

Structured Data for Diagnostics Labs: MedicalTest, Price and Home Collection Service

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:

  • DiagnosticLab descends from Organization, not LocalBusiness. For a lab with a street address and visiting hours, you also want a LocalBusiness subtype such as MedicalBusiness. 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.
  • MedicalTest has no price. Price belongs to an Offer, and offers hangs off a Service or Product, 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 with additionalProperty on some types, but there is no such property on Service, 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:

  1. The page as a MedicalWebPage (schema.org) with mainEntity pointing at the test, lastReviewed and reviewedBy if a pathologist or radiologist actually reviewed it, and medicalAudience.
  2. The test as a MedicalTest with name, alternateName for the names patients use, and a description in plain language.
  3. The service as a Service with serviceType, provider pointing at the lab, areaServed, offers and availableChannel. Link it to the test with isRelatedTo, a property schema.org defines for Service and Product.
  4. The lab as the @id of 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 price and describe the offer in visible text.
  • Home-collection fees are separate. Either model a second Offer for 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 eligibleRegion on each Offer. Do not publish a single price for a catalogue whose real price depends on where the sample is taken.
  • priceValidUntil only 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, signDetected or affectedBy unless the lab's pathologist or radiologist has approved the exact wording and the page shows the same content to patients.
  • Use usedToDiagnose sparingly, and only with a named MedicalCondition the 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.

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

Book my free audit

Fasting, sample type and report turnaround

These are the facts patients most want and the facts the vocabulary handles worst. Treat them in layers.

Visible text first. Preparation instructions (fasting duration, medicines to discuss with the doctor, sample type) must come from the lab's approved sample-collection guide. The page should name the source, say who approved it and show a review date. This content is a clinical instruction, so the marketing team transcribes it and does not edit it.

Markup second, and only where a property exists. There is no standard property for fasting. Put the instruction in the description of the Service or MedicalTest if the same text appears on the page. Do not invent fastingHours.

Turnaround as a service attribute. ServiceChannel has a processingTime property typed as a duration, which fits "report available within a stated time" when that time is a service level you actually control. If turnaround varies by test, location or sample batch, publish the range in visible text and leave the structured field empty rather than setting a number you cannot keep.

Report turnaround is the most common source of angry reviews for labs. A marked-up promise of "same day" that is wrong on some Saturdays is worse than no promise.

Modelling home collection

Home collection has three facts patients need: where, how to book and what it costs.

  • Where. Put areaServed on the Service. Use city-level City or AdministrativeArea entries. For pin codes, schema.org's DefinedRegion accepts postalCode and addressCountry. A list of several hundred pin codes belongs on the page and in a data feed, not in each test's markup.
  • How. Declare a ServiceChannel with serviceUrl (the booking page), servicePhone and availableLanguage. Attach it with availableChannel.
  • What it costs. A second Offer or visible text, as above.

Keep the channel distinct from the walk-in channel. A single test can have two channels: collection at the centre, with serviceLocation pointing at the branch, and collection at home. If one is unavailable for a test (for example, one that needs imaging equipment or on-site preparation), the markup for that test should not declare the home channel.

Accreditation and reviews

Accreditation claims should be specific and provable. Where the lab holds NABL accreditation, the visible claim should state the certificate, the scope and the site it covers, because accreditation applies to a defined scope and not to the brand as a whole. In markup, hasCertification is defined for Organization and Service, and hasCredential for Organization and Person. Use one consistently, and mark only the scope you can document.

Do not add aggregateRating to your own lab or your own services. Google's review snippet guidelines treat self-serving reviews for local businesses and organisations as ineligible. Reviews belong where independent third parties collect them.

An audit method for a lab site

You can test your own catalogue without a benchmark.

  1. Crawl and extract. Pull the structured data for every test and panel page. Count how many have a Service, an Offer and a MedicalTest, and how many have none.
  2. Reconcile price. Join extracted prices to the billing or LIS price master. Differences mean either the page or the master is wrong, and both are worth knowing.
  3. Reconcile collection areas. Compare declared areaServed against the cities where a phlebotomist can actually be dispatched.
  4. Read the Search Console query list. In the Performance report, filter to test names and to modifiers such as "price", "cost", "home collection" and "fasting". Note which pages rank for these and whether those pages show the information the query asks for.
  5. Run the Rich Results Test and the schema validator on a sample of each template, since the lab, the test and the panel pages are different templates.

If you are reaching for this level of detail on a multi-city chain, our schema markup service and the diagnostic centre marketing guide cover the surrounding page architecture. The advanced medical schema article deals with the generic entity patterns, so this piece does not repeat them.

Checklist

  • Lab declared once as MedicalBusiness plus DiagnosticLab (or your validated equivalent), referenced by @id everywhere.
  • Each test as a MedicalTest; each panel as a MedicalTestPanel with subTest.
  • A Service and Offer per test with price equal to the visible price, in INR.
  • No normalRange, diagnostic claims or interpretation unless approved by the clinical lead and shown on the page.
  • Fasting and preparation text sourced from the lab's sample-collection guide, with reviewer and date.
  • Home-collection areas, booking channel and fee declared separately from walk-in.
  • No self-published aggregateRating.
  • A monthly diff of markup prices against the price master.
Filed underdiagnostic lab schema markupMedicalTest schemaMedicalTestPanel schemapathology lab structured datahome collection schema markuplab test price 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 structured data for diagnostics labs medicaltest price and home.

Explore client work →