How Do You Run Webinars and Events on a Webflow Site?

How do you run webinars and events on a Webflow site?

One Events Collection, one page template, and a registration form that hands off to whatever runs the session. The Collection holds the date, the description and the speakers. The webinar platform holds the attendance. Keeping those jobs separate is what stops this becoming a maintenance problem.

Almost every B2B company we work with has event pages built by hand, one static page per webinar, abandoned the week after. Six months later the site has eleven orphan pages with dead dates on them.

Here is the structure we build instead, and the honest version of what events do for pipeline.

What should the Events Collection contain?

Seven fields cover it. Title, a rich text description, a Date/Time for the start, a Date/Time for the end, an Option for the format, a Link for the registration URL, and a Switch for whether it is featured. Webflow stores Date/Time values in ISO 8601 format, which matters later.

Add speakers as a MultiReference to a People Collection if you already have one, because speaker bios get reused across the site. If you do not have one, plain text is fine and you can normalise later.

Use the VideoLink field for the recording. Webflow documents it as accepting video URLs from platforms like YouTube or Vimeo, so the same item can serve as the live page before the event and the recording page after it.

How do you handle past versus upcoming events?

Sort and split on the date field, never on a manual toggle. Put two Collection Lists on the same index page, one filtered to future dates and sorted ascending, the other filtered to past dates and sorted descending. That gives you an events index that maintains itself every day.

The manual alternative always fails. Somebody forgets to untick a box, and your homepage advertises a webinar that happened in March.

Keep the past list short on the index page and let the archive live on its own page. Old events are useful for search and for proof, not for the first screen a prospect sees.

Where does registration actually happen?

On the platform that runs the session, most of the time. A Webflow form that collects a name and email and then a separate manual invite is a broken process waiting to happen. Send people to the registration flow that issues the calendar invite and the reminders.

The exception is when you want the lead in your own system first. Then use a Webflow form, pass the submission to your CRM or automation layer, and let that create the registration. Our Webflow forms guide covers the submission and notification settings.

Either way, decide who owns the follow-up email before you build the page. That single question resolves most of the arguments about where the form should live.

Should you add Event structured data?

Read Google's rules first, because a pure webinar may not qualify. Google's Event structured data documentation, last updated on 8 September 2026, requires name, startDate and a location that includes an address and a venue name, and startDate must be ISO 8601 with a timezone offset.

The important line for B2B is in the exclusions. Google's page explicitly lists virtual experiences that have no real-world component among the things that do not qualify as events, alongside trip packages, short-term discounts, business hours and membership-only events.

So mark up your conference sessions and your in-person dinners. For an online-only webinar, do not promise anyone rich results. Our guide to schema markup for SEO covers where the value actually sits.

What else does the markup need if the event is real?

Google recommends description, endDate, eventStatus, images at 16x9, 4x3 and 1x1 ratios, the venue name separate from the event name, organizer, performer, and an offers block with availability, price, priceCurrency as a three-letter ISO 4217 code, a ticket URL and validFrom.

Handle cancellations the documented way. Google says to set eventStatus to EventCancelled and to keep all other values the same as they were before the change, rather than stripping the page. For a reschedule, update the dates and optionally include previousStartDate.

One format detail people get wrong: for an all-day event use the date with no time component, and when the start hour is unknown, use the date alone rather than midnight.

What happens to the page after the event?

It becomes the recording page, at the same URL. Swap the registration link for the video, add a summary of what was covered, and keep the date visible. You have then converted a one-day asset into a page that can rank and be cited for years.

Write the summary as prose, not as slides. The transcript is not the asset. Three paragraphs that answer the questions the session answered is what makes the page useful to somebody who will never watch 45 minutes of video.

If the recording is gated, decide deliberately. Our notes on gating content in B2B SaaS set out when a form in front of a recording costs more than it collects.

How do you avoid a graveyard of dead event pages?

Have a rule and let the CMS enforce it. Events older than 18 months with no recording get unpublished. Events with a recording stay, retitled around the topic rather than the date, because "our Q2 webinar" is not a phrase anybody searches for.

The date-based split does the rest. Past events drop off the upcoming list automatically, so nothing needs to be tidied by hand at the end of a quarter.

Check the archive twice a year. A list of sessions from three brand refreshes ago says more about your standards than any about page.

What about recurring webinars?

Model each occurrence as its own item. It is tempting to have one page for a monthly demo session, but a single page cannot carry the right date, the right speaker or a recording. One item per occurrence keeps every page honest.

If the same session repeats weekly, that is not really an event, it is a standing offer. Build it as a normal page with a scheduling link and stop pretending each instance is news.

The test is whether somebody would ever link to one specific occurrence. If not, it does not need a CMS item.

Do events actually drive pipeline for B2B?

Less directly than most marketing plans assume. TrustRadius, in its 2026 report covering 1,862 buyers and 444 vendors, found that buyers ranked product demos, free trials, prior experience and user reviews as the most influential resources when selecting a vendor. Webinars did not make that list.

That is not an argument against running them. It is an argument for treating a webinar as a content and relationship asset rather than a conversion event, and for measuring it on the recording page traffic and the conversations it starts.

The same report found transparent pricing has been the number one buyer wish-list item four years running. If you have a choice between another webinar and publishing your prices, publish your prices.

What would we build first?

The Collection with its seven fields, one Collection Page template, and an index page carrying the two date-filtered lists. Then run one real event through the whole flow, including the switch to a recording page afterwards, before you scale the programme to a monthly cadence.

That order matters, because the recording step is the one every team skips, and it is where most of the long-term value of an events programme actually lives.

If you want help modelling events alongside the rest of your Webflow CMS, we are happy to walk through it. You can see how we build at phoenix.studio.