Free Event Schema Generator — Event JSON-LD Markup
Event Schema Generator
An Event schema generator produces JSON-LD markup describing name, startDate, location and eventStatus so search engines and event-listing crawlers can parse a page as a scheduled event. Google requires name, startDate and location (or a VirtualLocation for online events) as a minimum, and adding offers with price and availability makes the listing eligible for a rich result showing date, venue and ticket price directly in search. Fill in the event fields below to generate the markup.
Generate valid Event schema JSON-LD with name, startDate, location and offers. Free event schema generator for concerts, webinars and conferences, no signup.
Enter the event name, dates and location
Provide the event name, startDate and endDate in ISO 8601 format, plus a physical address or a VirtualLocation URL if the event streams online. These four fields are the minimum Google checks for eligibility.
Add ticketing and organizer details
Enter offers with price, priceCurrency, availability and a ticket URL, plus the organizer name and performer if relevant. This is what lets the rich result show a price and a link to buy.
Copy the JSON-LD into your page head
The generator outputs a single script tag. Paste it inside the head or body of the event's own page — not a listing page covering multiple unrelated events — then validate before publishing.
Frequently asked questions
What fields are required for Google's Event rich result?
Google requires name, startDate and location at minimum, with location needing either a full postal address or a VirtualLocation URL for online events. Offers and performer aren't mandatory but strongly recommended — listings with pricing and availability tend to show more detail in the search result.
Can I mark up a page that lists multiple events?
No. Google expects one Event object per distinct event on its own URL. A listing page can link out to individual event pages, each carrying its own Event schema, but bundling several events into a single page's markup violates Google's structured data guidelines and can suppress the rich result.
Where should the Event JSON-LD script go?
Anywhere in the page's head or body — Google's crawler reads the whole rendered HTML, not just the head. Most sites place it in the head alongside other meta tags for consistency, inside a single script tag with type application/ld+json.
What happens to an Event rich result after the event date passes?
Google typically stops showing the rich result once the event has ended, and expects eventStatus to be updated to EventCancelled or EventPostponed if plans change. Leaving stale past-dated events marked up on a live page can trigger a manual structured data warning.