Event
A workshop, a concert, a book launch: if people can show up to it on a specific date, Event schema tells machines exactly when, where, and how to get in.
When to use it
Use Event on a page about one specific thing happening at a specific time that the public can attend. Fern & Ink runs an "Intro to Letterpress Workshop" in the studio a few times a year. Each session has a date, a start time, a price, and a limited number of seats. That's a textbook event.
Google can show events with dates and locations in search, and in its event listings. Valid markup makes the page eligible; it doesn't guarantee anything.
What isn't an event: your business hours, a sale that runs all month, a coupon, a travel package, or a members-only gathering. Google's guidelines say not to mark those up as events, and it's good advice anyway. An event is something people attend, not something they buy.
The code
Here's the markup for the January session of the workshop. It would sit on that session's page, https://fernandink.example/workshops/intro-to-letterpress-2027-01-16/, which shows the same date, time, price, and address in the visible content.
{
"@context": "https://schema.org",
"@type": "Event",
"@id": "https://fernandink.example/workshops/intro-to-letterpress-2027-01-16/#event",
"name": "Intro to Letterpress Workshop",
"description": "A hands-on, three-hour beginner class. Set type by hand, mix ink, and print a set of cards on our Vandercook press to take home.",
"image": "https://fernandink.example/images/workshop-press.jpg",
"startDate": "2027-01-16T10:00:00-06:00",
"endDate": "2027-01-16T13:00:00-06:00",
"eventStatus": "https://schema.org/EventScheduled",
"eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
"location": {
"@type": "Place",
"name": "Fern & Ink Studio",
"address": {
"@type": "PostalAddress",
"streetAddress": "412 Main St SE",
"addressLocality": "Minneapolis",
"addressRegion": "MN",
"postalCode": "55414",
"addressCountry": "US"
}
},
"offers": {
"@type": "Offer",
"price": "85.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://fernandink.example/workshops/intro-to-letterpress-2027-01-16/",
"validFrom": "2026-11-16T09:00:00-06:00"
},
"organizer": { "@id": "https://fernandink.example/#organization" },
"performer": { "@id": "https://fernandink.example/about/#maya" }
}
The organizer and performer lines point at entities you already described in the Organization and Person lessons. If those aren't on this page, write them out instead: { "@type": "Organization", "name": "Fern & Ink", "url": "https://fernandink.example/" }. Google looks for a name (and, for the organizer, a URL), so make sure one of the two approaches gives it that.
The properties
| Property | What it holds | Status |
|---|---|---|
name | The event's title, as shown on the page. | Required |
startDate | Start date and time in ISO 8601, with a time zone offset. | Required |
location | A Place with a name and a PostalAddress. | Required |
endDate | When it ends. Use it for anything with a known finish, and always for multi-day events. | Recommended |
eventStatus | Scheduled, cancelled, postponed, or rescheduled. Google assumes scheduled if you leave it out. | Recommended |
offers | An Offer for tickets: price, currency, availability, URL, and when sales open. | Recommended |
organizer | Who runs it, with a name and URL. | Recommended |
performer | Who's on stage, or teaching. A Person or Organization. | Recommended |
image, description | A real photo of the event and a short summary. | Recommended |
previousStartDate | The old date, only when an event has been rescheduled. | Recommended |
eventAttendanceMode | In person, online, or both. Part of Schema.org, not listed in Google's current event docs, but cheap and clear. | Optional |
Dates need a time zone
Event dates use ISO 8601: year, month, day, then a T, then the time, then the offset from UTC. 2027-01-16T10:00:00-06:00 means 10 a.m. on January 16, 2027, six hours behind UTC.
That offset is the part people get wrong. Minneapolis is -06:00 in winter (Central Standard Time) and -05:00 in summer (Central Daylight Time). So a June session of the same workshop would be 2027-06-12T10:00:00-05:00. Check the offset for the actual date, not today's date. Leave the offset off and Google will guess from the location, but there's no reason to make it guess.
If an event lasts all day or you don't know the start time yet, you can use the date on its own: 2027-01-16.
One event, one occurrence
Fern & Ink runs this workshop in January, March, and June. That's three events, not one. Each session gets its own page (or at least its own Event block) with its own date and its own ticket link. Don't write one Event with a vague "runs several times a year" description, and don't put the whole calendar on a listing page and call it a single event. A workshops page that lists all three can link to each session's page; the markup lives on the session pages.
The same goes for one event in several places at once: one Event per location.
Tickets with Offer
The offers block describes how to get in. price is the lowest price available, including any fees, and it's 0 for a free event. priceCurrency is a three-letter code like USD. url should go to a page where the public can actually buy a ticket for this session.
availability takes InStock, SoldOut, or PreOrder. When the January session fills up, change it to https://schema.org/SoldOut at the same time you update the page. validFrom is when tickets go on sale. If sales haven't opened yet, leave availability out and keep validFrom.
When plans change
Events get cancelled, postponed, and moved. Don't delete the markup when that happens. Update eventStatus and leave the original startDate in place, unless there's a new date.
EventCancelled: it's not happening. Keep the original dates.EventPostponed: it's delayed, and there's no new date yet. Keep the original dates until you know.EventRescheduled: there's a new date. Put the new date instartDateand the old one inpreviousStartDate.
Say a snowstorm moves the January session back a week. Only these lines change:
{
"@context": "https://schema.org",
"@type": "Event",
"name": "Intro to Letterpress Workshop",
"eventStatus": "https://schema.org/EventRescheduled",
"previousStartDate": "2027-01-16T10:00:00-06:00",
"startDate": "2027-01-23T10:00:00-06:00",
"endDate": "2027-01-23T13:00:00-06:00"
}
That's an excerpt to show the changed lines. On the real page, keep location, offers, and everything else from the full example.
In person, online, or both
eventAttendanceMode says how people attend: OfflineEventAttendanceMode (in person), OnlineEventAttendanceMode, or MixedEventAttendanceMode. For an online session, the location is a VirtualLocation with a url. For a mixed event, location can be an array holding both the Place and the VirtualLocation.
{
"@context": "https://schema.org",
"@type": "Event",
"name": "Letterpress Q&A with Maya Lund",
"startDate": "2027-03-04T19:00:00-06:00",
"eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
"location": {
"@type": "VirtualLocation",
"url": "https://fernandink.example/live/letterpress-qa/"
}
}
One honest note: Google's current event guidelines say virtual-only events aren't supported for its event features. The markup is still valid Schema.org and still useful to other tools, but don't promise a client online events will show up in Google's event listings.
Common mistakes
- Leaving off the time zone offset, or using the summer offset for a winter date.
- Marking a sale, business hours, or a coupon as an
Event. - One
Eventfor a whole series instead of one per date. - Deleting the markup when an event is cancelled instead of setting
EventCancelled. - Leaving
availabilityasInStockafter the page says "Sold out." - Status values written as plain words (
"Scheduled") instead of the fullhttps://schema.org/EventScheduledURL.
Try it
Fern & Ink adds a summer session on Saturday, June 12, 2027, from 1 to 4 p.m., same price. Copy the full example and change the @id, startDate, endDate, and offers.url for the new session. (Hint: it's summer, so watch the offset.) Then imagine it sells out, and update one more line.
Check yourself
- My event has a
name, astartDate, and alocationwith a full address. - My dates include the right UTC offset for the date of the event.
- Each date of a recurring event has its own
Event. - My
offersprice, availability, and URL match the ticket info on the page. - I know to update
eventStatus, not delete the markup, when plans change.
Events alongside the other rich-content types: Schema Markup Explained, Part 3: FAQ, Person, Event, Recipe, and Reviews.