SwiftSchema Logo

    SwiftSchema

    Intuitive Schema Generation at Your Fingertips

    AboutLearnContact

    Business Event Schema Generator — Promote Conferences and Meetups

    Generate valid BusinessEvent JSON‑LD in minutes. Clarify dates, venue or virtual access, organizer, and ticket Offers to improve understanding and visibility.

    Try the BusinessEvent Generator

    Why many event pages underperform

    Pain points we solve

    • Date/time and venue details are unclear or missing timezone information.
    • Hybrid or online access is ambiguous without a clear attendance mode and join URL.
    • Organizer information is missing, reducing trust and context.
    • Ticket Offers omit price/currency or URL, limiting clarity and conversions.

    How SwiftSchema helps

    Solution

    The BusinessEvent generator focuses on the essentials: start/end dates with timezone, attendance mode (online, in‑person, or hybrid), a concrete location (Place or VirtualLocation), and organizer details (Person/Organization).

    It supports ticket Offers (price, priceCurrency, availability, and URL) and images to improve presentation, outputting copy‑ready JSON‑LD for your event page.

    How it works

    How it works

    1. Choose BusinessEvent in the generator below.
    2. Enter event name, description, and start/end dates with timezone (ISO 8601).
    3. Set attendance mode and add a Place (with PostalAddress) or a VirtualLocation URL.
    4. Add organizer (Person or Organization) and an Offer with price, currency, and URL if ticketed.
    5. Copy JSON or Script, paste on your event page, and validate in the Rich Results Test.
    Generate BusinessEvent JSON‑LD

    Paste once per event. Validate. Ship.

    What is BusinessEvent structured data?

    BusinessEvent is an Event subtype for professional gatherings such as conferences, summits, networking meetups, trade shows, demos, or roadshows. It captures the who/what/where/when of your event, including organizer info, attendance mode (in-person, online, hybrid), schedule, venue, and ticketing details. Accurate schema helps search engines display event cards, highlight key info (dates, location, price), and connect searchers to registration pages faster. Even if your event is private or invitation-only, structured data clarifies which company is hosting and why it matters.

    Required and recommended properties

    1. name
       — official event title (e.g., “B2B Growth Summit 2026”).
    2. startDate
      /
      endDate
       — ISO 8601 timestamps with timezone offsets (
      2026-04-10T09:00:00-05:00
      ).
    3. location
       —
      Place
      with
      name
      ,
      address
      (PostalAddress). For online, use
      VirtualLocation
      .
    4. eventAttendanceMode
       —
      OfflineEventAttendanceMode
      ,
      OnlineEventAttendanceMode
      , or
      MixedEventAttendanceMode
      .
    5. eventStatus
       — optional but helpful (
      EventScheduled
      ,
      EventPostponed
      ).
    6. description
       — summary of agenda, target audience, or value.
    7. organizer
       — Person or Organization.
    8. image
       — hero art (1200px+), logos, or venue photos.
    9. offers
       — price, currency, availability, and ticketing URL (if applicable). Mention
      availabilityStarts/Ends
      .
    10. performer
      /
      speaker
       — optional; list featured speakers or hosts (Person/Organization).

    Handling virtual and hybrid events

    • Use
      VirtualLocation
      with
      url
      pointing to the streaming or registration page.
    • Set
      eventAttendanceMode
      to
      OnlineEventAttendanceMode
      for virtual-only or
      MixedEventAttendanceMode
      when you have both in-person and online components.
    • Provide
      organizer
      and
      performer
      details even for virtual events; this assures participants the event is legitimate.
    • If you gate access behind a registration form, mention that in the description and ensure the
      offers.url
      leads to the form.
    • For hybrid events, include both a
      Place
      and
      VirtualLocation
      . Clarify hybrid logistics in the visible content (e.g., “In person in Austin + livestream for remote attendees”).

    Content prep checklist

    • Define agenda, keynote speakers, workshops, and networking opportunities.
    • Confirm venue details: address, room names, capacity, on-site amenities (parking, Wi-Fi, accessibility).
    • Gather imagery: past event photos, venue shots, speaker headshots.
    • Set ticket tiers (free, early bird, VIP) with pricing/currency, along with discount deadlines.
    • Decide on refund policy and display it on the event page (schema doesn’t capture refunds, but the content should).
    • Collect organizer details (company, contact email, social links) so you can populate
      organizer
      and
      sameAs
      .

    Implementation workflow

    1. Create/update the event landing page with the content above, ensuring all details are accurate.
    2. Generate BusinessEvent JSON‑LD using this form. Fill required fields and optional ones like
      performer
      ,
      about
      ,
      sponsor
      .
    3. Include Offers for ticketing:
      price
      ,
      priceCurrency
      ,
      url
      ,
      availability
      ,
      validFrom
      .
    4. Embed the schema once per event page (preferably in the
      <head>
      ). Avoid duplicate Event markup from other plugins.
    5. Validate using Rich Results Test and the Schema Markup Validator.
    6. Monitor Search Console’s Performance > Search Appearance (Events) if event search features become available; otherwise track page clicks/conversions manually.

    Recurring or multi-day events

    • For a single multi-day event, use
      startDate
      /
      endDate
      covering the full span and describe the daily agenda in content.
    • For recurring events (monthly webinars, annual summits), consider EventSeries to describe the entire series, plus individual Event pages for each occurrence.
    • Update schema status if an event is postponed or canceled:
      eventStatus: EventPostponed
      or
      EventCancelled
      . Update content and send comms to registrants.
    • Keep historical event pages live (with a “Past event” label) to preserve SEO equity; just mark them as completed in schema (
      eventStatus: EventCompleted
      ).

    Ticketing and Offers

    • For free events, set
      price: 0
      and
      availability: InStock
      . Include a registration URL.
    • For tiered pricing, add multiple Offer objects (Early Bird, General Admission, VIP) with
      availabilityStarts/Ends
      .
    • If tickets are sold via Eventbrite, Hopin, or similar platforms, set the
      offers.url
      to the platform page and mention the provider in content. You can still add Offers even if you’re not processing payments directly.
    • Track conversions by UTM-tagging the Offer URLs in schema (but keep canonical links clean if possible).

    Troubleshooting checklist

    • Missing timezone: always include offset (e.g.,
      -05:00
      ). For UTC, use
      Z
      or
      +00:00
      .
    • No organizer: add
      organizer
      even if it’s the same brand as the site; clarity builds trust.
    • Partial location data: include full PostalAddress, not just the venue name.
    • Offers without price: if you reference tickets, specify price/currency or state that it’s free (price 0). Don’t leave Offers blank.
    • Out-of-date schema: update
      eventStatus
      and
      offers
      whenever you change scheduling or pricing.

    Common Errors & Fixes

    • No organizer: always include
      organizer
      (Person/Organization) to legitimize the event.
    • Missing timezone: use full ISO 8601 timestamps with offset for
      startDate
      and
      endDate
      .
    • Incomplete ticket info: include price, currency, and ticket URL when selling or registering attendees.
    • Virtual details omitted: for online events, include
      VirtualLocation
      and
      eventAttendanceMode: OnlineEventAttendanceMode
      .
    • Duplicated schema: disable overlapping Event markup from plugins when embedding this JSON‑LD.

    Required properties

    • name
    • startDate
    • location.name

    Recommended properties

    • image
    • url
    • organizer.name
    • offers.price
    • offers.priceCurrency
    Minimal JSON-LD
    Validate
    {
  "@context": "https://schema.org",
  "@type": "BusinessEvent",
  "name": "B2B Growth Summit",
  "startDate": "2026-04-10T09:00:00-05:00",
  "location": {
    "@type": "Place",
    "name": "Convention Center"
  }
}

    FAQs

    Online events?Show
    Use OnlineEventAttendanceMode and provide a registration URL.
    Multiple days?Show
    Use startDate/endDate and consider an EventSeries for recurring events.

    Related types

    Browse all schema types

    References

    Generate Business Event schema

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

      Schema Type

      💼 Business Event Schema Generator

      Event subtype for conferences and meetups. Add organizer, agenda, and ticketing.

      Generated Schema

      Validate your schema here.