Event pages on BrightStar are generated automatically the moment you publish, with SEO optimization built into the structure rather than bolted on afterward. You don't start from a blank page — the layout, meta tags, and schema markup are already in place, drawn from the details you entered when you set up the event. This article goes deeper into how each part of that page comes together: what's actually on it, how the SEO pieces work, what happens when someone shares it, and how the URL is built. Where there's room to override a default, that's noted too.
What's on an event page?
Every BrightStar event page is built from four sections, in the same order, whether it's a single evening of kirtan or a week-long retreat. The hero at the top carries your event image, the title, date, and location, and a call-to-action button that takes a visitor straight to tickets — often the first thing people see from a shared link or a search result, which is why uploading an image at the recommended 1920x1080 size matters; it keeps the crop clean instead of awkward.
Below that sits the details section: your full description, which supports HTML so headings and formatting carry through, a schedule if the event runs across multiple sessions, and an embedded venue map so people can see where they're going before they commit. The tickets section lists whichever ticket types you've made available, their pricing and remaining availability, and opens the checkout modal when someone is ready to buy. Last comes the organizer section, showing your name and logo, contact information, and social links — often the only part a returning attendee reads, since they already know the event and just want to confirm it's really you running it.
None of these blocks are forced to appear. The schedule only renders when there's day-by-day itinerary data behind the event, and accommodation options show up only once rooms have actually been defined, so a simple one-off gathering doesn't end up with empty sections on the page.
How does BrightStar handle SEO automatically?
Behind every event page, BrightStar fills in the meta tags that search engines and social platforms read before a person ever loads the page itself. The og:title comes from your event title, og:description is pulled from the first 160 characters of your description, og:image comes from your event image, and a canonical URL points back to the event page so there's one authoritative version of it. If you want more control, meta_title and meta_description let you override those defaults outright, and you can set a custom canonical URL as well.
The default title isn't just the raw event title — it's built in order from the event title, a short date, the city, and then the BrightStar brand name, which is why a well-named event usually reads correctly without you touching anything. The default description strips out markup and truncates near 155 characters at a word boundary rather than mid-sentence; if there's no description at all, it falls back to a generated line naming the event, the place, and the date.
Alongside the meta tags, BrightStar generates JSON-LD schema markup automatically — Event schema, Offer schema for the tickets, Place schema for the venue, and Organization schema for the organizer — so none of it needs to be added by hand. The schema type is picked from the event's category, so a kirtan or sound-healing listing is emitted as a music event rather than a generic one, and the offer schema carries the lowest price among your non-add-on ticket types along with an in-stock or sold-out status.
What happens when someone shares your event page?
When your event page gets shared, each platform reads different pieces of the same meta data. Facebook picks up og:image, og:title, and og:description; Twitter uses twitter:card with a large twitter:image; and LinkedIn reads the structured event data directly. The page itself carries share buttons for Facebook, Twitter, LinkedIn, email, and copy link, plus a one-click iCal download so someone can add your event to their calendar without leaving the page.
The image in that preview has a fallback chain behind it, which matters if you haven't uploaded a banner. BrightStar tries the uploaded banner first, then the cover image, then a presenter's headshot, then the photo of the first linked artist that has one, and only falls back to the site's default image if none of those exist. Relative image paths are rewritten to absolute URLs before any of this happens, because several messaging apps won't fetch a relative one, and the image is declared at 1200 by 630.
What does your event URL look like?
Every event page lives at a predictable address: https://brightstarevents.com/events/{organizer_slug}/{event_slug} — for example, https://brightstarevents.com/events/sunrise-yoga/summer-retreat-2025. Because that full path can be unwieldy to say out loud at a door table or print on a flyer, BrightStar also provides a short URL in the form https://bstar.events/xyz123, pointing to the same page and easier to hand someone in person.