Wedding website examples, page by page.

A standard wedding website needs six pages; destination weddings need eight. The six core pages are home, our story, schedule, RSVP, registry and FAQ. Unlike standard wedding websites, destination wedding websites require two additional pages: travel and accommodations.

The best wedding website examples are ones you can click through. The Aisle site gallery has ten: ten designs for the same wedding, the weekend of Aisle's founders, Walt and Perrie, above Merano in South Tyrol. The details stay the same and only the layout changes.

These are custom-built design examples, separate from the templates in the Aisle editor, and the gallery is read-only. For a complete guest site with a schedule, RSVP, room details, dress code, registry and travel chapters, open the example wedding website, where you can also try other templates and colors.

A wedding website should include six core pages: home, our story, schedule, RSVP, registry and FAQ. A destination wedding adds travel and accommodations, each as its own page.

A guest should be able to tell what the wedding is, when and where within thirty seconds. Use the checklist below to test your own draft.

A welcome message sits under your names on the home page. Keep it to two or three sentences that say what is happening, when and where, and point to the next step: the RSVP or, for a wedding abroad, the travel page. Sample wording for an invented couple, Maya and Theo:

• Plain: "We're getting married on Saturday, June 12, 2027, in Mallorca, and we hope you can come. This site has the schedule, where to stay and how to get here. Please RSVP by May 1."
• Warm: "Three days in Mallorca with our favorite people in one place. Start with the travel page, book a room, then tell us you're coming."
• Formal: "Together with their families, Maya and Theo invite you to their wedding on Saturday, June 12, 2027."

The destination wedding RSVP guide covers choosing a reply date and wording your RSVP request.

Keep the page around it simple: one wide photo of the place and no gallery, or every essential on one long page (date, location, airport, hotel block, dress code, RSVP).

The our story section says how you met and how you got here, with a few photos. Write how you met and got engaged in about eighty words, in your own voice. Choose a few moments and give each a detail only the two of you would know. Or tell it twice, one line from each of you. Sample wording for both:

• One short paragraph: "We met in line for coffee on Theo's first day at a new job. Maya let him go ahead, and he was late anyway. It took him a month to ask her to dinner and one evening to burn it. Since then: two apartments, one loud cat and a lot of Sunday walks that end at the same bakery. Theo proposed on one of those walks, with the ring in a paper bag beside the croissants."
• One line each: "Her version: he was late and blamed the coffee line. His version: she let me go ahead of her, so this is technically her fault."

An about us section introduces each of you to the guests who have only met one of you. A pair of short bios does it, a few lines each, and they read better when you write each other's. Sample wording:

• Maya, by Theo: "Grew up in Chicago, designs book covers and has never arrived anywhere late. First on the dance floor."
• Theo, by Maya: "A civil engineer from Gothenburg who reads the manual first. Makes the best cinnamon buns at this wedding."

A travel page covers flights, the airport and the transfer to the venue. One approach worth copying is to write the transfer three times: for guests who are driving, for guests who are not, and for anyone landing after 10pm. Sample wording, with brackets where your details go:

• If you are driving: "Pick up your rental car at [airport]. The drive to [venue] takes about [time], and parking is at [place]."
• If you are not driving: "Our shuttle leaves [airport] arrivals on Friday at [times]. Add your flight number to your RSVP and we will hold a seat."
• If you land after 10pm: "The shuttle will have stopped. Book a taxi with [company] before you fly and give the driver this address: [address]."

Or replace the written guide with an illustrated map: the hotels and the ceremony site pinned, each pin opening its details.

A destination wedding website has to work as a trip plan as well as an invitation. Travel and accommodations each get their own page, and the schedule covers every day of the weekend. If you are planning a multi-day wedding weekend, a guest's account of one shows how the days ran.

The gallery sites above are all destination examples: a wedding weekend in the Italian Alps. In the example wedding website, look at two chapters. Getting here lists the nearest airports with the route from each, and Where to stay shows a guest their room, dates and check-in time.

One more idea: a countdown to the final RSVP deadline and the last day to book the hotel block at the discounted rate, not to the wedding day. If you are still choosing a builder, see destination wedding website builders compared. For the rest of the planning, see the destination wedding planning checklist.

• Write the schedule in your own words. "Friday: welcome with mezcal" says more than a spreadsheet row, as long as the time and place sit next to it.
• Add a playlist page. The example wedding website has one where each guest adds a song.
• Give every FAQ answer its own link, so a guest can send another guest the exact answer.

For the questions and wording of the FAQ page itself, see wedding website FAQs.

A wedding website's name is the end of its web address. Choose one a guest can read off a printed card and type without asking: two first names or two surnames are easier to spell than a nickname, and a hyphen is one more thing to mistype on a phone.

On Aisle the address is aisle.wedding/ plus the part you choose (maya-and-theo, or mayaandtheo2027): 2 to 63 characters of lowercase letters, numbers and hyphens, with no hyphen at the start or end. An address is refused if another couple holds it, or if it is one of the 40 words Aisle keeps for its own pages, such as registry and faq. Change it later and Aisle keeps your last 8 addresses, each redirecting permanently to the current site.

A custom domain is a separate decision, covered in What wedding website should you use? The wedding website builders comparison covers the builders themselves.

• Burying the RSVP link below the fold where guests miss it.
• Writing an Our Story section that runs 800 words instead of 80.
• Omitting transfer details for destination weddings.
• Skipping the FAQ page or including fewer than ten questions.
• Using a web address with nicknames or unusual spellings guests cannot type from memory.

• A wedding website is a dedicated site where couples share wedding details with guests and collect RSVPs.
• Every wedding website needs six core pages: home, our story, schedule, RSVP, registry and FAQ.
• A destination wedding website requires two additional pages: travel and accommodations.
• The our story section should be about eighty words written in your own voice.
• A guest should understand what the wedding is, when and where within thirty seconds.
• Name your wedding website something guests can read off a printed card and type without asking.