By Forever Farrah Published 2026-09-17.
What to put on a wedding website, when to launch it, how to handle registry and RSVP pages, and the privacy settings that keep your guests and your home safe.
A wedding website should hold everything guests need to plan: date, times and addresses, the schedule of events, travel and accommodation, dress code, RSVP, and a quiet link to your registry. Launch it before you send save-the-dates, so guests can find details as soon as they know the date, and keep updating it until the wedding. For privacy, use a password or a hard-to-guess address, leave out your home address, and do not advertise when your home will be empty.
The Emily Post Institute's wedding website advice is to have the website ready before you send save-the-dates, and certainly before the invitations. The save-the-date can then point guests to it. For the wider timeline, see when to send save-the-dates and invitations, or use the invitation timeline tool below.
When to send save-the-dates, invitations and RSVP reminders
You do not need every page on day one. Launch with the date, location and travel information, then add the schedule, dress code and RSVP when invitations go out.
| Page | What to include |
|---|---|
| Home | Your names, date, city, and a short welcome |
| Schedule | Each event guests are invited to, with times and addresses |
| Travel and stay | Nearest airports or stations, parking, hotels, any room block and its deadline |
| RSVP | The deadline, meal choices, dietary needs, accessibility needs |
| Dress code | What the dress code means in plain words |
| Registry | A link, kept low-key |
| FAQs | Children, plus-ones, parking, weather, photos during the ceremony |
| Our story | Optional: how you met, kept short |
List only the events every visitor to the site is invited to. Emily Post advises leaving off details, such as the rehearsal dinner, that not all guests are invited to. If some guests are invited to more events than others, send those details privately or use a website that shows each guest only their own events.
An RSVP form on the website saves you chasing paper cards. Ask for the name of each guest, whether they are coming to each event, meal choices and dietary needs, and a clear deadline. See when should wedding RSVPs be due and what to do when wedding guests don't RSVP. Forever Farrah's wedding website and guest list collect RSVPs per event, with meal choices, straight into the guest list you seat from.
State the policy kindly and clearly in the FAQs, then address invitations to match. See wedding plus-one etiquette and child-free wedding etiquette.
Emily Post's registry etiquette says it is fine to link your registry on your wedding website, but not to make it the most prominent feature, and not to put registry information on the invitation itself. A page called "Registry" with a warm line of thanks is enough.
Explain what you mean, not just the label. "Black tie" means different things to different people; see what does black tie mean at a wedding. If you are asking guests to avoid a colour, or the venue has grass or stairs, say so.
A wedding website is public unless you make it private, and it holds your full names, a date and a location.
Guests will check the site in the final week. Update it if times, the venue or the weather plan change, and put the most urgent details at the top of the home page. Send a short message to guests too, since not everyone will look.
Before you send save-the-dates, so the address can go on them. Add the RSVP page and full schedule by the time invitations go out.
Many couples add it to an enclosure card or the save-the-date rather than the main invitation, which is what Emily Post suggests. Either way, make sure every guest can find it.
If you are sharing times, places or travel details, a password is a sensible default. It keeps the information for the people you invited.
Your home address, events that not every guest is invited to, dates your home will be empty, and anything personal you would not want strangers to read.
Loading Forever Farrah…