Discuss your event

THE FULL EXPLANATION / JOURNEY 03, STEP 04

Give search systems a labelled description of the show.

Fans read the concert pages. Alongside them, MusicEvent structured data identifies the performer, place, dates, offers and status. We use Schema.org labels expressed as JSON-LD, aligned with the visible information.

← Return to this step in the journey

Keep graph, vocabulary and format distinct

The graph is the connected information. Schema.org supplies labels such as MusicEvent and performer. JSON-LD is a format for expressing those labelled facts inside the page.

Use approved data that agrees with the visible content. Stable identifiers let related pages refer to the same event. Appropriate official identity references can clarify the artist or venue, while offers and lifecycle status require the same accuracy as the booking information fans see.

What this gives the promoter

Human-readable content and machine-readable facts reinforce the same story.

This component works alongside the other discovery foundations. Useful content, consistent event facts, accessible pages and approved updates need to agree. The fictional example demonstrates the approach and does not establish an actual search placement or assistant citation.

Can hidden structured data say more than the visible page?

It must not introduce contradictory or unsupported claims. The machine-readable description supports the approved visible concert facts.

Explore the example.

The NOVA concert and campaign are fictional demonstrations. Links open the existing example in a new tab; they do not connect live data or complete a purchase.

Open the concert example ↗ (opens demonstration in a new tab)

YOUR NEXT EVENT

Give your event its own digital home.

Tell us about the show and what you want to achieve. We’ll agree the right scope together.

Discuss your event