Skip to content

[event name] [city] / [topic] meetup [city]

Events pages

Events pages answer searches shaped like "[event name] [city] / [topic] meetup [city]", such as "data engineering meetup tulsa". Someone deciding whether to go. When, where, who is speaking, and how to register. The pattern suits service firms and product companies. Every page needs 9 things its siblings don't have, starting with name, and Heddle rates its doorway risk as low.

What you get: events pages only for searches people in your market actually make, each with facts of its own, so none reads as a copy of another. We measure the searches before anything is written, and a page missing anything listed below isn't published.

low doorway riskEvent, one node per session with a stable @id, its own share card, and the same node on every page that lists itceiling 80%

Who is searching

Someone deciding whether to go. When, where, who is speaking, and how to register. After the day, someone who missed it, or who is deciding whether the next one is worth it, wants to know what actually happened.

What every page needs

A row missing any of these is skipped by heddle validate. It isn't published thin.

  • nameThe event's own full name, as its organiser writes it; a third-party event takes its organiser's full name in the title.
  • startLocal time with its offset, 2026-09-18T18:00:00-07:00. A bare timestamp gets rewritten in UTC and moves an evening event to the next day.
  • endSame form as start. Search Console reports an Event without one.
  • zoneIANA timezone of the venue.
  • venueName and address of the place, or 'online'.
  • organizerWho runs it. If the company sponsors or attends someone else's event, the organizer is them and the company is the sponsor, never the organizer.
  • descriptionWhat the session is about, in two or three sentences.
  • performersSpeakers by name. Search Console reports an Event without a performer.
  • registrationWhere to register while there are seats; removed once the event is past.

What the family shares

By design, every page in the family carries the same sections (the group or series; venue directions; how to propose a talk). Everything else comes from the row.

How the pages link

Series or chapter page lists every session (with its Event node, not a bare link); the events index carries every node; a feed (events.json or RSS) lists them for anyone syndicating.

What to avoid

  • The company as organizer of an event it sponsors or attends.
  • A recap that summarises the deck instead of telling the day.
  • Offers or a register button on an event that has happened.
  • Attendance, reactions or questions nobody recorded.
  • Photos that are not of the session.

Doorway risk

Heddle rates this family's doorway risk as low, for the reason its spec gives. Each event is a real occurrence with its own date, place and speakers. The risk is mechanical instead. Markup that renders correctly to a person and is broken for a machine, which the events check holds. Heddle's uniqueness check fails any built page whose eight-word sentences repeat on its siblings beyond 80%.

Questions

What should a events page include?

A page goes out only when its row has name, start, end, zone, venue, organizer, description, performers and registration, the parts a template can't write. The family shares the group or series, venue directions and how to propose a talk.

Can events pages be doorway pages?

Heddle rates the risk as low. Each event is a real occurrence with its own date, place and speakers. The risk is mechanical instead. Markup that renders correctly to a person and is broken for a machine, which the events check holds. Built pages are checked against their siblings, and one whose eight-word sentences repeat beyond 80% fails.

How should events pages link to each other?

Series or chapter page lists every session (with its Event node, not a bare link); the events index carries every node; a feed (events.json or RSS) lists them for anyone syndicating.

Work with us

Find out if events pages fit your site.

Tell us about your business and who buys from you. On a short call we'll show you the searches your buyers make where you don't show up yet, and what the agents would do about them in their first month.

On the call, for your site

  1. The searches your buyers makeMeasured, with how many people make each one
  2. Where you show up, and where you don'tOn Google and in ChatGPT's answers
  3. The agents' first monthThe pages, fixes and links they would start with

Catalog version ddb1b16