Ask a search engine to describe your dental practice and you get something strange: a name, a phone number, an address that may or may not be current, and a list of services that looks like it was assembled from a directory in 2019. The machine can read your pages. It just has to guess what kind of thing they are describing.
Structured data is the part of your site that tells the machine instead of letting it guess. It is also the part most practices leave half done, and the part agencies most often get wrong in ways that cost a site its credibility.
What Structured Data Is Actually For
Schema is a shared vocabulary for describing the things on the web. A page is a web page, a practice is a local business, a dentist is a person, an implant consultation is a service. When you mark up your pages in that vocabulary, you are handing a machine a clean set of facts it would otherwise have to infer from layout, guessing and repetition.
Two practical things happen when the facts are clean:
- Search engines and AI systems can connect your pages to the same practice, the same address and the same dentists, instead of treating each page as an anonymous document that happens to mention a dentist.
- You stop depending on the machine guessing. A guessed address is a coin flip. A declared address is a fact.
What structured data does not do is make you rank, get recommended, or appear in an AI answer. Nobody can promise that, and we will not. What it does is remove an entire class of error from the process.
The Types That Matter For a Dental Practice
Swipe the table sideways to see every column.
| Type | What It Describes | Why It Matters Here |
|---|---|---|
Dentist | A single practice location | The base type for a dental office, and the one that carries address, hours, phone and services |
MedicalBusiness | A medical business that is not one location | The right choice for a clinic, a hospital or a multi-specialty group; it is the parent type of Dentist |
Organization | The business behind the locations | Useful for a group practice or a brand with more than one office |
Person | A named dentist | Connects a provider's name, credentials and profile page to the practice |
Service | One treatment you offer | Links a treatment page to the provider and to the area you serve, so a local question can find it |
FAQPage | The questions and answers on a page | Describes real questions a patient asked, in a form machines can read |
Most practices need three of these and ignore the rest: one Dentist entity for the location, one Person entity for each dentist, and one Service entity for each treatment page. If you run several locations, add an Organization that holds them together.
A Minimal Example, With a Fake Practice
The practice below does not exist. We use a made-up name on purpose, because nobody should copy a business name out of a schema example and into their own site.
Here is the smallest useful set, written as a list instead of a wall of punctuation:
@contextpoints at the schema.org vocabulary.@typeisDentist.nameisLakeside Family Dental.addressis aPostalAddresswithstreetAddress,addressLocality,addressRegion,postalCodeandaddressCountry.telephoneis the number a patient calls, formatted the way you write it everywhere else.urlis the page a human actually lands on.openingHoursSpecificationlists your hours, including the weekday and Saturday difference if you have one.sameAslists the other profiles that describe this same practice, so the engine can tie the records together.employeepoints at thePersonentities for your dentists, so the provider and the location are connected.
That block is small on purpose. You can extend it later. You cannot repair a wrong one.
Every value in the markup must already be true and visible on the page. Markup is a claim about your site, not a second version of it.
The Mistakes That Get Sites Ignored
Invented Credentials
The tempting move is to add an award, a certification or a rating that makes the practice look better. The rules that govern structured data are explicit that marked-up content has to be visible on the page, so anything invented is a false claim in machine-readable form. The same goes for marking up a review rating that does not appear on the page, which is the most common way we see a review schema get a site's structured data thrown out.
Markup For Content Nobody Can See
Marking up a service you do not offer, a location you have closed, or an answer tucked behind a menu so the engine cannot see it is describing a practice that does not exist. It also contradicts the page, which is the fastest way to have the whole block rejected.
Duplicated Entities
One practice, one entity. The usual failures: a separate Dentist entity on every treatment page, entities for the same location with slightly different addresses, and the practice and the brand each described as their own organization. Every duplicate is another version of you, and the engine has to pick one.
Code That Was Never Validated
A JSON-LD block with a trailing comma, a property that does not exist for that type, or opening hours that say you are open on a day you are closed. None of it throws a visible error. It is quietly ignored, and you will never know why. Validate the syntax, keep one canonical entity, and give each entity one permanent identifier that the rest of your pages reference.
The Honest Limits
There is no special schema for AI. No type and no combination of types guarantees that an assistant will name your practice, and we will not sell you one.
There are other limits worth being straight about:
- Clean markup does not replace content. It describes the page. The page still has to answer the question.
- A
FAQPageblock tells a machine what is on the page. Whether that turns into a visible result in the search engine is a separate question, and the visible result is not the point. The point is that the question and the answer are legible. - Markup does not settle a contradiction. If your page says you take walk-ins and your listings say you do not, describing both sides in schema does not fix it.
- Nothing here changes what your patients should be told about their care. That is a conversation with their own dentist, not with a machine and not with us.
Where This Sits With Everything Else
Schema is infrastructure. It is worth doing because it removes ambiguity, not because it is a magic unlock. It works with real pages, real reviews and consistent listings, and it is useless on top of a site that contradicts itself.
If your site does not have those pages yet, Smart AI Websites builds them with the markup already in place. If you have the pages and the markup is a mess, that is the first thing we fix when we start measuring. You can see the whole method in Dental AI Visibility.
Read Next
- Why Online Reviews Matter for Dental AI Visibility - the other half of the evidence, and how to build it.
- The Complete Dental AI Marketing Strategy for 2027 - where schema sits in the year-long plan.