A Real Wedding Website Example: 170 Guests, 100% RSVP Rate

Search for wedding website examples and you'll mostly get template galleries: screenshots of layouts filled with stock photos of models, sample names, and paragraphs of placeholder text about a couple who doesn't exist. They tell you what a design looks like with nothing in it, which is the least useful version of the question.

So here's a real one. It's my own wedding website, it had a hundred and seventy guests on it, and every single one of them RSVP'd.

Replied, to be clear, not attended. A good number said no, and that's normal. Nobody expects a full house, and attendance isn't really the number you control.

Knowing where all hundred and seventy stood is the part that matters, because silence tells you nothing. A guest who hasn't answered might be undecided, or might be waiting to hear about flights, or might never have received the invitation at all, and from your side those look identical. You end up wondering whether the email landed in spam, whether the link worked, whether you have the right address for someone you haven't spoken to in two years.

A no is information. Silence is a question you carry around until the caterer wants final numbers. Getting to zero unanswered meant there was nothing left to wonder about.

Have a look at it here. The guestbook entries are real messages from real guests. Nothing on it is sample text.

Why the response rate is the interesting number

A hundred percent is unusual. The normal experience of collecting RSVPs is chasing: a first wave of replies within a week, a long quiet middle, then a fortnight of individually messaging people you love while trying not to sound annoyed. Caterers want final numbers, and you're guessing.

Being honest about it, the design is not the only reason we heard back from everyone. A guest list that is mostly close family and friends replies better than one padded with obligations, and some of it was down to people we would have chased anyway. If your list is four hundred people including colleagues and distant relatives, don't expect the same result from any website.

But a meaningful part of it was removing reasons not to reply, and those parts generalise.

What actually moved the number

No account, no app. Guests tap the link and they're in. Every account you ask someone to create is a place they stop, and the older half of your guest list stops there permanently. This sounds obvious and a surprising number of platforms don't do it.

The RSVP is short. Are you coming, who with, what do you eat, anything we should know. Every additional question costs you completions, and most of the extra questions people add are things they never end up using. There's a longer version of this in what to include on your RSVP form.

It was built for a phone first. Nearly everyone opened it on a phone, plenty of them one-handed. Big tap targets, no pinching, no tiny date pickers. The RSVP flow got rewritten more than once, and the changes that mattered were unglamorous: fewer fields per screen, bigger buttons, clearer labels.

Invite codes instead of a shared password. Each guest gets a code that already knows who they are, so they aren't typing their own name and hoping it matches the list. It also means the site can stay private without a password everyone forgets. See password or invite code.

A reason to come back. The guestbook is the underrated part. People replied, then returned later to read what others had written, and some added photos. A site guests revisit is a site they engage with, and it turns the RSVP from a chore into the entrance to something.

Knowing exactly who hadn't replied

The other half of a hundred percent isn't guests replying, it's you knowing precisely who hasn't. Chasing five named people is a ten minute job. Chasing "some of the hundred and seventy" is a spreadsheet, an evening, and a decent chance of messaging someone who already replied.

Responses came in and got matched against the guest list automatically, with anything ambiguous flagged for me to look at rather than silently guessed. A submission from a nickname, or someone replying for their whole family, or a name spelled two different ways, all of which happen constantly, surfaced instead of quietly creating a duplicate.

So the outstanding list was always accurate and always current. I could see at a glance who hadn't answered and nudge exactly those people, which is what closes the last twenty percent. The design got guests to reply easily; the tracking is what made the follow up small enough to actually do. More on that in wedding RSVP tracking and what to do when guests aren't RSVPing.

What's actually on the site

Section by section, and roughly in the order guests need them.

The hero answers who, when and where in about two seconds. That's the whole job. Most guests land, read it, and leave satisfied.

The details carry venue, timings, dress code and anything practical. Dress code is the single most asked question at every wedding, so it goes here and not buried in an FAQ. Wording examples here.

The story and wedding party are the parts guests enjoy but nobody came for. They belong below the practical stuff. Nice to have, never first.

The RSVP is the point of the whole thing.

The guestbook and gallery are what the site becomes after the wedding, and they're the reason it's worth keeping live afterwards rather than taking down the week after.

The FAQ catches the rest: parking, kids, gifts, when to arrive. Every question you answer here is a text message you don't get. Examples here.

What I'd tell you to copy

Put the practical details above the romance. Cut your RSVP form until it hurts, then check whether you'd actually use the fields that are left. Open the finished thing on the oldest phone in your family and try to RSVP on it without helping. Give guests a reason to come back after they've replied, because a site they visit once is a form, not a website. And whatever you build on, make sure you can answer "who hasn't replied yet" in one glance, because you will ask that question every week for two months.

None of that requires our platform. It's just what worked, on a real wedding, with a real guest list.

If you want to build your own

Always & Forever exists because I built that site for my own wedding first and then rebuilt it properly so other couples could use it. You can set one up and preview the whole thing before paying anything, which means you can see your own names and photos on it before deciding whether it's for you.

If you'd rather start with the process than the product, how to make a wedding website walks through the whole thing step by step, including the options that aren't us.