Building an event website: what it should include
The pages a participant needs, the order they read them in, and how to publish an event website without a developer.
Updated October 2026 · All guides
An event website must answer four questions from the home page: what, when, where, and how to register. Then add the programme, the speakers, directions to the venue and an FAQ page. Most visitors read it on a phone: check every page at that size before publishing.
Step by step
Put the essentials at the top of the home page
The event name, the date, the city and a registration button must be visible without scrolling, on a phone too.
Publish the programme as soon as it holds
An incomplete programme is better than none: publish the outline, then add sessions as they are confirmed. Filters by day, room or topic become useful beyond about twenty sessions.
Introduce the speakers
A photo, a name, a job title and one line on what they will talk about. Speakers are happy to share their page, which helps spread the word about the event.
Explain how to get there
Address, map, public transport, parking, accessibility, check-in times. It is the most visited page the day before and on the morning itself.
Answer questions before they are asked
An FAQ page (dress code, meals, refunds, replay) saves dozens of emails.
Translate if your audience needs it
If part of your audience speaks another language, translate at least the home page, the programme and the registration form.
The most common mistakes
- Hiding the registration button at the bottom of the page or behind a menu.
- Editing the live page while people are registering, and showing a half-changed programme.
- Never looking at the site on a phone before sending it out.
Doing it with LiveEvent
In LiveEvent, you start from a site template (conference, trade show, seminar, evening event, online, festival), add blocks, and publish on your subdomain or your own domain. The live version does not change until you republish.
Frequently asked questions
- How long does it take to build an event website?
- It depends mostly on your content. From a template, the structure is there right away; what takes time is writing the copy and gathering the photos and the programme.
- Do I need one website per event?
- It is better: each edition keeps its own address and pages, and the next one is prepared without touching the one that is live.
- Should an event website be indexed by Google?
- Yes if it is public: set a title and description for each page, with the event name, the city and the year. A site for employees only does not need to be indexed.