Wedding Websites: What to Include and Privacy Considerations

A wedding website has become close to standard for UK weddings, and it earns its place genuinely well - it's the natural home for details you don't want cluttering a printed invitation, and it's far easier to update than a paper RSVP if something changes.

What actually belongs on it: venue details and directions, accommodation suggestions for guests travelling in, RSVP collection (including the dietary and allergen questions covered in catering for dietary and allergen needs), your gift list or gift-fund details (see gift lists, explained for why this belongs here rather than on the invitation itself), dress code, a rough timeline for the day, and any FAQ items you find yourself answering the same question about repeatedly by text.

What I'd leave off, or at least gate behind a login: anything that reveals your home address or that of family members, detailed travel dates that broadcast when your home will be empty, and full names and contact details of your wedding party beyond what's needed for guests to recognise them. Most wedding website platforms offer a password-protected option - it's worth using if you're including any information you wouldn't want fully public and indexed by search engines.

On search engine visibility specifically: by default, most wedding website platforms are publicly accessible and can end up indexed by Google unless you specifically restrict them - worth checking your platform's privacy settings directly rather than assuming a website only reachable via a link you send out is actually private from search.

On photos: if you're planning to share photos from the day publicly (on the website itself or via a linked gallery), it's worth checking with anyone who might reasonably prefer not to be publicly identifiable online - this applies more than people expect once children, guests with public-facing jobs, or anyone with personal safety reasons for limited online visibility are on the guest list.

What I'd actually do: build the website with the assumption that its link could end up shared more widely than you intend - guests forward invitations and links more than couples expect - and keep anything genuinely sensitive (full addresses, precise travel dates, anything you wouldn't want a stranger to have) off it entirely or behind a password, rather than relying on the link staying private.