SwiftSchema Logo

    SwiftSchema

    Intuitive Schema Generation at Your Fingertips

    AboutLearnContact

    Event Series Schema Generator — Summarize Recurring Events

    Generate clean EventSeries JSON‑LD to describe recurring events with organizer, dates, location or online mode, and link to each Event occurrence.

    Try the EventSeries Generator

    Why many series pages underperform

    Pain points we solve

    • The series page doesn’t clarify attendance mode or date span.
    • Organizer and location details are missing, reducing context.
    • Individual Event instances aren’t marked up or linked from the series page.
    • Manual JSON‑LD is inconsistent with the per‑event pages.

    How SwiftSchema helps

    Solution

    The EventSeries generator captures the series‑level details: name, optional start/end dates, attendance mode, organizer, and location name.

    Mark up each occurrence with Event JSON‑LD and link them from the series page to create a cohesive structure that is easy to navigate and understand.

    How it works

    How it works

    1. Choose EventSeries in the generator below.
    2. Enter the series name and optional date span (startDate/endDate).
    3. Set attendance mode (online/offline/mixed) and include organizer and location name when applicable.
    4. Create separate Event pages/sections for each occurrence and link them from the series page.
    5. Copy JSON or Script, paste on the series page, and validate in the Rich Results Test.
    Generate EventSeries JSON‑LD

    Paste once per series. Validate. Ship.

    What is EventSeries structured data?

    EventSeries describes recurring or ongoing event programs (weekly meetups, lecture series, monthly webinars). It provides umbrella metadata (name, schedule span, attendance mode, organizer, location) while individual sessions use Event schema. Search engines use it to identify the overarching series, cluster related events, and understand recurrence patterns.

    Essential properties

    1. name
       — official series title.
    2. startDate
      /
      endDate
       — optional span covering the series’ run (season, year).
    3. eventAttendanceMode
       —
      OnlineEventAttendanceMode
      ,
      OfflineEventAttendanceMode
      , or
      MixedEventAttendanceMode
      .
    4. location
       —
      Place
      or
      VirtualLocation
      representing the default venue/platform.
    5. organizer
       — Person or Organization responsible for the series.
    6. description
       — summary describing the series theme and cadences.
    7. image
       — hero image or promotional graphic.
    8. eventSchedule
       — optional
      Schedule
      with recurrence rules.
    9. subEvent
       — list of Event objects representing upcoming occurrences.

    Content prep checklist

    • Publish a landing page describing the series theme, target audience, cadence, and registration info.
    • List upcoming occurrences (date/time) with links to detail pages.
    • Clarify whether sessions are free/paid, online/in-person, and provide registration CTA.
    • Introduce organizers/instructors and highlight notable guests.
    • Provide archive links to past sessions or recordings if available.

    Implementation workflow

    1. Update the series landing page with the information above.
    2. Generate EventSeries JSON‑LD with series-level data (name, description, attendance mode, organizer, location, span).
    3. List upcoming events in
      subEvent
      or via Event links; each occurrence should have its own Event schema (EducationEvent, MusicEvent, etc.).
    4. Include
      eventSchedule
       when sessions recur on a predictable cadence (weekly, monthly).
    5. Embed the EventSeries schema on the landing page; ensure you also include Event schema for the current occurrence on the relevant page.
    6. Validate via Rich Results Test; fix warnings about missing organizer or location.

    Linking EventSeries and Event schema

    • Each Event should reference the series via
      superEvent
      .
    • EventSeries can list
      subEvent
      entries or simply link to the detail pages.
    • Keep start/end dates in sync; update the series’
      endDate
      when the season wraps.

    Troubleshooting checklist

    • Missing organizer/location: include these to build trust and clarity.
    • Confusing attendance mode: set
      eventAttendanceMode
      and clarify in the content if sessions alternate formats.
    • No linked events: make sure each occurrence has Event schema and is linked from the series page.
    • Stale schedules: update
      startDate
      /
      endDate
      annually or per season.
    • Duplicate schema: avoid embedding both EventSeries and Event for the same data block unless you differentiate series vs occurrence clearly.

    Required properties

    • name

    Recommended properties

    • startDate
    • endDate
    • eventAttendanceMode
    • location.name
    • organizer.name
    Minimal JSON-LD
    Validate
    {
  "@context": "https://schema.org",
  "@type": "EventSeries",
  "name": "Weekly Tech Meetup",
  "startDate": "2026-03-01",
  "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode"
}

    FAQs

    Do I still mark up individual events?Show
    Yes, include Event for each instance and link from the series page.
    Online series?Show
    Use OnlineEventAttendanceMode and include registration URL on page.

    Related types

    Browse all schema types

    References

    Generate Event Series schema

    Fill in page details, copy JSON or Script, and validate.

      Schema Type

      🗓️ Event Series Schema Generator

      Summarize a recurring series of events with organizer, dates, location, and attendance mode.

      Generated Schema

      Validate your schema here.