Event Schema (Event)
The event schema (Event) is a structured data markup based on the Schema.org standard, with which you describe dates, concerts, courses, or trade fairs in a machine-readable way. Search engines and AI assistants can thus recognize name, date, location, price, and ticket link unambiguously. This increases the chance that your event appears correctly and prominently in search results and AI answers.
Why the event schema matters
Dates are tricky for humans and machines alike, because they bundle many individual details: date, time, location, price, availability. If all of this appears only as running text on your page, a search engine has to guess which date is meant or whether the event takes place online or on site. With the event schema, you deliver these details in a clear, fixed format. Google can build a so-called rich snippet from it, that is, a highlighted search result with date and location. AI assistants like ChatGPT or Perplexity draw on the same data when someone asks: What's going on in my city this weekend? Without markup you often remain invisible for these answers.
How it works technically
The event schema is usually embedded as JSON-LD. This is a small data block in your page's source code that describes the event as an object of type Event. In it, you provide fields like name, startDate, endDate, location, offers (for ticket prices), and eventAttendanceMode (on site, online, or hybrid). The eventStatus field is important, with which you signal whether an event is taking place, has been postponed, or has been cancelled. Search engine crawlers and AI crawlers read this block without anything changing in the display for your visitors. The schema code thus runs invisibly in the background and complements what people see on the page anyway.
Common mistakes
The most common mistake is a missing or incorrectly formatted date. startDate must be in ISO format including the time zone, for example 2026-09-12T19:00:00+02:00, otherwise Google discards the markup. Just as often, the location with a full address is missing, or for online events the virtual URL. Another classic: the schema code contradicts the visible text, for example a different date in the JSON-LD than on the page. Such contradictions cost trust and can lead to devaluation. And finally, many mark up only the event name but leave out price, availability, and organizer – yet it is exactly these fields that make your result rich and citable in the first place.
Relevance to AI recommendations
AI assistants increasingly answer specific, time-bound questions: Which concerts are on in July, are there free spots in the pottery course, when does the fair open? To give such answers, the models need reliable, structured facts. The event schema delivers exactly that in a form a machine can adopt without room for interpretation. This also lowers the risk of hallucinations, that is, invented or outdated details, because the model finds a clean date instead of a vague passage of text. Anyone who marks up their events in a structured way increases the likelihood of being named and linked in AI answers. The event schema is thus a practical building block of AI visibility.
Example
A music school announces a summer concert. Instead of just writing running text, it stores an event schema in the source code: name Music School Summer Concert, startDate 2026-07-18T18:30:00+02:00, location with the address of the town hall, offers with admission of 8 euros and a ticket link, plus the organizer. Now if someone asks an AI assistant: What's going on in our city on the evening of July 18?, it can name the concert with the correct date, location, and price and point to the page. Without markup, the event would probably remain invisible to the AI.
Common questions
Do I need programming skills for the event schema?
Not necessarily. Many content management systems and plugins generate the JSON-LD automatically when you enter date, location, and price into a form. For custom pages, a developer or a schema generator helps. Afterwards, check the result with Google's Rich Results Test.
What happens if an event is cancelled or postponed?
Then you should update the eventStatus field, for example to EventCancelled or EventPostponed, and enter a new date when postponing. That way search results and AI answers stay current, and you avoid directing interested people to an event that is no longer taking place.