July 13, 2026

English

DeutschFrançaisItalianoEspañol

How to Keep Your Wedding Website Private

A wedding website gathers information you would never pin to a public noticeboard: your full names, the exact date and time your home will be empty, the venue address, personal photos and — through the RSVP — your guests’ allergies and phone numbers. No need to get paranoid, but it’s worth understanding the three privacy layers that exist and deciding which ones you want.

Layer 1: only the people you choose get the link

The foundation of everything: your website isn’t linked from anywhere public. It’s not in a directory, the venue doesn’t share it, it’s not on your social media. It only reaches the people you hand the link to, usually over WhatsApp.

That alone filters out 99% of the world, with one important caveat: links get forwarded. The invitation you send your aunt can end up in the 40-person family group chat, and from there anywhere. If your guest list is closed, pair the link with a clear note: “this invitation is personal”. Our article on digital invitation etiquette covers how to say it without sounding rude.

Layer 2: keep it out of Google (noindex)

Even if nobody publishes your link, search engines crawl the web constantly. If your page isn’t protected, searching your names could surface the wedding to anyone: coworkers, exes, strangers.

The technical fix is called noindex: an invisible tag that tells Google and friends “this page must not appear in search results”. It changes nothing for your guests — the site works exactly the same — but it takes you out of the public shop window. If you use an invitation platform, check that it applies noindex by default; if you built the site yourselves, add the tag before sharing the link.

Note the limit: noindex keeps you off Google, but it doesn’t stop anyone who has the URL from opening it. That’s what the third layer is for.

Layer 3: an access code

The digital equivalent of a key: anyone opening the link sees a screen asking for a code before anything is shown. Without the code there are no names, no date, no address, no photos.

When is it worth switching on?

• If you publish personal photos and don’t want a stranger with the link browsing them.
• If the guest list is closed and you don’t want layer-1 forwards turning into surprise guests.
• If the site shows a private address (the family house, a relative’s estate).

How do you share the code without confusing guests? Keep it simple: put it in the same message as the link (“use the code EMMAANDJACK to enter”). A memorable code — your names, the date — protects just as well as a cryptic one and prevents 90% of the “it won’t let me in” messages.

What your guests see (and what they don’t)

Privacy also works inwards. Things your guests should be able to take for granted:

• Their RSVP answers are for you alone. Grandma’s allergies or a friend’s phone number must never be visible to other guests; only the couple sees them, in their dashboard.
• The form asks for the minimum. Every piece of data you request is data you’re responsible for. In what to ask on your RSVP we explain why a postal address, for instance, is almost never needed.
• No public guest lists. Avoid displaying who has confirmed on the website: it’s other people’s information, and it invites awkward comparisons.

Our practical recommendation

For most weddings, layer 1 + layer 2 (private link and noindex) is enough and adds zero friction. Add layer 3 (a code) if there are intimate photos, private addresses or a strictly closed list. Whatever combination you choose, decide before sending the first invitation: switching on a code when half the family already has the link open creates more confusion than security.

Privacy done well is invisible: your guests just see a beautiful invitation that opens first try. Everything else works in silence.

Wedding websiteEtiquette

← Back to the blog