What's the difference between eventAttendanceMode and location?

eventAttendanceMode tells search engines whether the event happens in person, online, or both (OfflineEventAttendanceMode, OnlineEventAttendanceMode, or MixedEventAttendanceMode), while location says where - either a physical Place with an address, or a VirtualLocation with a URL. A hybrid event needs MixedEventAttendanceMode plus, per Google's guidance, two location entries (one Place, one VirtualLocation); this generator covers the common single-location case for either mode.

Why does eventStatus need a full schema.org URL instead of just the word 'Cancelled'?

That's the exact format the spec defines: eventStatus is a reference to an EventStatusType enumeration member, such as https://schema.org/EventCancelled, not a bare string. This generator builds that full URI automatically from the status you pick, including updating it correctly when a scheduled event is later postponed or cancelled.

Do I need to fill in the offers section?

Only if the event has tickets or registration you want reflected in search results. Leaving price blank skips the whole nested Offer object, so you still get valid Event markup with just name, dates, and location - free or invite-only events commonly omit offers entirely.

What happens if an event's status changes after I've already published the schema?

Update eventStatus (and startDate, if it's rescheduled) on the live page as soon as the change is confirmed - Google's guidance explicitly expects publishers to keep eventStatus current, since stale 'Scheduled' markup on a cancelled event is a common source of user complaints from search traffic.

Event Schema Generator - Event JSON-LD with Location & Offers

Overview

Introduction

Event schema is what lets a concert, conference, or webinar show up in Google's dedicated event search results and Events carousel, complete with date, location, and ticket price, rather than as a plain link. Getting the nesting right by hand is fiddly: location is either a Place or a VirtualLocation depending on the event format, and both eventAttendanceMode and eventStatus have to be full schema.org URIs, not plain words.

This generator takes the fields that actually drive Event rich results (name, dates, location, attendance mode, status, and an optional ticket offer) and outputs a correctly-nested JSON-LD block ready to paste into a page's <head>.

What Is Event Schema Generator?

A form-driven generator for Event JSON-LD, covering both physical events (a venue name and address, nested as a Place) and virtual or hybrid events (a join URL, nested as a VirtualLocation).

It also builds the eventAttendanceMode and eventStatus properties as the full schema.org enumeration URIs the spec requires, and an optional nested Offer for ticketed events.

How Event Schema Generator Works

Name, startDate, and endDate map directly to their Event properties; the location toggle switches the form between physical-venue fields (venue name, street address, city, region, postal code, country) and a single virtual-event URL field.

eventAttendanceMode and eventStatus are built from toggle buttons and expanded to their full https://schema.org/... form automatically; if a price is entered, it's combined with currency, a ticket URL, and availability into a nested Offer object.

When To Use Event Schema Generator

Publishing a conference, concert, meetup, or webinar page and wanting it eligible for Google's Events rich result and Events carousel.

Updating an existing event's schema after it's rescheduled, moved online, or cancelled, so the visible eventStatus stays accurate.

Often used alongside Structured Data Validator, Local Business Schema Generator and Organization Schema Generator.

Features

Advantages

Switches between a nested Place and a nested VirtualLocation automatically based on whether the event is physical or virtual, without needing to remember either shape.
Expands eventAttendanceMode and eventStatus to their full schema.org URI form automatically, both easy to get wrong writing JSON-LD by hand.
Only builds the nested Offer object when a price is entered, so free events still produce valid minimal Event markup.

Limitations

Covers a single location per event; true hybrid events that need both a Place and a VirtualLocation listed together aren't modeled by this generator's single location toggle.
Doesn't validate that a virtual event's URL is actually reachable or that a physical venue's address is real.
Supports one ticket Offer; events with multiple ticket tiers (early bird, VIP, and so on) need one generated Offer merged manually per tier, or an AggregateOffer shape not covered here.

Examples

An in-person conference talk with tickets

Input

Name: DevToolbox Summit 2026
Start: 2026-09-12T09:00:00-07:00
End: 2026-09-12T17:00:00-07:00
Attendance mode: Offline
Status: Scheduled
Venue: Moscone Center, San Francisco, CA, US
Offer: 149.00 USD, https://example.com/tickets, InStock

Output

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "DevToolbox Summit 2026",
  "startDate": "2026-09-12T09:00:00-07:00",
  "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
  "eventStatus": "https://schema.org/EventScheduled",
  "endDate": "2026-09-12T17:00:00-07:00",
  "location": {
    "@type": "Place",
    "name": "Moscone Center",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "San Francisco",
      "addressRegion": "CA",
      "addressCountry": "US"
    }
  },
  "offers": {
    "@type": "Offer",
    "price": "149.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/tickets"
  }
}
</script>

Attendance mode and status are expanded to full schema.org URIs automatically, and the venue is nested as a Place with a PostalAddress.

Best Practices & Notes

Best Practices

Keep eventStatus current on the live page whenever an event is postponed, rescheduled, or cancelled, rather than leaving stale 'Scheduled' markup.
Include a real, specific startDate with a timezone offset (not just a bare date) whenever the event has a defined start time, so search results show accurate local timing.
For virtual events, use the actual join or livestream URL as the VirtualLocation url, not a generic homepage link.
Only add an Offer when tickets or registration genuinely exist; an Offer with a placeholder price misrepresents the event.

Developer Notes

eventAttendanceMode and eventStatus are both schema.org enumerations, meaning valid values are full URIs (https://schema.org/OfflineEventAttendanceMode, https://schema.org/EventScheduled) rather than plain strings; this generator stores the short form internally and expands it at build time so the form stays readable while the output stays spec-correct.

Event Schema Generator Use Cases

Adding structured data to a conference, meetup, or concert landing page before tickets go on sale
Publishing a webinar or livestream page with a VirtualLocation join URL
Updating an existing event page's eventStatus after a postponement or cancellation

Common Mistakes

Writing eventAttendanceMode or eventStatus as a bare word like "Online" or "Cancelled" instead of the full https://schema.org/... URI the spec requires.
Leaving a virtual event's location empty instead of providing a VirtualLocation with a real join URL.

Tips

Run the generated output through the Structured Data Validator tool in this category before shipping, to confirm the location and date fields are both present and well-formed.
For hybrid events, generate the Offline version for the venue details and manually add a second VirtualLocation entry to the location array if your platform requires both.

Event Schema Generator