What to Put on a Wedding Website: Sections, Ideas and Wording

Put on your wedding website the answers to every question a guest might otherwise text you: the date, times and addresses, how to get there and where to sleep, the dress code, whether kids and plus-ones are coming, the registry and how to RSVP. That's the whole brief. Picture an aunt in a supermarket queue, phone in one hand, trying to remember what time the ceremony starts. If she finds it in ten seconds, your site works.

Start with the questions guests actually ask

Before you write a word, think about the messages you'd get in the months before the wedding. Each one is a section waiting to happen.

If you only have an evening, build those and publish. Your story, a gallery, wedding party bios: lovely, and not one guest will skip the wedding because they're missing.

Writing each page

Home page

Names, date, place, one welcoming line. A countdown or a favorite photo if you like.

Our story

Two or three short paragraphs on how you met and how the proposal went. People who only know one of you read this closely, and it gives strangers at the same table an easy opener. Warm, not memoir. If it runs past two screens on a phone, cut it.

Schedule

Every event guests are invited to, with time, place and dress code. Give the real start time of the ceremony, then a separate arrival time. Guests read "4:00" as four o'clock, not "four-ish".

Only list events that everyone who can see the site is invited to. If the rehearsal dinner is close family only, tell those people yourself. A public schedule with an invite-only line on it is a hurt feeling waiting to happen.

Travel and accommodation

The most-visited page on any wedding site with out-of-town guests, so give it some care:

• Nearest airport or train station, and roughly how long the drive is.
• Parking at the venue, or a plain "please take a taxi or rideshare".
• Shuttle pickup times and places, if you're running one.
• Hotels holding a room block, with the booking code and the date the block releases.
• One or two cheaper places nearby, for the cousins on a budget.
• For a destination wedding: passport, entry or visa notes linked to the official government page, and a nudge on when to book flights.

Things to do

Traveling guests appreciate a short list: a couple of restaurants, a coffee spot, one or two sights. Make it yours. "The bar where we had our first date" beats anything a tourist board would write.

RSVP

The reply-by date should be the most visible thing on the page. If guests can reply on the site, print that on the invitation too. On a free BrideSpark wedding website, guests type their email under RSVP and open their own household's reply; meals, allergies and plus-ones land in your guest list without you copying anything over. Only people on that list can reply, so a forwarded link won't quietly add strangers to your headcount. For wording and how to pick the deadline, see our guide to wedding RSVP wording and deadlines.

Registry and funds

Link each registry and any honeymoon or house fund. Traditional etiquette keeps registry details off the invitation, since printing them there can feel like a gift is the price of a seat. The website is a different place. People go there looking for exactly this, so you're answering a question, not making a request.

Registry wording you can borrow

Short, grateful, no pressure. Adapt freely:

For a honeymoon or cash fund:

For a "no gifts" wedding:

What to avoid: anything that reads like an instruction ("Cash only", "We prefer money"). A sentence on why you'd like a fund is what turns it from a transaction into a story.

The FAQ page: awkward things, said once

This is where you say the slightly uncomfortable things one time, kindly, so nobody has to ask you at a birthday party. Take the ones that apply and skip the rest.

Dress and comfort

• What should I wear? Name the dress code, then translate it: "Cocktail attire, so suits or dresses. The ceremony is on grass, so you may want block heels."
• Is it indoors or outdoors? Add the plan if it rains.
• Is the venue accessible? Step-free access, seating for older guests, somewhere quiet to sit.

Who's invited

• Can I bring a plus-one? "We've kept our guest list small, so we can only host the guests named on your invitation. Your RSVP will show how many seats we've saved for you."
• Are kids welcome? "We love your little ones, but our wedding is adults-only." Or: "Kids are very welcome. There'll be a kids' table and activities."

Logistics

• What time should I arrive? Twenty minutes before the ceremony is a sensible default to state.
• Is there parking? Or the nearest bus, tram or train.
• Will there be food for dietary needs? "Yes. Tell us on your RSVP and we'll pass it to the caterer."
• Who can I call on the day? A wedding party member's number. Not yours.
• When is the RSVP deadline? Yes, again. On a wedding site, repeating yourself is good manners.

Photos

• Can I take photos during the ceremony? If it's unplugged, this is where you say so.
• Can I post on social media? If you'd rather people waited, or used a hashtag, spell it out.

Build it in three passes

You don't need a finished site on day one. Most couples know the venue long before they know the shuttle times, so publish in layers and tell guests when something new goes up.

Pass one, with the save-the-dates. Go live roughly six to eight months before the wedding, or eight to twelve for a destination wedding or a guest list that mostly has to travel. Date, location, travel and hotel blocks. Print the address on the save-the-date so people can start booking.

Pass two, before the invitations. Two to three months out, add the schedule, dress code, FAQ and registry. When invitations go out, open the RSVP and state the deadline. The Emily Post planning timeline has invitations in the mail six to eight weeks before the wedding, which is when your RSVP page starts doing real work.

Pass three, the week before and after. Final timings, a weather note and the day-of contact go up the week before. Afterwards, add a thank-you and a photo gallery, and send the link one last time.

What to leave off (and why)

A wedding website tells anyone who reads it exactly when you'll be at a venue, which also means when your home is likely to be empty. It can hand a scammer enough detail to sound convincing, too. None of the precautions cost anything:

• Add a password if the site has detailed travel plans, the full schedule or family information. Guests type it once.
• Never post your home address, or your honeymoon dates and destination.
• Keep guests' details off it: no guest list, no children's full names, no phone numbers beyond one day-of contact who has agreed to it.
• Skip full birthdates and anything else that could help someone guess a security question.
• Send the link directly to guests rather than posting it publicly on social media.
• Warn guests about scams. Say you will never ask for payment by text or email, and that the only registry links are the ones on your site.
• Pick a site that's hidden from search engines, so googling your names doesn't turn it up.

We built BrideSpark wedding websites to stay out of search engines by default, with an optional password on top, so only people with the link (and the password, if you set one) can open them.

Extras guests remember

Not required, but these are the bits people mention at the reception:

• "How we met", told twice, once by each of you. The versions rarely match, which is the fun of it.
• A song request on the RSVP, so the dance floor is partly built by the people on it.
• A local map with the venue, the hotels and your favorite bar pinned.
• Meet the wedding party, one line each on how you know them.
• What you're most excited about: the food, the band, the view from the terrace.
• A design that matches your save-the-dates and invitations, so the whole set looks like it belongs together.
• A photo gallery after the wedding, so guests find and download the pictures in one place instead of chasing each other for them.

One note on voice: a formal invitation can sit happily next to a warmer website, but the two shouldn't sound like different weddings.

The phone test

Before you send the link, hand your phone (or theirs) to a friend who hasn't seen the site and ask them to find three things: the ceremony time, the hotel code and the RSVP deadline. Then check the details only you can:

• Names spelled correctly, dates and times checked twice.
• Every address opens the right place in a map app.
• Hotel codes tested, release dates correct.
• RSVP deadline matches the invitation.
• Registry links open on a phone.
• Password set if you want one, and printed on the invitation or sent with the link.

If your friend comes back with no questions, you're done. For what comes next, see how to make a wedding guest list and the wedding checklist.

Frequently asked questions

When should I make my wedding website live?

Before the save-the-dates go out, around six to eight months before the wedding, and earlier for a destination wedding. Launch with the essentials and add the schedule, FAQ and RSVP later.

Should I put the registry on the wedding website?

Yes. The website is the accepted home for registry links. Leave them off the invitation itself and keep the wording short and grateful.

Should a wedding website have a password?

It's worth it if the site includes detailed travel plans, a full schedule or family details. Share the password along with the link, on the invitation or in your message to guests.

What should I not put on a wedding website?

Your home address, your honeymoon dates, guests' personal details, full birthdates, and any event that not every guest is invited to.

Do I put the wedding website on the invitation?

Yes. It usually goes on the save-the-date and on the invitation or a separate details card, especially if guests RSVP online.

Is it OK to mention adults-only or no plus-ones on the website?

Yes, and the FAQ is the best place for it. One clear, kind sentence saves you a lot of one-on-one conversations.