When should the wedding website go live?
As soon as the core facts are settled: date, venues, dress code. The page's advantage is that you fix things by editing once, so guests always see the current version. Publish when it is true rather than when it is perfect.
Do guests need an account to reply?
No. They open the link you sent, say yes or no, add names within your limits, and leave. Nothing to install and no password of their own to remember, which is exactly why the reply rate beats a group chat.
Can we keep parts of the site private?
The whole site can be password-protected, with the password shared in the invitation message. Useful when the link circulates beyond your guest list. Anything you would rather not publish, like vendor choreography or surprises, simply does not go on the page.
How much of the schedule should be public?
Everything guests take part in: arrival, ceremony, meals, and roughly when it ends. Rows they can scan in one scroll. The getting-ready timeline, the speeches you would rather not preview, and the send-off plan are yours to keep off the page.
What if the venue or timeline changes after we share the link?
Edit the page. Everyone who opens it afterwards sees the corrected version: no reprinting, no re-messaging the whole list. For guests who already screenshotted the old details, send one short note pointing at the changed line, and the page does the rest.