KLYR Media Logo
HomeBlogMedical Organization Schema: What to Mark Up and How
Healthcare Marketing
November 18, 2026
11 min read

Medical Organization Schema: What to Mark Up and How

How MedicalOrganization, Physician and Pharmacy schema work, which properties to add for a clinic, doctor or pharmacy, and how to keep the markup accurate.

Medical Organization Schema: What to Mark Up and How

Medical Organization Schema: What to Mark Up and How

Clinic administrator updating website schema markup

Medical organization schema is a block of JSON-LD code on your website that tells Google, in a format machines read, who you are: a clinic, a pharmacy, a physician’s office or a hospital. Use the most specific type that fits (Pharmacy, Physician, IndividualPhysician, MedicalClinic), give each location and each doctor its own entity, and make every value match what patients can see on the page. Do that and Google has far less guessing to do about your practice. Skip it, and you leave your identity to whatever Google can infer from your copy.

This guide is for owners and administrators of independent pharmacies, clinics and practices. You do not need to write code yourself, but you do need to know what should be in it.

Klyrmedia
Make Your Healthcare Website Easier to Understand
Klyrmedia builds healthcare websites and supports local SEO, helping practices strengthen their online presence with healthcare-focused digital services.
Visit

TL;DR

  • MedicalOrganization is the schema.org parent type for hospitals, clinics, pharmacies and physician offices. Pick the most specific child type that matches you.
  • Physician and IndividualPhysician describe the doctor. MedicalOrganization types describe the place. Link the two with practicesAt, member and shared @id values.
  • Every value in your markup has to match the visible page. Never put patient information in it.
  • Validate before you publish, then re-check after every site change. Schema helps Google understand you. It does not guarantee a rich result or a ranking.
  • Multi-location groups need one entity per location, not one blob on the homepage.

Table of Contents

What MedicalOrganization schema actually is

Schema.org is the shared vocabulary that Google and other search engines read. It defines MedicalOrganization as a medical organization, physical or not, such as a hospital, institution or clinic. Google’s August 2026 usage data on that page puts it in use on 10,000 to 100,000 domains, so you are not early adopting anything.

The type itself adds three properties of its own:

  • healthPlanNetworkId: the name or ID of an insurance network you participate in.
  • isAcceptingNewPatients: true or false.
  • medicalSpecialty: what you practice.

It also inherits the ordinary Organization properties: name, URL, logo, address, telephone and so on. Those inherited ones do most of the identity work.

The practical value is disambiguation. There may be three “Main Street Family Care” listings in the country. Structured data, together with a consistent name, address and phone number, helps Google tell yours from the others. Google’s own Organization documentation says the markup helps it understand administrative details about an organization and that some properties, such as the logo, can influence what shows in Search results and the knowledge panel.

One more point from Google’s page: no Organization property is strictly required. The advice is to add as many relevant ones as apply, and to use the most specific subtype of Organization that matches you.

Which type fits your practice

This is where most healthcare sites go wrong. They paste a generic Organization or LocalBusiness block and stop. Here is how to choose.

You are Primary type Notes
A hospital or health system Hospital Child of MedicalOrganization.
A clinic or group practice MedicalClinic Use one entity per location.
A physician’s office Physician or PhysiciansOffice Schema.org says Physician covers an individual physician or a physician’s office considered as a MedicalOrganization.
A single doctor IndividualPhysician A person-level page, such as a provider bio.
An independent pharmacy Pharmacy Sits under both MedicalOrganization and MedicalBusiness.
The parent brand of several sites MedicalOrganization A homepage that represents the whole group.

Schema.org’s Pharmacy type is a child of both LocalBusiness (through MedicalBusiness) and MedicalOrganization. For an independent pharmacy that is useful: you get the local business fields patients rely on, such as hours and address, and the medical identity.

The Physician type is defined as an individual physician or a physician’s office considered as a MedicalOrganization, and it has two more specific children: IndividualPhysician and PhysiciansOffice. That is the answer to the question of when to use Physician markup instead of MedicalOrganization. Use Physician for the doctor and the office as a practice entity, use the broader MedicalOrganization only when nothing more specific fits, such as an umbrella brand.

Physician and doctor schema: the properties that matter

For a provider bio page, the IndividualPhysician type offers these fields worth filling in:

  • name, image and url of the provider page.
  • medicalSpecialty: the specialty, from schema.org’s MedicalSpecialty list.
  • practicesAt: the MedicalOrganization where the physician practices.
  • hospitalAffiliation: a Hospital, if the physician has one.
  • availableService: a MedicalProcedure, MedicalTest or MedicalTherapy the physician offers.
  • occupationalCategory: the job category.
  • usNPI: the 10-digit National Provider Identifier that the Centers for Medicare and Medicaid Services issues to U.S. health care providers.

The NPI is the one most practices forget. It is public, it is unique to the provider, and it ties your markup to a real-world record. If a provider’s NPI is already shown on your site or in a public directory, adding it to the markup is a clean way to say “this is the same person.”

A simple example

Here is the shape of a physician entity connected to a clinic. Yours will have more fields, and every value must be replaced with your real, visible information.

{
  "@context": "https://schema.org",
  "@type": "IndividualPhysician",
  "@id": "https://www.example-clinic.com/providers/jane-doe#physician",
  "name": "Jane Doe, MD",
  "medicalSpecialty": "PrimaryCare",
  "usNPI": "1234567890",
  "practicesAt": {
    "@id": "https://www.example-clinic.com/locations/downtown#clinic"
  }
}

And the clinic it points to:

{
  "@context": "https://schema.org",
  "@type": "MedicalClinic",
  "@id": "https://www.example-clinic.com/locations/downtown#clinic",
  "name": "Example Clinic, Downtown",
  "url": "https://www.example-clinic.com/locations/downtown",
  "telephone": "+1-555-555-0100",
  "isAcceptingNewPatients": true,
  "medicalSpecialty": "PrimaryCare",
  "member": {
    "@id": "https://www.example-clinic.com/providers/jane-doe#physician"
  }
}

The @id values are the glue. When the clinic’s member and the physician’s practicesAt point at the same identifiers, you have told Google the relationship in both directions without repeating yourself.

Multi-location practices: one entity per location

If you run three clinics, a single block on the homepage with all three addresses stuffed in is the wrong move. Do this instead:

  1. Give each location its own page and its own entity with its own @id, address, phone number and hours.
  2. Use one parent MedicalOrganization for the brand, and link locations to it.
  3. For a physician who sees patients at more than one site, use practicesAt as an array of locations rather than a single employer.
  4. Keep the reference two-way: member on the organization, and the physician’s side pointing at the same @id.

The weak point in multi-location setups is drift. A location moves, a phone number changes, a provider leaves, and the markup keeps saying the old thing. If your listings, your electronic medical record scheduling and your site fall out of step, patients call the wrong number and book the wrong place. We cover that problem in syncing multi-location clinic listings to your EMR, and the same discipline applies to your markup.

Keep it truthful and HIPAA-safe

Google’s general structured data guidelines say markup must represent the visible content of the page. Don’t mark up content that readers can’t see, and don’t mark up anything irrelevant or misleading. Mark up “accepting new patients” only if your page says so. List a specialty only if you actually practice it.

There is a second rule that is ours, not Google’s: markup is public. Anyone can read it in the page source. So it describes your practice, your providers and your services. It never contains anything about an individual patient. Not a name, not an appointment, not a condition. Schema.org’s health and medical documentation is explicit that this vocabulary is built for web discovery and is not designed for clinical markup or clinical data exchange. That is exactly the line to hold.

FAQ markup is where practices most often drift into risky territory, because answers can sound like individual advice. Keep them general, educational and consistent with the page. We walk through that in our guide to HIPAA-safe medical FAQ schema.

Keep it truthful and HIPAA-safe

How to add and test it

The process is short. The discipline is in the checking.

  1. Inventory what is visible. List the name, address, phone, hours, providers and services that actually appear on each page.
  2. Choose the types. Use the table above. One entity per location, one per provider.
  3. Write JSON-LD. It goes in the page’s HTML, usually in the head. Most healthcare sites run on a CMS, and a plugin or template field can output it, but check what it generates. Default output is often a thin LocalBusiness block.
  4. Validate it. Google recommends running pages through its Rich Results Test and fixing critical errors, then using the URL Inspection tool in Search Console to confirm Google can reach the deployed page and that nothing blocks it, per its Organization guidance.
  5. Fix the usual errors. The common ones are mismatched phone numbers, a duplicate entity with conflicting data from a plugin and a theme, markup for a provider who left, and fields that are empty or hold placeholder text.
  6. Re-check after changes. Redesigns, plugin updates and new locations are when markup quietly breaks.

A note on the testing tools: Google’s Rich Results Test only reports on the types Google supports for rich results. A type like MedicalClinic may carry valid, useful properties that still produce no rich result preview. That is normal, and it is not a failure.

What schema will and won’t do

Be realistic. Schema is a clarity tool. Google says Organization markup helps it understand and disambiguate an organization and can influence visual elements such as the logo and the knowledge panel, and it also says structured data features are not guaranteed to appear. Markup will not replace good pages, a complete Google Business Profile, strong reviews or local relevance.

Where it pays is the combination. Clean markup supports a site that already says clearly who you are, what you treat, where you are and how to book. When your markup, your visible page and your business listings all agree, you give search engines fewer reasons to hesitate. If you are deciding what to do first, our guide on which healthcare schema to add first puts the types in priority order, and your Google Business Profile attributes should say the same things your markup says.

A pre-launch checklist

  • Each location has its own page, its own entity and its own @id.
  • Name, address and phone match your site footer, your Google Business Profile and your EMR scheduling.
  • Each provider has a page, a specialty and, where public, an NPI.
  • isAcceptingNewPatients matches what the page says today.
  • No patient information anywhere in the code.
  • Only one source of markup per page, so a plugin and a theme don’t output competing versions.
  • The deployed URL passes validation and is reachable by Google.

Where this fits in your bigger marketing picture

Schema is one layer of a healthcare SEO program, along with page content, local listings, speed, reviews and service area pages. If you are building out location pages, see how we think about service area pages for healthcare.

If you would rather not hand-edit JSON-LD across a dozen provider pages and several locations, that is work we take on as part of our Healthcare SEO Service, and our HIPAA Web Design Service builds sites with compliance considered from day one.

Klyrmedia

Most independent pharmacies and clinics we talk to have the same story. The site looks fine. Nobody has looked at what it says to Google. A generic plugin spits out a thin LocalBusiness block, the phone number differs from the one on the Business Profile, and a provider who left two years ago is still listed.

That is not a coding problem. It is a consistency problem, and it leaks patients quietly. The patient who calls a dead number never shows up in a report.

We work only in healthcare, so we start from the real constraints: HIPAA, multiple providers, locations that change, and front desks with no time to maintain code. Our view is that schema should be built once, tied to the same facts your site and listings already state, and checked whenever something changes. That is how we approach it for the clinics and pharmacies we work with.

Opinly

FAQ

What is the difference between MedicalOrganization and Physician schema?

MedicalOrganization is the broad type for hospitals, clinics and similar organizations. Physician is a more specific type for an individual physician or a physician’s office, and it adds fields such as usNPI and hospitalAffiliation. Use the most specific type that fits, and connect the two with shared @id values.

Should an independent pharmacy use MedicalOrganization?

Use the Pharmacy type. Schema.org places it under both MedicalOrganization and LocalBusiness through MedicalBusiness, so it carries the medical identity and the local details like hours and address.

Does physician schema markup improve my rankings?

It helps Google understand who you are and who your providers are. Google does not promise any specific rich result from this markup, so treat it as a foundation that supports your pages and listings rather than a ranking switch.

How do I mark up a doctor who works at several locations?

Give the physician a single entity with a stable @id, and list each location in practicesAt. Each location should be its own MedicalOrganization entity, and the organization side should reference the physician as a member using the same @id.

Can I include patient reviews or details in my markup?

Keep patient information out of markup entirely, since the code is public. Only mark up content that is visible on the page and genuinely represents it, as Google’s structured data guidelines require.

Sources

Share this article: