Schema Markup for Healthcare

Published March 19, 2026

Healthcare businesses — dentists, clinics, pharmacies, therapists, psychiatrists — operate in a space where trust is not optional. When someone asks an AI assistant to recommend a dentist or find a therapist nearby, the AI needs to confirm more than just location and hours. It needs to understand the type of care provided, the specialties offered, and whether the provider can serve the user's specific need.

Schema is how a healthcare business communicates those details to AI in a structured format. The AIFDS healthcare blueprint library contains 60+ blueprints covering dentists, clinics, pharmacies, therapists, and psychiatrists — all built from research into which schema fields AI systems actually read.

Why Healthcare Is Different

The core findings apply across every industry, but healthcare adds a layer most do not: the match between provider and patient needs to be specific. A user asking for "a pediatric dentist that takes Delta Dental" can only be matched if the provider's schema includes specialty and insurance information.

Healthcare also carries higher liability. AI is more cautious when recommending providers because a bad recommendation has real consequences. A controlled experiment showed AI cites more readily when it can shift high-stakes answers to a qualified human source — which means the completion gap between what AI knows generally and what a specific provider can do is where citations happen.

For healthcare, LLM visibility means giving AI enough structured information to make a confident, specific match — not just a category-level one.

What AI Needs from a Healthcare Business

The fields that matter follow AI's standard decision chain, but shift toward clinical precision and patient-provider matching.

Provider type and specialty

AI uses schema type to classify the provider — Dentist, Pharmacy, MedicalClinic, and others. Specialty fields tell AI what kind of care is offered. Without this distinction, AI matches broad queries but misses the specific ones where conversion is highest.

Physical address and geo coordinates

Healthcare is local. Patients travel to providers. AI matches location-based queries to providers by proximity — the same way it does for local businesses. Without a structured address and coordinates, AI cannot confirm the provider is near the user.

Contact information

Phone and email are critical for healthcare. A patient recommended a therapist by AI needs to be able to call and schedule. AI treats contact data as both a trust signal and functional data it can serve directly to users.

Hours of operation

Availability matters differently in healthcare. A user looking for an urgent care clinic at 7 PM needs to know it is open. A patient searching for a therapist needs to know office hours align with their schedule. Hours in schema give AI a direct answer.

Services and procedures offered

This is where healthcare schema diverges most from other industries. A dental practice that offers cosmetic dentistry, orthodontics, and emergency care needs each service represented. AI matches patient queries to specific services — not just to the provider category.

Accepted insurance and payment

While not universally applicable, insurance and payment information helps AI pre-qualify the match. A user asking for a dentist who takes their specific insurance plan can only be matched if that information is structured. Even listing accepted payment methods gives AI more to work with than a bare provider listing.

The Core Problem

The pattern matches every other industry: the problem is missing schema, not wrong schema. Most healthcare websites were built for human visitors. Credentials, services, and contact information are all on the page — but not in schema. AI reads structured data first. A beautifully designed dental practice website with no JSON-LD is a website AI struggles to understand.

Schema is eligibility. If AI cannot confirm what you specialize in, where you are, and whether a patient can reach you, you are not in the consideration set.

How the AIFDS Healthcare Blueprints Are Organized

The healthcare blueprint library is organized by provider type, then by page type. Dentists, clinics, pharmacies, therapists, and psychiatrists each get their own set covering homepage, services pages, provider pages, contact, FAQ, and more — each with the exact JSON-LD fields AI needs.

Implementation Priority for Healthcare

Start with the homepage. Include provider type, specialty, address, hours, contact information, and a description of services offered.

Add individual service pages. Each service or procedure should have its own page with schema. This is how AI matches patients to specific care, not just to the practice generally.

Ensure directory alignment. Google Business Profile, Healthgrades, Zocdoc, Yelp — these are the directories AI cross-references. Context consistency between schema and directories is essential. Inconsistencies weaken AI confidence.

Structure provider details. If the practice has multiple providers, each one should be represented with their name, credentials, and specialties. This helps AI match specific provider queries — "a female therapist specializing in anxiety" — not just practice-level ones.

Browse Healthcare Blueprints Validate Your Schema

David Valencia writes about how AI systems find, parse, and cite websites.

Related research

Which Schema Fields Do AI Systems Actually Read?

The pillar research this article builds on.

Read →

Schema Markup for Local Businesses

Overlapping findings for location-dependent businesses.

Read →

Homepage Schema for AI

Why the homepage is the highest-impact starting point.

Read →

Framework

See what AI reads from your site right now

Paste your URL into the AIFDS validator and get a field-by-field report of what AI systems can see.

Open Validator →