Use cases

How to build a simple wedding website with RSVP

3 September 2026 · 2 min read

A wedding website doesn't need a template marketplace or a monthly subscription behind it. Guests need the date, the venue, a rough schedule, a registry link if you're using one, and a way to actually tell you they're coming. That's one page, and it's the kind of thing a static site was always meant for.

What actually needs to be on it

Date and venue at the top, since that's what everyone's actually looking for. A schedule if there's more than one event, ceremony and reception separately if the times or locations differ. Travel and hotel info if guests are coming from out of town. A registry link if you have one. Keep it to that; a wedding page doesn't need to be a whole itinerary of the relationship.

RSVP without a backend

A static page can't collect and store form submissions on its own, so RSVPs need one extra piece. Embedding a Google Form works and costs nothing, the responses land in a spreadsheet you already know how to read. A floating WhatsApp button is the other option: a guest taps it, a prefilled message opens with their name already in the text, and they just confirm and send. It's a Growth tool on a Pro full site, so no code goes on the page itself.

Start simple, upgrade if you want a custom domain

A microsite gets a page live in minutes at a free yourname.makemysitelive.com address, which is enough for most weddings. If you'd rather share something like sarahandtom.com, that needs a Pro full site with a custom domain connected, which also unlocks the WhatsApp RSVP button above.

Keep it private if it's a small wedding

Not every wedding page needs to be open to anyone with the link. Password protection is a toggle on a Pro full site, so only guests you've actually invited can open it.

Update it as plans change

Venue changes, a schedule shifts, a hotel block fills up, upload a new version and the same link shows the update instantly. Nobody needs a new link texted to them because a detail moved.

Key takeaways

  • A wedding page needs about five things: date, venue, schedule, travel/registry info, and a way to RSVP.
  • RSVP without a backend works through an embedded Google Form, or a WhatsApp button with a prefilled message on a Pro full site.
  • Start as a free microsite; upgrade to a Pro full site if you want a custom domain like yournames.com.
  • Password-protect the page on a Pro full site if it shouldn't be open to anyone who gets the link.

Frequently asked questions

Can guests RSVP directly on the page?

Not natively, since a static page has nowhere to store a submission on its own. Embed a Google Form, or add a WhatsApp button on a Pro full site so a guest's reply comes straight to your phone with a prefilled message.

Do I need a custom domain for a wedding website?

No. A free microsite at yourname.makemysitelive.com works fine. A custom domain like yournames.com is available if you upgrade to a Pro full site.

Can I keep the page private to just our guest list?

Yes, with password protection on a Pro full site. Share the password along with the invite so only actual guests can open it.

What if the venue or schedule changes after we've shared the link?

Upload a new version. The link stays the same, so guests who already have it always see the current details.

Share this article

Keep reading

More from the blog

Ready to go live?

Create a free account and publish your first site in 2 minutes.

Get started free