Structures your neighborhoods, delivery radius, and catering coverage so AI knows exactly where you operate. When someone asks "restaurant delivery in North Loop" or "catering near downtown Minneapolis," this page tells AI whether your restaurant covers that location.
Location is everything for restaurants. AI needs to know not just where your restaurant is, but every neighborhood and area you serve — especially if you offer delivery or catering. Without a structured service area, AI can only match you to queries for your exact address.
areaServed field accepts an array of geographic entities, letting you declare every neighborhood, city, or region where you provide delivery or catering.City object with a name, and include the broader State to give AI regional context.GeoCircle with geoMidpoint and geoRadius to define the boundary.PostalAddress so AI can calculate proximity and match your restaurant to "near me" queries relative to your physical location.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
nameurltelephoneaddressCopy 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 Restaurant 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. Domain 3. Faq answer 4. Faq question 5. Neighborhood or city 6. Phone number 7. Restaurant name 8. Service areas page description 9. Service areas page title 10. State 11. Street address 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 Restaurant 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 this template and replace every YOUR_* placeholder with your own data. Add or remove areas from the areaServed array to match your actual coverage.
{
"@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",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/service-areas/#breadcrumb"
}
},
{
"@type": "Restaurant",
"@id": "https://YOUR_DOMAIN.com/#business",
"name": "YOUR_RESTAURANT_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"address": {
"@type": "PostalAddress",
"streetAddress": "YOUR_STREET_ADDRESS",
"addressLocality": "YOUR_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
},
"areaServed": [
{
"@type": "City",
"name": "YOUR_NEIGHBORHOOD_OR_CITY_1"
},
{
"@type": "City",
"name": "YOUR_NEIGHBORHOOD_OR_CITY_2"
},
{
"@type": "City",
"name": "YOUR_NEIGHBORHOOD_OR_CITY_3"
},
{
"@type": "City",
"name": "YOUR_NEIGHBORHOOD_OR_CITY_4"
},
{
"@type": "City",
"name": "YOUR_NEIGHBORHOOD_OR_CITY_5"
},
{
"@type": "State",
"name": "YOUR_STATE"
}
]
},
{
"@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",
"@id": "https://YOUR_DOMAIN.com/service-areas/#faq",
"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 if possible. AI matches "near me" queries to specific names in your areaServed array. If someone searches "restaurant delivery in North Loop" and you only list "Minneapolis," AI may not make the connection. Include neighborhood names alongside city names for the best coverage.
Use GeoCircle when you deliver within a radius around your location rather than to specific named areas — for example, "free delivery within 3 miles." You can combine both approaches: list your primary neighborhoods and add a GeoCircle to define your delivery boundary.
If your delivery and catering areas differ significantly, consider listing all areas in a single areaServed array and using your FAQ or page copy to explain which services reach which areas. Schema does not natively support service-specific area mapping, but AI reads both the structured data and the visible page content to build a complete picture.