Does each event need its own detail page for Google?

Definition: For Google's Event search experience, each event needs a unique URL, which Google calls a leaf page, with Event structured data on that URL. A leaf page focuses on one event, while a schedule or listing page covers multiple events and is not the page Google recommends for this feature. Google's Event structured data documentation states this requirement directly.

Key facts

• Google's Event structured data documentation says that each event must have a unique URL, a leaf page, and markup on that URL.
• The event experience supports pages focused on a single event. Google recommends event posting pages instead of pages that list schedules or multiple events.
• For several performances on different days with individual tickets, Google says to add a separate Event element for each performance.
• Schema.org defines an Event as something happening at a certain time and location, and says repeated events may be structured as separate Event objects in its Event type definition.

Why does Google require a single-event page?

Google's Event documentation, updated on 8 September 2026, makes the rule page-specific: the target page must contain an event type from Schema.org, each event must have a unique URL, and the markup must be on that URL. The same documentation says that Google's event experience supports pages focused on one event and recommends event posting pages rather than pages that list schedules or multiple events.

This makes an event index, venue calendar, or archive useful for navigation, but it is not the documented target for the event experience. The detail page is the page whose URL identifies the individual event and whose markup describes that event.

How should several dates or performances be represented?

Google distinguishes an event that runs over several days from several performances. For one multi-day event, its guidance says to provide both the start and end dates. When different performances occur on different days and each has individual tickets, the guidance says to add a separate Event element for each performance. Together with the unique leaf URL rule, this means each separately represented performance needs its own event URL and markup when it is treated as an individual event.

Schema.org provides a broader model. Its Event definition describes an event at a time and location and says that repeated events may be separate Event objects. The eventSchedule property can associate an Event with a Schedule for a series of repeating events. Schema.org says an Event associated with a Schedule should take its dates from that Schedule rather than using startDate or endDate on the Event itself. That model describes the vocabulary; Google's Event page sets the page and URL conditions for Google's event experience.

What belongs on the detail page?

Google lists location, location.address, name, and startDate as required properties for eligibility. It also says the event name, start date, and location must accurately describe the event. A short JSON-LD pattern based on Google's standard event example looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "The Adventures of Kira and Morrison",
  "startDate": "2025-07-21T19:00-05:00",
  "location": {
    "@type": "Place",
    "name": "Snickerpark Stadium"
  }
}
</script>

The page must be accessible to Google and free from blocks such as robots.txt, noindex, or login requirements. Google tells site owners to validate the code with the Rich Results Test, use URL Inspection on deployed pages, and submit a sitemap to help Google learn about future changes.

Related terms

• Structured data
• JSON-LD
• Canonical URL
• XML sitemap

FAQ

Can a calendar page carry all the Event markup?

Google's Event documentation says its event experience supports pages focused on a single event and recommends event posting pages instead of pages listing schedules or multiple events. Use the calendar as a listing and place each event's markup on its unique detail URL.

Does every performance need its own page?

For different performances on different days with individual tickets, Google says to add a separate Event element for each performance. Its separate rule requiring a unique leaf URL means each such event needs its own URL with markup.

Is a unique URL enough for eligibility?

No. The page also needs an event type from Schema.org, Google's required properties, accurate event information, and access for Google. The documentation directs site owners to the Rich Results Test and URL Inspection for checks.

Sources

1. Google Search Central, "Event (Event) structured data", 8 September 2026
2. Schema.org, "Event - Schema.org Type", undated

---

Check how a page reads to answer engines. Open the GEO score analyzer