Event Schema Stack
Event pages with rich details, breadcrumb context, and FAQs. Works for general events and subtypes like MusicEvent or BusinessEvent.
When to use this stack
- Event pages with ticket offers and location details
- Tour or one-off events needing clearer eligibility and navigation
- Pages where FAQs address access, tickets, and schedule changes
What is included
Core event entity; use relevant subtype (MusicEvent, BusinessEvent) with dates, location, and offers.
Clarify access, tickets, parking, and schedule changes.
Give navigation context for the event within the site.
Properties across the bundle
Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.
Required properties
- eventAttendanceMode
- itemListElement[].name
- location.name
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- offers.price
- offers.priceCurrency
- startDate
Recommended properties
- description
- endDate
- eventStatus
- image
- itemListElement[].item
- location.address
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- offers.availability
- offers.url
- organizer.name
- performer.name
Combined JSON-LD
Paste this as one script tag, then replace every example value with data from the live page.
[
{
"@context": "https://schema.org",
"@type": "MusicEvent",
"@id": "https://www.example.com/events/summer-sounds#event",
"name": "Summer Sounds Live",
"description": "Outdoor summer concert featuring indie and electronic artists.",
"startDate": "2026-08-12T19:00:00-05:00",
"endDate": "2026-08-12T22:30:00-05:00",
"eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
"eventStatus": "https://schema.org/EventScheduled",
"image": [
"https://www.example.com/images/summer-sounds-hero.webp"
],
"location": {
"@type": "Place",
"name": "Riverside Amphitheater",
"address": {
"@type": "PostalAddress",
"streetAddress": "500 River Rd",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78702",
"addressCountry": "US"
}
},
"organizer": {
"@type": "Organization",
"name": "City Events",
"url": "https://www.example.com"
},
"performer": [
{ "@type": "MusicGroup", "name": "Indie Collective" },
{ "@type": "Person", "name": "DJ Aurora" }
],
"offers": {
"@type": "Offer",
"price": "59.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://tickets.example.com/summer-sounds"
}
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Is there parking on site?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Paid parking is available at the Riverside Garage next door; rideshare drop-off is at Gate B."
}
},
{
"@type": "Question",
"name": "What if it rains?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The event is rain or shine. In severe weather, we will email ticket holders with reschedule information."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Events", "item": "https://www.example.com/events" },
{ "@type": "ListItem", "position": 3, "name": "Summer Sounds Live", "item": "https://www.example.com/events/summer-sounds" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
Common errors and fixes
- Missing currency or availability
Use ISO currency codes and complete schema.org availability URLs in Offer data.
- Incomplete shipping details
Include shippingDestination.addressCountry and deliveryTime.transitTime with units.
- Return policy is not connected
Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.
- FAQ answers differ from the page
Keep structured FAQ answers identical to visible answers.
Stack FAQs
Can I use MusicEvent or BusinessEvent?
Yes. Use the subtype that matches the event. Required fields (name, startDate, location, offers) remain the same.
Do I need offers for free events?
If free, you can omit price/priceCurrency; still set availability and a registration URL if applicable.