Every medicine in my pharmacy has two descriptions. There is the box the patient reads: friendly design, brand name, a few reassurances. And there is the label a professional reads: the exact compound, the strength, the manufacturer, the batch, the expiry. The patient’s box persuades. The professional’s label informs, in a standardized format anyone trained can read in seconds.
Your website has the first kind of description and, in most cases, is missing the second entirely. Schema markup is the professional label for your practice: a standardized layer of information, invisible to human visitors, that tells machines exactly what your website is about. This is a dental practice. It is at this address. These are the clinicians and their qualifications. These are the treatments. These are the answers to common questions.
For years, skipping it cost practices a little. Now it costs a lot, and this piece explains why, what to add, and how to check your own site in about ten minutes, with no code knowledge required.
Why This Suddenly Matters Much More
Search engines have read schema for over a decade, using it to show richer results: star ratings under listings, FAQ dropdowns, opening hours. Useful, but cosmetic enough that many practices ignored it without much penalty.
What changed is who is reading. Google’s AI Overviews and assistants like ChatGPT and Perplexity now compose direct answers to patient questions, including “which practice should I choose” questions, and they compose them from information they can confidently verify. A machine reading a page without schema has to infer what the page is about from prose written for humans. Inference means uncertainty, and when the topic is health, cautious systems respond to uncertainty the same way every time: they leave you out of the answer.
Schema removes the guesswork. It is you, telling the machine, in the machine’s own language, exactly who you are. In my piece on how ChatGPT chooses which dentist to recommend, machine-readable structure is one of the five signals that decide the answer. This is that signal, in detail.
What It Looks Like (Do Not Worry, You Will Not Write This)
Schema usually lives in a small block of code called JSON-LD, tucked into a page’s header. Here is a simplified example for a dental practice, just so the concept is concrete:
{
"@context": "https://schema.org",
"@type": "Dentist",
"name": "Example Dental Clinic",
"address": {
"@type": "PostalAddress",
"streetAddress": "12 Example Road",
"addressLocality": "Example City"
},
"telephone": "+00 0000 000000",
"url": "https://exampledental.com",
"medicalSpecialty": "Dentistry",
"employee": {
"@type": "Person",
"name": "Dr. A. Example",
"jobTitle": "Principal Dentist"
}
}
To you, that is a wall of brackets. To a machine, it is the clearest possible statement of who you are. That asymmetry is the entire point.
The Five Types That Matter for a Practice
- Your organization. The foundation: a Dentist, MedicalClinic, or Physician type declaring your practice’s name, address, phone, hours, and website. This must match your Google Business Profile and every directory exactly. Consistency is the currency here; contradictions between sources are what make machines skip you.
- Your people. Person markup for each clinician, with name, role, and qualifications, connected to your organization. Health-cautious systems care enormously about who is behind the care. Named, credentialed people are a trust signal; an anonymous practice is a risk.
- Your treatments. Markup on each key treatment page describing the service offered. This is what lets a machine connect “dental implants” queries to your practice specifically, rather than to dentists in general.
- Your answers. FAQPage markup on pages that answer patient questions. AI systems assemble answers from question-and-answer content constantly, and this markup hands them your answers in their preferred format, with your name attached.
- Your breadcrumbs. Small markup describing how pages relate: this implant page belongs under this dental practice. It helps machines understand your site as one coherent entity instead of scattered pages.
Check Your Own Site in Ten Minutes
- Open Google’s free Rich Results Test at search.google.com/test/rich-results.
- Paste in your homepage address and run the test. Then do the same for your most important treatment page.
- Read the result. If it reports detected items like Organization, LocalBusiness, Dentist, Person, or FAQPage, you have something in place, and the question becomes whether it is accurate and complete. If it reports nothing, your website is speaking only to humans, and every machine reading it is guessing.
- While you are there, check one competitor: whichever practice keeps appearing when you search your main treatment locally. If they have markup and you do not, you have found one concrete reason machines prefer them.
The Mistakes That Waste the Effort
- Markup that contradicts reality. Schema saying one address while your business profile says another is worse than no schema. You have now put the contradiction in writing, in the machine’s own language.
- Marking up what is not on the page. Schema must describe content that actually exists on the page. Claiming FAQ answers or reviews that are not visibly there violates the guidelines and erodes exactly the trust you are trying to build.
- Set and forget. New clinician joins, prices change, a treatment is retired, and the markup quietly goes stale. Schema needs the same light maintenance as your business profile: a review a few times a year.
- Plugin false confidence. Website platforms and SEO plugins often add generic markup automatically. It is better than nothing, but it usually says “a business exists here” rather than “a specific dental practice with these named clinicians offers these treatments.” The value is in the specificity.
Do You Need a Developer, and How Big a Job Is This?
Usually yes, and usually small. For a typical practice website, complete schema across the key pages is bounded work: days, not months, for someone who has done it before. If your site runs WordPress, SEO plugins such as Rank Math or SEOPress can carry much of it, configured carefully rather than left on defaults. What matters is that someone who understands both the technical guidelines and your clinical reality writes the actual content of the markup, because it is a statement of fact about a healthcare provider, and it should be treated with the same care as anything else you publish under your name.
An Honest Caveat
Schema is necessary, not sufficient. It will not rescue thin content, generic reviews, or an inconsistent identity, and nobody can guarantee what any AI system will say about you. What schema does is remove the guesswork that keeps cautious machines from recommending you at all. It is the cheapest, most bounded fix on the entire AI visibility list, which is exactly why it belongs near the top of it.
Where This Fits in the Bigger Picture
Schema is one of six areas we check in the AI Audit, alongside what AI assistants actually say about you, your entity consistency, your crawlability, your review substance, and your competitor picture. If the ten-minute check above came back empty, that is worth knowing before your next marketing conversation, whoever it is with. Ask them about schema. If they cannot explain it in plain language, you have learned something useful about them too.