--- title: "Destination wedding website: what to include and when" description: "A destination wedding website carries the whole trip: flights, hotel block, transfers, day-by-day itinerary and an early RSVP. The checklist, with wording." canonical: https://ueventi.com/blog/destination-wedding-website-guide last-updated: 2026-10-15 --- Guide·Oct 15, 2026·6 min read # Destination wedding website: what to include and when A destination wedding website carries the whole trip: flights, hotel block, transfers, day-by-day itinerary and an early RSVP. The checklist, with wording. ![Dvir Atias](/authors/dvir-atias.jpg) Dvir Atias Founder On this page - [What a destination wedding website needs beyond a local one](#what-a-destination-wedding-website-needs-beyond-a-local-one) - [When to launch a destination wedding website](#when-to-launch-a-destination-wedding-website) - [RSVP twice: a soft yes early, a firm yes later](#rsvp-twice-a-soft-yes-early-a-firm-yes-later) - [Privacy: password the site](#privacy-password-the-site) - [Example: Mia and Lucas, Tulum, four days](#example-mia-and-lucas-tulum-four-days) - [Writing for guests who are not sure they can come](#writing-for-guests-who-are-not-sure-they-can-come) - [Frequently asked questions](#faq) A destination wedding website has to do everything a local one does and also act as the trip’s travel agent: which airport to fly into, where to stay and by when to book it, how to get from the airport to the hotel, what happens each day and which of it you are paying for, and what to pack. It needs to go live earlier - ten to twelve months out, before anyone books a flight - and it usually needs two RSVPs: an early “are you planning to come” so you can hold rooms, and a firm one later. Below is the page-by-page checklist, an example itinerary for a four-day wedding in Tulum, and welcome and FAQ wording you can adapt. All of it can be built on the [free wedding website builder](/wedding-website): the travel page, the day-by-day schedule and the [RSVP](/online-rsvp) with a question per event are standard sections, and the site can be password protected in one click, which matters when the villa address is on it. ## What a destination wedding website needs beyond a local one ### A travel page that answers the booking questions - The airports, in order of convenience, with the drive time from each to the hotel. - The host hotel or resort, the group rate, the booking link or code, and the cutoff date in bold. - One or two alternatives at different price points, with a line on how far they are from the venue. - Transfers: whether you are arranging a shuttle, what rideshare and taxis are like, whether to rent a car. - Passport and visa notes, the currency and whether cards are widely accepted, plug type, and the time zone. ### An itinerary by day, hosted vs on your own Guests are giving you a long weekend and a flight. The kindest thing you can do is tell them, by day, what is planned, what is hosted and what is on their own dime, and where the free hours are. Use the words “hosted” and “on your own” plainly. The [schedule examples](/blog/wedding-website-schedule-examples) include a four-day layout. ### Weather, packing and dress Say what the weather does in that month, what the ceremony surface is (sand, grass, stone) and what shoes work, and whether evenings need a layer. Then give each event its own dress line; the [dress code wording](/blog/wedding-website-dress-code-wording) has beach formal and garden party versions. ### What to do nearby Three restaurants you love, one beach or walk, one thing worth a half-day. Not a guidebook - a short list that makes the free afternoon feel hosted. Guests will use it more than you expect. ### A way to reach you, and a way to reach each other A WhatsApp group for the weekend, or at least one phone number that is not yours - a sibling or the planner. Put the number on the site and in the final reminder message. The [sharing guide](/blog/how-to-share-your-wedding-website) covers using the invitation message to carry it. ## When to launch a destination wedding website Earlier than a local one. A local site goes live before the save-the-dates, typically eight to twelve months out. A destination site should be live ten to twelve months out with the travel page finished first, because the first thing guests do after the save-the-date is look at flights. The schedule can say “details coming” for a while; the hotel block and its cutoff cannot. The general timeline is in [when to make your wedding website](/blog/when-to-make-your-wedding-website). Months before What the site must have 12 Date, place, host hotel with group rate and cutoff, airports, a short welcome, early RSVP 9 Day-by-day itinerary with hosted vs on your own, transfers, passport and currency notes 6 Dress by event, packing list, nearby recommendations, registry page if you have one 3 Firm RSVP open with per-event questions, final timings, weekend contact number 1 RSVP closed, shuttle times, the WhatsApp group link, a 'what to do if your flight is late' line ## RSVP twice: a soft yes early, a firm yes later Hotel blocks and venue minimums are decided long before a normal RSVP deadline. Ask an early, low-pressure question - “Are you planning to join us? A quick yes helps us hold the right number of rooms” - at the save-the-date stage, then open the real RSVP, with meal and per-event questions, about three months out. Make it clear that a yes on the early question does not book a room. With Eventi, both can go out as a message with Yes and No buttons, and the reminders to people who have not answered stop the moment they do; see [how reminders stop](/blog/reminders-that-stop-when-guests-answer). The firm deadline should still land three to four weeks before the wedding, per the [RSVP deadline guide](/blog/wedding-rsvp-deadline), or earlier if the venue needs it. ## Privacy: password the site A destination site usually contains a villa or private-resort address, a day-by-day schedule of when everyone is out of their rooms, and sometimes the hotel block code. That is more than a local site reveals. Eventi sites are hidden from search engines by default; for a destination wedding, add the password too, and put it in the invitation message and on the printed save-the-date. The [password ideas](/blog/wedding-website-password-ideas) post has rules for picking one guests can type on a phone at an airport. ## Example: Mia and Lucas, Tulum, four days Sixty guests, a beach ceremony on Saturday, everyone flying in through Cancun. Their site uses the Mediterranean design and has five pages: Welcome, Travel, Schedule, FAQ, RSVP. The schedule page reads: Day Plan Hosted? Thursday Arrivals. Shuttle from Cancun at 2 and 6. Casual drinks at the beach bar from 8. Drinks on us, dinner on your own Friday Free morning. Welcome party on the sand at 6, tacos and music, flat shoes. Hosted Saturday Ceremony at 5 on the beach, cocktails at 5:45, dinner and dancing under the palapa until late. Hosted Sunday Farewell brunch 10 to 12. Cenote trip at 1 for anyone staying another night. Brunch hosted, cenote on your own Monday Shuttle to Cancun at 9 and 1. Shuttle hosted Their welcome message, adapted from the [welcome examples](/blog/wedding-website-welcome-message-examples): > We are getting married in Tulum on Saturday, April 18, and we would love for you to make a long weekend of it. Everything you need to book is on the Travel page - please reserve your room by January 15 to get the group rate. The Schedule page says what is planned each day and what is hosted. If you have any question at all, text Mia’s sister Ana at the number on the FAQ page. We cannot wait to see you on the beach. Three of their FAQ answers, in the pattern from the [FAQ examples](/blog/wedding-website-faq-examples): > Do I need a passport? Yes - a passport valid for the dates of travel. US citizens do not need a visa for a short stay in Mexico, but check the current rules for your own passport before you book. > Which airport? Cancun. The drive to the resort is about an hour and forty minutes. We are running shuttles on Thursday and Monday at the times on the Schedule page; outside those, the resort can book a private transfer for you. > What should I pack? Light layers, a swimsuit, sandals for the sand and real shoes for the dinner. The ceremony is on the beach, so leave the heels for Saturday night under the palapa. ## Writing for guests who are not sure they can come Not everyone can take four days and a flight, and your site should make a no feel fine. One line in the welcome - “We know this is a trip, and we understand completely if it is not possible” - does more than any amount of logistics. For guests who want to come but cannot afford the host resort, the cheaper alternative on the travel page is the kindness that makes it possible. And if you are doing a celebration at home afterwards, say so: it lets people decline the trip without declining you. The [examples pillar](/blog/wedding-website-examples) has a destination section with four more couples. A destination wedding website on Eventi is free to build and publish with the RSVP included, and it can be published in more than one language if your guest list needs it. The only paid parts are a one-time custom domain and, if you want them, invitations delivered as WhatsApp or SMS messages with reply buttons, which is the channel most guests on a trip actually read. ## Frequently asked questions ### How early should a destination wedding website go live? ### Should a destination wedding website have two RSVPs? ### Should I password protect a destination wedding website? ### How do I say which events are hosted and which are not? ### Can guests RSVP to each day separately? [ ← Previous 22 wedding party bio examples for your website ](/blog/wedding-party-bio-examples)[ Next → 10 wedding website schedule examples to copy ](/blog/wedding-website-schedule-examples)