Event Schema for Multiple Occurrences

[Your_Workshop]

I am wondering the best way to mark up an event page with multiple occurrences. For example, we have an event that happens over the course of 4 sequential weekends:
9/28-9/29
10/5-10/6
10/12-10/13
10/19-10/20

Our website allows us to enter multiple occurrences that results in a single event listing page which outputs all dates (to eliminate duplicate content, titles, metas, etc.) but allows each occurrence to output individually on our events calendar in the respective individual date. Each time the event is shown, it links to the same listing page.

I am wondering if we can add event schema on a single listing multiple times to cover each occurrence. In the above example, we would have 4 schemas on the listing page for each date range/weekend. In our current schema, we end up with a start and end date identified as 9/28-10/20 but it is not clear that the event is just happening on the weekends with gaps in between.

Any suggestions are welcome however, we are really trying to NOT list each as an individual event on the website both for the duplicate content issue and the extra burden on our client that lists events for a very large geographic area.

[effectdigital]

That does sound tricky. Maybe you could consider them to be sub-events

• https://schema.org/Event
• https://schema.org/superEvent
• https://schema.org/subEvents

... but I am unsure as to whether subEvents can have specified dates (start / end)

I might look more to something like EventSeries

• https://schema.org/EventSeries

"An EventSeries is a collection of events that share some unifying characteristic. For example, "The Olympic Games" is a series, which is repeated regularly. The "2012 London Olympics" can be presented both as an Event in the series "Olympic Games", and as an EventSeries that included a number of sporting competitions as Events.

The nature of the association between the events in an EventSeries can vary, but typical examples could include a thematic event series (e.g. topical meetups or classes), or a series of regular events that share a location, attendee group and/or organizers."

This would seem to be a better schema to use in your situation.

This is the JSON-LD example of implementation from Schema.org:

• https://d.pr/f/WDYKni.txt (TXT file)

It looks like it could be re-engineered to do what you want

Whilst Google don't explicitly state that they support EventSeries yet, IMO their documentation cycle for what they do support is wildly out of whack. I have seen front-end instances of them experimenting with loads of schema that isn't in their official documentation. As such I wouldn't be overly, dramatically bothered by that. At the end of the day, the home of schema is Schema.org. I actually often push for schema which Google don't explicitly state that they cover, and I'm often pleasantly surprised

It doesn't always yield fancy rich-snippets, but it does help Google to gain contextual awareness and rank pages more appropriately. In fact you can read about that here: https://www.searchenginejournal.com/google-follow-our-structured-data-requirements-to-ensure-rich-result-eligibility/329679/

"Independently, you’re always welcome to use structured data to provide better machine readable context for your pages. Which may not always result in visible changes, but can still help our systems to show your pages for relevant queries."