Your service areas page tells AI exactly where your dental practice draws patients from and which neighborhoods, cities, and metro regions you serve. This blueprint structures your geographic coverage into machine-readable entries so AI systems can confidently recommend you for location-specific dental queries.
Location is the most common filter in dental searches. When someone asks AI "dentist near the North Loop" or "dental office in Edina," AI needs structured geographic data to match you. A service areas page without structured data forces AI to parse paragraph text for neighborhood and city names — and it misses most of them.
areaServed array on your Dentist node should list every neighborhood, city, or region you draw patients from. Each entry should use the appropriate Schema.org type: City, AdministrativeArea, or State.City type. This is the most precise signal and directly matches "dentist in [city]" queries.AdministrativeArea with the region name. This catches broader queries like "dental offices in Hennepin County."WebPage node should describe this as a service areas page so AI understands the purpose of the content.Without structured area data, AI may know your practice exists but cannot confirm whether you serve the location the patient is asking about — so it recommends a competitor whose coverage is explicit.
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
nameurltelephoneCopy 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 Service Areas 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. City 2. County 3. Domain 4. Faq answer 5. Faq question 6. Phone number 7. Practice name 8. Service areas page description 9. Service areas page title 10. State 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 Service Areas" - 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. Add or remove entries in the areaServed array to match every neighborhood, city, and region your practice serves.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Dentist",
"@id": "https://YOUR_DOMAIN.com/#practice",
"name": "YOUR_PRACTICE_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"areaServed": [
{
"@type": "City",
"name": "YOUR_CITY_1"
},
{
"@type": "City",
"name": "YOUR_CITY_2"
},
{
"@type": "City",
"name": "YOUR_CITY_3"
},
{
"@type": "City",
"name": "YOUR_CITY_4"
},
{
"@type": "City",
"name": "YOUR_CITY_5"
},
{
"@type": "AdministrativeArea",
"name": "YOUR_COUNTY_1"
},
{
"@type": "AdministrativeArea",
"name": "YOUR_COUNTY_2"
},
{
"@type": "State",
"name": "YOUR_STATE"
}
]
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/service-areas/",
"name": "YOUR_SERVICE_AREAS_PAGE_TITLE",
"description": "YOUR_SERVICE_AREAS_PAGE_DESCRIPTION",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/service-areas/#breadcrumb"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/service-areas/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Service Areas",
"item": "https://YOUR_DOMAIN.com/service-areas/"
}
]
},
{
"@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"
}
}
]
}
]
}
List every city and major neighborhood you genuinely draw patients from. AI matches location queries literally — if someone asks for a dentist in Uptown and Uptown is not in your areaServed array, you will not appear in the recommendation. The more complete your list, the more location queries you match.
Use City for specific municipalities and AdministrativeArea for counties, metro regions, or other administrative boundaries that contain multiple cities. For example, "Minneapolis" is a City while "Hennepin County" is an AdministrativeArea. Using both gives AI precise and broad coverage data for your practice.
You can and should include areaServed on your homepage as well. The service areas page is where you provide the most comprehensive list, but repeating your primary areas on other pages reinforces the signal. Use the same @id for the Dentist node across all pages so AI treats them as the same entity.