What is event visibility?

Event visibility is the publishing setting that determines how people can discover and share an event page. It answers a practical question before promotion or RSVPs: should a guest be able to find this event through public paths, or should they see it only after receiving a link? Visibility shapes the route to an invitation. It does not decide whether the event is welcoming, who is a good fit, or whether sensitive information is protected.

Visibility creates a path to the event

For an independent host, visibility is about matching the page to the invitation plan. A public event page can support broader discovery: it is ready to share in a community post, a profile, a newsletter, or a message that guests may forward. An invite-link or unlisted page is designed for direct distribution, such as a gathering for a known group, a first test of a workshop, or a session shared with prior attendees.

The event itself can be equally real and equally well prepared in either setting. A small ceramics class may need public visibility because its host wants new neighbours to find it. A recurring supper club may need an invite link because the host is sharing it only with people already in the circle. The setting describes the discovery route, not the event’s importance.

Answer two questions before publishing

First, ask how should the right guest find this page? If the answer includes a public recommendation, a community listing, or a search, public visibility is usually the better fit. If the answer is a direct email, group chat, or personal message, an invite link may fit better. Choosing early keeps the event page, promotion plan, and guest expectations aligned.

Then ask what information would still be appropriate if the link travelled farther than planned? A public page should contain the details a newcomer needs to decide and join: the event promise, time, place, price or RSVP terms, capacity, and host context. An invite-link page may use a more bounded distribution path, but it should still be written for a first-time reader and exclude details that would be unsafe or uncomfortable if forwarded.

How visibility works in HereNow

HereNow presents visibility as a publishing choice. A published Public event can be opened by anyone and follows the site’s public indexing path. An Invite link event is published for people who receive its link and is marked with noindex for Google. Both settings can give guests a clear page with the event details and a low-friction RSVP action; the distinction is how the host expects that page to travel.

For public discovery, the technical conditions matter but do not create a promise. Google says a page must be publicly accessible, crawlable, working, and indexable to be eligible for indexing, while also making clear that indexing is not guaranteed. Google’s technical requirements are therefore a useful guide to the mechanics, not a forecast of attendance or search reach. For an invite-link page, Google’s noindex guidance explains why the page must remain accessible to a crawler for that instruction to work.

Visibility is not access control

An invite link should never be treated as a password. Anyone who receives it can open it, and anyone who can open it may forward it. Visibility can reduce intentional public discovery, but it does not make the page confidential. Google explicitly notes that a noindex tag only limits Google Search appearance; it does not stop users from accessing the page.

If information requires a true permission boundary, it needs an appropriate access-control decision rather than a less discoverable URL. The broader security principle is the same: access to a resource should be checked deliberately, not assumed from an identifier or a hidden-looking link. OWASP’s authorization guidance distinguishes access decisions from simple knowledge of a URL. For a host, the practical rule is simple: publish only the location, contact, and guest details you are comfortable being shared.

An illustrative language-exchange choice

Diego hosts a twelve-seat language exchange in a café. For the first session, he wants to invite only people from a local learners’ group while he tests the two-hour format. He creates a guest-ready page with the date, table location, language levels, capacity, and RSVP action, then shares an invite link in the group. He does not add private contact details or a list of attendees because the link could be forwarded.

After a successful first session, Diego wants new learners to discover the next one through the café’s community calendar and friends’ recommendations. He changes his publishing approach: the page is public, its description explains that beginners are welcome, and the registration terms are clear to someone who has never met him. The activity is similar; the visibility choice changes the way a future guest reaches it.

Make visibility a repeatable publishing check

Use the same brief check for every event, whether you start from an AI-assisted draft or write the page yourself:

• Discovery: Do I want guests beyond my direct contacts to find and share this event?
• Details: Would every visible detail be appropriate if the link were forwarded?
• Decision: Can a guest understand the promise, timing, place, and RSVP terms without asking a follow-up question?
• Review: Have I opened the shared page on a phone and confirmed the joining action is obvious?

For help with the page itself, read how to write an event page and how to collect RSVPs without requiring an account. When you are ready to apply the check, create an event in HereNow, choose the visibility that fits its invitation path, and review the guest view before sharing it.

Frequently Asked Questions

Does event visibility decide who is allowed to attend?

No. Visibility determines how a person discovers and opens the event page. Attendance depends on the event’s registration terms, available capacity, and any host process that follows. Make those terms clear on the page so guests understand what happens after they choose to RSVP or register.

Can I use an invite link for a public-facing activity?

Yes, if you want to distribute the invitation directly rather than encourage broader discovery. For example, you might send an invite link to a small mailing list before deciding whether to share a later session publicly. Just remember that the link can be forwarded, so it is not a confidentiality control.

When should I review an event’s visibility setting?

Review it whenever the invitation plan changes: before the first share, when you move from a pilot to a recurring session, or when the location and guest audience change. A short review keeps the information on the page aligned with how broadly you want it to circulate.