How to Make a UK Wedding Website Guests Actually Use

Plenty of couples spend an evening building a lovely wedding website, print the link on the save-the-dates, and then field the same questions by text for the next nine months. "What time should we arrive?" "Is there parking?" "Can we bring the kids?" The answers were on the site all along. The problem usually isn't the guests. It's that the site was built like a brochure, when guests use it like a timetable: they open it on a phone, look for one fact, and leave. Build it around those quick visits and people will actually use it.

Last updated: 21 October 2026

Jump to

• Why most wedding websites get ignored
• What guests actually look for
• What you can safely leave off
• Make it work on a phone first
• Getting guests to the site in the first place
• RSVPs that people finish
• Comparing ways to share wedding details
• Keep it useful after the invitations go out
• A page-by-page checklist
• A wedding website guests can open in seconds with GuestLive
• Frequently asked questions

Why most wedding websites get ignored

Guests rarely ignore a wedding website on purpose. They bounce off it for small, fixable reasons:

• It asks them to do something first. A sign-up screen, an app download or a password nobody wrote down is enough to send someone back to WhatsApp to ask you directly.
• The useful bit is buried. The ceremony time sits under three paragraphs about how you met.
• It was built on a laptop and viewed on a phone. Tiny text, a giant header photo and a menu that hides everything.
• It went stale. The site said one thing, a later message said another, and now nobody trusts either.
• They can't find the link again. It was on a save-the-date that is now somewhere behind the fridge.

Each of these has a simple fix, and none of them needs a fancier design.

What guests actually look for

Think about the questions you'll otherwise be answering by text. For most UK weddings, guests visit for the same handful of things:

1. When and where. Date, ceremony start time, the time to arrive (which isn't the same thing) and the full venue address with postcode.
2. Whether they're a day or evening guest. If you have both, make it obvious who is invited to what. We've covered the wording in day and evening guests on one wedding website.
3. Getting there and getting home. Parking, nearest station, local taxi numbers and the last train. At rural venues this matters more than anything else on the page.
4. Where to stay. A couple of nearby options and whether there's a room block or discount code.
5. What to wear. One clear line beats a vague "dress to impress". Mention anything practical too, such as grass, gravel or a chilly church.
6. Children and plus-ones. Say it kindly and plainly so nobody has to ask.
7. Food and dietary needs. When you'll ask for meal choices and how to tell you about allergies.
8. Gifts. Whether you have a list, a fund or would genuinely rather not. If you're asking for money, our guide to asking for a wedding fund without sounding rude has wording that works.
9. The RSVP button and its deadline.

Put the first three near the very top. If a guest only reads the first screen on their phone, they should still arrive at the right place at the right time.

What you can safely leave off

A shorter site gets read. These are nice to have, not essential, and they often push the important bits down the page:

• A long "our story" section. A few lines and a favourite photo are plenty.
• Full biographies of the wedding party.
• Countdown timers and animated headers that slow the page on a weak signal.
• Empty sections. If you aren't collecting song requests or running a gift list, hide that part rather than leaving a blank box. Guests skim, and empty sections look like a broken page.
• Anything private. Your home address, the full seating plan with surnames and children's names don't need to be on a site that can be forwarded.

Make it work on a phone first

Almost every guest will open your site on a phone, often in a car park, on a train or at a venue with patchy signal. Before you share the link, open it on your own phone with Wi-Fi switched off and check:

• Does it load quickly on mobile data? Big uncompressed photos are the usual culprit.
• Can you read the time and address without zooming?
• Does the postcode or map link open straight in a maps app?
• Can you RSVP with your thumb, without fiddly drop-downs or a form that resets when you switch apps?
• Does it open without an account or app? If a guest has to sign up just to see the start time, many simply won't.

If your venue is a barn, field or castle with thick walls, assume some guests will check the site with one bar of signal. Our piece on barn and castle Wi-Fi covers what to plan for on the day itself.

Getting guests to the site in the first place

A great site does nothing if nobody opens it. Give people several easy routes in:

• Put the link and a QR code on the save-the-date and the invitation. A short, readable link plus a code covers both the people who type and the people who scan. If you're making a code, this guide to a wedding photo QR code guests actually use has sizing and testing tips that apply to any wedding QR code.
• Send the link digitally too, by email, WhatsApp or text, so it's searchable in their messages months later.
• Answer questions with the link. When someone asks about parking, reply with the answer and "it's all on the website here". People soon learn where to look.
• Use it as the one place for updates. If timings change, change the site first and then send a short message pointing to it. That's how you avoid a sprawling group chat; see stop the WhatsApp wedding group for more on that.

RSVPs that people finish

The RSVP is usually the only thing you need every guest to actually do, so make it as short as possible:

• Ask only what you need: attending or not, names, meal choice if you're serving a set menu, dietary needs, and perhaps a song request.
• Give one clear deadline, and put it in the same place on the invitation and the site.
• Don't make people create an account to reply.
• Let people change their answer before the deadline. Plans change, and it's better to hear about it.
• Collect meal choices with the RSVP, rather than chasing them separately later. We explain why in collecting wedding meal choices during the RSVP.

Comparing ways to share wedding details

Keep it useful after the invitations go out

A wedding website that guests trust is one that stays current. A few habits help:

• Update the site before you message anyone. Then every message can simply point to it.
• Add a short FAQ as questions come in. If two people have asked, others are wondering.
• Add a "final details" note a week or two before the day: arrival time, weather plan, taxi numbers and any late changes.
• Switch the focus on the day itself. Once guests arrive, the most useful thing the site can do is help them share photos and messages. A voice-note guestbook and a shared photo album both work well from the same link.
• Keep it going after the wedding. A thank-you message and the link to everyone's photos give guests a reason to come back one last time.

A page-by-page checklist

1. Top of page: your names, the date, the venue with postcode and the time to arrive. One favourite photo is plenty.
2. Schedule: ceremony, drinks, meal, speeches, evening start and carriages.
3. Travel: parking, nearest station, taxi numbers and last trains, plus a note on lighting or terrain after dark.
4. Stay: two or three nearby options, and any room block or discount code.
5. RSVP: a short form and one deadline. A song request question is optional.
6. Gifts: a clear, kind line on what you'd like, with a fund or list link if you have one.
7. FAQs: dress code, children, plus-ones, dietary needs, and accessibility or quiet spaces.

A wedding website guests can open in seconds with GuestLive

If you'd rather not stitch a website, an RSVP form and a photo album together, GuestLive puts them behind one link. Guests open it in their phone browser, with no app to download and no account to create.

• Digital invitations you can send by email, WhatsApp or text, and update so every guest sees the latest version.
• RSVPs with dietary requirements, plus-one details, song requests and your own questions, plus gentle reminders for anyone who hasn't replied.
• A shared photo and video album that guests can upload to on the day and afterwards, and that never expires.
• Funds, a voice-note guestbook and a guest playlist if you want them.

Every feature can be switched off, so guests only see the parts you're actually using.

GuestLive is £29, once, for every feature, with no guest app and no guest limits. Details are on the pricing page.

Frequently asked questions

When should we send our wedding website link to guests?

Most UK couples put it on the save-the-date, around six to twelve months before the wedding, then include it again on the invitation. The earlier guests have it, the fewer questions you'll get by text.

What should go on the first screen of a wedding website?

Your names, the date, the venue with its postcode and the time guests should arrive. If someone reads nothing else, that's enough to get them there.

Should our wedding website be password protected?

It depends on how much personal detail is on it. If you keep it to practical information and leave off addresses and seating plans, a private link is usually enough. Add a password if you'd feel more comfortable.

Do older guests actually use wedding websites?

Yes, when it opens straight from a link or QR code with no sign-up. For anyone who'd rather not, a printed card with the key details and a phone number to call works alongside the site.

Can we use one wedding website for day and evening guests?

Yes. Give evening guests their own short section with their arrival time, and send them the same link with a note that says when they're invited from.

Should we include an "our story" page?

Only if you want to. Guests enjoy a few lines and a photo, but keep the practical details above it so nobody has to scroll past it to find the start time.