Event Website Design: What an Event Site Needs in 2026

Good event website design answers three questions within seconds, what is it, when and where is it, and how do I get a ticket, then makes buying that ticket easy on a phone. Everything else, the agenda, the speakers, the venue guide, exists to support that one decision.

This guide covers what an event site is for, the pages it needs, agenda and speaker pages, how the site hands visitors to your ticketing tool, two US rules on ticket prices and accessible seating, search and Event structured data, what to do before and after the day, and what it costs to build.

What an Event Website Is For

An event website exists to turn interest into registrations or ticket sales, and then to get those people to the right place at the right time. It works as a sales page before the event and as a reference guide in the final week.

That double role shapes the design. Months out, visitors want the pitch: who is speaking or playing, why it is worth the trip, and what it costs. In the last few days, the same visitors come back on their phones looking for the address, the doors-open time, the schedule and the Wi-Fi password. A site that only does the first job leaves attendees hunting through emails.

It also means the website and the ticketing system are separate tools. The website tells the story and answers questions; a ticketing or registration platform handles inventory, payment, confirmations and check-in. Design the site around a clean hand-off between the two.

The Pages an Event Website Needs

Most single events need six to eight pages, and the home page and tickets page do most of the selling. Put the date, the city and a Get tickets button in the header so they are visible on every page.

A small meetup can fold most of this into one long page with anchor links. The structure in our landing page design guide works well for that, with Get tickets as the single action. Larger events with several tracks or stages need the agenda and speakers as separate pages.

Agenda and Speaker Pages

Build the agenda and the speaker list from structured content, not hand-made pages. Each session and each speaker should be an entry with the same fields, so the list pages, detail pages and filters all stay consistent when the programme changes.

• Session fields: title, day, start and end time, room or stage, track, format (talk, workshop, panel) and the speakers linked to it.
• Speaker fields: name, photo, role, company, a short bio, links, and the sessions they appear in.
• Time zones: show times in the venue's local time and say so; for hybrid events, add the time zone abbreviation to every slot.
• Changes: mark a moved or cancelled session clearly on its card rather than quietly deleting it.
• Phone first: a day-by-day list with sticky day tabs reads better on a phone than a wide grid.

A CMS makes this practical. In Framer you would create Sessions and Speakers collections and reference one from the other; our Framer CMS guide shows how collections, references and detail pages work. Check your plan's collection limit before you start, because a festival with sessions, speakers, sponsors and news needs four collections.

Tickets and Registration: Link or Embed

Use a ticketing or registration platform for inventory, payment and check-in, and make the website hand visitors to it in one tap. Don't rebuild ticket sales inside a website builder.

You can connect the two in two ways. A link sends buyers to the ticketing platform's own event page. An embed places the checkout inside your site. Tito, for example, describes its ticket widget as a way to embed the registration form with custom CSS, or a single button that opens the form in a pop-up.

• One clear button. Use the same Get tickets label in the header, the hero and the tickets page.
• Deep-link ticket types. A button under the workshop pass should open that ticket type, not the start of the flow.
• Match the look. Bring your logo, colours and fonts into the checkout so the hand-off doesn't feel like another site.
• Track it. Tito notes that its widget is what you need for Google Analytics or your own tracking of completed orders; check the same for whichever platform you use, or you can't tell which pages sell tickets.

Show the Total Ticket Price Up Front

In the US, a business that shows a price for a live-event ticket must show the total price, including mandatory fees, more prominently than any other pricing information. This comes from the FTC's rule on unfair or deceptive fees, 16 CFR Part 464.

The rule's definitions list live-event tickets as a covered good or service. Total price means the maximum total of all fees and charges a buyer must pay, and government charges, shipping charges and optional extras may be left out. Section 464.2 sets the prominence requirement for any offer, display or advertisement that shows a price.

On the website, that means the tickets page, the hero and any "from $X" banner should show the total including mandatory service or booking fees, or leave the price off and send buyers to checkout. Check that your ticketing platform's checkout follows the same rule. This is a summary, not legal advice; ask your lawyer how it applies to your event.

Accessible Seating and an Accessible Site

US venues and ticket sellers covered by the ADA must give people with disabilities the same chance to buy accessible seating as everyone else buys tickets, and, when asked, describe that seating in enough detail for them to judge it themselves.

The rule is in the ADA Title III regulations at 28 CFR 36.302(f), which you can read on Cornell's copy of section 36.302. It requires accessible seating to be sold during the same hours, at the same stages, including pre-sales and general sales, and through the same methods as other tickets. When asked, the seller must say where accessible seats are still available; if seating maps are given to the public, they must identify accessible seating; and accessible seats can't cost more than other seats in the same section.

On the website, give accessibility its own section on the venue page: step-free routes, wheelchair spaces and companion seats, accessible toilets, quiet rooms, captioning or interpretation, and a named contact. Make sure accessible tickets can be bought online like any other ticket. The site itself should also work with a keyboard and a screen reader, with real text on the agenda rather than an image of a schedule.

Search, Speed and Event Structured Data

Mark up each in-person event with schema.org Event structured data so Google can show it with its date and place, and keep the pages fast on a phone, where most last-minute visits happen.

• Required properties: Google's event structured data guide lists name, startDate and location, with location.address, as required. Recommended ones include description, endDate, eventStatus, image, offers, organizer and performer.
• Physical events only: the same guide says virtual experiences with no real-world component aren't supported for event rich results. Schema.org's Event type still has an eventAttendanceMode property to say whether an event is online, offline or mixed.
• Speed: Google's Core Web Vitals guidance sets a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads. A large hero video is usually what breaks LCP.
• One set of facts: keep the date, venue name and address identical on the website, the ticketing page and every listing.

Before, During and After the Event

An event website changes with the calendar, so plan three states: selling, on the day and archive. Each one moves different content to the top of the home page.

If plans change, don't delete the event page. Google's guide says to keep the other properties unchanged and set eventStatus to EventCancelled for a cancelled event; for a postponed event with no new date, keep the original startDate and set EventPostponed; for a rescheduled one, update the dates and set EventRescheduled.

For a recurring event, keep each year's pages under a stable address such as /2026 and point the main domain at the current edition. Past programmes and recordings are your best evidence when you sell the next one.

Building It: Platforms and Costs

Most event sites can run on a website builder plan, because the ticketing platform carries payments and check-in. The choice is mainly about how often the programme changes and who will update it.

Prices are from Framer's pricing page and Webflow's pricing page, fetched today; both change, so check before you buy. Your ticketing platform charges its own fees on top. If you are choosing between the two builders, our Webflow vs Framer comparison goes through the differences, and how much a website costs covers domains, design time and the rest of the budget.

Waida Templates to Start From

Waida Studio doesn't make a conference template, so these two are our own templates with event listings built in. You would rename their collections to match your programme and point the ticket buttons at your ticketing platform.

Goal

Goal was built for football tournaments, sports events and athletic organisations. Its 11 pages include events and fixtures pages, team and player profiles and a live event hub, with a Tournaments CMS collection on Framer and Webflow and ticket or streaming buttons throughout. It suits a tournament, a league, a race or any event with a fixture list.

It costs $59 on Framer or Webflow, $39 in HTML and $49 in Next.js or Astro.

Check out Goal template

Camp

Camp is a code template for outdoor brands and trip operators, with 41 pages including an upcoming events list and nine event detail pages that show prices, dates and locations. It suits workshops, retreats, guided trips and other small-group events that sell places alongside products. It comes in HTML for $39 and in Next.js or Astro for $49.

Check out Camp template

Every Waida licence covers unlimited projects for one person with no attribution required, as set out in the licence terms, so an agency can reuse a template for each client's event. Figma files are sold separately for $19 each. You can browse more layouts in the business website templates.

Event website design comes down to a short list done well: the date, place and a Get tickets button on every page, an agenda and speaker list built from structured content, a one-tap hand-off to your ticketing platform, the total price including mandatory fees, accessible seating described in full, Event structured data, and a plan for the day itself and the archive afterwards.

To start quickly, Goal costs $59 on Framer or Webflow and Camp starts at $39 in HTML, and the free Framer templates cost nothing with a Waida account if you want a simpler base. If you would rather hand the setup over, our template customisation service adapts a template for you for $499, with delivery in seven days.