XooCode(){

PerformAction

PerformAction is a PlayAction subtype for performing (music, theatre, dance). Property: entertainmentBusiness (EntertainmentBusiness — the venue).

Full example of schema.org/PerformAction json-ld markup

The markup is verified as valid with Rich Results Test from Google.

schema.org/PerformAction
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PerformAction",
  "agent": { "@type": "Person", "name": "Performer" },
  "entertainmentBusiness": { "@type": "PerformingArtsTheater", "name": "Dunmore Concert Hall" }
}
</script>

Minimal valid version

The smallest markup that still produces a valid PerformAction entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/PerformAction (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PerformAction",
  "entertainmentBusiness": { "@type": "TheaterGroup", "name": "Example venue" }
}
</script>

Google rich results this unlocks

PerformAction is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). PerformAction becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common PerformAction mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    Missing entertainmentBusiness

    Wrong
    PerformAction with only agent
    Right
    Include the venue via entertainmentBusiness

    Perform verbs are venue-anchored.

Also mentioned in 1 other example

PerformAction also appears in PlayAction. See the full PerformAction schema page for every reference.

About the example data

Performance at the Dunmore Concert Hall.

Comments

Loading comments...

Leave a comment