Dental schema markup is structured data, usually written in JSON-LD, that tells search engines and AI systems the facts about your practice in a machine-readable format: that you are a Dentist, where you are, when you are open, which doctors work there and which services you offer. Schema does not directly boost rankings, but it removes ambiguity, supports rich results and makes your practice details easier for Google and AI assistants to trust and cite.

Schema is one of the most misunderstood parts of dentist SEO. Some vendors sell it as a ranking shortcut. Some website platforms add it automatically and badly. Many practices have conflicting markup from three different plugins, each saying something slightly different about the practice. This guide explains which schema types matter for dental websites, how to implement them correctly and which popular tactics no longer work.

What schema markup does, and what it does not do

Schema markup is a shared vocabulary maintained at schema.org and supported by Google, Bing and other search engines. It lets you label information on your pages so machines do not have to guess.

What it does:

Confirms facts Google may otherwise infer: business type, name, address, phone, hours
Connects entities: the practice, its locations, its doctors and their credentials
Makes certain pages eligible for rich results, such as breadcrumbs and review snippets where allowed
Gives AI-driven search features clean, structured facts to draw on

What it does not do:

It does not guarantee rich results; Google decides whether to show them
It is not a direct ranking factor in the way content and links are
It cannot make up for thin content or a weak website
Markup that describes content not visible on the page violates Google’s guidelines

Think of schema as clean labeling. It helps systems that are already looking at your site understand it with confidence.

The Dentist schema type

Schema.org includes a specific type called Dentist. It is defined as a type of LocalBusiness, MedicalBusiness and MedicalOrganization, which means it inherits the properties of all three. For a dental practice, Dentist is more precise than a generic LocalBusiness and should be your primary type.

The properties that matter most for a practice:

Property	What it describes	Notes
`name`	Practice name	Must match your Google Business Profile and signage
`url`	Website URL	The canonical URL for the practice or location page
`telephone`	Main phone number	Use the real practice number, consistent with your profile
`address`	Street address	A `PostalAddress` object, matching your listings exactly
`geo`	Latitude and longitude	Helps disambiguate location
`openingHoursSpecification`	Hours by day	Keep in sync with your profile, including changes
`image` and `logo`	Practice photo and logo	Real photos, accessible URLs
`priceRange`	General price level	Optional
`areaServed`	Cities or regions served	Be realistic; list actual service areas
`sameAs`	Official profiles	Google Business Profile, Facebook, Instagram, Yelp, professional directories
`medicalSpecialty`	Specialty focus	Use accurately; do not claim specialties you do not hold
`employee` or `member`	Doctors at the practice	Link to `Person` entities for each dentist

A clean example for a single-location practice

Below is a simplified JSON-LD example. Replace the details with your own, and make sure every fact matches what appears on the page and on your Google Business Profile.

{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "@id": "https://www.exampledental.com/#practice",
  "name": "Example Family Dental",
  "url": "https://www.exampledental.com/",
  "telephone": "+1-555-555-0100",
  "image": "https://www.exampledental.com/images/office-exterior.jpg",
  "logo": "https://www.exampledental.com/images/logo.png",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street, Suite 200",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "geo": { "@type": "GeoCoordinates", "latitude": 39.7817, "longitude": -89.6501 },
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday"],
    "opens": "08:00", "closes": "17:00"
  }],
  "sameAs": [
    "https://www.facebook.com/exampledental",
    "https://www.instagram.com/exampledental"
  ],
  "employee": { "@id": "https://www.exampledental.com/our-team/dr-jane-smith/#person" }
}

The @id values matter more than people realize. They give each entity a stable identifier so other markup on the site can refer to it instead of repeating it. Your doctor’s page can then describe the doctor as a Person who works for that same @id.

Schema for multiple locations

Each physical location should have its own location page with its own Dentist markup containing that location’s address, phone, hours and geo coordinates. A common mistake is placing every location’s details in sitewide markup on every page, which blurs which page represents which office.

A clean structure for a group:

An Organization entity for the brand, on the homepage
One Dentist entity per location, on that location’s page, with parentOrganization pointing to the brand
Person entities for doctors, linked to the location or locations where they practice

Schema for doctors: the Person type

Doctor pages are among the most valuable pages for trust, and schema helps connect each doctor to the practice. Useful Person properties include name, jobTitle, image, worksFor, alumniOf (dental school), hasCredential or award for verifiable credentials, and sameAs links to professional profiles. Only include credentials that are real and verifiable. Inflated credentials in markup carry the same ethical and regulatory risks as inflated credentials in copy.

This connects directly to experience, expertise, authoritativeness and trust, the qualities Google’s guidelines emphasize for health content. Our article on E-E-A-T signals for dental content covers the broader picture.

Schema for service pages

Service pages can describe the treatment using types such as MedicalProcedure or Service, connected to the practice with provider. This is optional and has a limited visible effect in standard search results today, but it adds clarity, particularly for AI systems summarizing what a practice offers. Keep it accurate and modest: describe the procedure the page actually covers. Our guide to dental service pages covers the content side.

FAQ schema: what changed

For several years, FAQ schema was a popular way to take up more space in search results. That changed in August 2023, when Google announced that FAQ rich results would only be shown for well-known, authoritative government and health websites. For most dental practice sites, FAQ markup no longer produces a visible rich result.

Google also stated that unused structured data does not cause problems, so there is no need to rush to remove existing FAQ markup. But practices should not expect it to change their appearance in results, and anyone selling FAQ schema as a visibility tactic is selling something that stopped working.

The content itself still matters. Well-written question-and-answer sections on service pages help patients and give search engines and AI systems clear answers to extract. Write the FAQs for people first. And write them by hand: auto-generated FAQ content frequently gets location, insurance or treatment details wrong.

Review schema: a common trap

Many practices want star ratings to appear next to their website in search results. Google’s guidelines do not allow businesses to show review stars for themselves using reviews they collect and display on their own site. Since 2019, self-serving review markup for a LocalBusiness or Organization is not eligible for review rich results. Adding AggregateRating to your Dentist markup using reviews you display on your own site will not produce stars, and markup that does not reflect visible, legitimate content can create problems.

The stars patients see next to your practice in the map pack come from your Google Business Profile. That is where review effort pays off.

Schema and AI search

AI Overviews and conversational assistants assemble answers from many sources. Clear, consistent facts help. When your website schema, Google Business Profile, directory listings and on-page content all state the same name, address, phone, hours and services, systems can trust those facts. When they conflict, they may not. Our article on schema and structured data for AI search covers this angle in depth. Consistency across listings, covered in our guide to local listings beyond Google, is part of the same job.

How to implement dental schema

There are three common approaches:

Approach	Pros	Cons
SEO plugin settings (for example Yoast or Rank Math on WordPress)	Easy, maintained automatically	Often generic; may default to `Organization` instead of `Dentist`
Custom JSON-LD added to the site template or specific pages	Precise and fully controlled	Needs a developer and maintenance when details change
Schema management platforms	Can deploy at scale without code changes	Must be checked to avoid duplicating or conflicting with existing markup

Whatever the approach, the most important rule is: one source of truth. Before adding anything, check what is already there. Run your homepage and a service page through Google’s Rich Results Test and the Schema Markup Validator. It is common to find a theme, an SEO plugin and a third-party tool each outputting their own version of the practice, with different phone numbers or hours.

A dental schema audit checklist

Is the primary type Dentist (or a more specific accurate type) rather than a generic type?
Is there exactly one practice entity per location, not duplicates from different plugins?
Do name, address and phone match the Google Business Profile exactly?
Are hours current, including recent changes?
Do doctor pages have Person markup connected to the practice?
Are sameAs links current and pointing to official profiles?
Is there any self-serving AggregateRating markup to remove?
Does every marked-up fact appear visibly on the page?
Does the Rich Results Test report no errors?

Our Google Business SEO guide covers aligning your profile with your website.

A doctor Person schema example

Here is a simplified Person example for a doctor bio page, connected to the practice entity above by its @id. Only include credentials the doctor actually holds and that appear on the page.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://www.exampledental.com/our-team/dr-jane-smith/#person",
  "name": "Dr. Jane Smith",
  "jobTitle": "General Dentist",
  "image": "https://www.exampledental.com/images/dr-jane-smith.jpg",
  "worksFor": { "@id": "https://www.exampledental.com/#practice" },
  "alumniOf": {
    "@type": "CollegeOrUniversity",
    "name": "Example University School of Dentistry"
  },
  "memberOf": {
    "@type": "Organization",
    "name": "American Dental Association"
  },
  "sameAs": [
    "https://www.linkedin.com/in/example-dr-jane-smith"
  ]
}

When this markup sits on the doctor’s page and the practice markup sits on the homepage or location page, both entities refer to each other consistently. Search engines can then understand that this specific doctor works at this specific practice.

Common schema errors on dental websites

Error	What it looks like	Fix
Duplicate practice entities	Theme, SEO plugin and a third-party tool each output a practice with different details	Choose one source and disable the others
Generic type	`Organization` or `LocalBusiness` instead of `Dentist`	Change the type to `Dentist`
Outdated details	Old phone number or hours in markup after a change	Update markup whenever profile details change
Every location on every page	Sitewide markup lists all offices	One location entity per location page
Self-serving review markup	`AggregateRating` from your own testimonials	Remove it; focus on profile reviews
Markup for invisible content	FAQs or services in schema that do not appear on the page	Only mark up visible content
Broken image URLs	Logo or image URLs that return errors	Use current, accessible URLs

Maintaining schema over time

Schema is easy to set and forget, which is how it drifts out of date. Build it into your routine:

Whenever hours, phone numbers or addresses change, update the Google Business Profile, the website and the schema on the same day
When a doctor joins or leaves, add or remove their Person markup with their bio page
After any website redesign, plugin change or theme update, rerun the Rich Results Test on key pages
Review all markup at least once a year as part of a technical audit

Schema and your Google Business Profile

Schema on your website and your Google Business Profile describe the same practice in two places. Google compares them. When the name, address, phone, hours and website match exactly, each reinforces the other. When they differ, for example a suite number on one and not the other, or an old tracking number in the markup, the inconsistency creates doubt. Treat the profile as the reference, update the schema to match and make both part of the same change process whenever practice details change.

Frequently asked questions

Does schema markup improve dental SEO rankings?

Not directly. It helps search engines understand your practice accurately and can make pages eligible for some rich results. Rankings still depend mainly on content, relevance, links, reviews and local signals.

Should I use the Dentist or LocalBusiness type?

Use Dentist. It is more specific and inherits the properties of LocalBusiness, MedicalBusiness and MedicalOrganization. Specialty practices may consider additional specific types where they accurately apply.

Is FAQ schema still worth adding?

For most dental websites, FAQ markup no longer produces visible rich results following Google’s 2023 change. The FAQ content is still valuable for patients and AI answers. There is no harm in existing markup, but do not expect visible gains.

How do I check my practice’s schema?

Use Google’s Rich Results Test for eligibility and errors, and the Schema Markup Validator at schema.org for a full view of every entity on the page.

Can schema cause problems?

Yes, if it is wrong or conflicting. Duplicate practice entities with different phone numbers, markup describing content that is not on the page and self-serving review markup can all cause confusion or violate guidelines. Accurate, consistent markup carries little risk.

Do specialty practices use a different schema type?

Schema.org does not have separate types for every dental specialty. Specialty practices typically still use Dentist, and may describe their focus with the medicalSpecialty property where a matching value exists. Accuracy matters more than finding a narrower type.

Does schema help with AI Overviews and chat assistants?

Structured data gives search systems clear, consistent facts about your practice. No one can guarantee that it changes what an AI assistant says, but accurate and consistent information across your schema, website and listings makes it easier for any system to describe your practice correctly.

Should every page have practice schema?

Typically the practice entity appears on the homepage and each location’s page, with other pages referencing it by its @id where needed. Repeating full practice details on every page is unnecessary and increases the risk of inconsistencies.

Who should manage our schema?

Whoever manages the website’s SEO should own it, working with the developer. The key is that one person is responsible, so changes to hours, phone numbers and doctors are reflected in the markup promptly.

Can schema include insurance plans we accept?

Schema.org has properties for health plans in some contexts, but support in search features is limited. The more reliable approach is a clear, current insurance page on your website and accurate information on your Google Business Profile.

How do we test schema after making changes?

Run the updated page through Google’s Rich Results Test and the Schema Markup Validator, confirm there is only one practice entity and that every value matches the profile, then use URL Inspection in Search Console to request recrawling of the most important pages. Recheck after the next plugin or theme update.

The bottom line

Schema markup is not a ranking trick. It is accurate labeling. Use the Dentist type, keep one consistent entity per location, connect your doctors, make every fact match your Google Business Profile and remove conflicting or outdated markup. Skip the tactics that stopped working, such as FAQ rich results and self-awarded stars, and put that effort into content and reviews instead.

Dental Schema Markup: Dentist, LocalBusiness and FAQ Structured Data Explained