Wedding website privacy: keep your day off Google.

Your wedding is not a public event

Your wedding is a private gathering of people who love you, and the website that carries the details for those people should be private too. Somewhere along the way the big template builders convinced a generation of couples that "wedding website" meant "public web page anyone can find." That's a business decision on their part, not a fact about weddings.

Here's what actually happens when you build on The Knot or Zola or Joy. Your page sits on their subdomain (theknot.com/us/your-names, zola.com/wedding/your-names). Google indexes it. Every couple's page adds a bit more content and a bit more link equity to the template builder's own domain. Your names, your date, your venue city, sometimes your registry, all searchable by anyone with your first names and a hunch. That's not a bug; it's the whole model. Their SEO is built on your wedding.

At Digithad we flip the default. Your site lives on your own URL (or a subdomain we set up for you), and it's private from the day it goes live. Search engines are told not to index it. No public link points at it. When your college roommate googles your names, nothing about your wedding comes back. Only guests who received the link know it exists.

That's the shape of the studio: bespoke wedding websites from $490, built for one couple, hosted for one year, hidden from the whole internet except the people you invited. It's a smaller footprint on purpose.

What "hidden from search engines" actually means

Hidden from search engines means three specific things working together, and every Digithad wedding site ships with all three on the day it launches.

First, a robots.txt file. Think of it as the sign on the front door of your website that tells crawlers (Google's, Bing's, DuckDuckGo's) what they may and may not look at. Ours reads, essentially, "please do not index anything here." Well-behaved crawlers respect it, and the major search engines are well-behaved on this specific rule.

Second, a noindex meta tag on every page. This is the belt to the robots.txt suspenders: a line of code in the head of your site that says, again, "do not add this page to your index." Even if a crawler wandered in without checking the front-door sign, the tag tells it to leave without taking notes.

Third, and this is the part nobody explains: your site is not linked from anywhere public. Search engines find pages by following links; if no public page links to yours, there's very little chance a crawler stumbles on it. Guests reach the site through the QR code on the printed invitation or a WhatsApp link from you. That's it.

Those three together are why your Digithad site doesn't show up in Google, doesn't show up in Bing, and doesn't get scraped into whatever people-search directory is fashionable this year. Quiet plumbing, real result.

Passwords: when to add one

A password is an optional second layer, and it's the right call for a specific set of weddings, not every one. Privacy from search engines already handles most concerns; a password handles the rest.

We recommend adding one when any of the following is true for your wedding. Your ceremony or reception is at a family home, so the site would otherwise be showing the address of a place people actually live. Your guest list includes public figures (a politician's kid, a musician you'd rather not read about in a gossip column, a colleague with a stalker they've had to file paperwork about). Your family has a situation that calls for extra discretion: a custody dispute, an estranged parent, a witness protection reality, a religious community you'd rather not have peering in. Any of those is a good reason. All of them are more common than couples expect.

When you do add a password, the rule is simple: the password lives on the printed invitation only. Not in the RSVP group chat, not in the mass email, not on the fridge of the friend who lost her invite. If someone loses theirs, you text them. This isn't paranoia; it's just how a password stays a password. On Digithad sites the password screen is warm, on-brand, and remembers guests on their own device so they enter it once and never again.

If none of those situations apply, skip the password. Default privacy is usually enough, and one less thing for grandpa to fumble on his phone at the airport.

Guest photos: the social-media policy

Guests want to share the day, and most of them will point their phones at you within thirty seconds of the first kiss. That's not a problem to solve; it's a habit to shape. The tool for shaping it is a single sentence on the QR card that sits on every table.

Here's the wording we've watched work at dozens of weddings:

Guests respect this rule for a reason that has nothing to do with obedience: you gave them something better than an Instagram post. You gave them the whole night's photos from every table, in one gallery, available before they're even home. That's a fair trade. The one aunt who still posts on Facebook does so with a photo of you laughing on the dance floor, not a photo of the venue's address plate. Nobody minds that one.

For the guest who wants to post publicly and asks you first (the friend who runs a small photography account, the cousin whose Instagram is basically a diary), just ask them to keep venue signage out of frame and to tag no one but the two of you. On the very rare occasion a guest posts something you'd rather they didn't (an unflattering photo of your grandmother, a corner of a document, a face someone didn't want online), you send one quiet DM and they take it down. Weddings run on goodwill; the goodwill is already there.

The uploads themselves land in your private gallery, on your private site. You moderate what stays. It's your day; the archive is yours.

The AI-scraping question

Every public web page is fair game for the crawlers that build AI training sets, and public wedding pages on template builders' domains are no exception. Your names, your love story, the "how we met" essay you wrote at midnight, the photo the site's SEO team compressed for social sharing: all of it can be, and often is, ingested wholesale. Not because anyone is out to get you; because the crawlers are indiscriminate and the pages are indexed.

A Digithad wedding site, private by default, isn't on that menu. Robots.txt blocks the mainstream AI crawlers. The noindex tag keeps the pages out of the search indexes that seed a lot of secondary scraping. No public link points at your site, so a crawler that ignores the robots.txt still has no path in.

Is this bulletproof? No. Nothing on the internet is bulletproof. A determined adversary with the URL and no ethics can still hit the page. But that's a very different threat model from "the entire open web is quietly harvesting this content on my behalf." One is a bad actor who has to actively target you; the other is the default state of a public wedding page in 2026.

If either of you is private about your online presence (you use a nickname on LinkedIn, you don't post photos of your kids from a previous relationship, you've chosen not to be Googleable on purpose), this matters. If neither of you thinks about it, it's still nice to know the wedding you spent a year planning isn't quietly feeding a model.

What happens to the site after the wedding

The site stays online for a full twelve months after your date, and during that year it becomes the memory album: the photographer's gallery, the video highlights, the speeches, the phone photos guests uploaded, all at the link everyone already has. Private the whole time, hidden the whole time, no login gate to fight with.

When the twelve months are up, we email you before we close it. If you want more time, we extend. If you want it archived, we ship you a download of the full site: HTML, images, guest uploads, the lot. It lands in your Dropbox or Drive, yours to keep on a hard drive next to your wedding album.

Then we take the site down. Nothing lingers on our servers. Nothing lingers on a template builder's servers as a "featured wedding" marketing tile they use to pitch the next couple. There is no dormant public page a curious ex or a data broker can rediscover in five years. The URL simply stops resolving.

That's the last piece of privacy, and it's the one couples forget to ask about at the beginning. What's the exit? On Digithad the exit is clean: you get everything, we keep nothing, the site returns to the quiet it came from.

Questions couples ask

Written by the Digithad studio

We build private, custom-designed wedding websites for couples who'd rather not hand their names, their date and their venue to a template builder's SEO team. Multilingual, bespoke, off the record. Updated July 2026.