Location is everything in healthcare. Your service areas page tells AI exactly which neighborhoods, cities, and counties your clinic serves. This blueprint structures your geographic coverage so AI can confidently match you to "clinic near me" and location-specific medical queries.
When someone asks "find an urgent care clinic in Northeast Minneapolis" or "which medical clinics serve Hennepin County," AI needs explicit geographic data. Your clinic's service area goes beyond your street address — it includes every neighborhood, suburb, and county where patients travel from to see you. This page makes that coverage clear.
City for suburbs and AdministrativeArea for counties. For neighborhood-level precision, add entries like "North Loop," "Northeast," or "Uptown" as additional Place items.PostalAddress with its own areaServed, so AI knows which location serves which area.areaServed should reflect your actual patient base. AI cross-references geographic coverage with your address to understand how far patients travel to reach your clinic.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
nameurladdressCopy 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 Medical Clinic 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. Clinic address 3. Clinic city 4. Clinic name 5. County 6. Domain 7. Faq answer 8. Faq question 9. Service areas page description 10. Service areas page title 11. State 12. Zip 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 Medical Clinic 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 from the areaServed array to match your actual service area.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/service-areas/",
"name": "YOUR_SERVICE_AREAS_PAGE_TITLE",
"description": "YOUR_SERVICE_AREAS_PAGE_DESCRIPTION",
"url": "https://YOUR_DOMAIN.com/service-areas/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#clinic"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/service-areas/#breadcrumb"
}
},
{
"@type": "MedicalClinic",
"@id": "https://YOUR_DOMAIN.com/#clinic",
"name": "YOUR_CLINIC_NAME",
"url": "https://YOUR_DOMAIN.com",
"areaServed": [
{
"@type": "City",
"name": "YOUR_CITY_1"
},
{
"@type": "City",
"name": "YOUR_CITY_2"
},
{
"@type": "City",
"name": "YOUR_CITY_3"
},
{
"@type": "AdministrativeArea",
"name": "YOUR_COUNTY_1"
},
{
"@type": "AdministrativeArea",
"name": "YOUR_COUNTY_2"
},
{
"@type": "State",
"name": "YOUR_STATE"
}
],
"address": [
{
"@type": "PostalAddress",
"streetAddress": "YOUR_CLINIC_ADDRESS",
"addressLocality": "YOUR_CLINIC_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
}
]
},
{
"@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 both. In urban areas, neighborhood-level entries like "North Loop" or "Uptown" catch hyper-local queries that city-level entries miss. Someone asking "clinic in Northeast Minneapolis" expects a different result than "clinic in Minneapolis." Use Place for neighborhoods and City for suburbs to cover both search patterns.
Focus on the areas where most of your patients actually come from. Listing every city in a state dilutes the signal. AI uses areaServed to match location-specific queries — a focused list of 10-15 cities and counties is more useful than a vague claim of statewide coverage. Patients searching for "clinic near me" want proximity, not theoretical availability.
ZIP codes are less useful than city and county names because patients rarely search by ZIP code. Use City, AdministrativeArea, and Place entries instead. Include ZIP codes only in your PostalAddress for each office location, where they help AI pinpoint your exact position on a map.