Eventually Ticketing
Sharing Your Events

Public event page indexing and SEO

Published public event pages at /e/:id are crawlable and indexable by search engines. Each page emits a canonical URL, Open Graph and Twitter card tags, and schema.org Event structured data, while the widget embed shell remains excluded from indexing.

Canonical public page and the widget embed shell

The hosted public event page at /e/:id is the canonical URL for every event. When you share an event on social media or in email campaigns, use the /e/:id link so search engines and social platforms treat it as the authoritative page.

The widget embed shell at /w/:uuid is always marked noindex. It is meant for embedding on your Squarespace site, not for direct sharing or search indexing.

Share the /e/:id link, not the widget embed URL, when you want the event to appear in search results or generate a rich social preview.

Public event pages may display a cookie consent banner for visitors in certain regions. The banner does not affect search indexing or structured data. For details, see Cookie consent and preference center.

Which events can be indexed

An event is indexable only when all of the following are true:

  • It is published, or it is a draft with a scheduled publish time that has already passed.

  • It is not pre-sale hidden.

  • The team is not in demo mode.

Events that do not meet all three criteria are still viewable if they are public, but they carry a noindex tag and are omitted from the sitemap.

The following event states are never indexed:

  • Completed events — the page remains viewable as read-only history, but it is noindexed.

  • Cancelled events.

  • Draft events without a past scheduled publish time.

  • Pre-sale-hidden events.

  • Events on a demo team.

Sitemap

A real sitemap is available at /sitemap.xml on your app host. It lists only indexable public event pages, using the event’s lastmod timestamp. The sitemap is cached for one hour and capped at 50,000 URLs.

Social sharing and structured data

Indexable public event pages emit the following metadata in the page head:

  • Canonical URL — points to /e/:id.

  • Open Graph tags — og:title, og:description, og:url, og:type (website), og:site_name (Eventually), and og:image when an event image is present.

  • Twitter card tags — twitter:title, twitter:description, twitter:image when present, and twitter:card as summary_large_image if there is an image, otherwise summary.

  • schema.org Event JSON-LD — includes the event name, URL, start and end dates, event status, attendance mode, location, organizer, and public ticket offers. For virtual events, the structured data uses the public event page URL rather than the join link. Add-on and gated tiers are excluded from the offers array.

Non-indexable events skip the JSON-LD structured data and instead carry a noindex meta tag.

What this means for sharing

When you share an event link in social posts, email campaigns, or SMS, use the public event page URL (/e/:id). The page will generate a rich preview with the event title, description, and image if available. Completed events still open for attendees who want to view details, but they will not appear in search results or generate structured data.

For more about finding and sharing event links, see Sharing a direct event link. For details on what attendees see when they open the page, see What attendees see when they register.

Was this helpful?