How does event markup distinguish an organizer from a performer?

Definition: In Event markup, organizer identifies the person or organization hosting the event, while performer identifies the person or group performing at it. Google's Event structured data documentation documents organizer.name, organizer.url, and performer.name for these roles.

Key facts

• Google defines organizer as an Organization or Person that hosts the event. Google Search Central encourages organizer.name and organizer.url when organizer is included.
• Google defines organizer.name as the name of the hosting person or organization and organizer.url as the event host's domain URL.
• Google describes performers as participants such as artists and comedians, with a nested PerformingGroup or Person for each performer.
• Schema.org defines an Event's organizer as an organizer of an Event and its performer as a performer at the event. Schema.org's Event type allows either an Organization or a Person for both properties.
• Schema.org's Person type inherits name as the name of the item and url as the URL of the item.

What does organizer identify?

The organizer object describes the event host. Google's Event documentation gives its value type as Organization or Person, then defines organizer.name as the name of the person or organization hosting the event. The field therefore describes the entity responsible for hosting, rather than the artist appearing in the programme.

Google defines organizer.url as the event host's domain URL. This is a URL on the nested organizer entity. A business, venue operator, association, or individual can be represented according to the type that matches the host described by the page.

What does performer identify?

The performer object describes the participants performing at the event. Google's Event documentation names artists and comedians as examples, and says to use a nested PerformingGroup or Person, one for each performer. Its documented performer.name value is the name of the participant, such as an artist or comedian.

Schema.org's Event type describes performer as an Organization or Person. Its Person type inherits the general name and url properties, so a nested person can carry those schema.org properties. Google’s Event feature table documents performer.name; it does not document a performer.url field.

Which URL belongs in each field?

The URL roles are different. Google's Event documentation defines organizer.url as the event host's domain URL. Google separately defines offers.url as the URL of a page that provides the ability to buy tickets, so a ticket purchase page belongs in the offer object rather than in organizer.url.

The relevant part of Google's example uses an organization as the organizer and a performing group as the performer:

"performer": {
  "@type": "PerformingGroup",
  "name": "Kira and Morrison"
},
"organizer": {
  "@type": "Organization",
  "name": "Kira and Morrison Music",
  "url": "https://kiraandmorrisonmusic.com"
}

This structure keeps the host's name and domain under organizer, while the participant's name stays under performer.

How should a site check the implementation?

Google's Event documentation says to validate structured data with the Rich Results Test, fix critical errors, and use the URL Inspection tool to test how Google sees deployed pages. The page states that it was last updated on 8 September 2026. A check should therefore inspect the nested object types, the host and performer names, and the URL role assigned to each field.

Related terms

• Structured data
• JSON-LD
• Organization structured data
• Person structured data

FAQ

Can the same entity be both organizer and performer?

Yes, if you are describing one entity that hosts the event and also performs at it. Put the entity's hosting role under organizer and its performing role under performer, using the names that correspond to those roles.

Does Google document performer.url for Event markup?

No. Google documents performer.name in its Event feature properties. Schema.org gives Person and Organization a general url property, but Google's Event documentation does not state how performer.url is handled for that feature.

Should you put a ticket link in organizer.url?

No. Google defines organizer.url as the event host's domain URL and describes offers.url as the page where a user can buy tickets.

Sources

1. Google Search Central, "Event structured data", 8 September 2026
2. Schema.org, "Event", undated
3. Schema.org, "Person", undated
4. Schema.org, "Organization", undated

---

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