Event schema for AI search
Updated July 1, 2026 · 5 min read
Event schema is structured data that describes an event's name, dates, location (physical or virtual), and ticket/offer details, so engines can accurately answer 'when is X', 'where is Y', and surface your event in relevant answers. Implement it with precise start/end times, a clear location (including online events), and offer/ticket info where relevant, keep it current as details change, and validate it - stale or inaccurate event data is both useless and a trust problem.
Key takeaways
- Event schema makes dates, location, and ticket info machine-readable for 'when/where is X' answers.
- Include precise start (and end) times, location (physical or virtual), and offers/ticket info.
- Handle online and hybrid events explicitly with the right location type.
- Freshness is critical - update or mark events cancelled/postponed as details change.
- Match markup to the visible page and validate it.
What Event schema does
Event schema tells engines the essential facts of an event: what it is, when it happens, where (a venue or an online URL), and how to attend (tickets/offers). This lets engines answer time- and location-specific questions accurately and surface your event when someone asks about it. For anything date-bound, it turns your event page into a machine-readable answer.
Key properties
Capture the facts an attendee needs:
- name, startDate, and endDate with precise date/time.
- location: a physical place, or a virtual location (URL) for online events.
- eventAttendanceMode for online/offline/hybrid.
- offers: ticket price, availability, and where to buy, when relevant.
Freshness is non-negotiable
Event data has a hard expiry - the date passes, details change, things get cancelled or postponed. Stale event markup is worse than none: it can surface wrong information. Keep dates, times, and status current, use the appropriate status fields for cancellations or reschedules, and remove or update past events. Accurate, current event data is the whole point.
Match the page and validate
As with all schema, the markup must match what's on the visible page, and it should be validated with a structured-data testing tool. Handle online events explicitly - don't omit location just because there's no venue; use the virtual-location approach so engines understand it's an online event. Accurate, current, validated Event schema is what earns the 'when/where is X' answer.
Frequently asked questions
How do I mark up an online event?
Use the virtual attendance mode and a virtual location (the event URL) rather than omitting location. Engines need to understand it's online with a way to attend - don't leave location blank just because there's no physical venue.
What's the most common Event schema mistake?
Stale data - not updating dates, status, or details as they change. Expired or wrong event info is worse than none because it can surface incorrect answers. Keep it current and use status fields for cancellations/reschedules.
What are the essential Event properties?
name, startDate (and endDate), location (physical or virtual), attendance mode, and offers/ticket info where relevant - the facts someone needs to know what it is, when, where, and how to attend.
Does Event schema need to match the page?
Yes - like all structured data, the markup must reflect what's visibly on the page, and you should validate it. Mismatched event data gets ignored and undermines trust.
Put this into practice — free.
Get your free AI-visibility audit and see where engines find you today.