Seminar guide
Seminar Landing Page: One Event, One Promise, One Action
A seminar landing page sells one event to one reader and asks for one action. Use this checklist for the promise, details, form, mobile layout, and tracking.
What makes it a landing page
A landing page is the first page a person sees after a click, and it has one job. A website’s home page has many jobs: it introduces the organization, serves current clients, and points to a dozen places. A seminar landing page drops all of them.
The test is simple. If a visitor could finish reading without ever learning the date of the event, you built a brochure. If they could finish by doing anything other than registering, you built a menu. Neither converts a stranger into a seat.
One event matters most. A page that lists three upcoming dates, or two different seminars, makes the reader choose before they have decided to come at all. Build one page per event, or one page per date with a single clear choice between sessions.
The five parts, in order
Read the page top to bottom on a phone and check that these appear in this order.
- The promise. One sentence naming what the guest will learn or decide, in their words. “How to read your retirement income options before you retire” tells a reader more than “Join our exclusive educational event.”
- The logistics. Date, start time, end time, venue and address, and whether food is served. Put these high on the page, not in a footer. A reader who cannot find the time will leave.
- Who it is for. Say who should come and who should not. This protects the room and your follow-up time.
- Who is presenting. A name, a role, and a sentence on why they are the right person. Use a real photo if you have one. Do not invent credentials, results, or testimonials.
- The form. Name, mobile number, and email, plus the consent line beside the button. Ask nothing else you will not use this week.
If you must cut something, cut the extras above the promise. Never cut the logistics.
One action
The form is the only action. Every other link on the page competes with it, so remove the navigation bar, the social icons, and the “about us” section. A privacy policy and a contact line are fine in a quiet footer.
Repeat the button once, after the details, so a reader who has read everything does not scroll back up. Both buttons open the same form and do the same thing.
Keep the form short. Each extra field is another reason to stop, and the follow-up needs only enough to confirm the seat and reach the person: a name, a way to contact them, and consent to do so. If the registration also collects a mobile number for text reminders, say so in plain language next to the button, along with how to opt out.
Mobile first
Most clicks from ads and invitations arrive on a phone, so design for that screen first and let the desktop version inherit it. Open the page on your own phone before it goes live, then check three things.
- The promise, the date, and the button are visible without scrolling far.
- The button is large enough to tap with a thumb, and the fields use the right keyboard (numbers for the phone field, email for the address).
- Nothing shifts, jumps, or covers the form while it loads.
Then check the page on a slow connection. A page that takes too long to appear is a page some people never see, and you will not know how many.
Track the source before you spend
A landing page that cannot say where its registrations came from makes every later number a guess. Before you buy any traffic, confirm that the page records the source with the registration itself. That means the tracking tag is on the page, the link the guest clicked carries its source, and the registration stores it.
Test it by registering yourself once from each channel you plan to use. Then open the record and read the source. If it is blank or wrong, fix it now, because you cannot reconstruct it after the ads have run.
Be careful with the numbers this produces. A page view is not a registration, a registration is not a confirmed seat, and a confirmed seat is not someone in the room. Count each separately. The seminar show rate guide explains why the gap between registered and attended is the figure worth watching.
Where the page hands off
The landing page ends the moment the form is submitted, but the guest’s experience does not. The page should hand off to a confirmation that arrives quickly and repeats the date, time, and place. A message that says “thanks, we’ll be in touch” does not tell the guest what to do next.
After the confirmation come reminders, a way to ask a question, and a check-in on the day. Each of those has its own guide. The seminar registration page guide covers the form, consent, and reply flow in detail, with a medical practice as its example. Medical practices carry compliance rules for what a page may say, so that guide is the better starting point for them. The seminar confirmation email guide covers what the first message should contain, and the seminar no-shows guide covers what happens between the click and the room.
Examples, labeled
These two sketches show the same structure for different readers. They are illustrations, not client pages and not results.
Advisory example. A financial advisory firm hosts a dinner on retirement income. The promise reads “What to decide about your income before your last day of work.” The logistics give the date, the restaurant, and the time. The page says it is for people within a few years of retiring. It names the advisor and the advisor’s role. It asks for a name, a phone number, and consent to text a reminder.
Medical example. A practice hosts an educational evening on a joint-health topic. The page states the topic, the date and place, and who the evening is for, and it names the physician presenting. It avoids any promise about outcomes, and a qualified person reviews the health language before it runs. The form is the same three fields and the same consent line.
In both, the page says one thing and asks for one thing.
A pre-launch checklist
Before you point any traffic at the page, run through this list.
- The promise is one sentence in the reader’s language.
- Date, time, and place are visible on a phone without hunting.
- There is one form and no competing link.
- The form asks only what you will use, with consent beside the button.
- You registered once from each channel and the source was recorded correctly.
- A confirmation arrived within minutes and repeated the details.
- The page loaded quickly on a slow connection.
The full guide collection covers each stage in order. For the work upstream of the page, how to fill a seminar starts from room size and works back to the registrations you need.
How Seminar Engine fits
Seminar Engine is a managed service run by Boydston Marketing, not a tool you build in yourself. It provides a branded registration page, a fast confirmation, a seminar-trained SMS assistant, reminders, mobile check-in, and source-level reporting, so the page, the follow-up, and the attendance record share one registration. It does not promise registrations, attendance, or new clients or patients. See the pricing page for what it costs.
The next step
If you are not sure whether your current page does its one job, book the free 30-minute audit. Robert will walk through your page, confirmation, and tracking, and tell you which part loses the most people. Book the audit.
Questions
What is a seminar landing page?
It is a single page built for one seminar, where a person who clicked an ad, email, or invitation can decide to attend and reserve a seat. It carries the topic, date, place, presenter, and one registration form, and it links nowhere that competes with that form.
How long should a seminar landing page be?
Long enough to answer the questions a stranger asks before giving a name and number, and no longer. For most seminars that is the promise, the logistics, who it is for, who is presenting, and the form, readable in one short scroll on a phone.
How do I know which ad produced a registration?
Carry the source with the registration at the moment it is created, using the tracking tag on the page and the link the guest clicked. A source typed in later by hand from memory is a guess, so test one registration from each channel before you spend.