Guides
Wedding Website Information Checklist: Public Details and Private Invitations
In this guide
A wedding website should answer general questions; a personal invitation should carry details intended for a particular guest. Put the public story, broad programme and travel guidance on the website, while keeping replies, individual seating and private team information in the appropriate invitation or workspace.
Before you start
Decide what anyone with the public address may see. Prepare approved wording and images, and keep private contacts, internal schedules and sensitive guest data out of public blocks.
Steps
- Open the wedding website editor and add a concise welcome, the programme you are ready to publish and practical travel information.
- Write useful FAQ answers: arrival time, dress guidance, transport arrangements and whom invited guests should contact for clarification.
- Use the supported language blocks you can actually maintain. Current wedding content and interface support should be checked separately from the language of this guide.
- Use “Save draft”, then “Preview”. Review the page as a visitor and inspect every link and image before using “Publish”.
- Send each invited person their intended personal invitation separately. Recheck the public page after any major programme change.
Filled example
Invented public copy: “Ceremony 16:00; reception from 17:00. Please use the north entrance. The last arranged shuttle departs at 23:30.” Keep “Nina’s table is Orchard 4”, her meal choice and the team’s loading instructions off this public page. The personal invitation can show only the details actually published for Nina.
Check the result
Open the published address in a context without your organizer session. Check what is visible publicly, whether the programme is current and whether individual actions lead to the intended invitation rather than exposing a shared guest list.
Limits and common problems
Saving a draft does not update the public site. A personal invitation is not an interchangeable public link. Do not promise automatic translations or a live custom domain until its setup is confirmed. If information changes, review both the public text and relevant private invitations.