FeaturesCommunityGuidesUse casesCompareToolsBlogPricing
Orlume logo

What to put on a wedding website

What to put on a wedding website, section by section: date and venue, schedule, travel, dress code, RSVP, registry and FAQ, and what to leave off.

The short answer

Put what guests need to show up on time and dressed right: your names, the date and venue on the first screen, the schedule of every event, travel and hotel details, dress code, the RSVP with its deadline, registry links and an FAQ. Leave off anything you would not want a stranger to know, such as your home address or when your house is empty.

  • Date, place and the RSVP button belong on the first screen.
  • Every event needs a time, an address, a dress code and who is invited.
  • An FAQ cuts the texts you get in the final weeks.
  • Leave off home addresses, travel dates and honeymoon details.

01The essentials

Guests visit a wedding site with practical questions. Answer them in the order people ask, and keep each answer short enough to read standing in a hotel lobby.

What guests look for, and where to put it
SectionWhat to includeWhy it matters
HomeNames, date, city, RSVP buttonThe one screen everyone sees
ScheduleEach event, start time, address, dress codeStops guests arriving at the wrong time or place
TravelAirports, hotel blocks, booking codes, deadlines, parkingHotel blocks fill up and expire
RSVPDeadline, attendance per event, meals, dietary needsCaterers need final numbers
RegistryLinks, or a note that you do not want giftsSaves awkward questions
FAQKids, plus-ones, dress code, photos, weatherAnswers the texts before they come

02Nice to have

These are optional, and guests skim them, but they make a site feel like yours rather than a template.

  • Our story: how you met, in a few short paragraphs.
  • Wedding party: names and a line about each person.
  • Things to do: restaurants and sights for guests who travel.
  • Photos: a few engagement photos, not an album.
  • After the wedding: a link to shared photos, if you collect them.

03What to leave off

A wedding site is often public, and your names make it easy to find. Hacker News readers have built tools that guess wedding site addresses from common first-name pairs, which shows how findable the default addresses are. Keep the site to what guests need and use a password for anything sensitive; whether a wedding website should be private explains the options.

  • Your home address or where you are getting ready.
  • Dates you are away on honeymoon, which tell people when your home is empty.
  • Bank details for cash gifts outside a registry provider.
  • Guest lists, or anything that shows who is or is not invited.

04How to word it

Write the way you would text a friend: plain and specific. "Cocktail attire: suits and dresses; the lawn is grass, so skip stilettos" beats "Dress to impress". Put deadlines in bold or in the first line of their section. Give times in the local time zone of the wedding, which matters when guests fly in.

Design matters less than clarity, but a consistent font and palette help the site match your invitations. Wedding color palettes and the best fonts for websites help, and two fonts are plenty: a serif for names and headings, a plain sans-serif for details.

05A page order that works on a phone

Most guests open the site from a text message, so design for a phone first. On a small screen, every section is a scroll away from the RSVP button, which is why it should appear at the top and again at the bottom.

  1. 1First screenNames, date, city, one photo, RSVP button.
  2. 2ScheduleEvents in time order, each with a map link that opens the phone's map app.
  3. 3Travel and stayHotel blocks first, because they have deadlines; then airports, parking and transport.
  4. 4FAQGrouped by topic, most-asked first.
  5. 5Registry and RSVPThe registry link, then the RSVP button again.

What people who tried it say

Couples on Hacker News say guests used the site for directions, schedule and RSVPs, and that some older guests still needed the essentials on paper or explained in person.

Looking for more first-hand opinions? Search Reddit for “what to put on a wedding website”. We link the live threads rather than summarizing them, so you read them in full.

Our take

the best wedding websites are short. If a section does not answer a question a guest would otherwise ask you, cut it.

Where this falls short

This covers what most Western-style weddings put online. Multi-day and destination weddings need more travel detail; some families prefer details by phone or in print for older guests.

Where Orlume fits

Describe your wedding in a sentence or two and Orlume lays out the essentials (date, schedule, travel, FAQ) as a designed page you can publish.

Free to start · No card required · Live in one click

Sources

  1. 1.Free wedding websites · Zola
  2. 2.Just the FAQs · Joy
  3. 3.Wedding website builders compared: Joy, Zola, The Knot and the rest · Paperlust

Orlume logoResearched and written by the Orlume team · Updated October 2026

Questions

People also ask.

More on what to put on a wedding website, answered briefly.

Should I put my registry on my wedding website?

Yes, as a link on its own page or in the menu. It is the expected place for it, rather than the invitation.

Should a wedding website have an our story section?

It is optional. Keep it short; families enjoy it, most guests skim it.

Should I put the hotel block on the wedding website?

Yes, with the booking link or code and the date the block expires.

What should I not put on a wedding website?

Home addresses, honeymoon dates, bank details and anything that shows who is not invited.

What questions go in a wedding website FAQ?

Kids, plus-ones, dress code, parking, weather, photos and gifts. Wedding website FAQ examples has sample wording.

Orlume logoStill stuck? Email us
Orlume logo

Build something that doesn't look AI-made.

Describe the site you want. Watch it get designed, not just generated. Then publish it to its own orlume.site address.

  • Free to start
  • No card required
  • Publish to a live URL
  • You own the code