Glossary

Event

A Schema.org type used to markup a scheduled occurrence, such as a concert, conference, or workshop, enabling it to appear in Google's event search experience with details like date, location, and ticket offers.

Get in touch Learn more

Stylish WeWork-like workspace with hot desks and document wall, professional searching through enterprise knowledge base on a mounted ultrawide display, warm industrial pendants overhead.

SCHEMA.ORG STRUCTURED DATA

What is Event?

A formal definition of the Event schema type, its role in structured data engineering, and its impact on search engine visibility for scheduled occurrences.

An Event is a Schema.org type used to markup a scheduled occurrence—such as a concert, conference, or workshop—with structured data, enabling it to appear in Google's event search experience. It communicates critical details like startDate, location, and offers directly to search engines, bypassing the need for algorithmic interpretation of unstructured text.

Implementing Event schema via JSON-LD is a core Schema Markup Engineering task that establishes a definitive entity signal. By linking an event to an Organization via performer or organizer and a Place via location, engineers create a semantic graph that reinforces Algorithmic Trust and Authority Signals, increasing the likelihood of rich result display.

STRUCTURED DATA ANATOMY

Key Properties of Event Schema

The Event schema type relies on a specific set of properties to communicate the who, what, when, and where of an occurrence to search engines. These properties determine eligibility for rich results and the accuracy of entity disambiguation.

Attendance Mode

The eventAttendanceMode property specifies whether an event is conducted online, at a physical location, or a mix of both. This is a critical signal for Google's event search experience.

OfflineEventAttendanceMode: Requires physical presence at a location.
OnlineEventAttendanceMode: Conducted entirely virtually.
MixedEventAttendanceMode: A hybrid event with both physical and virtual attendance options.

Using the correct enumeration ensures the event surfaces for the right audience queries.

Event Status

The eventStatus property communicates the lifecycle stage of the event to search engines, preventing users from encountering outdated listings.

EventScheduled: The event is planned and has not yet occurred.
EventPostponed: The event has been delayed but will occur at a future date.
EventCancelled: The event has been permanently called off.
EventMovedOnline: The physical gathering was shifted to a virtual format.

Maintaining accurate status prevents negative user experiences and preserves entity trust.

Performer & Organizer

The performer and organizer properties link the event to Person or Organization entities. This is a primary mechanism for entity disambiguation.

performer: Specifies who is presenting or entertaining at the event. Multiple performers can be listed.
organizer: Specifies the entity responsible for coordinating the event.

Linking these to canonical Knowledge Graph entries via the sameAs property strengthens the semantic association between the event and known real-world entities.

Location & Venue

The location property defines where the event takes place, accepting either a Place or VirtualLocation type.

Place: Used for physical venues. Nest a PostalAddress with streetAddress, addressLocality, addressRegion, and postalCode for maximum geo-precision.
VirtualLocation: Used for online events. Specify the url property to direct users to the live stream or meeting link.

Accurate location data is essential for appearing in localized event packs and map integrations.

Offers & Ticket Information

The offers property embeds an Offer type to communicate pricing and availability, enabling the ticket purchase rich result.

price: The cost of admission, specified as a number.
priceCurrency: The ISO 4217 currency code (e.g., USD, EUR).
availability: Indicates if tickets are InStock, SoldOut, or PreOrder.
validFrom: The date and time when tickets go on sale.
url: A direct link to the ticket purchase page.

Structured ticket data allows Google to display pricing directly in the search result, increasing conversion rates.

Start Date & Duration

The startDate property is mandatory for an event to be eligible for rich results. It must be provided in ISO 8601 format.

startDate: The exact date and time the event begins. Include timezone offset (e.g., 2025-10-28T19:00:00-05:00).
endDate: The date and time the event concludes. While optional, it is strongly recommended.
doorTime: Specifies when venue doors open, distinct from the event start time.

Precise temporal data ensures the event appears correctly in time-sensitive search queries and calendar integrations.

EVENT SCHEMA

Frequently Asked Questions

Clear answers to the most common technical questions about implementing the Schema.org Event type for rich search results.

Event Schema markup is a structured data vocabulary from Schema.org that defines a scheduled occurrence—such as a concert, conference, webinar, or workshop—in a machine-readable format. When implemented correctly using JSON-LD, it communicates the event's name, start date, location, performer, and ticket offers directly to search engine parsers. This enables the event to appear in Google's dedicated event search experience, complete with rich details like date badges, venue maps, and direct ticket purchase links. The markup functions by instantiating an Event type (or a more specific subtype like BusinessEvent, MusicEvent, or EducationEvent) and populating its required properties: name, startDate, and location. Optional but highly recommended properties include offers (for ticket pricing), performer, organizer, eventStatus, and eventAttendanceMode (to distinguish online, offline, or hybrid events). The structured data is embedded within the <head> or <body> of the event's landing page, where crawlers extract it to populate knowledge panels and event carousels.

SCHEMA IMPLEMENTATION

Common Use Cases for Event Markup

Implementing Event schema unlocks rich visual results and interactive features in search engines, driving higher click-through rates for scheduled occurrences. Below are the primary scenarios where structured data markup provides the most significant technical and business impact.

Live Performance & Concert Listings

Markup for music, comedy, and theater events enables the event search experience on Google, displaying a dedicated carousel with date, venue, and ticket availability. Use the offers property to specify ticket price ranges and performer to link to the artist's entity. This is critical for driving direct ticket sales from search results without requiring users to navigate to a ticketing platform first.

Rich Result

Search Feature

Virtual & Hybrid Conference Scheduling

For online or hybrid events, the eventAttendanceMode property distinguishes between OnlineEventAttendanceMode, OfflineEventAttendanceMode, and MixedEventAttendanceMode. Pair this with location specifying a VirtualLocation type with a url for the stream. This ensures your event surfaces correctly for users filtering by online-only or in-person attendance.

3 Modes

Attendance Types

Multi-Session Workshop Series

Use the superEvent and subEvent properties to model complex schedules. A single conference (superEvent) can contain multiple workshops (subEvent), each with its own distinct startDate and endDate. This hierarchical structure helps search engines understand the relationship between sessions and display the full agenda cohesively, improving crawl efficiency for large event catalogs.

Local Business Event Promotion

A LocalBusiness entity can host an Event to promote in-store classes, tastings, or workshops. By nesting the Event schema within the Organization or LocalBusiness markup, you strengthen the entity association between the venue and the occurrence. This is a powerful local SEO tactic to populate the 'Events' tab on a Google Business Profile and attract foot traffic.

Ticket Availability & Pricing Feeds

Integrate the offers property with an Offer type to provide real-time structured data on ticket inventory. Specify availability (e.g., SoldOut, InStock) and priceCurrency. For platforms with dynamic pricing, maintaining an accurate structured data feed prevents user frustration from stale data and qualifies the listing for the ticket booking rich result, which places a direct purchase link in the snippet.

Event Series & Recurring Instances

For repeating events like weekly webinars or monthly meetups, avoid creating duplicate pages. Instead, use a single EventSeries parent type and define individual subEvent instances for each occurrence. This consolidates ranking signals to a single canonical URL while providing search engines with the precise startDate and doorTime for every instance, ensuring users see the correct upcoming date.

SCHEMA COMPARISON

Event vs. Related Schema Types

Distinguishing the Event type from other time-bound or occurrence-based Schema.org types to ensure correct implementation.

Feature	Event	PublicationEvent	Course	Trip
Primary Purpose	Scheduled occurrence	Publication release	Educational class	Travel itinerary
Requires startDate
Requires location
Supports offers/tickets
Supports performer
Supports organizer
Google Rich Result eligibility	Event experience	None	Course info	None
Typical eventStatus values	Scheduled, Postponed, Cancelled	Scheduled, Published	Scheduled, Active	Scheduled, Cancelled

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.

Enterprise searchRAGPermissions

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.

AI agentsWorkflow automationGovernance

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.

AI integrationDecision supportModel routing

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.

Limited slotsGet a Free AI Consultation

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.

Talk to Us

Event

What is Event?