--- title: "When to make your wedding website: a timeline" description: "Make your wedding website before the save-the-dates go out, usually 8 to 12 months ahead. What to add at each stage, a 6-week version, when to close RSVPs." canonical: https://ueventi.com/blog/when-to-make-your-wedding-website last-updated: 2026-10-15 --- Guide·Oct 15, 2026·6 min read # When to make your wedding website: a timeline Make your wedding website before the save-the-dates go out, usually 8 to 12 months ahead. What to add at each stage, a 6-week version, when to close RSVPs. ![Dvir Atias](/authors/dvir-atias.jpg) Dvir Atias Founder On this page - [The short answer: before anything is printed](#the-short-answer-before-anything-is-printed) - [What to have on the site, month by month](#what-to-have-on-the-site-month-by-month) - [The six-week version](#the-six-week-version) - [What can stay “coming soon”](#what-can-stay-coming-soon) - [What to do if you are already late](#what-to-do-if-you-are-already-late) - [After the wedding](#after-the-wedding) - [Frequently asked questions](#faq) Make your wedding website before the save-the-dates go out, which for most couples means eight to twelve months before the wedding, as soon as the date and the city are set. It does not have to be finished to be useful: a site with your names, the date, the city and a “details coming soon” line already does its job, because guests will book flights and request time off against the date long before they need the schedule. Build it early, fill it in as you confirm things, and let it be the one place that is always current. Below is what the site should hold at each point in the engagement, a compressed version for a six-week timeline, and what to do with it after the wedding. Building takes about twenty minutes with the [free wedding website builder](/wedding-website), and every edit is live as soon as you save, so there is no cost to starting early. The [step-by-step guide](/blog/how-to-make-a-wedding-website) covers the build itself. ## The short answer: before anything is printed The site address goes on the save-the-date, so the site has to exist first. Most couples send save-the-dates six to nine months before a local wedding and nine to twelve months before a destination wedding. Work backward from that: pick the [site name](/blog/wedding-website-name-ideas), publish the first version, and only then order the cards. A name chosen after printing is the most common reason a wedding website link stops working. ## What to have on the site, month by month Time before the wedding What the site should have What can wait 12 months Names, date, city, a one-line welcome, the site name chosen and published Everything else 9 months Venue with address, nearest airports, hotel block with the cutoff date, save-the-date goes out with the link Schedule times, dress code, registry 6 months Schedule with times, dress code, the FAQ first draft, registry page, our story if you want one Shuttle times, final menu 3 months RSVP turned on with the deadline, invitations sent with the link, wedding party page, shuttle and parking Nothing major 1 month RSVP deadline passes; reminders go to anyone who has not replied; final details confirmed on the schedule Seating chart work moves to its own tool The week of An updates line at the top for weather, timing changes and day-of contacts; the schedule double-checked Thank-you page After Thank-you note, the album, a request for guests' photos; the site stays up and stays free Nothing ### Twelve months out: names, date, city You know three things and that is enough. Publish with the Envelope or Garden design and the AI’s first draft of the welcome, and write “Schedule and travel details coming soon” where the rest will go. Guests who hear the news will search for the site; make sure what they find is yours. Switching designs later keeps your text, so the choice is not final; the [template gallery](/wedding-website/templates) is the place to browse. ### Nine months out: travel first Out-of-town guests need the hotel block and the airports before they need the ceremony time. Add the venue address, the hotel names with the booking code and the cutoff date in bold, and the drive times from the airports. This is the version of the site the save-the-date points to. For a wedding abroad, the [destination wedding website guide](/blog/destination-wedding-website-guide) covers passports, currency and which meals are hosted. ### Six months out: the schedule and the FAQ Now the day has a shape. Add the schedule with times and places, the dress code in one line, and the FAQ with the questions you have already been asked. The [FAQ examples](/blog/wedding-website-faq-examples) and [schedule examples](/blog/wedding-website-schedule-examples) are built to be adapted in an afternoon. The registry page goes up now too, before anyone asks; see [how to add a registry](/blog/how-to-add-a-registry-to-your-wedding-website). ### Three months out: RSVP on, invitations out Turn on the [RSVP](/online-rsvp) with the deadline and the follow-up questions you need, then send the invitations with the link. If Eventi sends them as WhatsApp or SMS messages with reply buttons, answers start arriving the same day and reminders go automatically to anyone who has not replied. The deadline itself is covered in [when your RSVP deadline should be](/blog/wedding-rsvp-deadline); three to four weeks before the wedding is the usual answer. ### One month out: close the RSVPs The deadline passes. Send one final reminder to the holdouts, then call the three people who still have not answered. Give the caterer the count. Move the seating work to the [seating chart maker](/seating-chart-maker), which reads the yes list directly. ### The week of: an updates line Add a short section at the top of the home page for anything that changes: the rain plan, a shifted start time, the phone number of whoever is handling logistics. Guests will check the site on the day; make it the source of truth so nobody relies on an old text thread. ## The six-week version Short engagements compress the same steps. The order still matters: the site first, then the invitations. - Week 1: publish the site with names, date, venue and the hotel block. Skip the save-the-date; the invitation does both jobs. - Week 2: schedule, dress code, FAQ. Turn on the RSVP with a deadline two weeks before the wedding. - Week 2, same day: send the invitations with the link, by WhatsApp or text so they arrive immediately. The [WhatsApp walkthrough](/blog/how-to-send-wedding-invitations-on-whatsapp) is the fastest path. - Week 4: reminders to anyone who has not answered. With Eventi they are automatic. - Week 5: deadline. Final count to the caterer, seating chart done. - Week 6: updates line on the home page; the wedding. ## What can stay “coming soon” Almost everything except the date, the city and the RSVP deadline once you have one. Guests forgive a placeholder schedule; they do not forgive a wrong date. Use the placeholder honestly - “We will add ceremony times in March” is better than a blank section - and update the line when you do. Keep the story, the wedding party page and the photo album for whenever you feel like writing them, with the [our story examples](/blog/wedding-website-our-story-examples) as a starting point. ## What to do if you are already late If the invitations have gone out and there is no site yet, build it today and send the link in a short message: “All the details and the RSVP are now at ueventi.com/sites/emma-and-james.” Guests who already replied by phone or card can be marked in the guest list by hand, and everyone else gets the one-tap version. A site that arrives late is still better than a dozen separate texts about parking in the final week, and the [sharing guide](/blog/how-to-share-your-wedding-website) covers the message wording. ## After the wedding The site has a second life. Within a week, add a thank-you note at the top and a line asking guests to share their photos. When the album comes back, post it. Leave the site up: it costs nothing on Eventi, the hidden-from-search default still applies, and a year later it is the easiest place to find the photos. If you prefer to take it down, unpublishing is one click and the name is released. The single rule under all of this: the site exists before anything is printed, and it is edited rather than rebuilt. A site that goes up at twelve months with three facts on it will be the most useful page of the whole wedding by month three. For what each page should hold, see [what to put on your wedding website](/blog/what-to-put-on-your-wedding-website). ## Frequently asked questions ### How far in advance should I make my wedding website? ### Can I send save-the-dates before the website is done? ### When should the RSVP open on the wedding website? ### What if we have a short engagement? ### Should I take the wedding website down after the wedding? [ ← Previous How to share your wedding website: every channel ranked ](/blog/how-to-share-your-wedding-website)[ Next → Wedding website dress code wording, by dress code ](/blog/wedding-website-dress-code-wording)