Event Schema Markup Generator
Event schema markup helps Google understand your events and display them in rich, engaging formats across Search and Maps. When implemented correctly, it can surface key event details directly in search results and qualify your events for Google's Events carousel — increasing clicks, attendance, and trust.
Try an example
Fields
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Event"
}
</script>Event Schema Markup FAQ
Event schema markup is a type of structured data defined by Schema.org that helps search engines understand key details about events - such as the name, date, location, organizer, and ticket availability.
When you add Event schema to your pages, Google can display your events as rich results in Search and Google Maps, showing important details like dates, venues, and ticketing information directly in SERPs.
For example, a page for a concert with Event schema might appear in Google with date, time, location, and "Get Tickets" links, increasing visibility and conversions.
Adding Event schema markup helps your events stand out in Google Search and reach more potential attendees.
- Your events may appear as rich snippets in Search (with date, location, and price).
- Eligible events can show in the Google Events carousel, a high-visibility section above normal listings.
- It helps search engines correctly index and categorize your event pages.
- Users can quickly find essential info - improving CTR and attendance.
Whether you're hosting webinars, conferences, concerts, workshops, or exhibitions, Event schema gives your listings maximum exposure.
- Expired events still marked as active: Always remove or update past events. Google may flag outdated event data.
- Missing or incorrect date formats: Use ISO 8601 (YYYY-MM-DDThh:mm) with time zones for consistency.
- Wrong event type: Use OnlineEventAttendanceMode for virtual events and OfflineEventAttendanceMode for physical events.
- No visible event details on the page: Markup must match what's shown to users (name, time, venue).
- Omitting ticket or offer information: Not required, but including it increases the likelihood of showing enhanced snippets.
- Using a generic or unrelated image: Use a unique, relevant image at least 720px wide for best display in rich results.
- Invalid URLs for location or tickets: Always use fully qualified URLs (https://...) that are publicly accessible.
Yes - if your page lists multiple upcoming events (like a conference calendar), you can include an array of multiple Event objects within your JSON-LD.
Each should have its own name, startDate, and location.
Yes. For example:
- Organization schema for the host company
- FAQPage schema for event FAQs
- BreadcrumbList schema for page navigation
Just ensure each block describes distinct aspects of the page.
You can monitor impressions and clicks in Google Search Console > Enhancements > Events.
You'll see which events are eligible for rich results and how often they appear in searches.
- Event describes an occurrence (something that happens at a specific time).
- LocalBusiness describes a place or organization.
If you host recurring events at a fixed venue, you can use both - one for the location, one for the event.
Create separate Event entries for each date rather than one with a date range.
Google treats each instance as an individual listing.
Additional Resources
Official documentation and guides to help you get the most out of your schema markup.
Use our other schema markup generators
Physical business locations with hours and contact
Schools, NGOs, corporations, and similar entities
Video content with thumbnails and duration
Individuals with contact and professional info
Ratings for products, businesses, movies, and more
Generic web pages with breadcrumb navigation
Event schema at scale, zero manual effort
Running multiple events? Schema Pilot generates valid Event markup for each listing with dates, venues, and ticket info pulled from your pages.