Skip to content

Event schema: required properties, dates and cancelled events

How to write Event schema Google accepts: the three required properties, ISO 8601 dates with offsets, online events, and marking cancelled or rescheduled events.

By Crawlito · 9 min read

In short

  • Google requires three properties for Event markup: name, startDate and a location of type Place with a PostalAddress.
  • startDate should be ISO 8601 with a UTC offset, such as 2026-12-05T19:30-05:00; without an offset Google uses the time zone of the event's location.
  • Google removed the online event properties from its event documentation on June 5, 2025, and now says events must take place in a physical location.
  • For a cancelled event, change only eventStatus to EventCancelled and keep startDate and location; for a rescheduled one, update the dates and you can add previousStartDate.
  • Google's event experience supports pages about a single event, each with its own URL, and is limited to a list of countries and languages.
On this page

Event schema is JSON-LD that describes one event: what it is called, when it starts and where it happens. Google requires only three properties, name, startDate and location (a Place with an address), and recommends endDate, eventStatus, image, offers, organizer and performer. Dates should be ISO 8601 with a time zone offset, and when plans change you update eventStatus instead of deleting the event's dates.

This guide follows Google's Event structured data documentation and the schema.org Event type, and covers the parts that change most often: online events, which Google no longer supports, and cancelled, postponed and rescheduled events.

What Event markup is for, and who can use it

Google says Event markup can make events eligible for its event experience in Search and in other products such as Google Maps. Three conditions narrow that down, and they rule out more pages than the properties do:

  • One event per page. Google says each event must have a unique URL, a "leaf page", with markup on that URL, and that the event experience only supports pages that focus on a single event. A "What's on" calendar page is not the place for twenty Event blocks; each event's own page is.
  • Physical and public. Events must take place in a physical location and be bookable by the general public. Events that need a membership or an invitation before you can buy a ticket are not eligible, nor are spectator events held on school premises where the participants and audience are mainly minors.
  • Supported regions. At the time of writing Google lists Australia, Canada, India, the United Kingdom and the United States (English), Brazil (Portuguese), Germany (German), and Spain and Latin America (Spanish).

Google also lists things that are not events: trip packages, "buy your tickets now" promotions, business hours and coupons. Opening hours belong in LocalBusiness markup, not in Event. If your tickets are sold through a ticketing platform that already works with Google, Google says you can keep publishing there.

Valid markup makes a page eligible, nothing more: Google says it does not guarantee that marked-up events appear. The same markup is also a clear, machine-readable statement of the date and place for any other system reading the page; our overview of structured data for AI search covers what is known about that.

PropertyStatus in Google's docsNotes
nameRequiredThe event's title. Google warns: do not put the venue name here
startDateRequiredISO 8601 date and time
location (Place)RequiredWith location.address as a PostalAddress
location.nameRecommendedThe venue name; omit it if unknown
endDateRecommendedSame format as startDate
eventStatusRecommendedTreated as scheduled when missing
previousStartDateRecommendedOnly with EventRescheduled
descriptionRecommendedGoogle shows a snippet of it
imageRecommendedSeveral images in 16x9, 4x3 and 1x1; Google suggests 1920 px wide, minimum 720 px
offersRecommendedOne Offer per ticket type
organizerRecommendedOrganization or Person, with name and url
performerRecommendedPerformingGroup or Person

For offers, Google asks for the lowest available price including fees in price (use 0 for free events), the currency as an ISO 4217 code in priceCurrency, availability as InStock, SoldOut or PreOrder, a crawlable url that sells tickets for this specific event, and validFrom for when tickets go on sale. If tickets are not yet on sale, Google says you can omit availability and give validFrom.

A complete example for a single concert:

json
{
  "@context": "https://schema.org",
  "@type": "MusicEvent",
  "name": "Northern Strings: Winter Concert",
  "description": "An evening of Baroque and contemporary string music.",
  "startDate": "2026-12-05T19:30-05:00",
  "endDate": "2026-12-05T22:00-05:00",
  "eventStatus": "https://schema.org/EventScheduled",
  "location": {
    "@type": "Place",
    "name": "Riverside Hall",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "200 Water Street",
      "addressLocality": "Toronto",
      "addressRegion": "ON",
      "postalCode": "M5A 1A1",
      "addressCountry": "CA"
    }
  },
  "image": [
    "https://www.example.com/events/winter-concert-16x9.jpg",
    "https://www.example.com/events/winter-concert-4x3.jpg",
    "https://www.example.com/events/winter-concert-1x1.jpg"
  ],
  "offers": {
    "@type": "Offer",
    "url": "https://www.example.com/events/winter-concert/tickets",
    "price": 35,
    "priceCurrency": "CAD",
    "availability": "https://schema.org/InStock",
    "validFrom": "2026-10-01T10:00-04:00"
  },
  "organizer": {
    "@type": "Organization",
    "name": "Northern Strings",
    "url": "https://www.example.com/"
  },
  "performer": {
    "@type": "PerformingGroup",
    "name": "Northern Strings Quartet"
  }
}

MusicEvent is one of the schema.org subtypes of Event, along with ConferenceEvent, TheaterEvent, SportsEvent, ComedyEvent, Festival and others. A subtype is still an Event, so the same rules apply. Place the block in a <script type="application/ld+json"> element. Google says it can read structured data generated with JavaScript, but putting it in the server-rendered HTML means crawlers that do not run JavaScript see it too.

Dates, times and time zones

Most Event bugs are date bugs. Google's date and time guidelines come down to five rules:

  1. Use ISO 8601 with an offset. 2026-12-05T19:30-05:00 means 7:30 pm at five hours behind UTC. Google says that if you leave the offset out, it uses the time zone of the event's location, and that if you cannot fill in the correct offset you should leave it out rather than guess.
  2. Give both dates for multi-day events. A three-day festival needs startDate and endDate.
  3. Use a date alone when the time is unknown or the event runs all day: "startDate": "2026-12-05". Google reads a date-only value as that date at the event's location.
  4. Do not use midnight as a placeholder. Google calls out T00:00:00 as a common mistake. Use it only for an event that really starts at midnight.
  5. Mind daylight saving time. The offset is for the event's date, not today's. The concert above uses -05:00 in December, while the ticket sale opening in October uses -04:00. A template that hardcodes one offset is wrong for half the year.

The safest approach is to store event times in your CMS with an IANA time zone such as America/Toronto and let your code compute the offset when it writes the JSON-LD. To spot the common failures in a page's raw HTML:

bash
curl -s https://www.example.com/events/winter-concert | grep -oE '"(start|end)Date": *"[^"]*"'

A value with a time but no offset, or one ending in T00:00:00, is worth a second look.

Each performance with its own tickets is a separate event. Google says performances on different days, each with individual tickets, need their own Event elements, so a play with one ticketed performance a night for two weeks is fourteen Events, and Google's rule of a unique URL per event applies to each.

Online and hybrid events: what changed in 2025

schema.org still describes online events. It has an eventAttendanceMode property with three values, OnlineEventAttendanceMode, OfflineEventAttendanceMode and MixedEventAttendanceMode, and location accepts a VirtualLocation for a streaming URL, or a list combining a Place and a VirtualLocation for a mixed event. The EventStatusType enumeration also includes EventMovedOnline.

Google's support is narrower. Its Search Central changelog entry of June 5, 2025, "Updating our guidance for event structured data", says it "removed the online event properties" and that events must be bookable by the general public and held at a physical location. The current event documentation says that "Virtual experiences that have no real-world component aren't supported", does not mention eventAttendanceMode or VirtualLocation, and lists only four eventStatus values: EventScheduled, EventCancelled, EventPostponed and EventRescheduled.

In practice:

EventGoogle event experienceWhat to mark up
In person onlySupportedPlace with a PostalAddress
Hybrid, with a real venueCan be eligible, because it takes place at a physical locationPlace with the venue address; the online part is optional schema.org vocabulary
Webinar or livestream onlyNot supportedValid schema.org, but not eligible for Google's event experience
In-person event moved onlineNot documentedGoogle's docs have no EventMovedOnline, and a virtual-only event is not supported, so expect it to lose eligibility

Google does not document whether it reads the virtual parts of a hybrid event's markup. You can still use eventAttendanceMode and VirtualLocation for accuracy, since they are valid schema.org, but make sure the required Place is there. For a webinar-only page, do not invent a venue address to satisfy the location requirement: that would break Google's rule that markup must truly represent the page, set out in its structured data guidelines.

Cancelled, postponed and rescheduled events

The rule that matters most: when an event's status changes, keep the event in place and change its status. Google warns not to remove startDate, because it helps identify the unique event.

SituationeventStatusstartDate and endDateOther properties
Going aheadEventScheduled (or omit)Planned datesAs normal
CancelledEventCancelledKeep the original datesDo not remove or change them, including location
Postponed, no new date yetEventPostponedKeep the original dates until you know the new onesUnchanged
RescheduledEventRescheduledThe new datesOptionally add previousStartDate with the old start

A rescheduled event:

json
{
  "@context": "https://schema.org",
  "@type": "MusicEvent",
  "name": "Northern Strings: Winter Concert",
  "eventStatus": "https://schema.org/EventRescheduled",
  "previousStartDate": "2026-12-05T19:30-05:00",
  "startDate": "2027-01-16T19:30-05:00",
  "endDate": "2027-01-16T22:00-05:00",
  "location": {
    "@type": "Place",
    "name": "Riverside Hall",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "200 Water Street",
      "addressLocality": "Toronto",
      "postalCode": "M5A 1A1",
      "addressCountry": "CA"
    }
  }
}

Google says that if you add previousStartDate, you must also set eventStatus to EventRescheduled. schema.org allows previousStartDate for cancelled events too, but for Google, use it only with a reschedule. If an event is rescheduled more than once, previousStartDate can repeat, so give it an array of the earlier dates.

Update the visible page at the same time. A page that says "Cancelled" in a banner while the markup says EventScheduled, or the reverse, is the kind of mismatch Google's guidelines treat as markup that does not represent the page. Postponed events also need a follow-up: once a new date exists, switch to EventRescheduled and set the new dates.

What to do once an event is over

Google's event documentation does not say whether to remove markup after an event ends. What it does say is that the markup should describe the event accurately, so a past event with correct dates is not wrong, and you can keep a past event's page online as an archive. If you want a page to drop out of Google Search after a set date, the unavailable_after rule does that; use it only for pages you are happy to lose, because it affects the whole page, not just the event feature.

How to test Event markup and read Search Console

  1. Rich Results Test. Run the URL through Google's Rich Results Test and fix critical errors. A missing location, startDate or name makes the item ineligible.
  2. Schema Markup Validator. validator.schema.org checks the schema.org vocabulary, including properties Google's event documentation does not cover, such as eventAttendanceMode.
  3. Raw HTML. Use the curl command above to confirm the block is in the server response, and compare its dates, venue and status with the visible text.
  4. URL Inspection. After deploying, Google suggests checking the page with the URL Inspection tool and making sure it is not blocked by robots.txt, noindex or a login.
  5. Search Console reports. Google points to the rich result status report for event errors, the Unparsable structured data report for syntax problems, and the Manual Actions report.

When the report shows errors or an event appears with the wrong details, check the problems Google's troubleshooting section lists first: a missing or incorrect location (for example plain text instead of a Place with a PostalAddress), a date with no time zone offset or a midnight placeholder, and the event title placed in location.name, or the venue name in name. Syntax errors such as trailing commas are covered in common JSON-LD errors. If the report is clean but nothing appears, valid markup with no rich results goes through the other reasons, starting with the region, single-event and physical-location rules above.

Frequently asked questions

Which properties are required for Event schema?

Google requires name, startDate and location, where location is a Place with an address of type PostalAddress. Everything else, including endDate, offers and eventStatus, is recommended.

Does Google support Event markup for webinars and online events?

Not at the time of writing. Google removed the online event properties from its documentation on June 5, 2025, and says virtual experiences with no real-world component are not supported.

Should I delete the markup when an event is cancelled?

No. Set eventStatus to EventCancelled and leave startDate, location and the other properties as they were, as Google's documentation asks.

What time zone should startDate use?

Use the event's local time with its UTC offset for that date, such as 2026-12-05T19:30-05:00. Without an offset, Google uses the time zone of the event's location.

Can one page mark up several events?

It is valid schema.org, but Google's event experience only supports pages about a single event, each on its own URL. Put each event's markup on that event's page.

Check what crawlers receive on your event pages

Event markup only works when it is in the HTML crawlers get and agrees with the page. As a next step, run the free single-page check on one of your event pages, with no account needed, to see whether crawlers can reach and read it.

Filed under Structure and schema. Topics: structured-data, json-ld, google, checklist