Each relationship has a specific job.
The artist and supporting acts
The artist is a performer at this event. Supporting acts connect to the same concert as additional performers. Those relationships help make the line-up clear, while distinguishing the artist from this particular appearance.
The venue
The venue is where the show takes place. Its approved address and location distinguish this concert from other dates. A reference to Alexandra Palace does not require us to build a general venue directory inside the microsite.
The ticket offers
An offer describes the tickets available for the concert: the approved price, currency, availability and route to book. These facts need to match what a fan can actually buy, including the relevant fees and restrictions.
The organiser
The promoter is separate from the artist and venue. Its identity tells us who is organising the event, while the artist continues to lead the concert’s creative experience.
The tour context
A genuine tour relationship can explain how the concert fits into the artist’s wider activity. It should only be included where accurate. Another date on that tour remains a different event, with its own identity.
The same facts, expressed for machines.
The graph is the connected information. Schema.org supplies a shared vocabulary for labelling it: this is a music event, this is its performer, and this is its location. JSON-LD is a format used to carry those labelled facts inside a webpage.
Fans see the artist-led design and readable concert information. Search systems can also find a structured description behind the page. It supports the visible content; it must not contradict it or introduce hidden claims.
The concert receives a stable identifier. A line-up page and a times page can refer back to that same event, rather than accidentally describing competing versions of it.
Where appropriate, an artist or venue can also reference verified official sources. The Schema.org term sameAs identifies the same person, organisation or place. It should not be used to suggest that an artist and one of their concerts are the same thing.
One identity, kept consistent.
The graph becomes more useful when it stays aligned with the website. If an approved time changes, we update the relevant visible information and the structured description. Ticket availability, prices and event status need the same care.
A rescheduled concert should retain the appropriate event identity and clearly communicate its changed status. An archive should describe the show that actually happened, rather than silently becoming next year’s event.
This is why we start with an approved record of the concert’s facts and an agreed update process. Accuracy comes from the way we manage the information, as well as the code used to describe it.
A clearer foundation, not a placement promise.
Connected event facts reduce ambiguity about who is playing, where, when and how to book. Accurate event structured data can also support eligibility for search features that use it.
It does not automatically create a Google Knowledge Panel, place the concert in a platform’s internal knowledge graph or guarantee an AI citation. Search and AI systems decide what they retrieve, index and show.
The strongest approach combines the graph with useful concert answers, readable pages, clear access for crawlers and relevant links from the wider campaign. The graph is one important part of that work.
Read the official guidance.
These references explain the vocabulary and search principles behind this approach.
BACK TO THE BIGGER PICTURE
See the connections in context.
Return to the event graph step, then continue into machine-readable content and the other discovery foundations.
Return to Journey 3, step 3 →