Wedding Website With a Personal Link for Each Guest

A per-guest wedding link is a separate URL for every name on your list, and it opens with that guest already identified — their name on the invitation, their RSVP form already knowing who is answering. Nobody types their name into a search box, picks themselves out of a list, or replies as the wrong person. You send a different link to each guest, and each one lands somewhere that was addressed to them.

Last updated: August 2026

Most wedding websites give you one link for everybody. That single URL is the reason a chunk of your list never replies, and the reason the replies you do get are hard to trust.

What is a per-guest wedding invitation link?

It is one link per invited guest or household, generated from your guest list, carrying that guest's identity in the URL. When Sara opens hers, the page greets Sara, and the RSVP form submits as Sara — she taps yes or no and she is done. When her uncle opens his, he sees his own name. Neither of them has to prove who they are, and neither can accidentally answer for the other.

The alternative — the shared link — asks every guest to do an identification step before they can be useful to you: find yourself, spell yourself the way the couple spelled you, and hope there is only one of you.

Why does one shared link lose replies?

Because it puts work between the guest and the reply, and the guest is on a phone, in a queue, half-reading.

• The name-search problem. A shared RSVP asks the guest to find their entry. If the couple wrote "Mohammed Al-Sayed" and he types "Mohamed", he isn't there. He assumes it's broken and closes it.
• The duplicate problem. Two cousins share a name. One of them RSVPs, and you cannot tell which.
• The household problem. A shared form usually asks "how many of you are coming?" — a question people answer optimistically and inconsistently. A per-guest link already knows the household it went to.
• The forwarding problem. One link travels. It gets pasted into a family group chat, and now people you did not invite have the address, the time, and the RSVP form. See how to stop uninvited guests from crashing your wedding.

None of these are guest laziness. They are all the same design flaw: a page that does not know who is looking at it.

How do you set up a wedding website with a link per guest?

1. Build the invitation first. Pick a design, add your names, date, story and schedule. On our wedding invitation and RSVP page this part is free and needs no account — you see the finished thing at full size before paying anything.
2. Add your guest list. Type or paste the names. Households can be one entry ("The Haddad family") or individuals, whichever matches how you actually invite.
3. Each name gets its own link automatically. You do not build them one at a time; the list generates them.
4. Send each link to that guest. WhatsApp, SMS, email — one guest, one link. Sending on WhatsApp keeps the live preview intact.
5. Watch the replies land against names. Not a count — names. You always know exactly who has not answered yet, which is what makes chasing the non-repliers a short, specific job instead of a mass reminder to everyone.

What does a per-guest link change about the RSVP itself?

It makes every answer attributable, which is what turns a pile of replies into a number you can act on.

Because the page knows who is replying, it can ask the questions a caterer and a venue actually need, and attach each answer to a person: meal choice, dietary notes, whether the plus-one is coming, a song request. You end up with a list that reads "Nadia — attending, vegetarian, no plus-one" rather than "1 attending". That is the difference between a headcount and a number your caterer can cook to.

It also makes the door work. Every confirmed guest can be issued a QR entry pass tied to their name, scanned from an ordinary phone on the night — see wedding entry passes and QR check-in.

Per-guest links vs. one shared link

	Per-guest link	One shared link
What the guest does first	Taps yes or no	Finds themselves in a list
Spelling mismatches	Impossible — the link carries the identity	Common, and silent
Two guests with the same name	Distinct links, distinct replies	Ambiguous
Knowing who hasn't replied	A list of names	A count, and guesswork
Meal and dietary answers	Attached to the person who gave them	Attached to a row someone typed
If the link gets forwarded	Only that guest's invitation travels	Your whole RSVP form travels
Chasing replies	Message the specific names	Mass reminder to everyone, including people who already replied

Does a per-guest link cost more per guest?

It should not, and here it does not. The whole guest list is covered by one payment — $69, once, for the invitation, the website, unlimited RSVP replies, entry passes and 18 months online — and adding another name never adds another charge. A 40-guest wedding and an 800-guest wedding pay the same total.

That is worth checking wherever you build, because per-guest links are exactly the feature some tools use to justify per-guest pricing. If you are comparing, here is the per-guest pricing question in full.

Frequently asked questions

Do guests need an app or an account to open their link? No. It opens in whatever browser is already on their phone, like any web page. There is nothing to install and nothing to sign into — which matters most for older relatives, who are the guests most likely to abandon anything that asks them to register.

What if I add a guest after I've already sent the invitations? Add the name and that guest gets their own link, same as the rest. Nothing needs re-sending to anyone else, and there is no additional cost for the new name.

Can one link cover a whole household? Yes. Make the household a single entry and one link covers them, with the RSVP asking how many of the named people are coming. Use individual entries when you want individual answers — for a seated dinner with per-person meal choices, individual is usually what you want.

What happens if a guest forwards their link to someone else? They forward their own invitation, not your guest list and not a blank RSVP form. The reply still arrives attributed to the guest the link belongs to, so a forwarded link cannot quietly add a stranger to your headcount.

Can I still share one general link as well? Yes, and it is often the right thing for the wide announcement — a link in a family group chat that shows the invitation without an RSVP attached. Use per-guest links for the people you need an answer from.

Start with the guest list

If you already have your list, the per-guest links are the easy part — they come out of it. Build the invitation free and see the whole thing at full size before you pay, on the wedding invitation and RSVP page: one price for unlimited guests, a link with each guest's own name on it, and replies that arrive as names rather than numbers.