SwiftSchemaGenerate
    Schema stack

    Events Ticketing Hub Stack

    Ticketing hubs listing multiple events with CollectionPage context, FAQs, and breadcrumbs.

    Open generatorValidate in Rich Results Test
    Included schema
    Collection Page
    Event
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Ticketing hubs that list multiple upcoming events
    • Event category pages with dates, venues, and links
    • Pages where FAQs clarify refunds, entry, and accessibility
    Composition

    What is included

    Data contract

    Properties across the bundle

    Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.

    Required properties

    • description
    • endDate
    • itemListElement[].name
    • location.name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • startDate
    • url

    Recommended properties

    • eventAttendanceMode
    • eventStatus
    • hasPart.@id
    • inLanguage
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.url
    Copy-ready example

    Combined JSON-LD

    Paste this as one script tag, then replace every example value with data from the live page.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "CollectionPage",
    "@id": "https://www.example.com/tickets#page",
    "name": "Live Events — Tickets",
    "description": "Browse upcoming shows and secure tickets for live events in your city.",
    "url": "https://www.example.com/tickets",
    "inLanguage": "en",
    "hasPart": [
      { "@id": "https://www.example.com/tickets/summer-fest#event" },
      { "@id": "https://www.example.com/tickets/comedy-night#event" }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "Event",
    "@id": "https://www.example.com/tickets/summer-fest#event",
    "name": "Summer Fest 2025",
    "startDate": "2025-07-18T18:00:00-07:00",
    "endDate": "2025-07-18T22:00:00-07:00",
    "eventStatus": "https://schema.org/EventScheduled",
    "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
    "url": "https://www.example.com/tickets/summer-fest",
    "location": {
      "@type": "Place",
      "name": "Cedar Park Amphitheater",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "100 Arena Way",
        "addressLocality": "Austin",
        "addressRegion": "TX",
        "postalCode": "78701",
        "addressCountry": "US"
      }
    },
    "offers": {
      "@type": "Offer",
      "url": "https://www.example.com/tickets/summer-fest#buy"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Are tickets refundable?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Refunds are available up to 48 hours before the event. See the ticket terms for details."
        }
      },
      {
        "@type": "Question",
        "name": "Do you offer accessible seating?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Select accessible seating during checkout or contact support for assistance."
        }
      },
      {
        "@type": "Question",
        "name": "Can I transfer my ticket?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Tickets can be transferred from your account up to 2 hours before doors open."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Tickets", "item": "https://www.example.com/tickets" }
    ]
  }
]
    Workflow

    Implement and verify

    1. 01

      Start with the live page

      Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.

    2. 02

      Add one JSON-LD script

      Use the combined example as a template in the document head or before the closing body tag.

    3. 03

      Complete regional details

      Fill shipping destinations and timing for every region the page actually serves.

    4. 04

      Link the return policy

      Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.

    5. 05

      Match visible answers

      Add only FAQs that users can read on the same page, with identical answers.

    6. 06

      Validate after changes

      Run Rich Results Test after implementation and whenever price, availability, or policy data changes.

    Quality check

    Common errors and fixes

    • Missing currency or availability

      Use ISO currency codes and complete schema.org availability URLs in Offer data.

    • Incomplete shipping details

      Include shippingDestination.addressCountry and deliveryTime.transitTime with units.

    • Return policy is not connected

      Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.

    • FAQ answers differ from the page

      Keep structured FAQ answers identical to visible answers.

    Questions

    Stack FAQs

    Should I include one Event per listing?

    Yes. Include a separate Event for each listing and make sure dates and URLs match the visible cards.

    Do I need Offer details?

    Only if pricing or a purchase CTA is visible. Use offers.url to point to the ticket purchase section.

    Primary sources

    References