MedicalSpecialty schema for dental.

The MedicalSpecialty enumeration and the Dentist subtype

medicalSpecialty takes values from the Schema.org MedicalSpecialty enumeration. For dental practices, the relevant values include Dentistry (the general value), Orthodontic, Endodontic, Periodontic, plus references to the 12 ADA-recognized specialties through structured naming. The Dentist type is a subtype of MedicalBusiness under LocalBusiness and inherits the medicalSpecialty slot. The values must align with the practice's legally defensible scope of practice per the practitioners' training and board certifications, not aspirational positioning. Misalignment with the ADA-recognized specialty list trips ADA Section 5.I.1 for general dentists and exposes specialty practices to board complaints from competitors. The MedicalBusiness vs LocalBusiness spoke covers the inheritance chain.

medicalSpecialty vs availableService for procedures

medicalSpecialty describes the practitioner's recognized practice area (the broad clinical category). availableService with MedicalProcedure values describes the specific procedures the practice performs (mapped to CDT codes). The two layers work together rather than competing. A periodontist's medicalSpecialty reads Periodontic, and the availableService array enumerates D4000-block CDT procedures (D4341 scaling and root planing, D4263-D4266 bone replacement grafts, D4270-D4278 mucogingival surgery, etc.). An endodontist's medicalSpecialty reads Endodontic, and availableService enumerates D3000-block CDT procedures. Collapsing the two layers into one dilutes the entity signal: putting procedures inside medicalSpecialty or putting specialty values inside availableService blurs what each slot signals to Google's Knowledge Graph. The CDT codes and service schema hub covers the per-procedure work; periodontist SEO schema shows the deployment scope for that specialty surface.

SchemaPilot examples and common deployment patterns

Public deployment examples from tools like SchemaPilot and the broader dental-vertical SEO community show two recurring patterns. The first ships medicalSpecialty as a single string value ("Dentistry" for general practice, "Orthodontic" for an orthodontist) on a single Dentist node, simple and correct for a solo single-specialty practice. The second ships an array of medicalSpecialty values where the practice covers multiple recognized specialties or where multiple specialty-credentialed practitioners share the location. The array pattern is valid Schema.org but requires careful per-practitioner attribution so Google's Knowledge Graph reads which practitioner carries which credential. The wrong pattern collapses all practitioners' specialties onto one node without per-practitioner Person distinction, which trips ADA Section 5.I.1 for practitioners whose credentials don't support the claim.

Multi-practitioner facilities and Google rich-result eligibility

A multi-practitioner facility carries multiple specialty signals. The Organization-level node may set medicalSpecialty to the broadest accurate value (Dentistry). Per-practitioner Person nodes carry their individual medicalSpecialty reflecting the credentials of each practitioner. Per-location Dentist nodes may carry an array of values reflecting the specialties practiced at that physical location. The structure prevents over-claiming at the entity level while surfacing the real practitioner mix. As for rich-result eligibility: medicalSpecialty feeds the medical-vertical classification Google uses for the entity (YMYL classification under the Helpful Content System, Reviews System medical-content framework evaluation, medical-specialty disambiguation) rather than directly triggering a SERP rich result. Direct rich-result eligibility flows through other schema types (FAQPage, Article, BreadcrumbList, Review). The medicalSpecialty value is foundational rather than eligibility-triggering on its own. The full Dental SEO engagement deploys the per-slot schema across the practice's actual practitioner mix.