What should a wedding website include?
Your names, the date and time, the venue with a map, the schedule for the day, an RSVP form with a reply deadline, and what guests need to plan: travel, accommodation, dress code and gifts. Add an add-to-calendar button and keep everything on one page that works on a phone.
The basics, at the top
Most guests open the link once to save the date and come back two or three times before the day. Put what they need every time at the very top:
- Your names, as guests know you.
- The date and the start time. If the ceremony and the party are at different times, give both.
- The place, with the venue’s name, the town and a link to a map.
- An add-to-calendar button, so the date ends up in their calendar instead of a screenshot.
The schedule for the day
A simple timeline saves you a lot of messages: when to arrive, when the ceremony starts, when dinner is served and roughly when the evening ends. Guests with children, long drives or a last train home plan around it.
Keep it to the moments guests need to know. A minute-by-minute run sheet is for your coordinator, not the website.
The RSVP
This is the part that saves you the most work. A reply form on the page collects the answers in one place, instead of in texts, emails and comments at family dinners. Ask only what you’ll use:
- Whether they’re coming, and the names of everyone in their party
- Dietary needs and allergies
- Anything you need for planning, such as a song request or whether they need a seat on the bus
Always give a reply deadline, and pick it by working back from the date your caterer needs final numbers. We’ve written more about collecting RSVPs online.
Getting there and staying over
- Directions and parking, or the nearest station and how to get from there.
- Transport you’ve arranged, such as a bus from the ceremony to the party, with times.
- Where to stay, with a few options and any discount code you’ve agreed with a hotel.
- For a destination wedding: the nearest airport, when to book and anything about the local area guests should know.
Dress code, gifts and children
These are the questions guests feel awkward asking, so answer them before they have to:
- Dress code, in plain words. “Garden party: the ceremony is on grass” helps more than “smart casual”.
- Gifts, or a gift list, or a note that you’d rather have none.
- Children: whether they’re invited. Saying it clearly on the page saves an uncomfortable conversation later.
What you can leave out
A wedding website doesn’t need a long love story, a gallery of every engagement photo or a page about each member of the wedding party. One or two photos and a few warm sentences are plenty. Everything else pushes the practical details further down the page, and that’s what guests come back for.
Make it work on a phone
Nearly everyone opens the link from a message, on their phone. Test the page there before you share it: the text should be readable without zooming, the map link should open the phone’s map app, and the RSVP form should be easy to fill in with a thumb. If you’d like a page made for you, see our event websites.
Questions we get
When should the wedding website go live?
When you send the save-the-dates or the invitations, so the link can go with them. Guests who need to book travel will look for it straight away.
Should the wedding website be public?
It can be public but unlisted: only people with the link find it. Leave out anything you wouldn’t want a stranger to see, such as home addresses, and add a password only if the details are sensitive.
Do we need a separate page for each section?
No. For most weddings one page is easier for guests: they scroll once and find everything, without menus to tap through on a phone.
Want help with this?
We make interactive one-page websites for weddings, birthdays, christenings and memorials: 300€ fixed, with the domain and hosting included. See Event websites, or tell us what you’re working on and we’ll reply within one business day.