Schema for Dentists and Medical Practices: The Full Guide

For a dental or medical practice, schema markup is one of the most valuable things you can add to your website: it makes you findable in local search, helps Google connect the right provider to the right specialty and location, and increasingly determines whether AI systems can accurately represent your practice when patients research their options. Patients are already turning to AI to find and evaluate providers, and structured data is how you make sure yours is understood correctly.

But health is a "Your Money or Your Life" (YMYL) field, which means Google evaluates it with unusual rigor on trust and expertise, and it also means a lot of the dental- and medical-SEO advice out there is either outdated or simply wrong in ways that can cost you. So this guide does it accurately: the right schema types for your practice, how to establish your providers' credibility, the honest reality about review stars (most guides get this wrong), what changed for health sites in 2026, and how it all supports being found by patients and AI alike. Let's build it right.

The honest reality: what medical schema does (and doesn't)

Let's set accurate expectations first, because a lot of guides oversell this.

There's no special "medical rich result." Adding Dentist or MedicalClinic schema doesn't produce a unique visual result reserved for healthcare. What medical schema actually does is more foundational and, honestly, more valuable:

• Local visibility, it feeds Google structured hours, location, and services that support your presence in Maps and the local pack, where most new-patient searches land.
• Entity clarity, it disambiguates your practice and your providers, so Google connects the right doctor to the right specialty, location, and affiliation, rather than guessing from prose.
• E-E-A-T signals, it makes your providers' credentials and your content's medical review machine-readable, which is exactly what YMYL health content is evaluated on.
• AI patient search, it reduces ambiguity about who you are, what you treat, and where you operate, which supports accurate representation when AI systems answer patients' questions.

None of that is a flashy rich result, and all of it matters more than one. And an honest note we'll return to: no tool can guarantee AI citations or specific rankings, and we won't pretend otherwise, what good schema does is make your practice legible and trustworthy to the systems patients use. That's the real goal.

Choosing the right schema type

Getting the type right is the foundation, and it's where many practices leave value on the table by using something too generic. Here's the hierarchy, in plain terms:

LocalBusiness is the generic base, and using only this is the common mistake. It works, but it misses the medical-specific properties and sends a weaker signal about what your practice actually is.

MedicalBusiness is a healthcare-specific subtype of LocalBusiness. It adds business properties suited to practices, opening hours, accepted payment methods, service area, while signaling you're a medical entity.

MedicalOrganization describes healthcare institutions with medical-specific properties like specialties and affiliations. It's the organization-level type, best for larger or multi-specialty groups.

MedicalClinic is a subtype of both MedicalOrganization and MedicalBusiness, so it combines medical and business features. For most private practices, this is the best single choice.

Dentist is the specific type for dental practices, a healthcare business subtype purpose-built for dentistry. If you're a dental practice, use Dentist; it's more specific and accurate than the generic alternatives.

Hospital and Pharmacy are the specific types for those facilities.

Physician describes individual providers (covered in detail below), not the practice itself, but each doctor or dentist on your team.

The rule, as with schema generally: use the most specific accurate type. A dental practice should use Dentist, a general practice MedicalClinic, a multi-specialty group MedicalOrganization at the top with specific subtypes per department. Generic LocalBusiness is a missed opportunity.

A complete example: a dental practice with a provider

Here's how a practice and one of its providers connect:

{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "@id": "https://brightsmile.example/#practice",
  "name": "Bright Smile Dental",
  "image": "https://brightsmile.example/office.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "22 Elm Street",
    "addressLocality": "Austin",
    "addressRegion": "TX",
    "postalCode": "78704",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 30.2500,
    "longitude": -97.7500
  },
  "telephone": "+1-512-555-0100",
  "openingHours": "Mo-Fr 08:00-17:00",
  "medicalSpecialty": "Dentistry",
  "employee": {
    "@type": "Physician",
    "@id": "https://brightsmile.example/team/dr-santos#physician",
    "name": "Dr. Maria Santos",
    "medicalSpecialty": "Dentistry",
    "alumniOf": {
      "@type": "EducationalOrganization",
      "name": "University of Texas School of Dentistry"
    },
    "sameAs": [
      "https://www.linkedin.com/in/mariasantos-dds"
    ]
  }
}

Notice the practice is typed Dentist (specific, not generic), it carries the local details that feed Maps and the local pack, and it connects to a provider modeled as a Physician with credentials. That connection, practice to provider, is where a lot of the E-E-A-T value lives, so let's go deeper on both layers.

The local layer: getting found by nearby patients

For most practices, local search drives the majority of new-patient inquiries, so the business layer of your schema is doing real work.

Your practice type (Dentist, MedicalClinic, etc.) carries the local details Google uses for Maps and the local pack: your address, geo coordinates, telephone, openingHours, and service area. Fill these in completely and accurately, they're what let Google confidently place you for "dentist near me" and "pediatric dentist in [city]" searches.

Crucially, these details must match your Google Business Profile exactly, which we'll come back to under consistency, because for local healthcare, your schema, your Business Profile, and your on-page details all need to tell the same story. If you operate multiple locations, the patterns in our multi-location guide apply directly: each location as its own entity with its own complete details.

Your providers: Physician entities and E-E-A-T

This is where medical schema gets genuinely powerful for a YMYL field, and where most practices under-invest. Each provider on your team should be modeled as their own Physician entity, and doing this well directly feeds the expertise signals health content is judged on.

For each provider, mark up:

• medicalSpecialty, their specialty or focus area.
• credential, board certifications, degrees, and specialty qualifications. This feeds directly into Google's understanding of your team's expertise.
• alumniOf, their medical or dental school, connecting them to a recognized educational institution, a real expertise signal.
• memberOf or employee, connecting the provider to your practice entity, so the relationship is explicit.
• sameAs, links to their authoritative professional profiles and, where available, license verifications and professional registries.
• availableService, the services they provide.

Why this matters so much: for YMYL health content, Google wants machine-readable proof that real, credentialed experts stand behind your practice. A provider marked up with their credentials, education, and verifiable professional profiles turns "trust us, we're qualified" into structured, verifiable expertise. This is the same author-and-expert entity work that establishes E-E-A-T across any content, applied to healthcare providers, and it matters more here than almost anywhere, because health is exactly where Google scrutinizes expertise hardest. Our Person and author schema guide covers building strong provider entities in depth; the principles apply directly.

E-E-A-T for your medical content

Beyond your providers, the informational content on your site, condition explainers, "what to expect" pages, treatment overviews, carries its own E-E-A-T requirements, and two properties are specifically valuable for medical content:

reviewedBy, states who medically reviewed the content, connected to a credentialed Physician entity. For health content, "medically reviewed by Dr. [Name], [credentials]" isn't just good practice for patients, marked up with reviewedBy, it becomes machine-readable proof that a qualified professional stands behind the information.

lastReviewed, states when the content was last reviewed for medical accuracy. Health information ages, and a recent review date signals the content is current and maintained, a genuine trust signal for YMYL.

Together, these turn your medical review process into structured trust data. If your practice publishes patient-education content, and it should, both for patients and for AI visibility, having it genuinely reviewed by your credentialed providers and marking that up with reviewedBy and lastReviewed is one of the strongest YMYL signals you can send. It says, in machine-readable terms: real experts wrote and checked this, recently.

Procedures and conditions

Two more types add depth for practices that publish about what they treat:

MedicalProcedure describes procedures you offer, a root canal, an implant, Invisalign, a specific treatment. Marking up your procedure pages helps Google and AI understand exactly what you do, and connects your services to the conditions they address.

MedicalCondition is for informational content about conditions, a page explaining a condition you treat. It signals the page offers genuine medical information rather than marketing, and can connect to a recognizingAuthority for added credibility.

These create entity relationships between your content, conditions tied to the procedures that treat them, procedures tied to the providers who perform them, building the connected picture that helps both search and AI understand your practice's full scope of care.

The review stars reality (most guides get this wrong)

Here's an accuracy point that a lot of dental- and medical-SEO advice gets flatly wrong, and getting it right saves you effort and risk.

Your practice cannot show star ratings for reviews about itself on its own site. Google's self-serving review rule means a business, including a dental or medical practice, that marks up reviews about itself using LocalBusiness or Organization-type schema (which includes Dentist, MedicalClinic, etc.) is ineligible for the star rating rich result. This includes reviews embedded via third-party widgets on your own site.

So the common advice to "add Review schema to your practice page for star ratings" doesn't work and can flag your site. The star ratings you see for practices in local results come from Google's own reviews and independent third-party platforms, not from a practice marking up its own reviews. We cover the full rules in our guide to getting star ratings, but the healthcare-specific takeaway is: focus on earning genuine reviews on Google and the independent platforms that matter, keep your Google Business Profile strong, and don't waste effort trying to self-mark-up review stars. On-page review data can still help AI systems understand your reputation, it just won't earn you the star snippet.

What changed for health sites in 2026

A currency point that catches a lot of medical practices and the guides advising them: FAQ rich results are gone, including for health sites.

For a period, FAQ rich results were restricted to authoritative government and health sites, which led to lots of advice telling medical practices to use FAQPage schema for rich results. That advice is now outdated. Google fully retired the FAQ rich result in 2026, including the health and government eligibility that used to be the exception. So if you're following a dental- or medical-SEO guide that promises FAQ rich results for your practice, it's describing a feature that no longer exists for you.

FAQ content is still worth writing, real patient questions answered clearly are good for patients and for AI extraction, but don't implement FAQPage schema expecting the rich result, and be skeptical of any healthcare-SEO advice that still promises it. This is exactly the kind of currency gap where a lot of vertical-specific guidance has fallen behind.

Consistency: schema, Business Profile, and page must agree

For local healthcare especially, consistency across your sources is a make-or-break trust signal.

Your practice name, address, phone number, hours, and specialties must match exactly across your schema markup, your Google Business Profile, and your on-page content. If your schema lists one address and your Business Profile shows another, or your hours disagree, Google loses confidence in both signals, inconsistency doesn't just fail to help, it actively undermines the trust you're trying to build.

This matters more in healthcare because the details change often: you add a provider, adjust hours, stop accepting an insurance plan, add a service. Every one of those changes needs to flow into your schema, or your structured data drifts out of truth. Auditing your schema, Business Profile, and on-page details regularly so they all agree, and updating all three together when things change, is unglamorous and genuinely important. Stale practice schema (an old provider still listed, wrong hours, a dropped insurance still shown) is a real and common problem.

Medical schema and AI patient search

This is the fastest-growing reason to get your practice schema right, and it's worth understanding clearly.

Patients are increasingly using AI to research providers, asking ChatGPT, Perplexity, or Google's AI about conditions, treatments, and which practices to consider. When these systems answer, they parse structured data to understand who you are, what you treat, where you operate, and whether credentialed experts stand behind you. A practice with clear, complete, connected schema, the right type, provider entities with credentials, medically-reviewed content, consistent details, is a practice AI can represent accurately and confidently. One relying on prose is one AI has to guess about.

The honest framing, again: no schema guarantees your practice gets recommended or cited by AI, anyone promising that is overselling. What it does is remove the ambiguity that causes AI to misrepresent you or overlook you in favor of a practice it understands better. For healthcare, where patients are making real decisions about their care based partly on what AI tells them, being clearly and accurately understood is genuinely valuable, and it's exactly what a connected, credentialed, consistent entity profile provides.

Common mistakes to avoid

Using generic LocalBusiness instead of the specific type. Use Dentist, MedicalClinic, or the accurate specific subtype, they carry medical properties and send stronger signals that generic LocalBusiness doesn't.

Skipping provider (Physician) entities. Your providers' credentials are a major E-E-A-T asset in a YMYL field. Model each as a Physician with credentials, education, and profile links.

Trying to self-mark-up review stars. Practices can't earn star snippets from their own reviews on their own site. Focus on genuine reviews on Google and third-party platforms.

Relying on FAQ rich results. They're gone, including for health sites. Write FAQ content for patients and AI, but don't expect the rich result.

Inconsistent NAP across schema, Business Profile, and page. Mismatches undermine trust in all your signals. Audit and align them.

Stale schema. Practice details change often. An old provider, wrong hours, or a dropped insurance still in your markup misinforms patients and search engines. Keep it current.

Markup that doesn't match the page. As always, your schema must reflect what's genuinely on the page and true of your practice.

Implementing it on WordPress

Most practices run WordPress, often with a dental- or medical-specific theme, and your approach should make accuracy and maintenance manageable.

Check what your theme or SEO plugin outputs, many produce only generic LocalBusiness markup, missing the specific medical subtype, the provider entities, and the E-E-A-T properties that matter most in healthcare.

The real challenge is depth plus accuracy over time, the right specific type, each provider as a credentialed Physician entity, medically-reviewed content marked up, all consistent with your Business Profile and kept current as providers, hours, and services change. Hand-maintaining that is where most practices fall behind.

Generating from your content keeps it accurate. AI Schema Gen reads your practice pages and generates the right specific schema, Dentist or the accurate medical subtype, provider Physician entities with credentials, connected into your practice's entity profile, and because it generates from your live content, your details stay consistent and current as they change. It also keeps you clear of the common traps, like generating markup that matches your visible content rather than self-serving review claims that won't work. Browse the full schema type directory for any medical type mentioned here. Whatever route you take, the tests are: the specific accurate type; providers as credentialed entities; consistency with your Business Profile; and accuracy as your practice changes.

Validating your practice schema

Google's Rich Results Test validates your markup and flags errors. Test your practice page and provider pages.

The Schema Markup Validator checks broader schema.org validity, useful for the medical types and relationships that don't map to a specific rich result.

Cross-check consistency, confirm your schema's name, address, phone, hours, and specialties match your Google Business Profile and on-page content exactly.

Search your own terms, look up "dentist near me" and your practice name to see how you appear in local results and whether your details show correctly.

Running a dental or medical practice on WordPress? AI Schema Gen generates the right specific schema from your content, Dentist or your accurate medical subtype, providers as credentialed Physician entities, connected into your practice's entity profile and kept consistent as details change. Start free at aischemagen.com.