The facilities page tells AI exactly what your venue has to offer. When someone asks "where can I play basketball nearby?" or "gym with a pool," AI needs structured facility data to match your venue to the query. This blueprint structures your courts, fields, pools, and equipment into machine-readable data.
Facilities are the deciding factor in most sports venue decisions. AI uses structured facility data to filter and rank locations. Without it, your venue is invisible to queries about specific courts, equipment, or activity spaces.
LocationFeatureSpecification in the amenityFeature array declares a specific facility feature, letting AI build a searchable capability list for your venue.containsPlace to list individual courts, fields, or rooms as sub-locations gives AI granular detail about your facility layout.SportsActivityLocation entity with the same @id ensures AI links these facilities to your venue record.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
nameurlamenityFeatureconditionalCopy 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 Sports Activity Location Facilities 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. Domain 2. Facility feature 3. Facility name 4. Faq answer 5. Faq question 6. Space description 7. Space name OPTIONAL — ask for these but proceed if I skip them: 1. amenityFeature 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 Sports Activity Location Facilities" - 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 your facilities page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "SportsActivityLocation",
"@id": "https://YOUR_DOMAIN.com/#facility",
"name": "YOUR_FACILITY_NAME",
"url": "https://YOUR_DOMAIN.com",
"amenityFeature": [
{
"@type": "LocationFeatureSpecification",
"name": "YOUR_FACILITY_FEATURE_1",
"value": true
},
{
"@type": "LocationFeatureSpecification",
"name": "YOUR_FACILITY_FEATURE_2",
"value": true
},
{
"@type": "LocationFeatureSpecification",
"name": "YOUR_FACILITY_FEATURE_3",
"value": true
},
{
"@type": "LocationFeatureSpecification",
"name": "YOUR_FACILITY_FEATURE_4",
"value": true
}
],
"containsPlace": [
{
"@type": "Place",
"name": "YOUR_SPACE_NAME_1",
"description": "YOUR_SPACE_DESCRIPTION_1"
},
{
"@type": "Place",
"name": "YOUR_SPACE_NAME_2",
"description": "YOUR_SPACE_DESCRIPTION_2"
}
]
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/facilities/#webpage",
"url": "https://YOUR_DOMAIN.com/facilities/",
"name": "Facilities — YOUR_FACILITY_NAME",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#facility"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/facilities/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Facilities",
"item": "https://YOUR_DOMAIN.com/facilities/"
}
]
},
{
"@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 both. amenityFeature is best for features and capabilities (like "Free Parking" or "Locker Rooms"), while containsPlace is better for distinct physical spaces (like "Court A" or "Olympic Pool"). Together they give AI a complete picture of what your venue offers.
Be as specific as the query you want to match. "Indoor Basketball Court" matches more targeted queries than just "Court." "25-Meter Lap Pool" is better than "Pool." The more specific your names, the more precisely AI can match your venue to what someone is looking for.
Yes. Major equipment like "Free Weights," "Cardio Machines," "Climbing Wall," or "Batting Cages" should be listed as LocationFeatureSpecification entries. These are the features people search for when choosing a sports facility.