An Event is a Schema.org structured data type representing a scheduled occurrence happening at a particular time and physical or virtual location. It serves as the parent class for more specific event subtypes like BusinessEvent, MusicEvent, ScreeningEvent, or EducationEvent. By implementing Event markup with properties such as startDate, location, offers, and performer, organizations provide search engines with explicit, machine-readable details that power event-rich snippets, Google's event search experience, and AI-generated overviews.
Glossary
Event

What is Event?
The Event type is a foundational Schema.org class used to structure data about any scheduled occurrence at a specific time and location, enabling search engines to understand and display event details in rich results.
The Event type inherits from the top-level Thing class and supports critical linking properties like sameAs for entity disambiguation and organizer to connect the event to an Organization entity. Proper implementation requires a valid @type declaration and a unique @id Internationalized Resource Identifier to establish the event as a distinct node within an enterprise knowledge graph, ensuring unambiguous citation by retrieval-augmented generation systems.
Core Properties of Event Markup
The Schema.org Event type provides a standardized vocabulary for describing scheduled occurrences. Proper implementation of these core properties ensures AI-driven search engines can accurately parse, display, and cite event details in generative overviews.
Temporal Anchoring
The startDate property is the only strictly required field for an Event, establishing its position in time. Use ISO 8601 formatting to disambiguate time zones and durations.
- startDate: The precise moment the event begins (e.g.,
2025-10-15T19:00:00-05:00). - endDate: The scheduled conclusion, critical for calculating duration in calendar applications.
- doorTime: A distinct property for admission time, separate from the performance start.
- previousStartDate: Used to record the original date if an event is rescheduled, preserving historical accuracy for knowledge graphs.
Spatial Context
The location property connects an event to a physical or virtual space, enabling map integrations and local search relevance.
- Place: Link to a fully defined Place entity with a postal address and geo-coordinates.
- VirtualLocation: Use for webinars or live streams, specifying the
urlof the broadcast. - Text: A simple string like 'Downtown Conference Center' is valid but limits entity disambiguation.
- eventAttendanceMode: A critical enumeration (
OfflineEventAttendanceMode,OnlineEventAttendanceMode, orMixedEventAttendanceMode) that explicitly signals the delivery format to search crawlers.
Offer & Pricing Structure
The offers property links an Event to its commercial availability, enabling transactional rich results directly in search engine results pages.
- Offer: An embedded object specifying
price,priceCurrency, andavailability(e.g.,SoldOut,InStock). - AggregateOffer: Use when multiple ticket tiers exist, summarizing the
lowPriceandhighPricerange. - validFrom: Timestamps the offer's activation, preventing premature display of early-bird pricing.
- free: A Boolean property that, when set to
true, overrides price fields and signals a no-cost registration.
Performer & Organizer Attribution
Distinguishing the agent responsible for the event from the agent performing at it is crucial for accurate knowledge graph entity linking.
- organizer: The Person or Organization that plans and is legally responsible for the event. This entity often owns the canonical event data.
- performer: The Person or Organization actively presenting or entertaining at the event, such as a speaker, band, or workshop host.
- composer and director: Specialized sub-properties for creative works like concerts or theatrical plays.
- Always use a full Organization or Person type with a
sameAslink to Wikidata or a MusicBrainz ID to ensure disambiguation from similarly named entities.
Event Status & Classification
The eventStatus property communicates the lifecycle stage of the event to prevent user frustration and maintain data accuracy in AI overviews.
- EventScheduled: The default state; the event is confirmed to occur.
- EventPostponed: The event is delayed but a new date is not yet finalized.
- EventCancelled: The event will not occur; this status should trigger immediate de-indexing of the offer.
- EventMovedOnline: A specific status indicating a shift from a physical location to a virtual one, preserving the original entity ID.
- eventSchedule: For recurring events, use a Schedule node to define repeat frequency rather than duplicating Event entities.
Subject Matter & Typing
The about property and specific sub-types provide semantic context that helps generative engines categorize the event for topical queries.
- about: Links the event to a broader subject or Thing, such as a specific technology or historical period.
- subEvent and superEvent: Hierarchical properties that model relationships between a conference and its individual workshops.
- EventSeries: Use this parent type to group recurring events like monthly meetups, maintaining a single canonical entity for the series.
- keywords: A free-text field for internal tagging that, while not visible to users, provides additional signals to retrieval-augmented generation systems.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clear, technical answers to the most common questions about implementing the Schema.org Event type for generative engine optimization and rich result eligibility.
The Schema.org Event type is a structured data class that defines a scheduled occurrence happening at a specific time and location, enabling search engines and AI crawlers to parse event details with machine-readable precision. It serves as the parent class for more specific subtypes like BusinessEvent, MusicEvent, ScreeningEvent, and Festival. When implemented via JSON-LD, the Event type communicates structured attributes—including startDate, location, offers, and performer—directly to Google's knowledge graph and generative AI models. This allows your event to appear in event-rich results, Google Maps integrations, and AI-generated overviews. The type inherits from Thing, meaning it supports fundamental properties like name, description, url, and sameAs for entity disambiguation. For generative engine optimization, properly marked-up events become retrievable entities that AI assistants can surface when users ask about local happenings, conference schedules, or ticket availability.
Related Terms
Understanding the Event type requires familiarity with its parent classes, sibling types, and the properties that define its temporal and spatial constraints.
Thing
The top-level class in the Schema.org hierarchy from which Event inherits fundamental properties like name, description, url, and image. Every structured data entity ultimately descends from Thing, making it the root of all semantic relationships. When defining an Event, always ensure these base properties are populated to establish the entity's core identity for AI parsers.
EventStatusType
An enumeration that defines the lifecycle state of an event. Key values include:
- EventScheduled: The event is planned and confirmed.
- EventPostponed: The event has been delayed but not cancelled.
- EventCancelled: The event will no longer occur.
- EventMovedOnline: The physical gathering is now virtual.
Accurate status markup prevents AI-generated overviews from presenting outdated or incorrect availability information.
BusinessEvent
A child class of Event specifically designed for commercial gatherings. Use this instead of the generic Event type when marking up trade shows, industry conferences, networking meetups, or investor calls. It inherits all Event properties while signaling to search engines that the occurrence has a professional or commercial context, improving relevance for business-intent queries.
MusicEvent
A specialized subtype of Event for concerts, festivals, and live performances. Key distinguishing properties include performer (the artist or group) and subEvent (for multi-act festivals). Using MusicEvent rather than the generic Event type enables rich results that display artist names and performance schedules directly in AI-generated answers and search snippets.
ScreeningEvent
A subtype of Event representing a presentation of a creative work such as a film, documentary, or broadcast. Critical properties include:
- workPresented: The Movie or CreativeWork being shown.
- videoFormat: Indicates 2D, 3D, IMAX, etc.
- subtitleLanguage: Languages for subtitled screenings.
This granularity helps AI models distinguish between a generic cinema listing and a specific screening instance.
EventAttendanceModeEnumeration
An enumeration specifying how attendees participate. Values include:
- OfflineEventAttendanceMode: In-person only.
- OnlineEventAttendanceMode: Virtual only.
- MixedEventAttendanceMode: Hybrid events with both physical and remote options.
Combined with location (physical venue) and virtualLocation (stream URL), this enumeration provides AI crawlers with unambiguous attendance context for generating accurate event summaries.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us