Guides → Webinar promotion — landing page to recording archive

Webinar promotion — landing page to recording archive

Run a webinar end to end via SGEN — landing page, registration, reminder sequence, live coordination, and archived recording

A webinar lives or dies on three things: the registration page, the reminder cadence, and the recording archive. Most webinars get the first one right, half-do the second, and forget the third — leaving 70% of the asset's value on the table.

This recipe coordinates all three in SGEN. The landing page captures intent. The reminder sequence converts registration into actual attendance. The recording archive keeps the asset earning weeks after the live session ends.

What is this for?

Use this recipe to run a webinar where SGEN is the customer-facing surface — the page they register on, the emails they get, and the recording archive they revisit. The live broadcast itself runs on Zoom, StreamYard, Google Meet, or whichever tool the host prefers; SGEN holds the promotion and the archive.

The end state for a full webinar cycle:

  • A registration landing page at /webinar/<topic-slug>/ with the offer, the host bio, and the form.
  • A registration form that captures email and tags the contact for the reminder sequence.
  • A 4-email reminder cadence — confirmation, day-before, day-of, post-event.
  • A live-day operations checklist that catches the broken-stream and the missed-link.
  • A post-event recording archive page with the recording, the slides, the resources mentioned.
  • A blog post recap that pulls organic traffic to the archive for months.

Good use cases

Product launch webinar. A live demo plus Q&A tied to a major release. Attendance carries early conversion; the recording earns trickle conversion for weeks.

Thought-leadership webinar. A founder or subject expert on a specific topic. Builds brand authority, feeds the email list, and seeds the recording archive.

Customer training webinar. Existing customers learning a deeper use of the product. Reduces support load; the recording becomes onboarding material.

Co-marketing webinar. Two brands sharing audiences. The landing page lists both logos; the recording archive lives on both sites.

What NOT to use this for

  • Weekly recurring meetings. A standing internal meeting does not need a landing page or reminder sequence. Use a calendar invite.
  • Closed-door customer calls. A private call with a single account is sales, not webinar — no public registration page.
  • Pre-recorded "auto-webinars." This recipe assumes a live broadcast on a specific date. Auto-webinars are a different funnel with different mechanics.

How this connects to other features

  • Pages + SG-Builder — the registration page and the archive page are both SG-Builder pages. Build the registration page first; the archive page often forks from it.
  • Forms — the registration form is a SGEN Form connected to an email integration. The integration handles the reminder cadence.
  • Blog — the recap post lives in the blog and links to the archive page. Treat it as a separate publish event with its own social cross-post.
  • Custom Codes — open-graph image, calendar .ics link, and any tracking scripts ride on the landing page via Custom Codes.
  • Media library — the recording, the slide deck, and any post-event resources upload to the Media library and link from the archive page.

Before you start

You are signed in as an Administrator. You have the webinar date, time, and timezone locked. You have the host or hosts confirmed and the broadcast tool picked (Zoom, StreamYard, Google Meet, or similar). You have the broadcast URL or you know how to generate it.

You have the topic, the title, and the one-line description written. You have a hero image at 1200 × 630 px for open-graph. You have an email service connected to SGEN for the reminder cadence.

Where to find it

SurfaceAdmin pathOwner
Registration pageSidebar → Pages → SG-BuilderMarketing
FormSidebar → Forms → + Add NewMarketing
Email cadenceSidebar → Forms → Integrations → AutomationMarketing
Recording archive pageSidebar → Pages → SG-BuilderMarketing
Recap blog postSidebar → Blog → + Add NewMarketing

Steps

1. Build the registration landing page

Navigate to Pages. Click + Add New. Title the page with the webinar name. Slug is short — /webinar/<topic-slug>/. Avoid date-stamped slugs (/webinar/2026-06-15-launch/) — the page lives past the live date and the date in the slug ages it badly.

Open SG-Builder. Start from the brand's existing landing-page template. Required pieces:

  • Hero — 6 to 12 word headline naming what the attendee will learn or see.
  • Date and time block — clear date, time, timezone. Show two timezones if the audience is global.
  • Description — 50 to 150 words. What they will see live. What problem the webinar addresses.
  • Host bio — name, role, one sentence of context, headshot.
  • Form — embedded SGEN Form, two fields (name optional, email required).
  • Agenda — 3 to 5 bullets of what the live session will cover.

Save and publish. Confirm the page renders at the public URL.

yourdomain.com/webinar/launch-discipline

How a 3-person team ships 8 launches a year

Live walkthrough of the pipeline. Tuesday June 15, 1pm PHT.

2. Create the registration form

Navigate to Forms → + Add New. Title — <Webinar title> — Registration. Field list:

  • Email — required.
  • First name — optional.
  • One qualifying question — optional (What is your role? or What brings you to this webinar?). Useful for segmentation but cuts conversion 5 to 15%. Skip if registration volume matters more than segmentation.

Confirmation message: short and concrete. "You are registered. Check your inbox for the calendar invite and the join link."

Add a calendar .ics download or a "Add to Google Calendar" link in the confirmation message. The reader is most likely to add it to their calendar the moment they register.

Form — webinar registration

Email + optional name; nothing else

3. Wire the reminder cadence

Navigate to Forms → Integrations. Pick the email service connected to the form. Set up an automation with these emails:

EmailWhen it sendsJobLength
1. ConfirmationImmediateConfirm registration, share join link + calendar invite.50-100 words
2. Day-before24 hours before startRemind, restate the join link, set expectations.75-150 words
3. Day-of1 hour before startFinal reminder. Join link. No filler.30-50 words
4. Post-event6 to 24 hours after endThank, link to recording, link to next step.100-200 words

The join link goes in every email. Registered users lose the link constantly — putting it in every email solves the support ticket the host would otherwise field on the day of.

Reminder email 3 — day-of

Sends 1 hour before start

Tag the registrant with the webinar slug — webinar-launch-discipline or similar. The tag stays on the contact past the event and helps later cohort analysis.

4. Test the full registration flow

Submit a test registration with a real address you can read. Confirm:

  1. The contact appears in the email service within 30 seconds.
  2. The tag is applied.
  3. The confirmation email arrives within a minute.
  4. The join link in the email matches what the host expects.
  5. The calendar invite or "Add to Calendar" link works.

Test from at least two email addresses — one from the brand's domain, one from a personal Gmail. The two often hit different deliverability paths.

5. Promote registration

Drive traffic to the landing page through the brand's regular channels:

  • Email — one announcement to the list 2 to 3 weeks out, one reminder 1 week out.
  • Social — 3 to 5 posts across LinkedIn, X, and any community channels.
  • Blog — a teaser post if the topic warrants 600+ words of pre-event content.
  • Partner cross-promo — co-marketing partners share to their list and their followers.

Realistic registration conversion (visitors → registrants) runs 15 to 35% on warm traffic, 3 to 8% on cold. Show-up rate (registrants → live attendees) runs 25 to 50%. Plan promotion volume backward from the live attendance target.

6. Run live-day operations

The day of the webinar, two roles matter — the host (does the actual broadcast) and the operator (handles the chat, the tech, the late join links). The operator's checklist:

  1. Confirm the broadcast tool is open and the test stream looks clean — 30 minutes before start.
  2. Confirm the slides or demo screen is ready to share.
  3. Confirm the audio levels are clean. Test with one team member from outside the call.
  4. Open the chat or Q&A interface. Have one canned reply ready: "We will hold Q&A for the last 15 minutes."
  5. At the start time, press start. Greet the early attendees by name (read from the registration list).
  6. During the session, watch the chat for join-link problems. Re-post the join link in chat 10 minutes in for late arrivals.
  7. At the end, give the post-event teaser — "Recording will land in your inbox tomorrow."

7. Build the recording archive page

Within 24 hours of the live session, navigate to Pages → + Add New. Title — <Webinar title> — recording. Slug — /webinar/<topic-slug>/recording/.

Required pieces:

  • Hero — repurpose the registration page hero. Replace the live date with a one-line note: "Live session held [date]."
  • Recording — embed the video. YouTube, Vimeo, or Wistia — whichever the brand uses. Set it to public or unlisted as the strategy demands.
  • Slides — link to the slide deck (PDF or external).
  • Resources — bullet list of links to anything mentioned in the session.
  • CTA — the same next-step CTA used in the post-event email.

The archive page is the asset's long tail. Months from now, search traffic will land here. Treat it as a real landing page, not a recording dump.

yourdomain.com/webinar/launch-discipline/recording

How a 3-person team ships 8 launches a year — full recording

Watch the full 50-minute session. Slides and resources below.

8. Publish the recap blog post

Navigate to Blog → + Add New. Set the category to whichever pillar the topic fits — usually How-to or Industry context. Title the post [Recap] <Webinar title> or a tighter standalone title that pulls organic traffic.

The recap is the SEO surface for the webinar. Cover:

  • A one-paragraph summary of the session.
  • 3 to 5 key takeaways in numbered bullets.
  • An embedded video player linking to the recording.
  • Quoted lines from the session that landed well.
  • CTA to the archive page.

Tag the post with the webinar slug. Cross-post to social as usual.

9. Send the post-event email

The post-event email (the 4th in the reminder cadence) auto-sends per the automation set up in step 3. Confirm:

  1. The email landed in the post-event window (6 to 24 hours after end).
  2. The recording link in the email resolves to the archive page.
  3. The CTA matches whatever the live session promised at the end.

If the recording is not yet published when the auto-send fires, pause the automation until the archive page is live. A broken recording link in the post-event email is a credibility hit.

What success looks like

After the full cycle:

  1. The registration page resolves at the public URL with the open-graph preview correct on social.
  2. The reminder cadence delivered all four emails to all registrants.
  3. The live session ran without a broken stream or a missing join link.
  4. The archive page resolves at the public URL with the recording embedded and playing.
  5. The recap blog post is live, linked to the archive, and shared on social.
  6. The post-event email landed within the planned window with a working recording link.
  7. The contact list shows the cohort tagged with the webinar slug for future segmentation.

What to do if it does not work

Registrations are low. The landing page is not converting, or the promotion volume is not there. Check the registration conversion rate — below 5% on warm traffic is a page or offer problem. Above 5% but low absolute volume is a traffic problem.

Reminder emails are not sending. The automation is paused, mis-triggered, or the email service quota was hit. Open the automation in the email service and confirm it is active. Check the send report.

Show-up rate is below 25%. The reminder cadence is weak, or the registrants are not your audience. Strengthen the day-before and day-of emails with specifics. Look at qualifying-question answers (if asked) to see if the audience matches.

The join link broke at start time. The broadcast tool dropped or the link in the emails was wrong. Have a backup link ready on a separate broadcast tool. Post the new link in the chat of the original tool and in a quick email to registrants.

The recording is not ready 24 hours after the session. The post-event email is auto-firing with a broken link. Pause the automation immediately. Push the email when the archive is live.

The archive page is not pulling traffic. The page lacks the SEO and social surface to draw search and share traffic. Add a recap blog post (step 8), share to social, and let the post-event email drive the first wave.

Variations

Recurring monthly webinar series. Instead of a one-off event, the brand runs a monthly webinar on a fixed schedule — first Thursday of the month, 1pm. One registration page per topic, but the reminder sequence is templatized. The recording archive becomes a series page with all past sessions indexed. The blog recap for each session feeds a growing search surface.

On-demand "webinar" with a live Q&A session. Record the main content in advance; run only the Q&A live. Registrants watch the recording at their own pace before the scheduled Q&A date. The live session is shorter (30 minutes) and richer in audience engagement because everyone has seen the content. The archive page hosts both the recording and the Q&A clip.

Invitation-only training. No public registration page — invitations go out to a specific customer segment via email. The form captures only name and email (the qualifying question is not needed since the audience is already known). The reminder sequence uses the same four-email shape but with more personalized copy. The recording becomes private, linked only in the post-event email.

Webinar as a lead-magnet replacement. Instead of a PDF lead magnet, the brand offers a live webinar as the top-of-funnel asset. The landing page captures registrations; the drip sequence starts at confirmation and runs through the event. Post-event, the non-attendees receive the recording link as the "delivery email" they would have received for a PDF. The drip continues past the event with the same conversion handoff at the end.

Anti-patterns

Date-stamped slug that ages the archive. A slug like /webinar/2026-06-15-launch/ creates a URL that looks stale in search results and social shares six months later. Use a topic-based slug (/webinar/launch-discipline/) and let the page title carry the date context.

Skipping the archive page. The recording is uploaded to YouTube and the link is shared once in the post-event email. No archive page, no recap blog post, no permanent URL. Sixty percent of the asset's long-tail value is gone. The archive page and the recap post are not optional — they are where the ROI from the event accumulates over months.

Broken join link in the day-of email. The day-of email is the one the registrant opens on their phone five minutes before the session starts. If the join link is wrong, the session loses them at that moment. The join link goes in every reminder email. Test each email's link against the actual broadcast URL before scheduling the automation.

No qualification in the registration form. For thought-leadership and co-marketing webinars, understanding who is registering shapes how the session is run. One optional qualifying question ("What brings you to this webinar?" or "What is your role?") gives the host context on the audience composition without hurting conversion meaningfully.

Examples

Product launch webinar. Tuesday afternoon, 45-minute slot. Registration page emphasizes the live demo. Reminder cadence is tight — confirmation, day-before, day-of. 800 registrations, 280 live attendees. Recording archive pulls 1,200 views over the next 60 days; the recap blog post ranks for the product category.

Founder thought-leadership webinar. Monthly cadence, 30-minute slot plus 15 minutes Q&A. Registration page leads with the founder's name. Audience is mostly the email list. Show-up rate runs 40%. Archive feeds an ongoing playlist.

Customer training webinar. Existing customers, no public promotion — invitation-only via in-app message and customer email. 200 registered, 130 live. Recording becomes a permanent piece of the customer onboarding sequence. Support ticket volume on that feature drops 30% the following month.

Co-marketing webinar with a partner. Two brands, shared audiences. Registration page lists both logos. Each brand promotes to its list. 1,400 registrations split roughly evenly. Recording archive lives on both sites with slightly different page copy. Recap blog post on each blog.

Customer panel webinar. Three existing customers in conversation with the host. Registration page emphasizes the panel format. Show-up rate is high — readers are curious about real customer talk. Archive becomes a permanent piece of the sales enablement library.

The registrations list in Form Submissions shows the registered cohort, their tag, and their confirmation status in the days leading up to the session:

Form Submissions — Webinar Registration

Launch discipline — 14 days out
+ Add New
NameEmailStatusDate
Ada Lovelaceada@acmecoffee.comConfirmedApr 22
Grace Hoppergrace@acmecoffee.comConfirmedApr 21
Alan Turingalan@acmecoffee.comConfirmedApr 20
Margaret Hamiltonmargaret@acmecoffee.comPendingApr 22

Related recipes

  • Product launch playbook — a product launch webinar coordinates with the landing page, changelog, and email launch sends; plan both playbooks against the same launch date
  • Case study publishing workflow — customer panelists in a webinar often become case study subjects; the webinar recording is a strong source of interview quotes
  • Lead-magnet funnel — the webinar recording becomes a gated lead magnet in a future funnel; the archive page can carry the same capture form used in the lead-magnet recipe

Related reading


Last updated: 2026-05-25

On this page