Write an Event Landing Page

Drafts registration page copy for webinars, dinners and conferences: headlines, who it's for, takeaways, agenda, speaker bios, FAQ, plus a lean form with consent wording.

Example prompts

Once the skill is added, start a chat with one of these and attach your file if you have one.

  • Write the registration page for our customer roundtable in Austin. Audience is VP Ops at mid-market manufacturers.

  • Tighten these speaker bios to 40 words each and write the FAQ.

  • What form fields should our webinar page ask for, and what's the consent wording for EU registrants?

What this skill does

This skill writes the copy for one event's registration page, section by section: three headline options, a subhead with date, time and time zone, who it's for, concrete takeaways, the agenda, tight speaker bios, logistics and an FAQ. Everything is ready to paste into your registration platform or website builder.

It also recommends the registration form. Each field gets a Required, Optional or Drop call with a reason, plus plain consent wording for marketing opt-in, sponsor sharing and recording. If you paste an existing page, it lists the top issues before rewriting.

When to use it

  • Launching a registration page for a webinar, field event or dinner
  • Writing or tightening speaker bios for an event page
  • Deciding which fields a registration form really needs
  • Adding consent wording for EU and UK registrants
  • Fixing an event page that isn't converting

How it works

  1. 1Collect detailsAsks once for format, date and time zone, audience, takeaways, agenda, speakers and what data the form must capture.
  2. 2Write the topDrafts three headline options and a subhead that shows date, time, time zone and format without scrolling.
  3. 3Write the sectionsAdds who it's for, takeaways, agenda, bios, logistics and an FAQ using only facts you supplied.
  4. 4Design the formRecommends the fewest fields that meet your needs and writes unticked consent checkboxes in plain language.
  5. 5Check and hand overRuns a checklist for invented facts, lengths and consent, then returns a draft for your review.

What you'll need

  • Event title, format, date, time zone and location
  • Audience and the problem the event solves
  • Agenda and speaker details
  • Registration model and the data you need to collect

What you get

Page copy under fixed headings: headline options, subhead, CTA label, who it's for, what you'll learn, agenda, speakers, logistics, FAQ, registration form table with reasons, consent block, meta title and description, a share snippet, and a list of placeholders and open questions.

Tips

  • Put the time zone next to every time on the page, not just in the form.
  • Use 'Request a seat' for approval events so expectations are set before anyone clicks.
  • Capture UTM values in hidden fields instead of asking how people heard about you.
  • Ask one optional question like 'What do you want answered?' and use the answers in your reminders.

What's in the download

  • event-landing-page/SKILL.md7.2 KB
  • event-landing-page/references/form-and-consent.md3.2 KB
  • event-landing-page/references/page-example.md4.1 KB
Read the SKILL.md
---
name: event-landing-page
description: Writes registration landing page copy for B2B webinars, virtual events, field events, executive dinners, roundtables and conferences. Produces headline options, who it's for, what you'll learn, agenda, tightened speaker bios, logistics, FAQ, meta title and description, and a recommended registration form with field choices and consent checkbox wording for EU and UK registrants. Use for event pages, registration pages, webinar pages, event microsite copy or reviewing a page that isn't converting.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: promotion
  source: https://eventmarketingsoftware.com/skills/event-landing-page
---

# Event Landing Page

Writes the copy for one event's registration page, section by section, ready to paste into your registration platform, website builder or event site. It also recommends the form: which fields to ask, which to drop, and the consent wording, because the form is where most registration pages lose people.

## Intake

If the user has an `event-context.md` file, read it first and don't ask for anything it already answers (company, ICP, tone, privacy notice link).

Ask for whatever is missing in ONE message:

1. Event title (working title is fine), format, date, start and end time with time zone, location or "online", length.
2. Audience: job titles, company size or industry, and who it's not for.
3. The value: the problem it addresses and 3 to 5 things attendees will learn or get. Any proof (customer speaker, past attendee quote with permission, numbers they can source).
4. Agenda items with times, and speakers with title, company and any existing bio.
5. Registration model: open, approval required, capacity cap, paid or free, waitlist.
6. Where the page will live and any limits (character counts, fixed template sections).
7. Which data they need from the form and why (routing to sales, sponsor sharing, dietary needs, session choice), and whether EU or UK registrants are expected.

Work with partial answers. Use placeholders like `[VENUE ADDRESS]` instead of inventing details.

## Data sources (connectors optional)

- If a Google Sheets connector is available and the agenda or speaker list lives there, read it from the sheet.
- Otherwise, work from pasted text or an uploaded doc, CSV or XLSX, and return Markdown the user can paste section by section.
- Don't fetch URLs, including an existing page the user links to. Ask them to paste the current copy if they want a rewrite.
- Never require a paid service.

## Method

1. **Write for one reader.** Name the primary audience in a sentence before writing. Every section should answer "is this for me and is it worth my time?"
2. **Above the fold first.** Headline (outcome or problem, not the event's internal name), subhead with format, date, time and time zone, and one registration button. Give 3 headline options with different angles: outcome, problem, audience.
3. **Who it's for.** 3 to 4 bullets by role or situation, plus one "not for" line if it helps qualify (essential for dinners and roundtables).
4. **What you'll learn or get.** 3 to 5 bullets, each a concrete takeaway starting with a verb. No "insights" or "best practices" without saying which.
5. **Agenda.** Times in the event's time zone, short session names, speaker per item. For conferences, link tracks instead of listing everything.
6. **Speakers.** Bios at the length asked (default 40 words): current role, one credential relevant to this topic, one human detail if supplied. Third person. Cut adjectives like "visionary" and "renowned".
7. **Logistics.** Date, time with time zone, length, location with address or join method, cost, capacity, accessibility, recording or replay (only if confirmed), dress code for dinners.
8. **FAQ.** 4 to 6 questions people really ask: cost, replay, who should attend, can I bring a colleague, what data you collect and who sees it, how to cancel. Answers under 50 words.
9. **Form recommendation.** Use [references/form-and-consent.md](references/form-and-consent.md). Default to the fewest fields that meet the stated need, and mark each field Required, Optional or Drop, with a reason.
10. **SEO and share text.** Meta title under 60 characters, meta description 140 to 160 characters, and a share snippet for social posts.
11. **If reviewing an existing page,** list the top 5 issues in order of likely impact (unclear time zone, missing "who it's for", form too long, vague takeaways, buried CTA), then give the rewrite.

Domain rules that matter:
- Date, time with time zone and format must be visible without scrolling.
- One CTA label used consistently ("Save my seat", "Request an invite" for approval events). Repeat it after the agenda and at the bottom.
- Don't claim sponsors, attendee counts, ratings or speakers the user didn't confirm.
- If attendee data goes to sponsors or partners, the page and form must say so plainly (see the consent reference).
- Accessibility: descriptive button text, no information only in images, and ask what accommodations are offered.

## Output template

Return the page in this order, with these headings:

```
# Headline options (3, labeled by angle)
# Subhead
# Primary CTA label
# Who it's for
# What you'll learn
# Agenda
# Speakers
# Logistics
# FAQ
# Registration form
# Meta title and description
# Share snippet
# Open questions and placeholders
```

Registration form table:

| Field | Type | Required, Optional or Drop | Why | Notes |
|---|---|---|---|---|

Then the consent block wording, ready to paste.

Worked example: [references/page-example.md](references/page-example.md).

## Validation checklist

- [ ] Date, time with time zone and format appear in the subhead.
- [ ] 3 headline options with different angles; none over about 70 characters.
- [ ] Every takeaway is concrete and starts with a verb.
- [ ] Speaker bios match the requested length and contain only facts the user supplied.
- [ ] No invented numbers, logos, sponsors or replay promises.
- [ ] Form has a reason for every required field; consent checkbox is unticked and separate from terms.
- [ ] Sponsor or partner data sharing is disclosed if it happens.
- [ ] Meta title under 60 characters; meta description 140 to 160 characters.
- [ ] House style: contractions, plain words, no hype, no dashes as punctuation.

## Approval gates

- Return copy as a draft. Never publish, update a live page or change a form in a connected tool without showing the final copy and getting a clear yes.
- Consent wording is a starting point, not legal advice. Say so once and suggest the user's privacy or legal lead approves it.

## Privacy

- Recommend collecting only what the event needs. Every extra field is data you have to protect and a reason to abandon the form.
- EU and UK registrants: marketing consent must be a separate, unticked opt-in; registering for the event isn't consent to marketing. Sharing with sponsors needs clear disclosure and, depending on the user's lawful basis, its own opt-in.
- Don't ask for sensitive data (health, religion) unless the event needs it, such as dietary or accessibility needs, and then say how it's used and when it's deleted.

## Related skills

event-invite-sequence (emails that drive people to the page), event-social-kit (social posts with the page link), speaker-management (collecting bios and headshots).

FAQ

What should an event registration page include?
A headline that names the outcome or problem, a subhead with date, time, time zone and format, a short who it's for list, three to five concrete takeaways, the agenda, short speaker bios, logistics, an FAQ and one consistent call to action. The registration form should ask only for what the event needs.
How many fields should a webinar registration form have?
As few as meet a real need. Name, work email, company and job title cover most webinars, with country added when EU or UK registrants are likely so consent can be handled. The skill marks each field Required, Optional or Drop with a reason, and suggests moving nice-to-have questions to the confirmation page or check-in.
What consent wording do EU and UK registrants need?
Marketing consent should be a separate, unticked checkbox in plain language, with a link to your privacy notice. Registering for the event isn't consent to marketing. If you share attendee data with sponsors, say so clearly and get your legal lead to confirm the lawful basis. The skill drafts wording as a starting point, not legal advice.
Can this skill rewrite my existing event page?
Yes. Paste the current copy and form fields and it lists the top five issues by likely impact, such as an unclear time zone, vague takeaways or a long form, then returns a full rewrite under the same headings. It won't fetch the page from a URL, so paste the text.