Event schema
A scheduled occurrence with a start time, a location and an attendance mode.
Where to use it
Webinars, launches, conferences.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
{
"@context": "https://schema.org",
"@type": "Event",
"name": "Acme Reference",
"startDate": "2026-09-01T18:00:00+00:00",
"location": {
"@type": "VirtualLocation",
"url": "https://www.seoforsolos.com/live"
},
"endDate": "2026-09-01T19:00:00+00:00",
"eventStatus": "https://schema.org/EventScheduled",
"eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
"offers": {
"@type": "Offer",
"price": "249.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.seoforsolos.com/pricing"
},
"performer": {
"@type": "Person",
"name": "A Real Person"
}
}Generate a Event node with your own values in the schema generator, and lint what your page actually ships with the schema validator.
Properties
| Property | Status |
|---|---|
name | Required |
startDate | Required |
location | Required |
endDate | Recommended |
eventStatus | Recommended |
eventAttendanceMode | Recommended |
offers | Recommended |
performer | Recommended |
The three mistakes this type attracts
- 01A startDate without a timezone offset.
- 02Omitting eventAttendanceMode for an online event.
- 03Leaving eventStatus stale after a cancellation.
Related types
Where this appears in the playbook
- Structured data: what each type is for and which ones earned their place.
- The schema graph: composing types into one graph with stable identifiers.
- One JSON-LD script per page, holding one @graph
- Stable @id anchors that cross-reference rather than duplicate
- Optional fields are omitted, never emitted as empty strings
- Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.
Questions
What is the Event schema type for?
A scheduled occurrence with a start time, a location and an attendance mode. Use it on: webinars, launches, conferences.
Which Event properties are required?
Event requires 3 properties: name, startDate, location. It also recommends 5: endDate, eventStatus, eventAttendanceMode, offers, performer.
Does Event produce a rich result?
Event is eligible for a Google rich result when its required properties are present and valid. A validation error therefore has a visible cost in the search result itself.
What is the most common Event mistake?
The most common Event mistake is: A startDate without a timezone offset.