Put your wedding website password beside the website address on a details card, or send it privately if you want tighter control over who receives it. Before approving invitations, check three separate settings: password access, search-engine visibility, and the platform’s couple directory. Then test the complete guest journey while signed out.
A beautiful invitation can still leave guests stuck at a login screen. The opposite problem is easier to miss: a couple may hide their website from search results but leave the schedule open to anyone with its address. This guide helps you decide what to print, what to share separately, and what to test before mailing.
The cover is an original educational illustration, not a photograph of a product. Platform guidance was checked October 14, 2026; settings and labels can change.
Should you print the password on your wedding invitation?
For a typical guest-only website, printing its shared event password with the URL is a practical option. The recipient has both pieces of information in one place. A separate details card keeps the main invitation focused on the celebration and makes the access instructions easier to find.
However, a printed password travels with the invitation. Anyone who receives a forwarded photograph can read it too. If you are keeping a home address or limited-attendance event especially private, you may prefer to send the password directly to invited households. That adds a communication step, so assign someone to answer access questions.
This is an access decision, not an etiquette test. Choose the approach your guests can actually use and that matches the information you are sharing. A shared event password is also different from your personal account password. Never print the password you use to administer the website.
Three privacy controls that do different jobs
Do not assume a setting labeled “private” covers every way someone might discover or enter your website. Check the following controls separately:
- Password access: Does a visitor have to enter an event password before seeing the protected information?
- Search-engine visibility: Can the site appear when someone searches your names on Google or another search engine?
- Platform directory: Can someone find your celebration through the wedding platform’s own couple or event search?
Google explains that a noindex instruction controls appearance in search results; it does not prevent a person with the link from visiting the content. Password protection addresses access. Hiding a page from search and restricting entry therefore solve different problems.
Zola’s searchability guidance distinguishes search-engine and Zola visibility from the public/private setting. It also warns that search-result changes are not immediate. Do not assume that switching a setting erases information already seen, downloaded, or photographed.
Joy’s privacy documentation describes page-level visibility, an event password, and separate controls for Joy search and outside search engines. Check your actual platform rather than expecting every provider to offer the same controls.
A simple decision worksheet before you order
Write down your answers to these four questions before placing access instructions in the design:
- Who should see the information? All invited households, selected guests, or anyone interested in the celebration?
- What would be uncomfortable if shared? Consider a private residence, travel itinerary, guest contact details, or an event that only some guests attend.
- How will guests receive access? Choose the printed suite, a direct message, or another method your household list supports.
- Who handles problems? Name one contact who can check invitations, resend access information, and record an RSVP by another method.
For example, a couple holding their ceremony at a public venue might print a shared password in every suite. A couple hosting a small dinner at a family home might send those dinner details only to the dinner guests. The second couple does not need to put the dinner address on everyone’s website just because everyone is attending the wedding.
Do not use a single shared password as a substitute for guest-specific invitations. If your platform offers private events, verify what each guest can see. Otherwise, communicate restricted events separately.
Where to place the URL and password
Keep the website address, password label, and response instruction together. A guest should not need to turn over three cards to work out which password belongs to which link. If you use a details insert, give this information its own short block beneath an obvious heading.
For a minimal suite, ask whether your chosen model has space for a readable access line. Do not assume every card supports the same reverse-side printing or layout. Our details-card wording guide helps separate the essential invitation information from supporting logistics.
A QR code can sit beside the access block, but it does not replace the password or explain the next step by itself. Keep a typed address for guests who cannot scan. The QR code and RSVP guide covers scanning and placement; this checklist concerns what happens after the link opens.
Original wording examples you can adapt
Replace every bracketed field below before approving a design. These examples deliberately contain no working password or real couple’s information.
1. Password included in the printed suite
Wedding details and RSVP
Visit [wedding website address]
Website password: [event password]
Please reply by [response date].
2. Password shared directly
Visit [wedding website address] for our schedule and RSVP.
We will send your website access details directly.
Need help? Please contact [designated contact].
Use the second version only if you have a reliable way to reach each household. Send the access details before or when the invitations arrive, not after confused guests begin asking.
3. A separate option for guests who prefer to call
Please RSVP by [response date] at [wedding website address].
Website password: [event password]
You may also reply by calling [designated contact number].
4. A private sharing reminder
We are sharing these details with our invited guests.
Please keep the website address and password within your household.
The last example is a courteous request, not a technical safeguard. Use it alongside the appropriate website settings, and expect that a recipient could still pass information along.
Test as a guest, not as the website owner
Open a private or incognito window, or ask someone who is not signed into your planning account to test. Joy specifically recommends an incognito check because the browser you used to build the website may recognize you as its owner and skip the password prompt.
Give the tester only the access instructions that a guest will receive. Do not explain missing steps in advance. Ask them to complete this sequence:
- Type the printed website address and confirm the intended site opens.
- Check what information is visible before entering a password.
- Enter the event password exactly as shown on the proof.
- Find the correct event details and RSVP deadline.
- Check the response form using your platform’s preview or a controlled test entry.
- Confirm that unrelated guest details or restricted events are not exposed.
- Find the alternative contact method without asking you where it is.
Repeat the access steps on a phone. Pay attention to line breaks, easy-to-confuse characters, and whether the keyboard introduces a space. Follow your platform’s password rules; do not add a “case sensitive” warning unless you have confirmed that it is true for that platform.
Zola’s password guidance recommends telling guests where to retrieve their password and notes that Zola cannot give it out to them. Your printed contact route can save guests from searching the wrong help desk.
What if the password changes after printing?
Keep one record of the current website address, event password, and the version printed on your invitations. If you change the password, the printed copy will no longer provide current access. Notify invited households directly, explain the replacement clearly, and check that your chosen helper has the same information.
If a guest reports a problem, ask whether the website failed to open, the password was rejected, or their name could not be found in the RSVP form. Those are three different issues. Sending a new password will not fix a mistyped URL or a guest-list spelling mismatch.
Avoid solving access problems by making all event details public without reviewing the consequence. First use the alternate reply method and then correct the actual problem.
Invitation photographs need a separate check
Before posting your invitation online, make a sharing version that removes the website password, scannable code, private address, and any other information you do not want public. Inspect the finished image at full size. Google’s redaction guidance cautions against simply covering text in a document; create and check a final sharing copy rather than relying on an editable overlay.
Ask your photographer and anyone sharing stationery pictures to use that approved version. Printed cards, digital proofs, and public marketing photographs have different audiences. You can enjoy the design without publishing the information guests need to enter a private site.
Finish the access plan before approving your invitation proof
When choosing from LunaInvites invitation card sets, confirm the layout and included pieces for that model. For example, the Tulip Clear Acrylic Wedding Invitation lists a clear acrylic card and a notched pocket sleeve. Do not assume a separate website or RSVP insert is included.
LunaInvites prepares a digital design proof as the approval stage for a physical invitation order. Use that stage to check the access wording, readable URL, and any agreed placement. The website itself and its privacy controls remain with your chosen website provider.
The current shipping policy lists free US shipping and estimated total delivery of approximately 7–8 days after final proof approval, including 2 days of production. This is an estimate, not a guarantee. Finalize and test website access before approving the proof so that the delivery timeline does not become your deadline for fixing a broken guest journey.
Final check: The right people can enter, the intended details stay behind the chosen controls, and every guest has a clear way to ask for help. Once those three conditions are met, the access line is ready for the invitation design.