Nine questions, nine finished answers

Wedding website FAQ examples, and the nine questions guests ask

Updated September 2026Written by the Wedvite founders

A wedding website FAQ answers nine questions: where to stay, plus-ones, children, food, the dress code, arrival and finish times, parking, gifts and rain. Six of the nine belong in their own section and one belongs in the reply form, not the FAQ. All nine are written out below, complete, for you to copy and edit.

Build yours free

What questions do wedding guests actually ask?

Nine, in the order a guest's own decisions arrive. Where to stay comes first, because a guest books a room within days of hearing the date. Plus-ones and children come next, because both decide whether a household can say yes at all. Food arrives with the reply. The dress code and the timings are asked a fortnight out, parking the week of, and the weather on the morning itself.

1. Where should we stay?
2. Can I bring my partner?
3. Can we bring the children?
4. I am vegetarian. Will there be something I can eat?
5. Is there a dress code?
6. What time should I get there, and when does it finish?
7. Is there parking?
8. Are you doing a gift list?
9. What happens if it rains?

That order is by urgency, not by frequency. We have not measured which question guests ask most often, and neither has anyone who quotes you a percentage for it — so the sequence here is the one thing about it that can be checked: it follows the decisions a guest has to make, from booking a room to deciding whether to take a coat.

Nine is also the ceiling, not a target. A short wedding at one venue, half an hour from everyone, needs perhaps four of them. The list is here so you can rule questions out deliberately rather than discover one by answering it thirty times, which is how most couples find the gap in their own page. For the sections those answers then sit in, what to include on a wedding website is the companion page, and the wedding website checklist ticks them off one by one.

Does an FAQ section actually stop the messages?

Partly — and the honest version of that sentence is worth more to you than a number. We cannot see your phone, and nobody who tells you an FAQ cuts guest messages by some specific share can see it either; if you find a figure like that, it was invented. What can be checked is the arithmetic, and the arithmetic is the whole argument.

An unanswered question is not one message. It is one message per guest who wants to know, and each one is a thread rather than a line: the question, your answer, a thank you, and often a follow-up because your answer raised something else. Take a hundred guests and a parking question that occurs to one in five — pick your own share, the multiplication is the point. That is twenty threads, and at three or four messages a thread, sixty to eighty messages, arriving in the fortnight you have the least time. Writing the answer once costs you the few minutes it takes to type.

Three things blunt it, and they are why the rest of this page is shaped the way it is. An answer only works if the guest finds it before they start typing, so the list has to be short enough to scan. A vague answer generates more messages than no answer at all: "smart casual" reliably produces "does that mean a tie?" from a dozen people. And an answer filed in the wrong place is a hidden answer — which is the point of the next section.

The one part of this that is genuinely measurable is the reply form, and it is the clearest case on the page. Dietary requirements, meal choices and a coach seat collected as fields arrive as a list you can hand to a caterer. The same three things collected as replies to an FAQ arrive as messages you have to read and transcribe, which is the same work you were trying to avoid, moved later.

What do the nine answers actually say?

Each one below is complete: the question in the words a guest uses, then an answer you can copy and fill in. Everything in square brackets is a blank for you — a hotel, a time, a number — and everything outside them is wording that works as it stands. The children question comes with both versions, because that is the one answer where the two are not variations on each other.

Under each answer is the thing it turns on, which is usually one sentence doing most of the work, and a line saying where the answer actually belongs on your page. Read that line before you paste all nine into a single FAQ block, because only two of them belong there.

1. Where to stay

Asked the week they hear the date

“Where should we stay?”

We have held a block of rooms at [hotel] at [rate] a night, which includes breakfast. Call [phone] or book at [link] and say you are with the [surname] wedding. The rooms are held until [date] and go back on general sale after that, so book before then if you would like one. [Second hotel] is [number] minutes away and usually cheaper, and [area] has plenty on the usual booking sites if you would rather find your own.

The only sentence that matters here is the release date, and it is the one couples leave out. A guest who books on [date + 1] pays more and blames the page. Put the deadline in the same sentence as the rate, and when the block is released, change the text — a page still advertising a block that no longer exists does more damage than a page that never mentioned one.

Belongs in · the Where to stay section. Guests act on this months before anything else on the page, so it should not be sitting under a heading called FAQ.

2. Plus-ones

Asked before they reply

“Can I bring my partner?”

Your invitation names everyone we are able to invite, and the reply form will only let you add that number of people. [Venue] holds [number] people and we are already at that number, so we cannot add anyone beyond the names listed, however much we would like to. Please do not read it as a comment on anyone. If you think we have missed a name by mistake, message [name] on [contact] and we will check.

Two things make this answer work. It points at the invitation and the reply form rather than asking the guest to interpret a rule, and it names the constraint — the room — so the answer is about capacity instead of about the guest. The escape hatch at the end is not softness; it is how you catch the one household whose second name really was missed, before they decide not to come.

Belongs in · the FAQ. This is one of the two that genuinely belong there: it is a question about the invitation rather than about the day.

3. Children

Asked before they reply

“Can we bring the children?”

If the answer is no

We love your children and we have chosen an adults-only evening, so that everyone who comes can properly switch off for one night. The only children there will be [names], who are in the ceremony. We know that means arranging a sitter, and we are telling you now rather than in the invitation so you have as long as possible to sort it out. If it makes the difference between you coming and not coming, please tell us and we will talk.

If the answer is yes

Yes, please bring them. There will be [what] from [time] until [time], and [room] is set aside if anyone needs a quiet half hour or somewhere to feed a baby. Please add every child by name when you reply, so the caterers and the seating plan know about them. High chairs are available, and there is [changing facility] by [location].

Never write "adults preferred" when you mean no. It is the single most expensive phrase on a wedding website: half your guests read it as a polite no and arrange a sitter, the other half read it as a preference and bring a four-year-old, and you find out which at the door. Pick a word that has only one meaning, and if some children are invited and others are not, say that the reply form lists every invited guest by name.

Belongs in · the Children policy section. It changes whether a household can come at all, which makes it too important to be the fifth entry in an FAQ.

4. Food and allergies

Asked the moment they reply

“I am vegetarian. Will there be something I can eat?”

Yes. Tell us when you reply, in the box on the form, and [caterer] will cook a proper alternative rather than the same plate with the meat taken off. If it is an allergy rather than a preference, say so in the same box and name it, and we will pass it to the kitchen ahead of the day so you are not having a conversation about it at your table. The menu we are serving is [courses], and we will publish the final version here by [date].

This is the one answer on the page whose real job is to point somewhere else. Its whole purpose is to make the guest use the field instead of messaging you, so it names the box and says what happens to what they type. Anything vaguer than that produces exactly the messages the FAQ was meant to prevent.

Belongs in · the RSVP form, as a field, not the FAQ. A preference typed into a form arrives as a list you can hand the caterer; the same preference sent as a reply to an FAQ arrives as messages you have to transcribe.

5. Dress code

Asked a fortnight before

“Is there a dress code?”

[Cocktail] — a suit, or a dress you would wear to a good dinner. You do not need [black tie]; nobody will be in a [tuxedo] and you will not feel underdressed. Two practical things: the ceremony is on [grass], so anything that sinks will sink, and we move outside after [time] in [month], so bring a layer you do not mind being seen in. There is no colour to avoid and no colour to match.

A dress code is two answers pretending to be one: the register, and the ground. Name the register in the words a guest can act on, then tell them what the venue will do to their shoes and their shoulders. The last sentence is there to head off a whole genre of message, and if there is a colour you would rather guests avoided, this is where it goes, in one line, without a mood board.

Belongs in · the Dress code section. Guests come back to it more than once, and hunting for it inside an FAQ is the reason they message you instead.

6. Arrival and finish times

Asked a fortnight before, and again on the morning

“What time should I get there, and when does it finish?”

Please arrive between [time] and [time]. The ceremony starts at [time] and the doors close then, so anyone arriving later will be asked to wait until [number] minutes in. Drinks and photographs follow, dinner is at [time], the speeches are around [time] and the dancing starts at [time]. The bar closes at [time] and the last cars leave at [time]. If you can only come for part of the day, [part] is the bit we would hate you to miss.

Two different numbers, and the reason this question is asked at all is that most sites publish only one. The ceremony time is not the arrival time, and a guest who reads 2pm arrives at 2pm. Give the arrival window first, the start time second, and say what happens to a latecomer — that sentence, more than any other on this page, is the one that keeps your ceremony on time.

Belongs in · the Order of the day section, with the arrival time repeated as an FAQ entry, because that is the one guests get wrong.

7. Parking and getting there

Asked the week of the wedding

“Is there parking?”

Yes, [number] free spaces at [venue], first come first served, and cars can be left overnight until [time] the next day. The entrance is [description] and satnavs sometimes send you to [wrong turn] instead, so follow signs for [landmark]. If you would rather not drive, [taxi firm] covers the area on [phone] and is worth booking ahead for the way home, and we have a coach leaving [pickup] at [time] and returning at [time] — add your name to it on the reply form.

The satnav sentence is the one that earns its place. Most venues have a turning that phones get wrong, and every guest who gets it wrong calls someone on the day — usually you, usually while you are being photographed. Name the wrong turn. And if the coach needs numbers, say on the reply form here, so the answer collects the information instead of prompting a message about it.

Belongs in · the Getting there section, which is built for directions, shuttle times and parking together.

8. Gifts

Asked after they have replied yes

“Are you doing a gift list?”

Honestly, having you there is the present, and several of you are travelling a long way to be there, which is plenty. If you would still like to give something, we are putting money towards [thing] and there is [fund] at [link], or [shop] has a small list under [names]. Please do not feel you have to, and please do not bring anything large on the day — we go straight to [place] afterwards and have no way to carry it.

Guests ask this, so answering it is not grasping — but the order of the sentences is the whole etiquette. Release them first, give the route second, release them again. The last line is the practical one nobody writes and everybody needs: if you are leaving for the airport at midnight, say so, or you will spend the end of your wedding finding somewhere to put a boxed dinner service.

Belongs in · the Gifts section, below the practical details. It is the one answer that should be harder to find than the rest, not easier.

9. Bad weather

Asked the morning of the wedding

“What happens if it rains?”

The ceremony moves indoors to [room] at the same time, and nothing else about the day changes. We will decide by [time] on the morning and put the answer at the top of this page, so please check here before you set off rather than messaging us — we will not be looking at our phones. [Month] in [place] is usually around [temperature], and it drops to about [temperature] once the sun goes down, so a layer is a good idea whatever the forecast says.

This answer is only worth writing if you will keep the promise in it. Saying the decision will appear at the top of the page commits you to editing the page on the morning of your wedding, which takes a minute and saves an hour of messages — but a page that says check here and then says nothing is worse than a page that says we will text you. Decide which promise you can actually keep, then write that one.

Belongs in · the FAQ, and then the top of the page on the day itself, which is the one thing a printed programme cannot do.

Take the whole set

All nine questions and answers as one block, in the order above, with every blank still in brackets. Paste it into a document, delete the ones that do not apply to your wedding, fill in the brackets, and move each answer to the section it belongs in.

Which of these questions should not be in the FAQ at all?

Six of the nine, and one of them is not even a question. Guests do not read an FAQ to find the dress code; they look for the dress code, fail to find it, and then read the FAQ as a last resort before messaging you. An answer filed under a heading nobody is looking for is a hidden answer, and folding two thirds of these nine answers into one grey block at the bottom of the page undoes the work of writing them.

Six of the nine have a section of their own: Where to stay, Getting there — which is built for directions, shuttle times and parking at once — Dress code, Gifts, Children, and the Order of the day carrying your timings. Each is a place a guest can aim at, and each keeps the fact in exactly one location, which is the only reliable way to stop two versions of a shuttle time existing. Five of those six leave the FAQ completely; the Order of the day is the one exception, because the arrival time is worth repeating as an FAQ entry and nothing else on the page is.

Food is the sixth to leave, and it is not a question at all. Dietary requirements, a meal choice and a coach seat are fields on the reply form, so they arrive as a list rather than as a conversation, and the online RSVP page covers what the form can collect. That leaves the FAQ holding four entries: two of the nine — plus-ones and the wet-weather plan — the arrival time repeated on purpose, and whatever is peculiar to your wedding, such as a dry venue, a dress code with a cultural expectation behind it, or a ceremony guests have not been to the like of before.

Four to six entries, in other words, which is also what fits on a phone screen without scrolling past the first two. Our checklist of what to include files children, parking and gifts under the FAQ, and on a page that has no section for them that is still the better answer — an answer in an awkward place beats no answer. The rule here is the narrower one: wherever the design already ships the section, the section wins. And if your FAQ is longer than six entries, the fix is almost never editing it down — it is moving three of the answers up into sections of their own.

How do you put an FAQ on your own invitation?

There is no FAQ widget here, and pretending otherwise would waste your time. An FAQ on a Wedvite wedding website is a free-text section — you add "your own section", give it a heading such as Good to know, and type the four questions and answers into the body. You can add up to five of those free-text sections in total, and the reason one is usually enough is the previous section: the dress code, the travel notes, where to stay, the gifts line, the children note and the order of the day each already have a section of their own in the editor, with a heading a guest can aim at.

The reply form does the rest. Its full version collects who is coming, each guest by name, dietary requirements and a meal choice, a song, and whether they need transport to the venue — so the answers above that send a guest to the form can point at a field that is really there. You can see the shape of it on any of the live wedding website examples, or open a design from the template gallery and scroll to the bottom of it.

Then keep editing it. Every answer on this page has a detail in it that will change — a released room block, a confirmed shuttle, a decision made at eight o'clock on the morning about whether the ceremony is outside — and the whole advantage of a link over a printed card is that the same link says something different tomorrow. Guests keep the message they already have.

Building it costs nothing: design the whole invitation, write the FAQ, and your first 10 guests can open it before any money changes hands. Sending it to everyone is $49 at checkout today — $89 list, with the discount running until Oct 31 applied automatically — paid once whatever the guest count, and hosted through your wedding date and at least 90 days after, which matters here because an FAQ is only useful while the page is still up.

FAQ

Questions about writing the FAQ section

How many questions should a wedding website FAQ have?

Four to six, and the number matters less than what is left out. An FAQ only saves you a message if the guest finds the answer faster than they can type the question, and a list of fifteen is slower to scan than it is to ask. The nine answers on this page are a complete set for a typical wedding, but most of them belong in their own section rather than the FAQ, which leaves the FAQ holding the handful that are genuinely questions about the invitation: plus-ones, the arrival time, the wet-weather plan, and whatever is peculiar to your day.

Should the FAQ repeat what the dress code and travel sections already say?

No. Repeating a detail in two places is how the two versions end up disagreeing, and the one a guest happens to read is the one they will act on. Keep each fact in exactly one place and let the FAQ answer only what no section covers. The one defensible exception is the arrival time, because guests reliably read the ceremony time as the time to turn up, so saying it twice is cheaper than a ceremony that starts late.

How do you word an answer when the detail is not confirmed yet?

Say what is true, say when it will be decided, and name the place the answer will appear. "Shuttle times are being confirmed and will be on this page by the end of March" is a complete answer; a guessed time is not, because a guest will plan around it and then be told something different. Never publish a placeholder that reads like a fact, and never leave an old detail up because you have not got round to it — a released hotel block or a changed shuttle time misleads people far more than a blank would.

What if a guest asks something the FAQ does not cover?

Some will, and the FAQ has done its job if there are five of those instead of fifty. Give one named person and one route — a phone number, an email or a message box — and make it someone other than the two of you in the last fortnight. If a question arrives twice, that is not an interruption, it is an edit: add it to the page and the third person will never ask.

Should the answers be written in our voice or kept formal?

Your voice, with one exception. Guests read an FAQ to be told something plainly, and the entries that read like a contract are the ones that get misread — "adults preferred" being the classic. The exception is anything that sets a limit, such as the guest list or a deadline: there, choose the plainest wording you have, even if it feels blunter than the rest of the page, because a limit written warmly reads as negotiable.

Answer it once, not thirty times.

Copy the nine above, put each one where guests will actually look for it, and send a link you can still edit on the morning of the wedding.

Start your invitation

Wedding website FAQ examples, and the nine questions guests ask

Updated September 2026Written by the Wedvite founders

What questions do wedding guests actually ask?

1. Where should we stay?
2. Can I bring my partner?
3. Can we bring the children?
4. I am vegetarian. Will there be something I can eat?
5. Is there a dress code?
6. What time should I get there, and when does it finish?
7. Is there parking?
8. Are you doing a gift list?
9. What happens if it rains?

Does an FAQ section actually stop the messages?

What do the nine answers actually say?

1. Where to stay

Asked the week they hear the date

“Where should we stay?”

Belongs in · the Where to stay section. Guests act on this months before anything else on the page, so it should not be sitting under a heading called FAQ.

2. Plus-ones

Asked before they reply

“Can I bring my partner?”

Belongs in · the FAQ. This is one of the two that genuinely belong there: it is a question about the invitation rather than about the day.

3. Children

Asked before they reply

“Can we bring the children?”

If the answer is no

If the answer is yes

Belongs in · the Children policy section. It changes whether a household can come at all, which makes it too important to be the fifth entry in an FAQ.

4. Food and allergies

Asked the moment they reply

“I am vegetarian. Will there be something I can eat?”

5. Dress code

Asked a fortnight before

“Is there a dress code?”

Belongs in · the Dress code section. Guests come back to it more than once, and hunting for it inside an FAQ is the reason they message you instead.

6. Arrival and finish times

Asked a fortnight before, and again on the morning

“What time should I get there, and when does it finish?”

Belongs in · the Order of the day section, with the arrival time repeated as an FAQ entry, because that is the one guests get wrong.

7. Parking and getting there

Asked the week of the wedding

“Is there parking?”

Belongs in · the Getting there section, which is built for directions, shuttle times and parking together.

8. Gifts

Asked after they have replied yes

“Are you doing a gift list?”

Belongs in · the Gifts section, below the practical details. It is the one answer that should be harder to find than the rest, not easier.

9. Bad weather

Asked the morning of the wedding

“What happens if it rains?”

Belongs in · the FAQ, and then the top of the page on the day itself, which is the one thing a printed programme cannot do.

Take the whole set

Which of these questions should not be in the FAQ at all?

How do you put an FAQ on your own invitation?