Event Schema for AI Discovery: Making Events Findable by AI Assistants

What Is Event Schema?

Event Schema is a schema.org structured data type that provides machine-readable information about an event, including its name, date, time, location (physical or virtual), description, ticket availability, pricing, organizer, and performers. It enables search engines to display event rich results in Google Search and helps AI assistants answer queries about upcoming events, conferences, workshops, concerts, and local happenings.

Event-related queries are among the most time-sensitive questions users ask AI assistants. "What tech conferences are happening in San Francisco this month?" or "Best marketing webinars next week" require AI to find events with specific dates, locations, and topics. Event Schema provides this data in a structured format that AI can filter and match to user queries with precision.

Without Event Schema, AI must extract event details from unstructured page content -- parsing dates from natural language ("Join us on the 15th" vs. "March 15, 2026"), identifying venues from context, and guessing at ticket availability. Event Schema eliminates this ambiguity. For structured data fundamentals, see our JSON-LD basics guide.

Why Events Matter for AI Search

Event discovery is a natural use case for AI assistants. Users increasingly ask Siri, Google Assistant, ChatGPT, and other AI tools to find events based on criteria like location, date, topic, and price. This creates a direct path from Event Schema implementation to AI citation.

Event query patterns

AI assistants handle several types of event queries:

• Location-based -- "Events in Chicago this weekend" or "Conferences near me"
• Topic-based -- "AI SEO workshops" or "Marketing conferences 2026"
• Time-based -- "What's happening tonight?" or "Events next month"
• Price-based -- "Free events in my area" or "Conferences under $500"
• Combined -- "Free AI workshops in New York this quarter"

Each of these query types requires structured event data that matches the user's criteria. Event Schema provides the filterable properties -- date, location, price, topic -- that AI needs to match events to queries.

The local connection

Event queries have a strong local component. Research shows that 70% of queries to ChatGPT in many markets include a local or regional element. Events are inherently local (even virtual events have time zones), making Event Schema a natural complement to local SEO strategies for AI.

Complete JSON-LD Implementation

Here is a complete Event Schema implementation for an in-person event:

{
  "@context": "https://schema.org",
  "@type": "BusinessEvent",
  "name": "AI SEO Masterclass 2026",
  "description": "Full-day workshop covering AI SEO strategy, technical implementation, and content optimization. Hands-on exercises with real websites. Suitable for marketing professionals and business owners.",
  "image": "https://aimetrico.com/images/events/ai-seo-masterclass-2026.webp",
  "startDate": "2026-06-15T09:00:00-05:00",
  "endDate": "2026-06-15T17:00:00-05:00",
  "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
  "eventStatus": "https://schema.org/EventScheduled",
  "location": {
    "@type": "Place",
    "name": "TechHub Conference Center",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "123 Innovation Drive",
      "addressLocality": "Austin",
      "addressRegion": "TX",
      "postalCode": "78701",
      "addressCountry": "US"
    }
  },
  "organizer": {
    "@type": "Organization",
    "name": "AImetrico",
    "url": "https://aimetrico.com"
  },
  "performer": {
    "@type": "Person",
    "name": "Sarah Chen",
    "jobTitle": "Head of AI SEO Research"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://aimetrico.com/events/ai-seo-masterclass-2026",
    "price": "499",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "validFrom": "2026-03-01"
  }
}

Key implementation notes

• Use specific event types -- BusinessEvent, EducationEvent, MusicEvent instead of generic Event
• Include timezone in dates -- 2026-06-15T09:00:00-05:00 (ISO 8601 with timezone offset)
• Full address -- Include street, city, state/region, postal code, and country
• Offer with availability -- Tell AI whether tickets are still available

Required and Recommended Properties

| Property | Required | AI Value | Description | |---|---|---|---| | name | Yes | Critical | Event title | | startDate | Yes | Critical | Start date and time with timezone (ISO 8601) | | location | Yes* | Critical | Place or VirtualLocation (*required for in-person) | | eventAttendanceMode | Recommended | High | Offline, Online, or Mixed | | eventStatus | Recommended | High | Scheduled, Cancelled, Postponed, Rescheduled | | endDate | Recommended | Medium | End date and time with timezone | | description | Recommended | High | 100-300 character event summary | | image | Recommended | Medium | Event promotional image | | organizer | Recommended | High | Organization or Person hosting | | performer | Optional | Medium | Speakers, artists, or featured participants | | offers | Recommended | High | Ticket pricing and availability | | doorTime | Optional | Low | When doors open / check-in starts | | maximumAttendeeCapacity | Optional | Low | Venue capacity | | inLanguage | Optional | Medium | Language of the event |

Virtual and Hybrid Events

Virtual and hybrid events require specific Schema properties to communicate their online nature to AI models and search engines.

Virtual (online-only) event

{
  "@type": "EducationEvent",
  "name": "AI SEO Webinar: Getting Started",
  "startDate": "2026-04-10T14:00:00Z",
  "eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
  "eventStatus": "https://schema.org/EventScheduled",
  "location": {
    "@type": "VirtualLocation",
    "url": "https://zoom.us/j/123456789"
  }
}

Hybrid event (in-person + virtual)

{
  "@type": "BusinessEvent",
  "name": "AI SEO Summit 2026",
  "eventAttendanceMode": "https://schema.org/MixedEventAttendanceMode",
  "location": [
    {
      "@type": "Place",
      "name": "Convention Center",
      "address": {
        "@type": "PostalAddress",
        "addressLocality": "Austin",
        "addressRegion": "TX"
      }
    },
    {
      "@type": "VirtualLocation",
      "url": "https://aimetrico.com/summit-livestream"
    }
  ]
}

Attendance mode values

| Value | URL | Meaning | |---|---|---| | Offline | https://schema.org/OfflineEventAttendanceMode | In-person only | | Online | https://schema.org/OnlineEventAttendanceMode | Virtual only | | Mixed | https://schema.org/MixedEventAttendanceMode | Both in-person and virtual |

Event Status and Cancellations

The eventStatus property communicates the current state of an event. Keeping this property updated is critical -- AI models that recommend a cancelled event damage your credibility.

Status values

| Status | URL | When to use | |---|---|---| | Scheduled | https://schema.org/EventScheduled | Event is confirmed and happening as planned | | Cancelled | https://schema.org/EventCancelled | Event is cancelled and will not take place | | Postponed | https://schema.org/EventPostponed | Event is delayed but will be rescheduled | | Rescheduled | https://schema.org/EventRescheduled | Event has been moved to a new date | | MovedOnline | https://schema.org/EventMovedOnline | Previously in-person, now virtual |

When events are rescheduled

When rescheduling, update both the eventStatus to EventRescheduled and the startDate/endDate to the new dates. Also add the previousStartDate property with the original date so AI models can communicate the change accurately.

{
  "eventStatus": "https://schema.org/EventRescheduled",
  "startDate": "2026-07-20T09:00:00-05:00",
  "previousStartDate": "2026-06-15T09:00:00-05:00"
}

Recurring Events

Recurring events (weekly meetups, monthly webinars, annual conferences) require specific Schema handling. Each occurrence should have its own Event Schema with its own specific date, even if other details are identical.

Best practices for recurring events

1. Create separate pages for each occurrence (or at minimum, separate JSON-LD blocks)
2. Use specific dates for each occurrence -- do not use generic "every Tuesday" descriptions
3. Link occurrences using the superEvent property to connect individual occurrences to the event series
4. Update after each occurrence -- mark past occurrences as completed, ensure future dates are correct

Example: Monthly webinar series

{
  "@type": "EducationEvent",
  "name": "AI SEO Monthly Webinar - April 2026",
  "startDate": "2026-04-10T14:00:00Z",
  "superEvent": {
    "@type": "EventSeries",
    "name": "AImetrico Monthly AI SEO Webinar Series"
  }
}

Common event Schema mistakes

1. Missing timezone -- Dates without timezone offsets are ambiguous. Always include the timezone.
2. Past events with "Scheduled" status -- Update past events or remove them from your active event listings.
3. Generic Event type -- Use specific subtypes (BusinessEvent, MusicEvent) for better AI categorization.
4. No offers property -- Even for free events, include Offer with price: "0" to tell AI the event is free.
5. Incomplete address -- For in-person events, include full street address, not just city name.

Validate your implementation using our testing structured data guide.