Dental Schema Markup.
Dentist subtype of MedicalBusiness deployed against the 12 ADA-recognized specialties. CDT-code mapped availableService enumeration. Organization to subOrganization to Dentist hierarchy at multi-location scale.
A dental schema deployment is four field surfaces layered on the right entity type.
Flat LocalBusiness deployment leaves all of the medical-vertical metadata on the table. The Dentist subtype unlocks medicalSpecialty, availableService against CDT, healthPlanNetworkId, hasCredential, and the entity classification Google's Knowledge Graph needs to read the practice as a real dental practice.
Dentist as MedicalBusiness, not flat LocalBusiness.
Dentist is a subtype of MedicalBusiness under LocalBusiness in Schema.org. Using the specific subtype gives Google's KG the right entity classification (dental practice, not generic local business), enables the medical-vertical metadata fields, and signals YMYL appropriately for Google's Reviews System framework. Flat LocalBusiness deployment skips the entire medical-vertical surface.
medicalSpecialty against the 12 ADA-recognized specialties.
Schema.org's medicalSpecialty field needs values from a recognized taxonomy. The ADA's 12 recognized specialties are the right taxonomy: Dental Anesthesiology, Dental Public Health, Endodontics, Oral and Maxillofacial Pathology, Oral and Maxillofacial Radiology, Oral and Maxillofacial Surgery, Oral Medicine, Orofacial Pain, Orthodontics and Dentofacial Orthopedics, Pediatric Dentistry, Periodontics, Prosthodontics. Invented values dilute the entity.
availableService mapped to standardized CDT codes.
CDT (Current Dental Terminology) is the ADA's own, copyrighted, annually-updated procedure-code system used across insurance claims. Mapping availableService values to CDT codes (D0150 evaluation, D2750 crown porcelain fused to high noble metal, D9610 therapeutic parenteral drug, etc.) prevents entity dilution by ambiguous marketing terminology. We map every procedure page's primary service to its CDT code.
healthPlanNetworkId and hasCredential for the verification surface.
healthPlanNetworkId populated per location surfaces the practice in insurance-filter queries. acceptedInsurance reads the same surface in plain text. hasCredential on the practitioner Person node carries ADA-recognized board certifications (American Board of Orthodontics, American Board of Periodontology, American Board of Endodontics, etc.) for the YMYL verification Google's Reviews System weighs.
From schema audit to deployed Dentist entity in four weeks. Then the entity authority compounds.
Schema diagnostic
Existing schema audit (entity type, populated fields, missing medical-vertical metadata, AggregateRating provenance, FAQPage deployment). Search Console rich-result eligibility review. Practitioner credential inventory against ADA-recognized board certifications. Procedure-page audit for CDT-code mapping potential.
Schema architecture
Dentist node designed against the practice (or each DSO location). medicalSpecialty array populated against the 12 ADA-recognized specialties relevant to the practitioners. availableService mapped to CDT codes per procedure page. healthPlanNetworkId and acceptedInsurance populated. hasCredential nodes built on practitioner Person entities.
Deployment + validation
Schema deployed via JSON-LD blocks. Rich Results Test validation across every page type. Search Console schema-error monitoring switched on. Per-page Service schema deployed for commercial pages where appropriate. Article schema with author Person reference deployed for blog and research pages.
Schema maintenance
Annual CDT-code updates (ADA publishes annually, January 1). Quarterly review against Google's Reviews System framework updates. Schema-error monitoring continuous. New procedure pages get CDT-mapped on publication.
What practices ask about schema before they engage.
What does the diagnostic actually cover?
Dentist schema deployment on your site, and the Section 5 compliance posture of the existing content. Output is a per-page ledger of load-bearing pages, advertising-rule exposure (Section 5.B testimonials, Section 5.F.6 SEO claims, Section 5.I.1 NCRDSCB disclaimer coverage), and commercial-query gaps in front of revenue.Diagnostic only, or does it convert into something ongoing?
Why do you cite ADA subsections everywhere?
We're using a bundled dental-marketing platform. Why switch?
Why <code>Dentist</code> schema rather than just <code>LocalBusiness</code>?
Dentist is a subtype of MedicalBusiness under LocalBusiness in Schema.org. Using the specific subtype gives Google's Knowledge Graph the right entity classification (dental practice, not generic local business), enables the medical-vertical metadata (medicalSpecialty, availableService, healthPlanNetworkId, acceptedInsurance), and signals YMYL appropriately for Google's Reviews System. Flat LocalBusiness deployment leaves all of that on the table.Stop deploying flat LocalBusiness schema on a practice that needs the medical-vertical entity surface. Book a diagnostic.
We read your existing schema deployment, your Search Console rich-result eligibility, and your procedure-page CDT-code mapping potential. The diagnostic comes back with the entity-type fix, the medicalSpecialty enumeration, and the CDT mapping scope.