Event schema is structured data that tells search engines and AI assistants the essential facts about an event — its name, date, location, and how to attend or buy tickets. If you host concerts, webinars, workshops, conferences, or any dated happening, adding Event schema is the difference between being a paragraph a bot has to parse and being a clean, machine-readable record that can appear in search results, event carousels, and AI answers to questions like "what's happening this weekend near me."
What Event schema does and why it matters
When you mark up a page with Event JSON-LD, you hand search and AI systems the exact fields they need instead of forcing them to guess dates and venues from prose. That reliability is what gets you into rich results with the date and location shown directly, and into the shortlist of options an assistant reads out when someone asks about upcoming events. Without it, your event page competes as plain text and is far more likely to be summarized incorrectly — wrong date, wrong city — or skipped entirely.
Event schema is a specific type within the broader Schema.org vocabulary. If you are new to the format, start with our practical guide to JSON-LD and Schema.org, which covers how to embed structured data correctly before you specialize it for events.
The required and recommended properties
Google treats a handful of Event properties as required and several more as strongly recommended. Getting the required set right is what makes your markup eligible at all.
- name — the event's title, exactly as a person would recognize it.
- startDate — in ISO 8601 format with a timezone offset, e.g. 2026-09-14T19:00:00+02:00. This is the field people get wrong most often.
- location — a Place with a name and postal address for physical events, or a VirtualLocation with a URL for online events.
- endDate — recommended, and important for multi-day events so the listing shows the full range.
- eventAttendanceMode — whether the event is offline, online, or mixed. Essential now that hybrid events are common.
- eventStatus — scheduled, cancelled, postponed, or rescheduled. Keep this current; a stale "scheduled" on a cancelled event damages trust.
- offers — ticket price, currency, availability, and a URL to buy. For 2026, always express prices in euros.
- image and description — recommended for richer, more clickable listings.
Common mistakes that get Event markup ignored
The single most frequent error is a missing or malformed timezone on startDate. An event at "19:00" with no offset is ambiguous, and ambiguous data gets dropped. Always include the offset. The second common failure is marking up an event that isn't really an event — a general "special offers" page or a permanent product page — which violates the guidelines and can trigger a manual action.
Other pitfalls include listing the same event on multiple URLs without consolidating, forgetting to update eventStatus when plans change, and putting the markup on a page that doesn't visibly show the same information to human visitors. Structured data must match the visible content; hidden or contradictory markup is a policy violation. Before you publish, run your page through a validator — our guide on how to validate structured data shows which tools catch these errors and how to read their warnings.
Getting events into AI answers
Clean Event schema does more than earn rich snippets; it makes your events extractable by answer engines. When someone asks an AI assistant for events in a category or city, the assistant favors sources whose data is unambiguous and current. Local relevance helps here too — pairing Event markup with LocalBusiness schema for the venue strengthens the geographic signal that map and AI results rely on.
Keep every event page updated through its full lifecycle: publish it early with a correct startDate, update eventStatus the moment anything changes, and don't delete the page the day after — a well-marked past event still reinforces that your site is a reliable source for this category.
Not sure whether your Event markup is valid and visible to crawlers and AI? Run the CheckMy.site scanner to see exactly how bots read your structured data, spot missing required fields, and confirm your events are eligible for rich results and AI answers.