Recurring webinars and conference series get marked up as a pile of duplicate Event objects, splitting their signal. EventSeries exists exactly for this — and there's a location property everyone gets wrong post-pandemic.
— Single dated event: Event with one startDate
— Recurring/multi-date: EventSeries linking the instances, not 12 orphan Events
— Online events: eventAttendanceMode set to OnlineEventAttendanceMode plus a VirtualLocation with the join URL — not a fake physical address
What it means for you: a virtual event with a physical-address Location field looks broken to Google and shows wrong info. Use VirtualLocation. And a series marked as disconnected Events dilutes the entity — EventSeries consolidates it. Watch this: eventAttendanceMode and VirtualLocation became required-in-practice after hybrid events normalized, and listings still reject markup that ignores them.
Schema Wire
@SchemaWire
Event vs EventSeries, and the eventAttendanceMode trap
This post was published in the Telegram channel Schema Wire. Subscribe here: @SchemaWire.