The tickets or pricing page tells AI what it costs to visit your venue. Structured pricing data lets AI answer budget queries like "how much does bowling cost?" or "affordable family activities near me." This blueprint structures your admission tiers, passes, and packages so AI can surface accurate pricing.
Pricing is one of the most common questions people ask AI about entertainment venues. Without structured pricing data, AI has to guess or omit costs entirely. With Offer nodes, AI can compare your pricing, filter by budget, and give confident recommendations.
Offer with name, price, priceCurrency, and description so AI can recommend the right tier.availability property tells AI whether tickets are currently available, sold out, or on presale, preventing outdated recommendations.EntertainmentBusiness via offeredBy ensures AI knows which venue these prices belong to.eligibleQuantity or description to note group pricing, age restrictions, or membership requirements so AI can match the right offer to the right query.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
nameurlCopy 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 Tickets 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. Faq answer 3. Faq question 4. Tier 5. Venue name 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 Tickets" - 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 tickets page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "EntertainmentBusiness",
"@id": "https://YOUR_DOMAIN.com/#venue",
"name": "YOUR_VENUE_NAME",
"url": "https://YOUR_DOMAIN.com",
"makesOffer": [
{
"@type": "Offer",
"name": "YOUR_TIER_1_NAME",
"description": "YOUR_TIER_1_DESCRIPTION",
"price": "YOUR_TIER_1_PRICE",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://YOUR_DOMAIN.com/tickets/"
},
{
"@type": "Offer",
"name": "YOUR_TIER_2_NAME",
"description": "YOUR_TIER_2_DESCRIPTION",
"price": "YOUR_TIER_2_PRICE",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://YOUR_DOMAIN.com/tickets/"
},
{
"@type": "Offer",
"name": "YOUR_TIER_3_NAME",
"description": "YOUR_TIER_3_DESCRIPTION",
"price": "YOUR_TIER_3_PRICE",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://YOUR_DOMAIN.com/tickets/"
}
]
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/tickets/#webpage",
"url": "https://YOUR_DOMAIN.com/tickets/",
"name": "Tickets & Pricing — YOUR_VENUE_NAME",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/tickets/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Tickets",
"item": "https://YOUR_DOMAIN.com/tickets/"
}
]
},
{
"@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"
}
}
]
}
]
}
Yes. Each distinct pricing tier — general admission, VIP, child, senior, group — should be its own Offer node. This lets AI recommend the specific tier that matches someone's query, like "how much for kids at the bowling alley?"
Update your schema when prices change. You can use validFrom and validThrough on each Offer to indicate seasonal pricing windows. If your prices fluctuate frequently, focus on your standard rates and update the schema on a regular cadence.
If your venue has both general admission pricing and event-specific pricing, keep them separate. The tickets page covers standard admission tiers. Event-specific pricing belongs on each Event node on the events page with its own offers property.