A wedding website your guests will actually open
A wedding website has one user: a guest with a phone who opens it once, often on poor signal on the way to the wedding. It has to be quick, clear, and answer three questions — when, where, and what to wear.
Sections that make sense
The programme, a map of the venue, the dress code, accommodation, gifts, questions and answers. Turn on only what you need and reorder it — and the page looks like a wedding rather than like a corporate site.
Replies on the page itself
Guests answer straight from their invitation link — no registration, no app, under a minute. The replies feed into your guest list, meals and allergies included, ready for the caterer.
Your own address, and it loads instantly
An address of the form weddinglad.app/w/anna-a-petr, printable on an invitation. The page is static and downloads no application and no JavaScript to a guest’s phone — it is an ordinary page, which is why it loads in a garden on one bar of signal. It is also not rebuilt on every visit: it sits ready, with the date you last published it written on it.
It does not publish by accident
The site has a draft version and a published one. Until you publish, guests see nothing. Publishing is deliberate, so a note you wrote to yourself does not turn up in front of eighty people.
The old address keeps working
Invitations are printed and the address is on paper, and paper does not get rewritten. If you change the address later, the original stays yours and sends guests to the new one. Not instantly: it shows for a moment that the address has changed, so a guest notices and can write the new one down — and an instant redirect would break the back button, leaving them unable to get out. The old address is also never handed to another couple.
What never reaches the page
The guest list is not on the site — one family’s link resolves only their own invitation and cannot look at anyone else’s. Meals show a name and a description, never a price per head: what a guest’s dinner cost is not something a guest should read. Only the parts of the day you mark public are published, so supplier arrival times and internal notes stay with you. And a section you switch off is not saved into the public data at all — it is not hidden, it simply is not there.
Guests find their own table
The site includes a “where do I sit” page: a guest enters their name and gets a table number. It saves you and the best man the quarter of an hour before dinner when eighty people ask the same question and nobody can hear the answer.
An expired licence does not take the page down
When the full version ends, a published site keeps running. A guest clicking a link a week before the wedding and finding a dead page is the worst thing that can happen in this product — and it will not happen over a payment. Expiry blocks further publishing and tells you why; what guests already hold, it leaves alone.
Common questions
- Is the wedding website free?
- You can build and prepare it for free — you see exactly how it will look and pay nothing. Publishing it to guests is part of the full version, a one-off 490 CZK. One payment rather than a subscription, and once the site is out, it stays out.
- How is our address made?
- From your names, reduced to plain letters — “Anna & Petr” becomes anna-a-petr. You can rewrite it, as long as it is free and is not a word the app keeps for itself. Two weddings cannot share one address.
- Will strangers find our page through Google?
- No. Wedding pages are excluded from search engines — they carry names, a date and a place. Only the guests you give it to have the address.
- Can we edit the site after the invitations have gone out?
- Yes, and it is normal. Guests see changes once you publish them; until then they see the previous version rather than your draft.