A wedding website should include your names and date, ceremony and reception times with addresses and maps, an RSVP form with a clear deadline, the dress code, travel and accommodation notes, and a short FAQ. Nice-to-haves include your story, a schedule, registry links and a photo gallery. Leave off home addresses and keep the page passcode-protected.
Your wedding website has one job: to answer your guests’ questions before they have to ask you. Work through the sections below in order. The essentials come first, the extras after, and the last section covers what to keep off the page entirely.
What are the essentials every wedding website needs?
These are the sections guests look for first. If your page has nothing else, it should have these.
- Your names and the date, right at the top, so guests know they are in the right place.
- The ceremony: the church or venue name, full address, start time and a map with directions.
- The reception: venue, address, start time and a map, even if it is a short walk from the ceremony.
- An RSVP form with a clear reply-by date (see how to set your RSVP deadline).
- The dress code, in plain words, with a note on footwear if the venue has grass, sand or cobbles.
- A short FAQ covering children, parking, plus-ones and what time the evening ends.
What should go in the schedule and venue sections?
A simple timeline stops the same five questions arriving on your phone. List each part of the day with a time and a place: ceremony, drinks, dinner, first dance, cake, last dance. If there is a gap between the church and the reception, say so, and suggest where guests might wait.
For each venue, give the full address and a map link that opens in the guest’s own maps app. Add the practical details people forget: where to park, whether the venue is step-free, and whether taxis are easy to find late at night. An add-to-calendar button helps guests save the date with the right address attached.
How should the RSVP section work?
Ask only what you need. Every extra question makes it a little less likely that someone finishes the form. For most weddings that means: attending or not, the guest’s full name, and an email or phone number in case you need to follow up.
- Plus-ones: say clearly whether a guest may bring someone, and ask for that person’s name.
- Meal choices: only if your caterer needs them in advance, with dietary needs and allergies as a separate free-text box.
- Children: if they are invited, ask how many and their ages, as venues often price children’s meals differently.
- A message box: optional, but couples tend to love reading them.
What are the nice-to-haves worth adding?
Once the essentials are in place, these sections make the page feel personal and save you more questions.
- Your story: a few paragraphs about how you met. Keep it short; guests read it on their phones.
- Travel and accommodation: nearby hotels, the closest airport, and whether you have arranged transport.
- Registry or honeymoon fund: a short, gracious note with the links, rather than a wish list in your invitation.
- A photo gallery where guests can share their pictures after the day (see collecting guest photos with a QR code).
- A countdown, which guests enjoy checking more than you might expect.
- Local tips: a favourite restaurant, a beach, or what to do on the morning after.
- Traditions: a short explanation of customs your guests may not know (see Greek and Cypriot wedding traditions).
If your guests speak different languages, a page that switches between them is worth more than any decorative extra. A guest who can read the schedule in their own language is a guest who arrives on time.
What should you leave off a wedding website for privacy?
A wedding website is easy to forward, so assume it may travel further than you intend. A few things are better shared privately or not at all.
- Your home address, and your parents’ home addresses. If guests need to send something, ask them to message you.
- Details that announce when your home will be empty, such as honeymoon dates and destinations.
- Full guest lists, seating plans or anything naming other guests.
- Phone numbers for anyone who hasn’t agreed to be contacted by every guest.
- Photos of children other than your own, unless their parents have said yes.
The simplest protection is a passcode. A page that only opens with the code printed on your invitation keeps casual browsers and search engines out, while guests get in with one tap. Ever Yours pages work this way: guests need no account, just the private link and the passcode from their invitation.
How should you order the sections on the page?
Follow the order of your guests’ questions, not the order of your day. Most people open the page to check one thing: when, where, or how to reply. Put those near the top.
- Names, date and a short welcome.
- Ceremony and reception, with times and maps.
- RSVP.
- Schedule.
- Dress code.
- Travel and accommodation.
- Registry, FAQ and everything else.
When should your wedding website go live?
Ideally before your invitations go out, so the link works the moment a guest types it in. Many couples publish a simple version with the save-the-dates and fill in the detail closer to the day. Update the page whenever plans change, and tell guests when you do, as not everyone will check back on their own.
If you would like to see how these sections fit together on a real page, take a look at the demo wedding.
Quick answers
- Should we put our wedding registry on the website?
- Yes, the website is the best place for it. Keep the note short and warm, and link to the registry or fund rather than listing gifts on the page.
- Do we need a separate website for each language?
- No. A single page that guests can switch between languages is easier to keep up to date, as you only change each detail once.
- How long should our wedding website be?
- As short as it can be while still answering the common questions. Guests mostly read on their phones, so short sections with clear headings work best.