Wedding websites
What to Put on Your Wedding Website: A Complete Checklist
July 14, 20268 min read
Your wedding website should answer every question a guest might have before the day: who, when, where, what to wear, where to stay, and how to RSVP. The essential sections are a home page with the key facts, a schedule, travel and accommodations, an RSVP, a registry, and an FAQ — with optional Our Story, gallery, and dress-code pages. Put the information guests actually need to show up on time and prepared, and leave off anything private or logistical you would not want a stranger to read.
The essential pages every wedding website needs
A good wedding website is organized so guests can find any answer in a couple of taps. These are the pages that do the real work — start here before adding anything decorative.
- Home. Your names, the date, the city, and a clear RSVP button. This is the one screen everyone sees first.
- Schedule. What is happening, when, and where — especially important for multi-day weddings.
- Travel & stay. Airports, hotel blocks, directions, and parking so out-of-town guests can plan.
- RSVP. A simple way to reply, ideally with name lookup and no login required.
- Registry. Links to your registries or a note about gifts, so guests do not have to ask.
- FAQ. The recurring questions — dress code, kids, plus-ones, timing — answered once, publicly.
Home page: the first thing guests see
The home page has one job: confirm they are in the right place and give them the headline facts. Put your names, the wedding date, and the city front and center, with a prominent RSVP button. A single photo and a warm one-liner ("We're getting married — and we can't wait to celebrate with you") is plenty.
Resist the urge to cram everything here. The home page is a signpost, not the whole story — every other detail lives on its own page, one tap away. On Duva the home page auto-pulls your names and date so it is correct from the moment you publish, and the RSVP button is wired in by default.
Schedule and itinerary (especially for multi-event weddings)
The schedule tells guests exactly where to be and when. For a single-day wedding, list the ceremony and reception times and venues. For a multi-day or Indian wedding, give each event its own entry — mehndi, sangeet, haldi, ceremony, reception — with the date, start time, venue, and a per-event dress code.
Include an add-to-calendar link for each event so guests can save it in one tap, and a map link to every venue. The most common day-of question is simply "what time and where?" — a clear schedule answers it before anyone has to ask. Duva builds the schedule automatically from the ceremonies you enter, including per-event dress codes and add-to-calendar buttons, so it always matches your invitation.
Travel and accommodations
Out-of-town and international guests need this page more than any other. Cover the nearest airport(s), any hotel room blocks with the booking code and cut-off date, rough driving times, parking or shuttle details, and whether transportation is provided between venues.
If it is a destination wedding, go further: passport and visa reminders, the best time to book flights, local weather in that season, and a currency or SIM-card tip. Guests who feel looked after travel with far less stress — and you field far fewer one-off questions in the weeks before the wedding.
RSVP
The RSVP is the section your website exists to power, so make it effortless. Guests should be able to reply without creating an account or downloading anything — name lookup that matches them to your guest list is the smoothest path. Collect the number attending, meal choices if you need them, and, for multi-day weddings, which events each guest will join.
Tie the RSVP to your guest list so responses update your counts automatically instead of landing in a spreadsheet you maintain by hand. On Duva, guests RSVP by name lookup on the site or by verified text, party and household RSVPs are supported, and each ceremony keeps its own independent headcount.
Registry, FAQ, and Our Story
Link your registries rather than listing gift details on the invitation — guests will look for them on the website. If you would prefer contributions to a honeymoon or a cash fund, a short, gracious note here handles it without awkwardness.
The FAQ page quietly saves you dozens of texts. Answer the questions guests always ask: What is the dress code? Are kids welcome? Can I bring a plus-one? Is there parking? What happens if it rains? Is the ceremony indoors? An Our Story page (how you met, the proposal, your wedding-party bios) is a lovely optional extra — guests enjoy it, but it never replaces the practical pages above.
Dress code and contact details
Guests genuinely worry about getting the dress code wrong, so be specific. "Black tie," "cocktail," "festive Indian formal," or "garden-party — think linen and florals" all give people something concrete to work with. For multi-event weddings, list the dress code per event, since the mehndi and the reception rarely call for the same outfit.
Add a contact — a wedding email, or a point person from the wedding party — for questions the FAQ does not cover, rather than publishing your own phone number for hundreds of guests. A single "Questions? Reach us at hello@…" line keeps you reachable without opening the floodgates.
What NOT to put on your wedding website
A wedding website is semi-public, so leave off anything you would not want a stranger or an uninvited acquaintance to read. Do not post your home address, your guests' phone numbers or emails, or precise financial details of a cash fund.
Keep gift and registry talk gracious rather than demanding — never "no boxed gifts" phrasing or dollar suggestions. Skip inside jokes that only half the guests will understand, walls of text no one reads, and drama about who did or did not make the guest list. If a detail is sensitive or only relevant to a few people, send it to them directly instead of publishing it. Everything on the site should help a guest show up on time, dressed right, and ready to celebrate.
Frequently asked questions
What are the must-have pages on a wedding website?
Home (names, date, city, RSVP button), Schedule, Travel and accommodations, RSVP, Registry, and an FAQ. Optional additions include Our Story, a photo gallery, and a dedicated dress-code page. Those six essentials answer nearly every question a guest will have.
What information do guests actually need on a wedding website?
The practical logistics: exact dates, times, and venues; how to RSVP; where to stay and how to get there; the dress code; and gift or registry details. For multi-day weddings, they also need to know which events they are invited to and the dress code for each.
What should you not put on a wedding website?
Leave off your home address, guests' contact details, and precise cash-fund figures, since the site is semi-public. Avoid demanding gift wording, inside jokes, and long blocks of text. Send anything sensitive or guest-specific privately instead of posting it publicly.
How do you handle a multi-event schedule on a wedding website?
Give each event its own entry with date, time, venue, and dress code, and only show each guest the events they are invited to. Add an add-to-calendar link and a map for every event. Tools like Duva build this schedule automatically from the ceremonies you enter.
Do you need a wedding website if you send paper invitations?
Yes — a website holds the details a card cannot: full schedule, travel and hotel info, an FAQ, and a live RSVP. Many couples put a short URL on the paper invitation and let the website carry everything else, so guests always have the current information.