What is an event permalink?

An event permalink is the preferred, direct web address for one specific event. It is the link a host copies into an invitation, a reminder, a profile, or a post-event recap so every guest reaches the same source of truth. “Permanent” does not mean the event details can never change. It means the address is intended to remain the dependable way to reach that event while its practical information is updated.

A permalink identifies one event

Think of a permalink as the event’s street address on the web. The title tells people what the event is; the permalink tells a browser exactly where to go. A good event permalink points to one leaf page, rather than a calendar homepage, a search result, a message thread, or a temporary preview. That makes it useful when a guest returns later to check the start time, location, agenda, or registration status.

Unique event pages are also useful for the web’s event systems. Google’s event structured-data guidance calls for a unique URL for each event and asks that the page focus on that single event. That is a technical guideline for eligible event markup, not a promise that a page will appear in search. For hosts, the everyday benefit is simpler: one link prevents guests from wondering which version of the invitation is current.

What hosts use a permalink for

Once an event has a direct address, use that same address wherever the event appears. Send it in the first invitation, add it to calendar reminders, place it in a social post, and include it in any follow-up about a changed time or venue. Guests who saved the link can return without searching through an old conversation. A co-host can share the same page without recreating the details in another tool.

A permalink is not the same as a tracking link, a draft-only preview, or a general collection page. Tracking parameters can be useful for measurement in some contexts, but the guest-facing default should be the clean direct address. Google recommends URL structures that are logical and intelligible to people, and advises trimming unnecessary parameters that do not change content. Google’s URL-structure guidance is a good reason to copy the clean event link rather than a long, altered variation.

Events change. A workshop may move rooms, add a supply list, clarify its beginner level, or switch from a waitlist to available spots. Those are reasons to update the page, not to create a second invitation with a new address. Keeping the existing permalink lets every guest, bookmark, and shared message continue to lead to the revised information.

That long-lived expectation is the point behind the term permalink. The W3C’s classic guidance says that useful URIs should not change simply because the material behind them changes, because people may have bookmarked or shared the older address. “Cool URIs don’t change” is a helpful principle for a small event too: preserve the route guests already know, then improve the information they find there.

How HereNow event permalinks work

HereNow publishes event pages at /e/[slug]. When an event is published, the sharing flow generates a short hn- event code for the slug when one does not already exist. The same slug is used by the public event route, the canonical event path, and—for qualifying public events—the sitemap. When a host edits an existing event, the editor preserves its original slug rather than generating a new one.

This separates the event’s durable address from its headline. You can improve “Sunday Clay Class” into “Beginner Clay: Hand-Building for First-Timers” without needing a new link for every guest. Copy the published page address after you verify it opens correctly, then keep returning to that address when you share or update the event. Visibility is a separate choice: it determines how people discover the page, while the permalink identifies the page they reach.

Keep one canonical link in circulation

A single event can sometimes be reached through copied links, parameter variations, or different site paths. A canonical URL is the preferred representative address among similar versions. Google explains that canonicalization helps select a representative version of duplicate or very similar content, while a site’s canonical preference remains a signal rather than an absolute command. Google’s canonicalization overview explains why consistency helps both people and systems understand which address to use.

The host-facing habit is straightforward: use the clean published event link in every guest message. Avoid making several pages for the same session just because a description, image, or agenda needs a refresh. If the event is genuinely a different session with its own date, capacity, or registration decision, it deserves its own event page and permalink.

An illustrative workshop example

Nora creates a four-person natural-dye workshop from an AI-assisted draft, then publishes the guest-ready page. She copies its permalink into her local maker group, adds the same link to the reminder she sends two days before the workshop, and keeps it in her notes for future questions. When a guest asks whether fabric is included, Nora updates the page and replies with the same address rather than typing a separate explanation into every conversation.

After the workshop, Nora can add a short recap or use the page to point people toward the next session. If she creates a new workshop on a different date, she gives that new session its own page and permalink. The first link remains meaningful because it continues to identify the original gathering and its record.

Use the permalink as a publishing check

• Open the published event link on a phone before sharing it.
• Copy the clean address into the first invitation and reuse it everywhere.
• Update the existing event page when practical details change.
• Create a new event page only for a genuinely separate session.

Make the destination worth returning to by following this event-page writing guide, then use this agenda guide to make the on-page flow clear. When you are ready to make the link, create an event in HereNow, review the guest view, and copy its permalink into your invitation.

Frequently Asked Questions

Is an event permalink the same as an event title?

No. The title is the reader-facing name of the event, while the permalink is its direct web address. A host may refine the title for clarity after publishing, but guests should keep using the same event link unless the platform explicitly tells them that the address has changed.

Should every recurring workshop use the same permalink?

Use one permalink for one specific session. If a recurring workshop has a new date, capacity, registration decision, or agenda, a separate page gives guests a clearer source of truth. Reuse a single permalink only when you are updating the same event record, not creating the next occurrence.

Can I share an event permalink before I have finished the details?

You can share it once the event page is ready for guests, but it is better to check the core facts first: what is happening, when and where it takes place, what guests need, and how to RSVP. If something changes later, update the existing page and resend the same link where appropriate.