How to Host a Private Event on WordPress (Link-Only)

To host a private event on WordPress with Eventonomy, open the event, set Who can see this event to Private (only people with the link), save, and send guests the event’s address. The event drops out of every list, calendar and search on your site, search engines are told to ignore it, and anyone who opens the link can read the page and RSVP.

That last part is the one to read twice. Private here means link-only. It is not a guest list, and it is not a login wall. If you came looking for “only the people I invited can get in”, this post will tell you where the line sits so you can decide whether it’s enough.

Public, link-only, and login-required are three different things

When people say “private event” they usually mean one of three setups, and mixing them up is how an event ends up more exposed than the host expected.

Public means listed. The event shows in your archive, the calendar, search results and the feeds, and search engines can index it.

Link-only means unlisted but reachable. Nothing on your site points to the event, but the page loads for anyone who has the address. Think of an unlisted video: it isn’t hidden from a person holding the URL, it just isn’t advertised.

Login-required means reachable only after signing in. That’s a gate, and it’s a different mechanism from hiding something from listings.

Eventonomy’s Private setting is the middle one. Since version 1.8.0 it works this way by design: before that, a private event was invisible to everyone except managers, which meant a guest with the link got a 404 and couldn’t RSVP. A private event nobody could answer wasn’t much use.

What a link-only event hides

Once you save an event as Private, these things change for the public:

• It’s left out of the events list, the archive and the calendar views.
• It doesn’t appear in site search.
• It’s kept out of the public event feeds and the REST API’s public lists, so a visitor browsing your site, or a script paging through your events, won’t turn it up.
• The event page carries a noindex and nofollow instruction, so search engines are told not to list it.

The docs page on link-only events has the full table of what changes. The short version: if someone doesn’t have the address, there’s no route on your site that leads them to it.

What it still exposes

This is the honest part, and it matters more than the list above.

Anyone who has the link can open the event. No account, no password. If a guest forwards the message, pastes it into a group chat, or posts it somewhere, everyone who sees it can open the page and RSVP. Eventonomy can’t tell an invited guest from a guest’s cousin, because there’s no list of invited people to check against.

Noindex is a request, not a lock. Well-behaved search engines respect it. It doesn’t stop a person from sharing the page, and it doesn’t make the page secret from anyone who already has the address.

It isn’t a secure or invite-list feature. There’s no per-person invitation, no approval step, and no “only these email addresses” rule. If your event needs a real guest list, you’ll want to cap places, screen RSVPs yourself, or put the event behind a sign-in (more on that below).

So link-only is the right tool for “I don’t want this on my public calendar”, like a team dinner, a client preview, a school reunion or a wedding weekend. It’s the wrong tool for anything where a stranger turning up would be a real problem.

Set it up and share the link

The setup takes under a minute.

1. Open the event in the editor.
2. In the Visibility panel, find Who can see this event.
3. Choose Private (only people with the link).
4. Publish.

Then copy the event’s permalink and send it yourself, by email, a message or a printed invitation. Before you send anything, open the link in a private browser window to see what a guest will see. Check the page doesn’t show details you’d rather keep off a forwarded link, like a home address you only want confirmed guests to have.

If you build the page ahead of time, keep it as a draft while you and the host review it, then publish it as Private when the invitations go out. A draft private event still isn’t viewable by the public.

How RSVPs and the guest link work

Guests RSVP with a name and email. Eventonomy emails each one a private link to view, change or cancel their answer later, so nobody needs an account to say “actually, we can’t make it”. That link lasts seven days by default, and a guest can ask for a fresh one from the RSVP block. A developer can change the lifetime with the evnm_magic_link_ttl filter.

Two things worth knowing. The guest’s own link is separate from the event link: it manages one person’s RSVP, not the whole event. And the event link is still the key to the event page, so the earlier caveat applies: forward it and the next person can RSVP too.

If you’re running something with a headcount, our RSVP feature page covers party sizes, custom questions and the waitlist, and the wedding page walks through the same Private setting for an invitation-style flow. For paid or capped events, see how event registration handles places, and how the waitlist behaves when a date fills up.

The calendar file and search engines

An add-to-calendar download is still available on a private event, through the links on the page. Those links carry a private key, because the calendar file is addressed by the event’s number, and numbers are easy to count through. The key means someone can’t pull down private events’ calendar files just by trying 41, 42, 43. It’s a small detail, but it’s why a link-only event doesn’t leak through the calendar route.

On the search side, the page tells crawlers not to index or follow it, as covered above. If you’ve ever shared the address somewhere public before switching the event to Private, search engines may already know about it, so don’t rely on switching it afterwards to pull it back.

When link-only isn’t enough

If you need only signed-in people to open an event, Eventonomy has a developer filter for it, evnm_private_event_requires_login. It’s a code-level switch, not a setting in the editor, so it suits a site where someone can add a few lines of PHP. By default the filter is off and the link is enough.

For a members-only community, the better answer is usually to put the event inside the community space it belongs to, where the community’s own access rules apply. The communities page shows how events work with BuddyPress and BuddyNext. That’s a different mechanism from the Private setting, with its own purchase and setup, so read it before assuming it behaves the same way.

And if you need a true invite-only list, with approvals or named guests, that isn’t something the Private setting does. Treat the link as the invitation and plan around that.

A quick checklist before you send the link

• Open the event in a private window and read it as a stranger would.
• Remove anything from the page you wouldn’t want a forwarded link to reveal.
• Decide what happens if the link spreads: do you have a capacity limit or a waitlist ready?
• Send the link only to the people you mean to invite, and tell them it isn’t for sharing.
• Test one RSVP yourself, then use the guest link to change it, so you know what guests receive.
• If you’re using check-in on the day, see the check-in guide for how to match arrivals against RSVPs.

Link-only is a simple, honest tool: it keeps an event off your public pages and out of search, and leaves the rest to the people holding the link. Used for what it is, it works well.