Free Business Event Schema Generator

Why many event pages underperform

How SwiftSchema helps

How it works

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, EventCancelled, EventMovedOnline, EventRescheduled). schema.org has no “completed” status.
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 — optional; list featured speakers or hosts (Person/Organization). schema.org has no speaker property.

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; label them as past on the page; schema.org has no completed status, so leave eventStatus as EventScheduled.

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.
• Hybrid ambiguity: include both Place and VirtualLocation when hybrid; clarify in content.
• Wrong attendance mode: align eventAttendanceMode with the actual experience (online, offline, or mixed).

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.

On-page parity checklist

• Event title and dates on-page match name, startDate, and endDate (with timezone).
• Venue and address on-page match location PostalAddress; virtual join/registration link is visible and matches VirtualLocation/offers.url.
• Ticket pricing shown to users matches offers.price/offers.priceCurrency; availability reflects real inventory/status.
• Organizer name and logo on-page match organizer; include contact/social links where possible.
• If hybrid, both in-person and virtual details are present on-page and in schema.
• Only one Event/BusinessEvent schema block per event page; remove duplicates.

Validation and maintenance

• Validate with Rich Results Test after changes; spot-check Search Console for Event enhancements (if available).
• Update eventStatus when postponing/canceling/moving online; reflect changes in visible content.
• Revalidate after venue changes, time shifts, or ticketing URL changes.
• Keep lastReviewed current; assign an owner for event schema updates during the campaign cycle.