The provider profile page gives each dentist in your practice a verifiable identity that AI can reference. When a patient asks "tell me about Dr. Smith" or "is this dentist board certified?", AI pulls from the structured data here. This blueprint makes credentials, education, and specialties machine-readable.
Patients choose dentists based on trust. AI uses provider profile data to verify credentials and present dentists as qualified professionals. Without structured provider data, AI can only say your practice exists — not who works there or what qualifies them.
Dentist (Person) node with name, image, jobTitle, and medicalSpecialty gives AI the core profile data.hasCredential property lists degrees (DDS, DMD) and board certifications that AI uses as trust signals.alumniOf property with dental school and graduation year builds credibility in AI recommendations.Dentist (Organization) entity using worksFor links the individual to your practice.Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.
Researched and tested by Minnesota AI
namesameAsimagemedicalSpecialtynameCopy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.
You are implementing AIFDS-compliant JSON-LD structured data for a Dentist Provider Profile page. AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which structured data fields AI systems actually read, parse, and use when deciding whether to cite a page. Documentation at aifds.org. Before generating any code, ask me for the following information in a single numbered list. Do not generate schema until I have answered every required field. REQUIRED — do not proceed without these: 1. Credential name 2. Degree 3. Dental school 4. Dental specialty 5. Domain 6. Faq answer 7. Faq question 8. Healthgrades url 9. Job title 10. Linkedin url 11. Practice name 12. Provider bio 13. Provider name 14. Provider photo 15. Provider slug OPTIONAL — ask for these but proceed if I skip them: 1. Any additional details not covered above Once I provide the information, output a complete JSON-LD script block ready to paste into the <head> of my HTML page. Output requirements: - Valid JSON-LD wrapped in <script type="application/ld+json"> tags - schema.org vocabulary only - Every AIFDS-required field for this industry and page type included - Include this data attribute on the script tag: data-aifds="aifds.org Dentist Provider Profile" - No placeholder text — omit missing optional fields rather than fill with examples - After the code block, list any optional fields skipped that would strengthen AI citation
Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai
Copy the template below and replace every YOUR_* value with your own data. This block belongs in a <script type="application/ld+json"> tag in the <head> of each provider profile page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Dentist",
"@id": "https://YOUR_DOMAIN.com/providers/YOUR_PROVIDER_SLUG/#provider",
"name": "YOUR_PROVIDER_NAME",
"image": "https://YOUR_DOMAIN.com/YOUR_PROVIDER_PHOTO.jpg",
"jobTitle": "YOUR_JOB_TITLE",
"medicalSpecialty": "YOUR_DENTAL_SPECIALTY",
"description": "YOUR_PROVIDER_BIO",
"hasCredential": [
{
"@type": "EducationalOccupationalCredential",
"credentialCategory": "YOUR_DEGREE",
"name": "YOUR_CREDENTIAL_NAME"
}
],
"alumniOf": {
"@type": "EducationalOrganization",
"name": "YOUR_DENTAL_SCHOOL"
},
"worksFor": {
"@id": "https://YOUR_DOMAIN.com/#practice"
},
"sameAs": [
"YOUR_HEALTHGRADES_URL",
"YOUR_LINKEDIN_URL"
]
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/providers/YOUR_PROVIDER_SLUG/#webpage",
"url": "https://YOUR_DOMAIN.com/providers/YOUR_PROVIDER_SLUG/",
"name": "YOUR_PROVIDER_NAME — YOUR_PRACTICE_NAME",
"isPartOf": { "@id": "https://YOUR_DOMAIN.com/#website" },
"about": { "@id": "https://YOUR_DOMAIN.com/providers/YOUR_PROVIDER_SLUG/#provider" }
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/providers/YOUR_PROVIDER_SLUG/#breadcrumb",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://YOUR_DOMAIN.com/" },
{ "@type": "ListItem", "position": 2, "name": "Providers", "item": "https://YOUR_DOMAIN.com/providers/" },
{ "@type": "ListItem", "position": 3, "name": "YOUR_PROVIDER_NAME", "item": "https://YOUR_DOMAIN.com/providers/YOUR_PROVIDER_SLUG/" }
]
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_2"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_3",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_3"
}
}
]
}
]
}
Use Dentist as the type for individual dentists — Schema.org allows it for both the practice (organization) and individual practitioners. The @id differentiates them. Alternatively, you can use Person with "jobTitle": "Dentist" for clarity.
Include your dental degree (DDS or DMD), any specialty board certifications, and relevant professional memberships (ADA, state dental associations). Each credential as a separate EducationalOccupationalCredential gives AI verifiable data points.
Yes. Each dentist should have their own profile page with their own @id. AI increasingly serves queries about specific providers — "Dr. Johnson dentist reviews" — and individual pages let AI answer these directly.