The contact page makes your entertainment venue reachable through AI. When someone asks "how do I contact this place?" or "what are their hours?", AI pulls from the structured data on this page. This blueprint ensures your phone, email, address, and hours are all machine-readable.
The contact page is the definitive source for how to reach your venue. AI systems often pull contact details from this page specifically, so structured data here ensures accuracy across every platform that references your business.
ContactPoint node with telephone, email, and contactType gives AI a structured way to surface your contact information.PostalAddress with street, city, state, and zip ensures AI can give accurate directions.openingHoursSpecification on the contact page reinforces your hours for AI queries like "are they open right now?"ContactPage as the WebPage type tells AI this is specifically the page for reaching you.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
nameurltelephoneemailaddressgeoopeningHoursSpecificationCopy 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 Entertainment Business Contact 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. Email 4. Faq answer 5. Faq question 6. Latitude 7. Longitude 8. Phone number 9. State 10. Street address 11. Sunday close 12. Sunday open 13. Venue name 14. Weekday close 15. Weekday open 16. Weekend close 17. Weekend open 18. 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 Entertainment Business Contact" - 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 contact page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "EntertainmentBusiness",
"@id": "https://YOUR_DOMAIN.com/#venue",
"name": "YOUR_VENUE_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"address": {
"@type": "PostalAddress",
"streetAddress": "YOUR_STREET_ADDRESS",
"addressLocality": "YOUR_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "YOUR_LATITUDE",
"longitude": "YOUR_LONGITUDE"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday"],
"opens": "YOUR_WEEKDAY_OPEN",
"closes": "YOUR_WEEKDAY_CLOSE"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Friday", "Saturday"],
"opens": "YOUR_WEEKEND_OPEN",
"closes": "YOUR_WEEKEND_CLOSE"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Sunday",
"opens": "YOUR_SUNDAY_OPEN",
"closes": "YOUR_SUNDAY_CLOSE"
}
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"contactType": "customer support"
}
},
{
"@type": "ContactPage",
"@id": "https://YOUR_DOMAIN.com/contact/#webpage",
"url": "https://YOUR_DOMAIN.com/contact/",
"name": "Contact — YOUR_VENUE_NAME",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#venue"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Contact",
"item": "https://YOUR_DOMAIN.com/contact/"
}
]
},
{
"@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"
}
}
]
}
]
}
If your venue takes reservations or group bookings, add a second ContactPoint with "contactType": "reservations" and the dedicated phone number or email. This lets AI distinguish between general inquiries and booking requests.
Yes. AI systems may index the contact page independently. Including openingHoursSpecification here ensures that no matter which page AI reads first, it has your hours available to answer time-sensitive queries.
Parking is not a standard schema property, but you can include it in the venue description or use amenityFeature with a LocationFeatureSpecification for parking details. AI increasingly uses amenity data when recommending venues.