What to Put on Your Wedding Website: The Complete 2027 Checklist

Your wedding website needs nine things: your names and wedding date, the ceremony and reception details, a full schedule of events, travel and accommodation information, a working RSVP form, an FAQ section, registry links, a dress code, and clear contact information for questions. Everything else is optional. Get those nine right and your guests will stop texting you.

This guide is for couples planning a 2027 wedding who have locked in a date and venue and are now figuring out what actually goes on the site. It’s written page by page, so you can work through it in order. There’s a copy-paste checklist at the end.

Key takeaways

Seven core pages cover almost every wedding: Home, Our Story, Events, Travel, RSVP, FAQ, and Registry.

The FAQ page does the heaviest lifting. Most of the questions guests text you are answerable in one line each.

Your RSVP form should collect eight to twelve data points. Not four, and not thirty.

Launch date works backward from your invitations, not your wedding day. The URL gets printed on them.

What you leave off matters as much as what you include: home addresses, guest contact details, and anything a search engine shouldn’t index.

The 9 things every wedding website must have
The 7 core pages
Every RSVP field worth collecting
The FAQ questions guests actually ask
Optional pages worth adding
What NOT to put on your wedding website
Destination and multi-day weddings
When to launch each part
The technical checklist most couples skip
Free platform vs. built-for-you
Your copy-paste checklist
Skip the DIY stress
FAQ

The 9 things every wedding website must have

If you do nothing else, do these.

Your names and the wedding date, visible without scrolling
Ceremony details: venue name, address, start time
Reception details: venue, address, start time, and whether it’s the same place
A full schedule: welcome drinks, rehearsal dinner, ceremony, reception, next-day brunch
Travel and accommodation: nearest airport, hotel blocks, parking, transport
An RSVP form, with a deadline stated on the page
An FAQ section: dress code, kids, plus-ones, timing, parking
Registry links, or a clear, gracious note if you don’t have one
A way to reach you: one email address, not your personal phone numbers

Here’s when guests actually look for each of these, which is why the order on your homepage matters:

Element	Why it matters	When guests look for it
Names + date	Confirms they’re on the right site	Immediately, every visit
Ceremony & reception details	The two facts they can’t guess	On arrival, then again the week of
Full schedule	Determines how many nights they book	Within days of the save-the-date
Travel & accommodation	Flights and hotels get expensive fast	4–8 months out, before booking
RSVP form	Your headcount depends on it	Within 2 weeks of the invitation
FAQ	Prevents the text messages	Constantly, and especially the week of
Registry	Guests want to buy the right thing	After they RSVP yes
Dress code	The single most-asked question	2–3 weeks before the wedding
Contact	For the one thing you didn’t anticipate	Rarely, but urgently

Around 74% of engaged couples now build a wedding website (Joy, via Sara Does SEO’s 2026 industry roundup). That means guests arrive with expectations. They have used other couples’ sites, they know where to look for the dress code, and they notice when it isn’t there.

The 7 core wedding website pages (and what goes on each)

Almost every wedding fits into seven pages. Any fewer and guests scroll past what they need. Any more and things start getting lost.

1. Home page: the details guests need in 10 seconds

Your home page has one job: confirm the guest is in the right place, then give them the two or three facts they came for.

Include:

Both first names (and last names, if your guest list includes distant relatives and plus-ones who don’t know you both)
The full wedding date, written out as Saturday, 12 June 2027 rather than 06/12/27, which reads differently in Canada and the UK
City and venue name
A one-line countdown or “we’re getting married” statement
One strong photo
Clear navigation to RSVP and Travel, your two highest-traffic pages

Leave off:

Long welcome paragraphs. Nobody reads them.
Autoplaying music. This is 2027.
The full address of anything, at the top of the home page. It belongs on the Events page, where it has context.

Pro tip: Test your home page on a phone with the screen brightness turned down, standing up, in under ten seconds. That’s the actual usage context: a guest checking a detail in a car park. If they can’t find the date and venue in that state, restructure.

2. Our Story: how to write it without it being unreadable

Optional in theory, expected in practice. Older relatives genuinely read this page, so it’s worth twenty minutes. Keep it to 200–400 words.

A structure that works:

How you met (2–3 sentences)
One specific, true, slightly unglamorous detail. This is what makes it readable.
The proposal (3–4 sentences)
Why this venue or this date means something
3–6 photos with captions

What to avoid: a year-by-year timeline. It reads as a CV. One good anecdote beats eight chronological entries.

3. Events & Schedule: every event, not just the ceremony

The most common wedding website mistake is listing only the ceremony. Guests booking flights need to know whether there’s a welcome dinner on Friday and a brunch on Sunday, because that’s the difference between a two-night trip and a one-night trip.

For each event, list:

Field	Example
Event name	Welcome Drinks
Date and day	Friday, 11 June 2027
Start time (and end, if known)	7:00 pm – 10:00 pm
Venue name	The Fisherman’s Arms
Full address	12 Harbour Road, Portland, ME 04101
Who’s invited	All guests / Immediate family only
Dress code for that event	Smart casual
Any note	Drinks and canapés, no formal dinner

That “who’s invited” row prevents the most awkward conversation in wedding planning. State it plainly on the page and no one has to ask.

If your ceremony and reception are in different places, add travel time between them and say whether transport is provided. If it isn’t, say that too, so guests can arrange it.

4. Travel & Accommodations: the page that saves you 40 text messages

Guests travelling in will visit this page four or five times. Make it exhaustive.

Getting there:

Nearest major airport, with the drive time to the venue
Secondary/regional airport if it’s often cheaper
Nearest train station
Whether a rental car is necessary or a mistake (parking!)
Rideshare availability in the area, which is genuinely useful in rural venues where it collapses after 10pm

Where to stay:

Hotel blocks with the booking code and, critically, the date the block is released. Hotels commonly release blocked rooms four to six weeks before an event, so guests who book late find the rate gone.
Two or three price tiers. Not every guest can absorb the $340/night option.
Any accommodation actually walkable from the reception, flagged clearly
A note on Airbnb/VRBO availability if the area is limited

Parking and transport:

Whether parking exists at each venue and whether it’s free
Shuttle times, pickup points, and last departure
Whether cars can be left overnight, which is the difference between one drink and none

5. RSVP: the highest-stakes page on the site

Every other page is informational. This one is operational. Your caterer’s headcount, your seating chart, and your final invoice all trace back to it.

The page needs:

A clearly stated RSVP deadline, in the same sentence as the form
A guest-name lookup, so people can’t accidentally RSVP for someone else
An explicit yes/no, not just a “yes” button. Silence isn’t a decline, and you need to know the difference.
Confirmation on screen and by email, so guests don’t submit twice
A working mobile layout. Most RSVPs come in on a phone, often at odd hours.

Set your deadline three to four weeks before the wedding, which is the window where guests actually know their own schedules. For destination weddings, push to five or six weeks, since travel bookings take longer to lock in. Check it against two things before publishing: your caterer’s final headcount date, and your hotel block release date. The RSVP deadline has to fall before both.

6. FAQ: where 90% of guest questions get answered

This is the page that decides whether your phone goes quiet. Full list of what to include in the FAQ section below.

The format that works: question as a heading, answer in one or two sentences. Not paragraphs. Guests scan.

7. Registry: how to handle it without awkwardness

If you have one:

Link directly to each registry, one line each
Say how many there are, so guests know they’ve seen them all
If you have a cash or honeymoon fund, name what it’s for. “Toward our honeymoon in Japan” lands very differently from a bare payment link.
Include a shipping address only behind the registry’s own system, never printed on the page (see what not to put)

If you don’t:

One warm sentence is enough. Your presence is the gift, truly. If you'd like to do something anyway, a donation to [cause] would mean a lot to us. Then stop.

Never: put registry links on the home page, or in the invitation. The website is the correct and only place for them.

Every RSVP field worth collecting (and three to skip)

Under-collecting means chasing people. Over-collecting means abandoned forms. Here’s the balance:

Field	Required?	Why you need it	What it feeds
Guest name (from your list)	✅ Always	Prevents duplicate and rogue RSVPs	Guest list reconciliation
Attending: yes / no	✅ Always	Silence ≠ decline	Headcount
Number in party	✅ Always	Plus-ones and family units	Headcount, seating
Which events attending	✅ If multi-event	Welcome dinner counts differ from reception counts	Per-event catering
Meal choice	⬜ If plated service	Your caterer needs it 2–3 weeks out	Catering order
Dietary requirements & allergies	✅ Always	Safety, not preference	Catering, place cards
Email address	✅ Always	Confirmations and last-minute changes	Guest comms
Song request	⬜ Optional	Genuinely improves the dance floor	DJ brief
Accommodation: booked / need help	⬜ If out-of-town guests	Lets you flag block availability	Travel support
Shuttle: yes / no	⬜ If shuttles run	Determines vehicle count	Transport booking
Note to the couple	⬜ Optional	Older guests love this field	Nothing, but it’s kind

Three fields to skip:

Home addresses. You collected these for invitations already, on a separate list. Don’t duplicate personal data into a web form.
Phone numbers, unless you have a specific plan to use them. Collecting contact data you won’t use is a liability, not an asset.
Open-ended “anything else?” as a required field. It generates volume you have to read and act on.

The meal-choice trap: if you offer meal selection, you’re committing to tracking it per guest through to place cards. If you’re doing family-style or buffet service, don’t ask. You’ll create work for yourself that the caterer doesn’t need.

The FAQ questions guests actually ask

Copy this list, delete what doesn’t apply, answer in one or two lines each. Twenty-eight questions, grouped.

Dress code and appearance

What’s the dress code?
Is it indoors or outdoors? (This is really a shoes question.)
Are there colours we should avoid?
Is the ceremony on grass, sand, or gravel?
What’s the weather usually like then?

Timing 6. What time should I arrive? 7. What time does the ceremony actually start? 8. How long is the gap between ceremony and reception? 9. What time does it end? 10. Is there anything on the day before or after?

Guests and invitations 11. Can I bring a plus-one? 12. Are children invited? 13. Is there childcare on site? 14. Who’s invited to the welcome dinner? 15. My partner’s name isn’t on the RSVP, what do I do?

Getting there and staying 16. Where exactly is the venue? 17. Is there parking? 18. Is transport provided, and from where? 19. What time does the last shuttle leave? 20. Can I leave my car overnight? 21. Which hotel should I book? 22. Is there a room block code?

Food and drink 23. What food is being served? 24. Can you accommodate dietary requirements? 25. Is there an open bar?

Practical 26. Is the venue accessible / are there stairs? 27. Can I take photos during the ceremony? (State your unplugged-ceremony policy here if you have one.) 28. Who do I contact on the day if something goes wrong?

That last one matters more than it looks. Give a name and number for someone who is not you: a planner, a sibling, the best man. On the day, you should be unreachable.

Optional pages worth adding

Wedding party

Photos, names, and one line each on how you know them. Guests genuinely use this to identify who to ask for help. Keep the descriptions short and equal in length, because unequal ones get noticed.

Photo gallery

Engagement photos work well. Resist the 60-image dump; twelve good images load faster and read better. Every image needs alt text, both for accessibility and because guests on bad venue wifi will see the alt text before the photo.

What to wear

If your dress code is anything other than “black tie,” a dedicated page removes ambiguity. Show, don’t define: three or four example outfit images communicate “garden party formal” more effectively than any paragraph. Explicitly state footwear guidance for outdoor ceremonies.

Things to do in the area

For destination or out-of-town weddings, this page turns a wedding into a weekend. Six to ten recommendations: coffee, one casual lunch, one nice dinner, one walk or view, one rainy-day option.

Livestream and remote guests

If you’re streaming the ceremony, this page needs the link, the exact start time with time zone, and a short “what to do if it drops” note. Publish the link a week in advance so people can test it.

Kids, plus-ones, and the policies nobody wants to write

Write these once, on the website, in plain language, and let the site deliver the message. We're keeping our celebration to adults only, with the exception of immediate family is a complete answer. Having it on the page means you don’t have to say it out loud twenty times.

Password-protected and private pages

Useful for exact addresses, wedding party logistics, family-only events, and any detail you’d rather not have publicly readable. If you have a large guest list, one shared password is the practical option, since per-guest logins create more support requests than they prevent.

What NOT to put on your wedding website

Most checklists skip this part entirely. Your wedding website is a public web page, and it’s worth treating it like one.

Never publish:

Don’t include	Why
Your home address	It’s on a public page, tied to a date you’ll be away from home
Guests’ addresses, phone numbers, or emails	Their data, not yours to publish
Bank details, e-transfer addresses, or payment handles	Use the registry’s own system, always
A photo of your invitation suite	It typically contains your address and the RSVP link in full
Anything about the ceremony’s exact location if you’re keeping it private	Put it behind a password instead
Your travel dates for the honeymoon	Same reason as the home address
Vendor complaints or planning drama	It’s public and permanently indexable
Gift language that reads as an instruction	“No boxed gifts” causes more offence than it prevents

Two things worth checking that aren’t obvious:

1. Search indexing. By default, most wedding websites are crawlable, which means searching your names can surface your wedding date, venue, and schedule. If you’d rather it wasn’t, the site needs a noindex directive and a robots.txt rule. Ask whoever builds your site to confirm this. It’s a one-line change that becomes very difficult to reverse after the fact, because search engines cache.

2. Ads and vendor promotion. Free wedding website platforms are free because they monetise somewhere, and that usually means sponsored registry placements, vendor recommendations, and marketing emails to the guests who RSVP. Before you publish, view your site in an incognito window on a phone and scroll to the very bottom, where the promotional content tends to sit. If your guests are being shown sponsored offers underneath your ceremony details, decide now whether that’s acceptable to you.

Guest data is worth a separate look. When someone RSVPs on a free platform, they’re often creating a record in that platform’s marketing database. Check the privacy policy of whatever you’re using and see what it says about guest information. It’s a five-minute read, and most couples have never done it.

Destination and multi-day weddings: what changes

Wedding type	Additional pages/sections needed
Destination	Visa and passport requirements, currency notes, local SIM/data advice, airport transfer options, a “what the weather is actually like” section, recommended arrival and departure days
Multi-day	A per-day schedule page, separate RSVP per event, dress code per event, “who’s invited to what” stated plainly
Multicultural / multi-faith	An explainer of ceremony traditions and what guests should expect or do, attire guidance per ceremony, and the site in more than one language if part of your guest list needs it
Long weekend / holiday date	Early flight-booking guidance, a note that hotels sell out, and a clear “we recommend arriving Friday” line

For destination weddings, add one thing to your Travel page that most couples forget: a recommended flight-booking-by date. Guests will thank you and your room block will fill.

When to launch each part of your wedding website

The single most common timing error is building the site around the wedding date. Build it around your invitations instead, because your URL gets printed on them, and the site has to be live and correct before they’re mailed.

Save-the-dates typically go out six to twelve months ahead. Invitations follow six to eight weeks before the wedding, with a three-to-four week RSVP deadline behind them. Working from that, here’s the timeline:

When	What needs to be live
9–12 months out	Domain secured. Basic page: names, date, city, “details to come.”
8–10 months out	Full site live for save-the-dates: home, story, events, travel, FAQ
6–8 months out	Hotel blocks and booking codes added; travel page fully detailed
3–4 months out	Registry links added; dress code confirmed; FAQ expanded
6–8 weeks out	RSVP form live before invitations mail. Everything on the site must be final.
3–4 weeks out	RSVP deadline. Chase non-responders.
1–2 weeks out	Final logistics posted: shuttle times, parking, contact person for the day
Week of	Front-load the day-of details on the home page. This is the site’s highest-traffic week.
After	Thank-you note, photo gallery, and a decision about how long to keep the site online

Working backward: if your invitations mail 8 weeks before the wedding, and you want a couple of weeks of buffer to proof the site, your website needs to be finished around 11–12 weeks before the wedding day.

If you’re building it yourself, start earlier than that. Most couples badly underestimate how long the copywriting takes, and the copy is the slow part, not the design.

The technical checklist most couples skip

Free platform vs. built-for-you: an honest comparison

Free platforms are genuinely good, and for a lot of couples they’re the right answer. If your wedding is soon, your budget is tight, or you enjoy building things, use one. This comparison exists so you can make the choice deliberately rather than by default.

	Free platform	Paid subscription platform	Done-for-you build
Cost	$0 (domain often extra)	~$150–$300/year	One-time, typically $500–$1,500+
Who does the work	You	You	A designer
Time you spend	10–25 hours	10–25 hours	Roughly one form
Design	Template, shared	Template, better-looking	Custom to your wedding
Ads to guests	Usually yes	Usually no	No
Guest data	Often feeds platform marketing	Varies, read the policy	Stays with you
Support	Help centre	Help centre + email	A person who makes the edit
After the wedding	Site persists with ads, or lapses	Ends when you stop paying	Depends on the provider
Best for	Tight budgets, short timelines, simple weddings	Couples who want polish and don’t mind subscriptions	Couples with a specific visual identity, or no time

The honest summary: if your invitations are custom and your wedding has a specific look, a template will not match it, and that mismatch is visible to every guest who receives both. If your wedding is more relaxed about that, a free platform is genuinely fine and you should not feel bad about it.

Your copy-paste wedding website checklist

Paste this into your notes app and work down it.

CORE PAGES
[ ] Home: names, full date, city, venue, one photo, nav to RSVP + Travel
[ ] Our Story: 200–400 words, one good anecdote, 3–6 captioned photos
[ ] Events: every event: name, date, time, venue, address, who's invited, dress code
[ ] Travel: airport + drive time, train, rental car advice, rideshare reality
[ ] Accommodation: 2–3 price tiers, block codes, BLOCK RELEASE DATES
[ ] Transport: parking, shuttles, pickup points, last departure, overnight cars
[ ] RSVP: deadline stated, guest lookup, explicit yes/no, mobile-tested
[ ] FAQ: 15–28 questions, one-line answers
[ ] Registry: direct links, honeymoon fund named, no shipping address on page

RSVP FORM FIELDS
[ ] Guest name (matched to your list)
[ ] Attending yes / no
[ ] Number in party
[ ] Which events
[ ] Meal choice (only if plated)
[ ] Dietary requirements & allergies
[ ] Email
[ ] Song request
[ ] Shuttle yes / no
[ ] Note to the couple

DO NOT PUBLISH
[ ] Home address
[ ] Guest contact details
[ ] Bank / payment handles
[ ] Photo of the invitation suite
[ ] Honeymoon travel dates

TECHNICAL
[ ] Custom domain, registered in your name
[ ] Mobile tested on a real phone
[ ] Photos compressed, under 3s load
[ ] Alt text on every image
[ ] Contrast readable by an 80-year-old
[ ] Every link tested
[ ] HTTPS on
[ ] noindex confirmed (if you want privacy)
[ ] RSVP export tested
[ ] Post-wedding plan decided

TIMING
[ ] Domain secured 9–12 months out
[ ] Site live 8–10 months out (for save-the-dates)
[ ] Site FINAL 11–12 weeks out (before invitations print)
[ ] RSVP deadline set 3–4 weeks out (5–6 for destination)
[ ] RSVP deadline is BEFORE caterer cutoff and hotel block release
[ ] Day-of details posted the week of

Skip the DIY stress: How We at FavoredReply handles everything

Everything above is a real list of tasks. Most couples spend somewhere between ten and twenty-five hours on it, usually in the same months they’re also choosing a caterer and negotiating a seating chart.

FavoredReply is the version where you don’t do it. You fill in one short form with your names, date, venue, a link to your photos, and any inspiration you love. A designer then builds the whole site around your wedding. Not a template with your photos dropped into it, but a design made from your moodboard.

What’s included is roughly the checklist above: the seven core pages, a full RSVP system with meal choices, dietary notes, plus-ones and multiple events, a custom domain registered in your name, and hosting through your wedding day and six months after. No ads are ever shown to your guests, and guest data isn’t sold or shared with anyone. It’s one payment, with no subscription running quietly in the background while you plan a wedding.

Signature sites go live in about 21 days; Atelier, which adds a hand-drawn monogram, unlimited pages and password-protected sections, takes 30. When the venue changes the shuttle time three weeks out, you email a person and they make the edit. And when the hosting period ends, the site doesn’t vanish. It becomes a free keepsake page at your own domain, kept online permanently.

Whether that’s worth it depends on how you’d rather spend those twenty hours. Some couples enjoy building the site. If you’re not one of them, that’s the option.

Frequently asked questions

What should be on a wedding website?

A wedding website should include your names and wedding date, ceremony and reception details, a full schedule of events, travel and accommodation information, an RSVP form with a stated deadline, an FAQ section, registry links, and the dress code. Seven pages typically cover all of it.

When should I create my wedding website?

Create your wedding website eight to ten months before the wedding, so it’s live when save-the-dates go out. It must be completely finished about eleven to twelve weeks before the wedding, because your URL gets printed on invitations that mail six to eight weeks ahead.

Do I need a wedding website if I’m sending paper invitations?

Yes, the two work together. Paper invitations carry the formal announcement and the URL; the website carries everything that changes, like shuttle times, hotel availability, and last-minute logistics. Printing all of that on paper is expensive and impossible to correct.

Should my wedding website be private?

If you’d rather your wedding date, venue, and schedule weren’t publicly searchable, yes. That requires a noindex directive plus password protection on sensitive pages. Confirm with whoever builds your site, since search engines cache pages and the setting is difficult to reverse afterwards.

How many pages should a wedding website have?

Most weddings need seven pages: Home, Our Story, Events, Travel, RSVP, FAQ, and Registry. Destination and multi-day weddings often add two or three more, including things to do, per-day schedules, and password-protected pages for family logistics.

What should the RSVP deadline be?

Set your RSVP deadline three to four weeks before the wedding for a local celebration, or five to six weeks for a destination wedding. Check it against two dates first: your caterer’s final headcount deadline and your hotel block release date. It must fall before both.

Do free wedding websites show ads to guests?

Often, yes. Free platforms typically monetise through sponsored registry placements, vendor recommendations, and marketing emails sent to guests who RSVP. Check your site in an incognito window on a phone and scroll to the bottom, where promotional content usually appears.

What happens to a wedding website after the wedding?

It depends on the platform. Subscription-based sites go offline when you stop paying, and free sites often stay up indefinitely with ads attached. Decide before you build whether you want a permanent keepsake version, since migrating a site afterwards is far harder than planning for it.

The short version

What to put on your wedding website comes down to nine essentials across seven pages, one well-built RSVP form, and a short list of things to deliberately leave off. Get the FAQ page right and your phone stops buzzing. Get the timing right, building backward from your invitations rather than your wedding day, and you avoid the most stressful version of this task entirely.

Work through the copy-paste checklist above at whatever pace suits you. It’s designed to be finished in stages, not in one evening.

And if you’d rather hand the whole thing to someone else, including the design, the RSVP system, the domain, the hosting, and the person who makes the edits when your venue changes something, that’s what FavoredReply does. One form, one payment, live in about three weeks.