What to Put on Your Wedding Website: Complete Checklist

Put the information guests need to decide, plan, and arrive prepared on your wedding website: the date, location, RSVP, schedule, travel, hotel, transportation, dress code, guest policies, accessibility, registry, and a contact. Your story and photos can make the site feel like yours, but the logistics are what keep your phone from buzzing all weekend.

The Complete Wedding Website Checklist

Build the site in the order guests need it, not the order your template suggests. Start with the home, travel, and hotel pages before save-the-dates, then add the RSVP and detailed schedule as plans become final.

Section	What guests need	When to publish
Home	Names, date, city, short welcome, RSVP button	Before save-the-dates
RSVP	Deadline, invited names, event attendance, meals	Before invitations
Schedule	Dates, start times, locations, dress codes	Before guests book travel
Travel	Airports, driving, transit, passport notes	Before save-the-dates for destination weddings
Accommodations	Hotel blocks, deadlines, alternatives	As soon as blocks are signed
Transportation	Shuttle stops and departure times	Four to eight weeks before
FAQ	Plus-ones, children, attire, parking, accessibility	Start early; update continuously
Registry	Links and a short gracious note	Before shower invitations
Contact	Planning contact and day-of contact	Before invitations
Updates	Dated changes and weather backup	Whenever plans change

Zola’s wedding website guidance defines the site as a guest-information hub and recommends including date, location, lodging, registry, RSVPs, and password protection. That is a useful filter: logistics first, decoration second.

1. Home Page

The home page has one job: confirm the wedding guests have reached and point them to the next action. Keep these essentials above the stories, galleries, and countdown widgets:

• Both names
• Wedding date
• City and state or country
• A short welcome message
• A visible RSVP button when the form opens
• A note telling guests where to find updates

Example:

Welcome! We cannot wait to celebrate with you on September 19, 2027, in Asheville, North Carolina. Use this site to RSVP, book your stay, and find the full weekend schedule. Check back in August for final transportation details.

See 40 wedding website welcome message examples for other tones and wedding types.

2. RSVP Page

Make the deadline and lookup process obvious before asking a single question. A guest who cannot find their invitation needs a contact, while an invited plus-one needs a controlled name field rather than an open “add guest” box.

• The response deadline
• How to search for their invitation
• Whether responses are per household or per person
• How to correct a name or response
• Who to contact when the form does not work

Collect only what the wedding needs. Our guide to 25 wedding RSVP questions covers meals, allergies, shuttles, access needs, weekend events, and plus-one names.

3. Schedule

Show each guest only the events they are invited to attend. For every visible event, include enough detail to get them from the hotel door to the right seat:

• Full event name
• Day and date
• Start and end time
• Full address
• Dress code
• Arrival guidance
• Transportation note
• Whether food is served

Do not publish private events to guests who are not invited. Use guest-specific visibility if the platform supports it, or communicate those events separately.

Example:

Welcome Drinks
Friday, September 18 · 7:00–9:00 p.m.
The Foundry, 12 River Street, Asheville
Smart casual. Heavy appetizers and drinks will be served. Shuttle departs the Grand Hotel at 6:35 p.m.

4. Venue, Directions, and Parking

Include the full street address even when the venue is famous. Guests are navigating under time pressure, so give them the correct entrance, parking plan, and last-mile instructions:

• Correct map link
• Which entrance to use
• Parking-lot address
• Valet cost or cash requirement
• Walking distance from parking
• Rideshare availability after the reception
• Road closures, gates, or security checks

Never rely on a map pin alone. A rural estate may share a postal address with a service entrance, while a city venue may have different ceremony and parking entrances.

5. Travel

For out-of-town guests, explain the tradeoffs between the available routes instead of listing airport names with no context. Publish this section early enough that guests can use it before buying a ticket:

• Best airport and alternatives
• Approximate drive times
• Train or bus options
• Whether a rental car is useful
• Typical rideshare availability
• Recommended arrival and departure windows
• Links to destination-specific official guidance

For international weddings, direct guests to official government sources for passport, entry, visa, and health requirements. The U.S. State Department international travel checklist recommends checking destination-specific entry requirements and passport validity; the CDC destination directory provides current health guidance.

6. Accommodations

Hotel blocks come with deadlines, fees, and assumptions that can cost guests money. For every block, spell out:

• Hotel name and address
• Booking link
• Group code
• Discounted rate or rate range
• Booking cutoff date
• Deposit and cancellation basics
• Shuttle availability
• Accessibility contact

Offer at least one alternative when the block is expensive, small, or far from public transportation. The guide to sharing hotel block information gives you copy-ready wording for rates, deadlines, deposits, and shuttle tradeoffs.

7. Transportation

Post exact shuttle information when it is final, and add an expected confirmation date before then. “Transportation provided” creates more questions than it answers; a route table lets guests plan.

Route	Departure	Pickup point	Return
Grand Hotel → Venue	3:15 p.m. and 3:35 p.m.	Main lobby doors	9:30 p.m., 10:30 p.m., 11:30 p.m.
Venue → After-party	11:35 p.m.	North gate	One-way

Say whether seats must be reserved and what happens if a guest misses the last shuttle. A vague “transportation will be provided” creates more questions than it answers.

8. Dress Code

Name the formality level, then translate it into clothing and venue realities. Guests care as much about grass, heat, and religious-site coverage as they do about whether the label says cocktail or formal.

Garden cocktail: Cocktail dresses, jumpsuits, suits, and dressy separates are welcome. The ceremony is on grass, so block heels or flats will be easiest. Evenings can be cool; bring a light layer.

Add venue-specific facts:

• Grass, sand, gravel, or cobblestones
• Religious-site coverage requirements
• Typical temperature
• Whether the event is outdoors
• Any color request, phrased as a request rather than a rule

9. FAQ

Your FAQ should hold the questions that do not deserve their own page but still change a guest’s plan. At minimum, answer:

• When and how to RSVP
• Plus-one policy
• Children policy
• Dress code
• Arrival time
• Parking and transportation
• Accessibility
• Weather backup
• Dietary restrictions
• Social-media or phone policy
• Registry
• Day-of contact

Use our 30-question wedding website FAQ to copy the answers that apply.

10. Registry

The website makes registry information available without making it the focus of the invitation. Emily Post’s registry etiquette guidance recommends sharing it by word of mouth and on the wedding website, not on the wedding invitation.

Write one gracious sentence:

Celebrating with you is the best gift. For those who have asked, our registry and honeymoon fund are linked below.

Our wedding registry wording guide includes wording for physical gifts, cash funds, experiences, charities, and no-gift weddings.

11. Accessibility and Inclusion

Guests should not have to disclose a disability just to learn whether they can enter the building. Publish the access facts you already know and give one private contact for anything else:

• Step-free route
• Accessible parking
• Elevator details
• Accessible restroom availability
• Seating accommodations
• Service-animal policy if the venue has special procedures
• Quiet room or sensory notes
• Captioning or interpretation when provided
• A private contact for other needs

Use plain statements, not “contact us if you have special needs.”

12. Day-of Contact and Updates

List someone other than the couple and say what that person can help with. This is also where dated changes should live, so guests can tell the current plan from an old screenshot.

Day-of questions: Contact our planner, Jordan, at (555) 010-0148. Please do not call the couple on the wedding day; their phones will be off.

For a change, add a dated update at the top of the relevant page and message affected guests directly:

Updated September 18 at 2:00 p.m.: Saturday’s ceremony will take place inside the Garden Hall. Guest arrival time and parking remain unchanged.

What Not to Put on the Website

More information is not always more helpful. Leave out anything private, unconfirmed, or likely to confuse guests:

• Home addresses unless needed for an event
• Personal phone numbers that should not be public
• Private events visible to uninvited guests
• Detailed gift expectations
• Jokes that obscure a policy
• Unconfirmed plans presented as final
• Long biographies before essential logistics
• Travel or legal advice copied from an unofficial source

Consider password protection when the site contains guest names, private event details, travel itineraries, or personal contact information.

When to Build and Update the Website

The site does not have to be complete before it goes live. Publish the decisions guests need now, then use these milestones to add detail without posting guesses as facts:

1. Before save-the-dates: Home, date, city, travel basics, hotel block.
2. Before invitations: RSVP, schedule, dress code, FAQ, registry.
3. At the RSVP deadline: Reminders, contact corrections, event counts.
4. One month before: Transportation, parking, final arrival guidance.
5. One week before: Weather plan, emergency contact, final reminders.
6. After the wedding: Thank-you message, photo-sharing instructions, registry link only if still useful.

Even a complete website will not stop every guest from texting you. Daisy Chat can answer those questions from the current pages and send targeted updates when the parking, weather, or shuttle plan changes.

Frequently Asked Questions

What information is essential on a wedding website?

At minimum, include the couple's names, date, city, RSVP instructions and deadline, event schedule, venue address, dress code, travel and accommodation details, parking or transportation, guest policies, registry link, and a contact for questions.

When should we create our wedding website?

Create a basic site before sending save-the-dates. It only needs the date, city, travel basics, and hotel information at first. Add the RSVP form, full schedule, FAQ, dress code, and registry before invitations are mailed.

Should the wedding website be password protected?

Use a password when the site includes private names, contact information, travel itineraries, or guest-specific events. A password adds friction, so keep it short, print it clearly on the details card, and test it with someone outside the planning team.

Should every wedding event appear on the website?

Only show each guest the events they are invited to attend. Events open to everyone can appear on the public schedule. Rehearsal dinners, private breakfasts, and other limited events should use guest-specific visibility or direct invitations.

How do we tell guests that wedding website information changed?

Update the website first so it remains the source of truth, add a visible date to the changed information, then send affected guests a text or email with the change and a direct link. Do not expect guests to notice an unannounced update.