Planning
What to Put on Your Wedding Website (With Examples)

A wedding website exists to answer guest questions before they text you. Get these nine sections right and your phone stays quiet: the essentials (who/when/where), schedule, travel, dress code, RSVP, registry, FAQ, your story, and the hashtag.
The 9 sections guests actually use
- The essentials: your names, date, city — visible without scrolling
- Schedule: ceremony and reception times and addresses (link to maps), plus any welcome drinks or day-after brunch
- Travel & stay: nearest airport, hotel block with booking code, parking and transport
- Dress code: spell it out with examples — "cocktail: suits or jumpsuits, no jeans" beats "semi-formal"
- RSVP: the deadline and how to reply (see when to send invitations)
- Registry: linked, never itemized on the invitation itself
- FAQ: kids policy, plus-ones, weather plan, photos policy
- Your story: short and warm — three paragraphs, not thirty
- Hashtag & photo sharing: your wedding hashtag and a shared-album link
What to leave OFF
- Exact home addresses (yours or your parents') — privacy first
- Adults-only wording that singles anyone out — keep it general in the FAQ
- Anything you'd be uncomfortable with a coworker reading; the link travels
- Registry pricing pressure — list a range of price points quietly
Timing
Publish a simple version with your save-the-dates (6–8 months out), and complete it before invitations go out (6–8 weeks out). Password-protect it if you're sharing personal details.
Every question your website answers is a text you never receive.
When should our wedding website go live?
Should we password-protect our wedding website?
Do we put the registry on the invitation or the website?
While guests read your website, keep your side organized too — the free Everplanner dashboard tracks the countdown, budget and RSVPs in one place.
Put it into practice — free
No sign-up, no cost. Your plan saves privately on your device.
Open the free checklist

