Google has spent 2026 systematically narrowing which schema types still earn rich-result treatment, retiring FAQ display in May, having already deprecated HowTo rich results years earlier, and retiring several other types in a June 2025 cleanup. The pattern across every one of those removals is consistent: Google keeps the schema types that map to a genuine, ongoing business use case and removes the ones that were mostly used to grab search-result real estate. Event schema — the markup for conferences, webinars, and other scheduled gatherings — is explicitly one of the survivors, alongside JobPosting.
Despite that, most companies running a regular webinar series or an annual conference have never implemented Event schema at all, or have implemented it once for a single flagship event and then let it lapse for everything after. That gap matters more now than it did two years ago, because the same structured data that used to exist primarily to win a calendar-style rich result in classic search now does double duty as one of the cleaner, more reliably parsed signals an AI system uses to understand and cite time-bound content.
Why Does Event Content Need Its Own Schema Type Rather Than Generic Article Markup?
An event has a small number of facts that matter enormously and that generic Article schema has no dedicated field for: exactly when it starts and ends, where it happens or whether it is virtual, what it costs, and whether registration is still open. Event schema exists specifically to make those facts machine-readable in a standardized format, and an AI system fielding a query like "what AI conferences are happening in my industry next month" depends on exactly that structured date and location data to answer confidently rather than guess from unstructured prose.
Without Event schema, an AI system has to infer an event's date and status from body text, which is exactly the kind of ambiguity that reduces citation confidence covered throughout this series' schema guides. A blog post announcing a webinar in prose, with the date mentioned once in a sentence, is a far weaker citation candidate for a time-sensitive query than the same announcement with explicit Event schema declaring startDate, endDate, and eventStatus as structured fields.
What Does a Complete Event Schema Implementation Look Like?
The required properties are name, startDate, and location. The properties that separate a genuinely useful implementation from a bare-minimum one are the ones most organizations skip: eventAttendanceMode (declaring whether the event is online, in-person, or hybrid), eventStatus (so a cancelled or postponed event does not continue being cited as scheduled), and a properly nested offers object carrying registration price and availability.
{
"@context": "https://schema.org",
"@type": "Event",
"name": "The AEO Practitioner Summit 2026",
"startDate": "2026-09-15T09:00:00-05:00",
"endDate": "2026-09-15T17:00:00-05:00",
"eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
"eventStatus": "https://schema.org/EventScheduled",
"location": {
"@type": "VirtualLocation",
"url": "https://notioncue.com/summit-2026"
},
"description": "A one-day virtual summit covering AI citation tracking, schema strategy, and the current state of AEO measurement for B2B SaaS teams.",
"organizer": {
"@type": "Organization",
"name": "NotioncCue",
"url": "https://notioncue.com"
},
"offers": {
"@type": "Offer",
"url": "https://notioncue.com/summit-2026/register",
"price": "0",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"validFrom": "2026-07-01"
}
}For an in-person or hybrid event, the location object should use a full Place type with a structured PostalAddress rather than a plain text venue name — the same address-completeness principle covered in the local business AEO guide elsewhere in this series applies directly, since an AI system fielding a location-specific query needs the structured address to confidently match the event against a geographic filter.
What Happens to Event Schema After the Event Ends?
This is the single most common failure pattern with Event schema, and it is almost entirely avoidable. An event page left live after the event has passed, with its schema still declaring a future startDate or an eventStatus of scheduled, actively misleads any AI system that retrieves it — and repeated instances of stale event data erode the same domain-level trust signal covered throughout this series' freshness research.
Three options exist for a past event, and the right one depends on whether the content still has standalone value. If the event produced genuinely reusable content — a recording, a transcript, key takeaways — update the schema's eventStatus to reflect that it has concluded, and consider converting the page's primary schema to Article or VideoObject with the Event schema retained as supporting context rather than the page's primary type. If the page has no ongoing value beyond the event date itself, redirect it once the event concludes rather than leaving a stale, contradictory schema signal live indefinitely. If the event is part of a recurring series, the individual instance's page should redirect or clearly link forward to the next instance, using the same internal linking discipline covered in the internal linking guide elsewhere in this series.
How Does Event Schema Interact With FAQPage and Article Schema on the Same Page?
A well-built event landing page typically needs more than Event schema alone. A page announcing a webinar with a substantial description, a speaker bio section, and a Q&A block addressing common registration questions benefits from the same schema-stacking approach covered throughout this series: Event schema for the date, location, and registration facts; Article schema for the page's editorial content and authorship; and FAQPage schema for genuine registration or logistics questions, using the @graph array to link all three as related entities on one page rather than three disconnected blocks competing for the same content.
This stacking matters more for events than for most content types because an event page genuinely does need to answer several distinct question types simultaneously — what is this, when is it, how do I register, who is speaking — and a single schema type cannot cleanly represent all of them. The schema markup master guide elsewhere in this series covers the full stacking mechanics in more depth; this is the specific application of that principle to time-bound event content.
Does This Apply to Recurring Webinar Series the Same Way It Applies to a Single Annual Conference?
Yes, with one structural adjustment. For a recurring series — a monthly or quarterly webinar, for instance — each individual instance should have its own Event schema with its own specific date, rather than a single generic page reused indefinitely with the date manually updated each time. A single reused page with a repeatedly edited date creates exactly the kind of URL-level ambiguity covered in the canonicalization guide elsewhere in this series — an AI system that indexed the page for one specific date may continue citing that stale date even after the page content has moved on to the next instance.
The more reliable architecture is a stable series landing page (using EventSeries schema, a specific type schema.org added for exactly this use case) that lists and links to each individual dated instance, giving both the series as a whole and each specific occurrence its own clean, independently citable entity.
How NotioncCue Helps You Confirm Event Content Is Actually Earning Citations
Event and webinar content has a narrow, genuinely time-sensitive citation window — an AI system is far more likely to surface an upcoming event than one that already happened, which means the return on getting the schema right compounds only if you are actually tracking whether it is working during the window that matters.
The NotioncCue Citation Tracker monitors your tracked prompts weekly across all five major AI engines, which for an event-driven content strategy means you can track queries like "upcoming [category] conferences" or "[topic] webinars this quarter" in the weeks leading up to a scheduled event, and see directly whether your Event schema implementation is earning the citation during the window when it actually drives registrations, rather than discovering after the fact that the event was never surfaced at all.
Start your free NotioncCue trial and add your next scheduled event to your tracked prompt set at least four weeks before it happens — that gives you enough runway to see whether the citation is landing and to fix the schema if it isn't, before the registration window closes.
A fast audit for any organization running recurring events: pull a list of every event page still live on your domain and check whether the ones for past events still declare a future or "scheduled" status. This single-pass cleanup, run once, typically surfaces more stale schema than any other content type on a marketing site, precisely because event pages are so often built once and never revisited after the event concludes.
Frequently Asked Questions About Event Schema for AEO
Does Event schema still produce a visible rich result in Google Search?
Event rich results, including the calendar-style display in search and Google's dedicated events search experience, remain active as of mid-2026 and were not part of the deprecation wave that removed FAQ and HowTo rich results. Event is one of the schema types Google has explicitly continued supporting because it maps to a clear, ongoing user need rather than the more easily gamed use cases that got removed.
Should a cancelled event's page be deleted entirely?
Not necessarily immediately. Update the schema's eventStatus to EventCancelled first, since some users and AI systems may still be actively searching for status information about a previously announced event. Once enough time has passed that the cancellation is no longer a live query anyone is likely to ask, redirecting the page to a relevant current page is reasonable.
Is Event schema worth implementing for a single one-off internal event, or only for public conferences?
The AEO value is concentrated in publicly discoverable events that someone outside your organization might genuinely search for — a public webinar, an industry conference, a product launch event. A purely internal event with no public registration or public interest has no realistic citation upside from Event schema, since no one is running the kind of query the schema is built to answer.