Your service areas page tells AI exactly where you operate. Without it, AI has to infer your location from an address on a contact page and guess your reach. This blueprint structures every city, region, and state you serve so AI can confidently include you in location-based recommendations.
Location is one of the strongest filters AI applies. When someone asks "find a consultant in Denver" or "who offers this service in the Twin Cities," AI looks for explicit geographic data. A service areas page with structured data turns every location you serve into a matchable signal.
areaServed property on your organization node accepts an array of City, State, or Country objects. Each entry is a distinct geographic signal AI can match against user queries.GeoCircle with geoMidpoint and geoRadius gives AI a precise boundary instead of a vague "we serve the greater metro area."PostalAddress node with its own areaServed, so AI knows which office covers which region.WebPage node ties this page back to your organization, confirming that the geographic data belongs to your business entity.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
nameurlareaServedCopy 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 Professional Service 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. Latitude 6. Longitude 7. Organization name 8. Radius in miles 9. Service areas page description 10. Service areas page title 11. 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 Professional Service 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 the locations you actually serve.
{
"@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/#organization"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/service-areas/#breadcrumb"
}
},
{
"@type": "Organization",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_ORGANIZATION_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": "State",
"name": "YOUR_STATE"
}
],
"serviceArea": {
"@type": "GeoCircle",
"geoMidpoint": {
"@type": "GeoCoordinates",
"latitude": "YOUR_LATITUDE",
"longitude": "YOUR_LONGITUDE"
},
"geoRadius": "YOUR_RADIUS_IN_MILES"
}
},
{
"@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. Individual City entries match specific queries like "consultant in Minneapolis," while a State entry catches broader queries like "consultant in Minnesota." AI treats each entry as a separate match opportunity, so more specific entries mean more chances to appear in local results.
Use a Country entry in areaServed with "name": "US" and remove the GeoCircle. You can still list specific cities where you have a physical presence or strong client base. This tells AI you operate nationally but have concentrated expertise in certain markets.
No, it is optional. GeoCircle is most useful for businesses that serve a continuous radius — like a contractor who will travel 50 miles from their shop. If your coverage is defined by specific metro areas rather than distance, the City and State entries in areaServed are sufficient.