Event schema: how to mark up events for Google and AI
Event markup tells search engines when and where something happens. Here are the required fields, how to handle cancelled or online events, and common errors.
A concert, a webinar, and a store workshop all have the same problem. People search for them by date and place, and your page has to state both in a form a machine can read. Event schema does that. This guide covers which fields matter, how to handle changes, and the mistakes that get markup ignored.
What event schema does
Event markup is JSON-LD that describes one event: its name, start time, location, and ticket details. Google can use it to show your event in event listings and rich results. Eligibility is never guaranteed, and Google can change which features it shows.
AI answer engines are a different story. No vendor has published how they use event markup. Treat it as a clean, unambiguous statement of facts that any system can parse. The visible page still has to say the same things in plain text.
Required and recommended fields
Google's documentation lists a small set of required properties. Check the current event structured data page before you ship, since requirements can change. At the time of writing, the core set looks like this:
- name: the event title, as shown on the page.
- startDate: an ISO 8601 date and time, with a timezone offset if you know it.
- location: a Place with a name and address for in-person events, or a VirtualLocation with a URL for online ones.
Beyond those, fill in what you have. These fields help users and reduce ambiguity:
- endDate, so a listing shows how long the event runs.
- description and image, which should match the page.
- offers, with price, currency, availability, and the ticket URL.
- organizer and performer, which tie the event to a known entity.
- eventStatus and eventAttendanceMode, covered below.
Status and attendance mode
Events change. Schema.org has values for that, and using them beats deleting the page.
Event status
Set eventStatus to EventScheduled by default. If the event is called off, switch it to EventCancelled and keep the page live with a clear note. Use EventPostponed when there is no new date yet. When a new date is set, use EventRescheduled and update startDate. Use EventMovedOnline when an in-person event goes virtual.
Attendance mode
Use OfflineEventAttendanceMode for in-person events, OnlineEventAttendanceMode for virtual ones, and MixedEventAttendanceMode for hybrid. For hybrid events, list both a Place and a VirtualLocation under location.
Common mistakes
- Marking up a series as one event. Give each date its own Event with its own startDate, and ideally its own URL or a clear section on the page.
- Using Event for promotions. A sale or a discount period is not an event. Google's guidelines say not to mark those up.
- Dates that disagree with the page. If the markup says 14 March and the heading says 15 March, expect the markup to be ignored.
- Relative or partial dates. Use a full ISO 8601 value, not 'next Friday' or just a month.
- Stale past events. Leave old pages up if they have value, but do not keep them marked as scheduled.
Testing and maintenance
Run each template through the Rich Results Test after you add markup. Then watch the Enhancements reports in Search Console for errors that appear at scale. A single bad template can break hundreds of event pages at once.
If your events come from a database or a booking tool, generate the JSON-LD from the same fields that render the visible page. That keeps dates, prices, and status in sync without manual edits. It also means a cancellation updates both the text and the markup in one step.
What to do next
- Pick your five next events and confirm each has its own page or clear section.
- Add name, startDate, and location, then fill in offers, image, and organizer.
- Set eventStatus and eventAttendanceMode explicitly.
- Validate in the Rich Results Test, then check Search Console a week later.
- Build a rule that updates the markup whenever an event is cancelled or moved.