The audience arrives with five questions

What is on, when, where, who is involved, and how to get a ticket. A theatre website is doing its job when those answers are easy to find.

People come to a theatre website with a plan for an evening, or with a question from someone else. “Are they doing anything in November?”

The useful page answers five things, in an order a visitor can scan. What is on. When it is playing. Where it is. Who is involved. How to get tickets. If any one of those is buried, late, or trapped in a PDF from last season, the visit has already gone wrong, however good the photography is.

A general website tool can hold all of this. It starts from a blank page. The team invents the structure of a show every time, and then has to remember which field draws the dates. The answers drift apart: the hero says one month, the calendar says another, the ticket link points at a third.

Mobile visitors feel the drift first. They are on a bus, deciding tonight. They need the time and the ticket link without hunting through a desktop layout that was never checked on a phone.

A theatre site can treat those five answers as the page. The team fills in the show. The visitor finds the night. Search engines get the same clear facts. The design can still belong to that company. The questions stay the same from theatre to theatre.

When the answers are easy to publish, they stay current. When they are hard to publish, the photography stays beautiful and the facts go stale. Audiences came for the facts.

All posts

Early access

Theatre.show is in development.

We are building the first version now. Join the early access list to hear when it is ready and follow the development of the platform.

Join the early access list