Skip to content

Healthcare Schema Markup: Boost Your Medical SEO

Juwel Rana

By Juwel Rana · CEO & Founder

1,024 views
Close-up of a tablet displaying Google's search screen, emphasizing technology and internet browsing.

A practice website that tells Google nothing beyond its text leaves search engines guessing who the doctor is, what they treat and where they see patients. Healthcare schema markup SEO work fixes that by labelling those facts in a format machines read directly, and the vocabulary for doing it is already published for free.

Most of the effort belongs in a small number of types, and a couple of once-popular tactics have stopped working. Here's what to add, what to skip, and how to check it.

Why healthcare schema markup matters for medical SEO

Schema markup is structured data that describes a page's content using the Schema.org vocabulary, and Google recommends writing it as JSON-LD rather than weaving it through your HTML. It doesn't change what patients see. It gives search engines a labelled version of the same facts: this is a physician, this is their specialty, this is the office address.

Google is blunt about the limits. Google's structured data guidelines say valid markup makes a page eligible for a feature but that Google does not guarantee it will show up in search results.

So treat schema as groundwork, not a ranking switch. It earns its keep by removing ambiguity about your practice, and by making you eligible for the features that still exist.

Which schema types a healthcare site needs

Four types cover most practices: Physician for the provider or office, a LocalBusiness-style location record, MedicalWebPage for clinical content, and Organization details for a multi-site group. Pick the most specific type available rather than a generic one.

TypeUse it forProperties worth filling in
PhysicianA doctor or a physician's officemedicalSpecialty, availableService, hospitalAffiliation, usNPI, isAcceptingNewPatients
IndividualPhysician / PhysiciansOfficeSeparating the person from the office when both have pagesThe same set, split to match each page
MedicalWebPageCondition, treatment and procedure pagesspecialty, medicalAudience, reviewedBy, lastReviewed
LocalBusiness subtypeEach physical locationaddress, name, telephone, openingHoursSpecification, geo

The property lists come straight from the Schema.org Physician page, which defines the type as an individual physician or a physician's office considered as a MedicalOrganization. It inherits address, opening hours and telephone from its LocalBusiness parent, so one Physician record can carry both clinical and location detail.

How to mark up a physician or clinic page

Start with the provider profile, because it's the page that ties a named person to a specialty and a place. Add the doctor's name, medicalSpecialty, the services in availableService, and the hospitalAffiliation if there is one.

The usNPI property takes the provider's 10-digit National Provider Identifier. It ties the bio page to one identifiable clinician instead of a name that might match several.

If the practice is taking on patients, isAcceptingNewPatients says so in a form a machine can read. Keep it current. Stale markup that says yes while the front desk says no is worse than leaving it out, and Google requires that markup be a true representation of the page.

Getting the location record right

For each office, Google's local business structured data documentation lists address and name as the only required properties. Telephone, geo coordinates, a working URL for that specific location and opening hours are recommended.

Hours need care. Use full day names, write times as hh:mm:ss, and for a 24-hour clinic run from 00:00 to 23:59. A closed day takes the same time for opening and closing.

Give every location its own page and its own record. A group practice that puts four addresses in one block of markup on the homepage makes it hard for anyone to tell which phone number belongs to which office.

The same record should agree with your Google listing. If you haven't audited that yet, our guide to optimising a healthcare Google Business Profile covers the listing side, and the hours and phone number should read identically in both places.

Marking up condition and treatment pages

Condition and treatment pages are where a medical site does its real SEO work, and MedicalWebPage is the type made for them. Per Schema.org, it describes a web page that provides medical information, and it adds two properties of its own: specialty and medicalAudience.

The more interesting properties are inherited from WebPage. reviewedBy names the person or organisation that checked the content for accuracy, and lastReviewed records when that check happened.

Those two matter in healthcare because medical content is only as credible as the clinician behind it. If a cardiologist signs off on your article about blood pressure, say so on the page and then mirror it in markup. The visible byline and the structured data have to agree.

Don't invent a reviewer to fill the property. Marking up a review that never happened is the sort of mismatch that costs you eligibility, and in this field it's also a credibility problem no markup will repair.

Review stars and FAQ markup: what no longer works

Illuminated HTML code displayed on a computer screen, close-up view.

Photo by Nimit Kansagra on Pexels

Two tactics that dominated older healthcare SEO advice need updating. The first is putting your own patient reviews into markup to get stars in search results.

Google's review snippet guidelines are explicit that a business controlling reviews about itself makes its LocalBusiness or Organization pages ineligible for star ratings. That includes reviews pulled in through widgets such as Google Business or Facebook. Reviews of your practice on your own site don't qualify.

The second is FAQ markup. Google's FAQ documentation was changed on September 14, 2023 to say the rich result would only show for well-known, authoritative government and health websites. On May 8, 2026 it added a notice that the feature would no longer appear in Google Search from May 7, 2026, and on June 15, 2026 the documentation was removed, per Google's FAQ structured data page.

For a medical site this is a useful correction. Health sites were the one category that still qualified, and even they no longer get the result. Writing clear question-and-answer sections is still good content. Adding FAQPage code to chase a search feature that has been retired is wasted effort.

Common mistakes that cost eligibility

Most schema problems on medical sites come from the same few habits. They're all avoidable with a short review before launch.

  • Marking up content patients can't see. Google says hidden content isn't eligible, and markup must reflect what's on the page.
  • Using a generic type when a specific one exists. Google's own advice for locations is to use the most specific subtype available.
  • Copying one template across every doctor, so each profile claims the same specialty and affiliations.
  • Leaving old hours, phone numbers or accepting-patients flags in place after the practice changes.

The penalty for getting this wrong is narrower than people fear. Google describes a structured data manual action as the page losing eligibility for rich results, and says it doesn't affect ranking in web search. That's a reason to fix errors promptly, not a reason to panic, and you can see any action in Search Console's Manual Actions report.

Other industries hit the same problems with different vocabulary. Our write-ups on fintech schema markup and real estate schema markup show how the type choices change while the rules about honesty stay identical.

How to test and maintain your markup

Run every template through Google's Rich Results Test before it goes live, since Google says it catches most technical errors. After deploying a few pages, check them with the URL Inspection tool to confirm Google can reach them, then submit a sitemap so changes get tracked.

Then set a recurring check. Markup is generated from templates, so a redesign, a new plugin or a CMS migration can strip it silently, and nobody notices until a location shows the wrong hours in search.

On a larger site, build the schema into the page templates and populate it from the same fields that render the visible content, so the two can't drift apart. That's the kind of work we handle in our web development and digital marketing services, where structured data is wired in during the build rather than bolted on afterwards.

If you only have an afternoon, do this: add a Physician record with specialty, services and NPI to each provider page, give each office a location record with correct hours, and put reviewedBy on your ten most-visited condition pages. Test all three before publishing.

Frequently asked questions

Is JSON-LD the right format for a medical site?

Yes. Google lists JSON-LD as its recommended format, and it sits in a single block rather than being threaded through your page's HTML, which makes it easier to maintain from a template.

Will schema markup improve my rankings?

Google says valid markup makes a page eligible for a feature, not that it will display, and its structured data penalties concern rich result eligibility rather than ranking. Treat schema as clarity for search engines, not a ranking lever.

Can I add my patient reviews to my schema?

You can, but Google's guidelines make a business's own LocalBusiness or Organization pages ineligible for star ratings when the business controls the reviews about itself. Don't expect stars from reviews hosted on your own site.

Should I still add FAQ schema to health pages?

Google's documentation says the FAQ rich result stopped appearing in Search from May 7, 2026, so the markup no longer gets you a visible result. Keep the questions on the page for readers, but skip the code.

Cover photo by AS Photography on Pexels

Sources

Latest Blog

View from below of a tall tree with green leaves and sunlight filtering through.Tree Service Marketing • Reputation Management

Reputation Management for Tree Service Companies

A homeowner can't judge a pruning cut or a rigging plan from the driveway, so they judge your reviews. Here's how to collect them, answer them and stay inside the rules.

Read More
Close-up of a spherical smart speaker with illuminated base, perfect for modern interiors.Healthcare Marketing • Voice Search

Voice Search Optimization for Healthcare Providers

A spoken answer has no page two. Here's how a practice gets named when a patient asks a phone for care nearby, from Google and Apple listings to structured data and page copy.

Read More
A software developer engaged in coding on dual monitors in a modern office setting.GoHighLevel • MVP

How to Build an MVP Without Coding Experience

You can learn whether people want your product before anyone writes code. Here's the order to work in, from one testable assumption to a first real version.

Read More
Tree surgeon using a chainsaw to prune branches while secured with ropes in Kowloon, Hong Kong.Tree Service Marketing • Landing Pages

Tree Service Landing Pages That Convert: Design Tips

A tree service landing page has one job: get a worried homeowner to call or request a quote. Here's how to build the page around that job, from the first screen to the form.

Read More
Close-up of laptop with coding software and a motivational coffee mug on a desk.GoHighLevel • Vibe Coding

Vibe Coding vs Traditional Development: Which Is Right?

Vibe coding gets you a working demo fast, but the research on speed and security is less flattering than the hype. Here's where each approach belongs and how to decide for your project.

Read More
Colorful financial chart showcasing trends and metrics, ideal for business analysis.Healthcare Marketing • Healthcare SEO

Top Healthcare Marketing Trends to Watch in 2026

AI summaries are absorbing clicks, tracking pixels carry legal risk, and local profiles shape who gets the call. Here are the healthcare marketing trends worth acting on this year.

Read More

Subscribe to our newsletter

Offers, insights and updates — a couple of times a month, never more.