For couples · Guests
What to Put on a Wedding Website, and When to Publish It
Publish only the details guests need to make a decision, using a clear information plan that changes as the wedding approaches.
On this page
Publish information when it helps a guest act
A wedding website should answer the next practical question a guest has: should I reserve the date, how do I get there, what time should I arrive, how do I respond, and whom should I contact? Start with confirmed essentials and add detail as it becomes reliable. A long FAQ is less useful than a short page with current answers.
| Guest decision | Publish when | Include | Keep private or verify first |
|---|---|---|---|
| Reserve the date | date and place are stable | date, city/area, travel lead time | unconfirmed venue details |
| Book travel or rooms | travel plan is ready | airports/stations, transport notes, room block terms if applicable | advice that implies visas or legal entry rules |
| Attend the day | timeline is confirmed enough | arrival time, locations, dress guidance, accessibility contact | internal supplier schedule |
| Respond | RSVP process is live | deadline, named response route, dietary/plus-one instructions | a deadline not based on your contracts |
| Prepare for changes | one contact route is agreed | update date and urgent-contact approach | personal contact details you do not want public |
Write in layers
Give travelling guests early notice without pretending that every operational detail is settled. A save-the-date is an early notice; it is not your final RSVP system. Keep the response deadline tied to the backwards plan in your RSVP deadline worksheet.
For a destination or cross-border event, state what you know about the event itself and direct guests to official authorities for passport, visa, health or local-entry requirements. Do not turn a wedding website into unofficial travel or legal advice.
Worked example
For a fictional celebration in Porto on 7 September 2027, the first page says: “Please reserve 7 September; the celebration is in Porto.” Once the venue is signed, it adds the neighbourhood, a recommended arrival window and the couple’s accessibility contact. When catering needs the final count, it adds the RSVP deadline and dietary prompt. The page never publishes a pickup time until transport is actually booked.
Run a final guest-information check
Read the page as someone who has never visited the city. Can they identify the date, place, next action and latest update? Then compare it with the invitation and guest list: names, RSVP route and deadline should agree.
Cakd’s public wedding website and guest records can keep guest-facing information and responses connected. Keep private planning notes, vendor contacts and internal decisions out of the public page. For the invitation list behind it, use a defined guest and plus-one policy.