Your wedding website needs nine pages of words, not five. Welcome, our story, RSVP, travel and FAQ are the ones every guide covers. The four that actually generate the texts are the weekend schedule, the dress code, the gift page and the photo page, and most wording guides either skip them or hand you a placeholder like "[link]" and call it a template.
This page is a swipe file for all nine. Every example sits in its own block with real line breaks, so you can copy it, paste it into your builder, and swap the bracketed parts. Nothing below is a placeholder standing in for wording we did not write.
One scope note. This guide is the words that go on your website. The words on the invitation that points to it are a different job, covered in our guide to digital wedding invitation wording.
A wedding website exists to answer the questions a guest would otherwise text you: where, when, what to wear, which parts am I invited to, how do I reply, and what do you want as a gift. If a page does not answer one of those, it is decoration.
Here is the whole site at a glance, with the question each page settles.
| Page | The question it answers | Target length | Publish by |
|---|---|---|---|
| Welcome / home | Am I in the right place, and when is this? | 3–4 sentences | Save-the-date |
| Our story | Who are these two people to each other? | 150–250 words | Save-the-date |
| Schedule of events | Which parts am I invited to, and when? | One block per function | Invitation |
| Travel and accommodations | How do I get there and where do I sleep? | 3 mini-sections | Save-the-date |
| Dress code | What do I wear, per event? | 1–2 sentences per function | Invitation |
| RSVP | How do I reply, by when, and what happens if I don't? | 4 sentences plus form | Invitation |
| Gifts | What do you actually want? | 2 sentences | Invitation |
| Photos | Can I take them, and where do they go? | 2 short blocks | 2 weeks out |
| FAQ | Everything else, before anyone has to ask | 8–12 questions | Invitation |
The standard five-page set was designed for a wedding that happens on one afternoon. A 2026 wedding is frequently a Friday welcome party, a Saturday ceremony and reception, and a Sunday brunch, often with three different guest lists layered inside one event. The schedule page is what tells a guest which layer they are in. Without it, you get the same question forty times: "are we invited to the Friday thing?"
Dress code, gifts and photos get skipped for a different reason. They feel awkward to write, so couples bury one line about each in the FAQ and hope. Each one deserves its own short page, because each one is a decision your guest has to make before they arrive.
Pick a register and hold it. A formal welcome message next to a jokey FAQ reads like two different couples got married on the same website. The fastest way to check: read the first sentence of every page out loud, in order. If one of them sounds like a different person wrote it, rewrite that one, not the others.
| Element | Working limit | Why |
|---|---|---|
| Welcome message | 40–70 words | It is read on a phone, above the fold |
| Our story | 150–250 words | Guests want the highlight reel |
| Each schedule block | 20–35 words | It is scanned, not read |
| Each FAQ answer | 2 sentences | A third sentence invites a follow-up question |
| Gift note | 2 sentences | Short reads as gracious, long reads as a pitch |
Your welcome message has three jobs and one rule. The jobs: confirm the guest is in the right place, state the date and city, and point at the RSVP. The rule: the deadline appears here as well as on the RSVP page, because this is the page guests land on when they finally get around to replying.
Your story page should hit three beats: how you met, the moment you knew, and the proposal. Aim for 150 to 250 words. Guests are reading it standing up, on a phone, while the RSVP form waits one tap away.
Your RSVP page needs four things in the copy: how to respond, the deadline, what information you need from each guest, and what happens if they do not reply. Most couples write the first one and then spend the following month chasing silence.
If some of your guests still go quiet after all of that, and a few always do, the follow-up is a separate skill with its own timeline and scripts. We wrote that up in what to do when wedding guests don't RSVP. Do not solve it by adding a second RSVP channel. One channel, repeated, beats three channels merged by hand.
Do: Put the deadline on the button itself. "RSVP by June 5" removes the last excuse. Don't: Offer the form, an email and a phone number at once. Three channels means three lists and one aunt who answers all three differently.
A schedule page has one job that most wedding websites get wrong: it has to make clear which events each guest is invited to, and give them a way to answer for each one. A schedule is not a paragraph. It is a set of blocks, one per function, each with a time, a place, a dress code and its own reply.
This is where the standard single-RSVP website breaks. If your welcome message, your schedule and one RSVP button live on one page, a guest can tell you they are coming, and you still do not know whether they mean the welcome party, the reception, the brunch or all three. The answer arrives later, in a group chat, one message at a time. Writing the schedule properly is half the fix. The other half is whether the reply mechanism behind it can hold separate answers.
Work your deadlines backwards from whoever needs numbers first, which is almost never the reception caterer.
| Function | Who needs the number | Deadline, counting back from the wedding |
|---|---|---|
| Rehearsal dinner | Restaurant, often on a private-room minimum | 6 weeks |
| Welcome party | Bar or venue, on a per-head package | 6 weeks |
| Ceremony and reception | Caterer's final count, plus seating chart | 4 weeks |
| Farewell brunch | Venue, usually flexible | 3–4 weeks |
| Room block release | Hotel | 6–8 weeks |
Write that instruction only if the tool behind your site can hold separate answers per function. On Lumhe, each function is a sub-event inside one event, with its own date, time, venue, guest list and RSVP. Different guests can be invited to different functions, so a guest sees only the events on their own list and replies to each one independently, and you see a live count per function instead of one blended number. Reminders go only to people who have not answered that specific function, so the friend who already said yes to Saturday is not nudged about Saturday while you are still chasing Friday.
Lumhe is not a wedding website builder. It will not give you a story page or a travel page. What it gives you is the invitation and the reply mechanism your schedule wording depends on: you upload the invitation you already made, as an image, a video, a PDF or typed text, and add each function separately.
Your travel page answers three questions in order: how do I get there, where do I sleep, and how do I get around. Use those as bold mini-headers so an out-of-town guest can skim to the one they need.
Do not publish a dress code without translating it. "Cocktail attire" means five different things to five guests, and the guest who guesses wrong remembers it for a decade. Name the code, then say what it means in clothes, then name the terrain.
| Dress code | What to tell guests it means | Terrain note to add |
|---|---|---|
| Black tie | Tuxedo or floor-length gown | Almost always indoors |
| Black tie optional | Tuxedo or dark suit; long or midi dress | Say whether a dark suit is genuinely fine |
| Cocktail | Suit or sport coat; cocktail dress, jumpsuit, dressy separates | Name the flooring |
| Garden party | Suit without a tie; midi or floral dress | Grass means block heels |
| Smart casual | Collared shirt, chinos; sundress or nice separates | Say whether jeans are in or out |
| Festive | Anything you'd wear to a good party, with color | Give one example so nobody overthinks it |
Say gifts once, in two sentences, on a page of their own. Short reads as gracious. A long explanation reads as a pitch, no matter how the sentences are arranged.
The gap in almost every wording guide is the couple who would rather receive money than items. The usual template stops at "a contribution to our honeymoon fund: [link]", which is not wording at all. It is a placeholder pointing at a mechanism the couple has to go and find. If you would rather receive money, your gift page has to answer three things: that money is genuinely welcome, that no amount is expected, and how a guest actually sends it.
The wording above only works if there is somewhere for the money to go. In the US, guests reach for whatever app is already on their phone, which means your page has to name your rails rather than assume theirs.
| How a guest sends money | What you have to publish | What a guest needs |
|---|---|---|
| Venmo | Your handle | The app, and a US bank account |
| Zelle | Phone number or email | A bank that supports it |
| Cash App | Your $cashtag | The app |
| PayPal | Email or PayPal.me link | An account or a card |
| Bank transfer | Account details, shared privately | Nothing extra, works internationally |
| Check or cash on the day | A card table | Nothing |
Lumhe's Digital Lifafa is built for exactly this handoff. You add your payment ID, whichever one you already use, including UPI for family sending from abroad. The guest pays from whichever app they already have and uploads the receipt, and it reaches you wrapped in an occasion-themed digital envelope that you open. Lumhe never touches the money: it is a direct transfer between your guest and you, and the envelope is the part Lumhe adds. Optional themed envelope designs cost $0.49 to $1.99. Keep your registry wherever it already lives, at Zola or anywhere else, and let this page carry both.
Photo wording fails in a specific way. The template says "our photographer will catch everything and we'll share the photos with you," then hands the reception over to a hashtag. Neither half is a mechanism. A hashtag scatters your photos across accounts you cannot see, and "we'll share them with you" turns into a link you have not sent by August.
Write three separate blocks: what happens during the ceremony, what happens during the reception, and where every photo ends up.
Moments is Lumhe's version of that shared place: a photo timeline attached to the event itself. Guests upload, everything collects in one organised spot, and it does not expire or close when the event ends. It is not a group chat and not a Story, which is the whole point. A hashtag scatters, a chat scrolls away and a Story disappears in a day, and none of the three are somewhere you can point a guest twelve months later. If you want to compare what is out there before committing, we looked at the best wedding photo sharing apps.
Your FAQ answers the questions guests are too polite to ask. Answer each one in two sentences, warmly and specifically. A vague answer generates the exact text you built the page to prevent.
On the invitation, your website gets one line, near the bottom, after the date, time and venue. You do not need to explain what a website is. You need a URL and a deadline.
Sending paper? Put a QR code under that line for the relatives who will not type a URL. Sending digitally? The line becomes a button. For everything else on the invitation face, including host lines, formality and per-function scope lines, see the digital wedding invitation wording guide.
Two structures work, and the choice changes what you have to write. A full website builder gives you seven or nine pages and expects you to fill them. An event page gives you one screen, which forces the wording to be shorter and sharper but cannot hold a story page. Many couples end up with both: a website for the reading, an invitation and RSVP flow for the replying.
The two columns nobody publishes are the ones that decide it: whether the tool tracks a reply per function, and which invitation formats it accepts.
| Platform | Pages or format | Invitation formats accepted | Per-function / multi-event RSVP |
|---|---|---|---|
| Lumhe | Not a website builder. Event with sub-events | Upload your own image (JPG/PNG), video, PDF or typed text. No template library yet | Yes. Each function is a sub-event with its own date, venue, guest list and RSVP |
| Mixily | One event page | Event page with an image and typed text | Not per function. One event, one RSVP |
| The Knot | Multi-page wedding website | Template-based website and invitation designs | Website can list multiple events; RSVP is questionnaire-style |
| Zola | Multi-page wedding website plus registry | Template gallery; invitation product is print-focused | Website lists events; RSVP is questionnaire-style |
| WithJoy | Multi-page wedding website | Template gallery | Website lists events; RSVP is questionnaire-style |
| Google Forms plus a free site | Whatever you build | Nothing. You link out | No. You build columns and reconcile them yourself |
Verify feature support and current pricing with each platform before you commit, because plans change. On price: Mixily states its free tier "covers 50 invites and 40 RSVPs per event," with "Lite at $19 and Pro at $29 if your guest list is bigger." Those are Mixily's published figures for those tiers, not ours, and they should be re-verified before you budget around them. On Lumhe, event creation, invitations, per-function RSVP tracking and Moments are free forever, with no per-event and no per-guest charge. The only paid extra is optional themed Digital Lifafa envelope designs at $0.49 to $1.99.
Be clear-eyed about what Lumhe does not do. There is no website builder, no template library yet, and no printed stationery. If you want a story page and a travel page, build those on a website builder. What Lumhe replaces is the part your wording keeps promising: separate replies for separate functions, an invitation in whatever format you already made it, one permanent place for photos, and a clean way for guests to send money.
Publish in three waves, matched to when guests need each answer. The most common wording failure is not bad copy: it is a travel page that goes live after guests have already booked flights.
| Stage | Timing | Pages that must be live | Wording that must exist |
|---|---|---|---|
| Save-the-date | 8–12 months out | Welcome, our story, travel | Date, city, hotel block deadline |
| Invitation | 8–10 weeks out | Schedule, dress code, RSVP, gifts, FAQ | Per-function RSVP instruction, deadline with a consequence |
| Final stretch | 2–3 weeks out | Photos, updated FAQ, day-of timings | Unplugged line, album link, arrive-by times |
| After | Week after | Thank-you, album | Album link, thank-you note |
The hotel block deadline is the one date that has to be published in wave one. Everything else can arrive with the invitation.
Leave the site up for at least a year, and change three things: a thank-you at the top, a link to the photos, and the removal of anything that now reads as a live instruction. A site still saying "RSVP by June 5" in November looks abandoned.
Nine things: a welcome message with your names, date and city; your story in 150 to 250 words; a schedule with a block per event; travel and hotel details; a dress code with a translation; RSVP instructions with a deadline and a stated consequence; a two-sentence gift note; photo instructions with one link; and an FAQ of 8 to 12 questions. If a guest could text you a question, the site should already answer it.
State the method, the deadline and the consequence in that order: "Please RSVP below by [date]. If we haven't heard from you by then, we'll assume you're unable to join us and release your seat." Ask for meal choice and dietary needs inside the form rather than by email later. If your wedding has more than one function, add a line telling guests to answer for each event on their invitation.
Write one block per function with its own time, venue and dress code, then a single instruction: "Please RSVP to each event you're invited to by [date]." Only publish that line if your RSVP tool tracks each function separately, because otherwise guests tap one button and you still have to ask who is coming to the brunch. Set the rehearsal-dinner and welcome-party deadlines about two weeks earlier than the reception deadline.
In two sentences on the gift page: say what the money is for, say that any amount is generous, and then say how to send it. Naming actual methods, such as a Venmo handle, a Zelle number or a bank transfer on request, is what turns the sentence into something a guest can act on. Never put it on the invitation itself, and never make it the first thing the page says.
Three blocks: no photos during the ceremony if you are going unplugged, photos welcome at the reception, and one link where every photo ends up. Skip the hashtag. A hashtag scatters your photos across accounts you cannot see, while one shared album keeps them together and stays available after the wedding.
One line near the bottom: "Find all the details and RSVP at [yourwebsite.com]." Add a QR code on printed invitations, and turn the line into a button on digital ones. Do not put registry or gift information on the invitation; let the website carry it.
Before your save-the-dates go out, because the save-the-date carries the URL. At that stage you only need the welcome message, the story and the travel page with the hotel block deadline. The schedule, dress code, RSVP, gifts and FAQ pages can arrive with the invitation, 8 to 10 weeks out.
Welcome, 40 to 70 words. Our story, 150 to 250. Each schedule block, 20 to 35. Each FAQ answer, two sentences. Guests read this on a phone while doing something else, and a third sentence in an FAQ answer usually invites a follow-up question rather than settling one.
Planning a wedding weekend? Upload the invitation you already made to Lumhe, whether that is an image, a video, a PDF or typed text, then find and connect with your guests by name, phone number or email inside Lumhe and send it to them directly. Add each function separately, so the welcome party and the reception have their own guest lists and their own RSVPs, and you always know the headcount for each one. After the wedding, everyone's photos collect in Moments, a shared timeline that does not expire, which is the real destination for the photo wording on your site. Guests who want to send money instead of a gift can do it through Digital Lifafa: you add your payment ID, they pay from whichever app they already use and upload the receipt, and it arrives wrapped in a digital envelope you open. Lumhe never touches the money. You can also share your invitation link on WhatsApp, iMessage, Instagram or any other platform. Explore Lumhe.
SEO keyword table
| Keyword | Type | Placement |
|---|---|---|
| wedding website wording examples | Primary | H1, intro, "What Every Wedding Website Page Needs to Answer", FAQ |
| wedding website wording | Secondary | H1, intro, "Where the Wording Lives: Website, Event Page, or Both" |
| wedding website welcome message | Secondary | "Welcome Message Wording: Formal, Casual, Short" |
| wedding website rsvp wording | Secondary | "Wedding Website RSVP Page Wording, With a Deadline and a Stated Consequence" and FAQ |
| wedding registry wording for website | Secondary | "Gift Wording: Registry, No Gifts, and Money Gifts" |
| wedding website faq wording | Secondary | "Wedding Website FAQ Page Wording" |
| how to mention wedding website on invitation | Secondary | "How to Mention Your Wedding Website on the Invitation" and FAQ |
| wedding website our story examples | Secondary | "Our Story Wording" |
| wedding weekend schedule wording | Long-tail | "Wedding Weekend Schedule Wording, With Per-Function RSVP Instructions" and FAQ |
| per-function RSVP wording | Long-tail | "Wedding Weekend Schedule Wording", "Where the Wording Lives" |
| wedding website photo sharing wording | Long-tail | "Photo Sharing Wording: Unplugged Ceremony, Shared Album, After the Wedding" and FAQ |
| asking for money instead of gifts wording | Long-tail | "Gift Wording: Registry, No Gifts, and Money Gifts" and FAQ |
| wedding website dress code wording | Long-tail | "Dress Code Wording, and How to Translate It" |
| when to publish wedding website pages | Long-tail | "When to Publish Each Page" |
Find and connect with guests by name, phone, or email. Manage multi-event schedules with individual RSVP headcounts for each ceremony or gathering, collect shared memories in permanent Moments timelines, and receive blessings through Digital Lifafa wrappers.
Explore Lumhe for FreeDesign a beautiful event invitation in seconds and share it with a link — free, no app needed.
You have a guest count and a card you like. You want one number. The reason you cannot find one is that the Paperless Post cost for a wedding is quoted three di
Here is what to do when wedding guests don't RSVP: work backwards from the earliest final-count date in your vendor contracts, set one guest-facing deadline at
Good birthday invitation wording removes every reason a guest has to not reply yet. A missing end time, an unclear drop-off policy or a vague "RSVP soon&qu