how do i make a website for an event that ends on time?

web · 2026-09-16 · 3 min

an event site has a deadline and an expiry date, which makes it a different job from a business site. visitors need five things fast: what it is, when, where, how much, and how to get in. everything else is decoration that can wait until the basics are true.

the site can live on a subdomain or a path of your main site, and it should be built to be thrown away or archived. a wedding, a workshop, a festival: same shape.

the five things, in order

the first screen carries name, date, city, and one button — tickets, registration, or the calendar link. do not make people scroll to find out when it happens.

then the programme, the practical information (address, parking, accessibility, what to bring), and the people behind it. a map embed is useful; a stock photo of a crowd is not.

tickets: if you sell them, use a service that handles the payment and the confirmation email (eventbrite, dice, a stripe payment link for small events). if it is free, a form with a confirmation email is enough. either way, say clearly what happens after someone registers.

the technical bits

add event schema to the page: name, start date, location, price, availability. it is structured data, not magic, but it helps search results show the date instead of a generic snippet.

make the date visible in the title and in the text. "workshop di ceramica, 14 marzo" beats "workshop di ceramica" for anyone searching in march.

put the event on a calendar link (google calendar, ics file) next to the registration button. people forget, and a reminder is the cheapest attendance tool you have.

after the event

do not leave the page live with last year's date. either archive it with a line saying it is over, or redirect it to the next edition. an outdated event page is worse than no page: it shows up in search and sends people to a dead registration.

keep the domain or subdomain for at least a year if you plan another edition. redirects are easier than rebuilding trust with google.

faq

should the event have its own domain?

only if it is an annual thing with its own identity. for one edition, a subdomain or a page on your site is cheaper and inherits your existing traffic.

how do i stop spam registrations?

a honeypot, a rate limit, and a confirmation email that requires a click. captchas help, but they also lose real people on a phone.

what do i do with the site after?

archive it with a clear "this edition is over" note and a link to the next one, or redirect it. never leave the old date and an active form.