Websites & Digital Experiences
What an event website should include
The short answer
An event website should answer five questions in its first screen or two: what is it, when and where, who is it for, what does it cost, and what do I do next. Everything else (the schedule, practical details, sponsors) supports those answers.
Most people arrive on an event website with one question and very little patience. They might be deciding whether to buy a ticket, checking a date, or trying to find where to park. The site’s job is to answer that question quickly, then make the next step obvious.
Start with the answers people came for
The first screen or two should say, in plain words:
- What it is. The name and one sentence that a stranger would understand.
- When and where. Dates, city and venue, not hidden in an image.
- Who it is for. Attendees, exhibitors, speakers or all three.
- What it costs. A price, a range, or “free”, and how to register.
- What to do next. One clear button.
If a visitor can’t answer those five questions without scrolling and guessing, the design is working against the event.
Make the next step obvious
Pick one primary action (register, buy tickets, apply, join the waitlist) and let it lead. Repeat it in the header and after the main sections, but don’t surround it with a dozen competing buttons. If tickets aren’t on sale yet, say when they will be and offer a simple way to be told.
Give the practical details a proper home
A schedule or programme, directions and parking, accessibility information, what to bring, the refund policy and a way to reach a human. These are the pages that answer most of the questions an organizer would otherwise get by email, so they deserve to be easy to find and easy to read on a phone.
Show who is involved
Real names and faces build confidence: speakers, guests, vendors, performers. If sponsors matter to the event, give them a clear place and give prospective sponsors a clear explanation of what is on offer and who to talk to.
Plan for the day after
A site that still says “tickets on sale now” months after the event ends tells visitors the event is forgotten. Decide in advance what the site becomes afterwards: a recap with photos, a thank-you, the date of the next edition, and a way to hear about it. For a recurring event, keeping the same address and updating it each year usually serves visitors and search engines better than starting again.
The technical basics that quietly matter
- Design for phones first; many visitors will never see the desktop layout.
- Keep pages fast and text easy to read, with enough contrast and a visible keyboard focus.
- Give each page its own title and description so search results make sense.
- Publish the dates and location in a form search engines can read, not only inside images.
Questions
01 How many pages does an event website need?
Fewer than most people expect. A home page that answers the key questions, a schedule or programme, practical information and a way to register is enough to start. Add pages when your audience starts asking for them.
02 Should an event have its own domain?
It can help if the event is a brand in its own right and you plan to keep the address from year to year. If it is one event within a larger organization, a section of the main site may serve visitors better. Either way, avoid changing addresses every edition.
03 What should the site do after the event ends?
Stay useful. Show a recap, say thank you, announce the next date when it is known, and offer a way to be notified. An abandoned countdown does the opposite.
Want help with Websites & Digital Experiences?
See what it includes