Event Schema Generator - JSON-LD for Event Rich Results
Import existing JSON-LD
Paste JSON-LD or a full <script> tag. Matching fields fill the form; properties the form doesn't cover are kept in the output as they are.
Event Details
Status
Location
For online or mixed attendance. Emitted as a VirtualLocation.
Tickets & People
JSON-LD Output
What is Event schema?
Event schema is structured data that describes a scheduled event, such as a concert, workshop, festival, or sports match: its name, start and end times, venue, ticket prices, and current status. It uses the schema.org Event type or a subtype like MusicEvent or SportsEvent. Google uses it to list the event in its event search experience.
Each event date needs its own Event. A three night run of a play is three events, each with its own startDate and ticket link. Online events use a VirtualLocation with the stream or registration URL, and mixed events list both a Place and a VirtualLocation. The generator builds the right location from the attendance mode you pick.
Event schema example (JSON-LD)
A complete example you can adapt. Paste it into the page's HTML, or build your own with the generator above.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MusicEvent",
"name": "The Lantern Sessions: Live at Riverside Hall",
"startDate": "2026-09-18T19:30:00-04:00",
"endDate": "2026-09-18T22:30:00-04:00",
"eventStatus": "https://schema.org/EventScheduled",
"eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
"description": "An evening of acoustic folk with The Lantern Sessions and special guest Ana Ruiz.",
"image": [
"https://example.com/events/lantern-sessions-16x9.jpg"
],
"location": {
"@type": "Place",
"name": "Riverside Hall",
"address": {
"@type": "PostalAddress",
"streetAddress": "75 Water Street",
"addressLocality": "Hudson",
"addressRegion": "NY",
"postalCode": "12534",
"addressCountry": "US"
}
},
"offers": {
"@type": "Offer",
"url": "https://example.com/tickets/lantern-sessions-2026-09-18",
"price": 35,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"validFrom": "2026-06-01T10:00:00-04:00"
},
"performer": {
"@type": "MusicGroup",
"name": "The Lantern Sessions"
},
"organizer": {
"@type": "Organization",
"name": "Riverside Arts Collective",
"url": "https://example.com/"
}
}
</script> Which Google rich result does it enable?
Event markup makes the event eligible for Google's event experience: a list of upcoming events with dates, venues, and ticket links that appears for searches like "concerts near me" or "jazz this weekend". Pages that list events from many organizers, such as ticketing sites and local listings, use it as well as venue and promoter sites.
Google only shows events that take place at a physical location. An online-only event with a VirtualLocation is valid schema.org markup and other search engines can read it, but it is not eligible for Google's event results. A mixed event with a real venue is eligible.
Required and recommended properties
| Property | Status | Notes |
|---|---|---|
name | Required | The event title. Do not stuff in the venue or ticket price. |
startDate | Required | ISO 8601 date and time with a time zone offset. |
location | Required | A Place for in person events, a VirtualLocation for online ones, or both for mixed events. |
location.address | Required | A PostalAddress for the venue. |
location.name | Recommended | The venue name. Leave it out if you don't know it. |
endDate | Recommended | When the event finishes, in the same format as startDate. |
eventStatus | Recommended | Scheduled, Postponed, Cancelled, Rescheduled, or MovedOnline. |
offers | Recommended | One Offer per ticket type, with price, currency, availability, and a ticket URL. |
image, description | Recommended | Images in 16x9, 4x3, and 1x1 ratios help the listing stand out. |
performer, organizer | Recommended | Typed objects with a name, and a URL for the organizer. |
Common Event schema mistakes
- Marking up a single event that spans several separate dates. Create one
Eventper date. - Deleting markup for a cancelled event. Set
eventStatustoEventCancelledand keep the original date so people see the update. - Omitting the time zone offset, which can show the wrong start time to people in other regions.
- Using event markup for things that are not events, such as a sale, a coupon, or a course that can be started at any time.
- Expecting Google event results for a webinar. Online-only events are not eligible, even with correct
VirtualLocationmarkup.
Postponed, rescheduled and moved online
Keep the markup when plans change and update eventStatus
instead. For a postponed event with no new date yet, use
EventPostponed and leave the original startDate.
Once you have a new date, switch to EventRescheduled, set the
new startDate, and add the old one as
previousStartDate. If an in-person event becomes a stream,
use EventMovedOnline and change the attendance mode to
online.
Dates and time zones
Write start and end times with the venue's UTC offset, such as
2026-09-18T19:30:00-04:00. A time with no offset is
ambiguous, and a bare date like 2026-09-18 tells Google the
day but not the start time. Use the offset in force on the event date,
not today's: a New York event in January is -05:00, in
September -04:00.
Related Tools
Local Business Schema Generator
Generate LocalBusiness JSON-LD for Google Maps and local search results.
Product Schema Generator
Generate Product JSON-LD with price, availability, and review stars.
Article Schema Generator
Generate Article JSON-LD for rich results with headline and thumbnail.
FAQ Schema Generator
Generate FAQPage JSON-LD. Rich results limited to government and health sites since August 2023.