The webinar registration page: one job, done in ten seconds.

Make the trade obvious, then get out of the way.

A registration page is not a sales page and not a preview of the session. The visitor is deciding exactly one thing: whether an hour of their time, on that date, is worth what this promises. Every element either helps them decide or delays them.

The trade has four terms, and a page that answers all four in the first screen converts the people who were always going to convert. What do I get. What does it cost me — an hour, on a specific date, at a specific time. Who is asking. What happens if I cannot make it. Hide any one of those and you have asked the visitor to do work to find it, and some fraction of them stop instead.

The ten-second test

Show the page to someone who has never heard of you and ask three questions: what is this about, when is it, and what do I have to give up to attend. If they have to scroll to answer any of the three, that answer is in the wrong place. The test takes ten seconds and it is more reliable than any opinion you will get about the design.

Do the same test on a phone before you do it anywhere else. A first screen that works on a laptop and pushes the date below the fold on a phone is a page that fails for most of the people who see it.

Long is not the problem. Padded is.

The advice to keep registration pages short is a proxy for the real rule, which is that nothing should be on the page that does not help the decision. A long page for a paid half-day workshop with a real agenda can be exactly right. A long page that restates the same promise in four different registers is padding, and padding reads as uncertainty about the offer.

The most common failure is not length at all. It is a page trying to do a second job — selling the product the session is about, establishing your whole professional history, or teaching enough that attending becomes optional. Each additional job competes with the one the page has.

Specific beats clever, and it is not close.

The title is the only part of the page that travels. It goes in the subject line, the social post, a partner’s email, the calendar entry and the reminder ten minutes before you start. It has to work read alone, out of context, by someone who is not looking at the page.

A clever title is one that only makes sense once you already know what the session is. It rewards the people who were coming anyway and loses everyone who needed the title to do its job. A specific title names the audience, the problem or the outcome — ideally two of the three — and reads the same at the top of an inbox as it does under a hero image.

The stripped test

Delete the page and read the title alone. If a stranger can tell who it is for and what changes for them, keep it. If it only works once the subhead explains it, your subhead is the title and the title is decoration.

Curiosity is not the enemy here — unresolved ambiguity is. A title can hold something back and still be specific about the territory. What it cannot do is require the reader to guess at the subject.

Patterns that keep you honest

• →How to [outcome] without [the cost they expect to pay]. Works when the expected cost is the real objection and you genuinely remove it. It fails badly if the session does not.
• →[The task] for [specific audience]: [the part everyone gets wrong]. The exclusion in the middle is doing the work. It repels the wrong room, which is the point.
• →The [artifact] I use to [outcome], walked through end to end. The strongest pattern when you actually have the artifact, because it names the thing they leave with.

Under the title, one line of who it is for and the shape of the session: length, live, and whether there is time for questions. That line does more for the decision than a second paragraph of promise.

Fix the title before promotion starts. Changing it mid-window means the partner’s email, the calendar entry someone already saved and the page no longer agree, and the person who registered a week ago now has an appointment for something with a different name. The title is also a promise the room has to keep — the script template starts from it deliberately.

Write the time the way a stranger reads it.

The date and time are the second half of the trade — the price. Pages that bury them are asking people to commit to an unknown cost, and the ones who register anyway are the ones most likely to discover a conflict later.

Write out five things: the weekday, the date, the start time, the timezone, and the duration. People plan by weekday, they commit by duration, and they miss sessions over the timezone.

Timezones, properly

Best is the time converted into the visitor’s own timezone with the label visible, so they can see both what it means for them and what the source time is. A conversion without a label is worse than a label without a conversion: a bare number that silently changed is the exact thing that makes someone distrust every other time on the page.

If your builder cannot convert, write the source timezone explicitly with its offset rather than an abbreviation alone — abbreviations collide across regions and change with daylight saving. Then repeat the same string everywhere: the page, the confirmation, the calendar entry and every reminder should read identically.

Two sittings, one registration

Offering a second time is a real lever when a meaningful part of your audience is in another region. Build it as a choice on one page rather than two separate pages: two pages split your source tracking, double the thing you have to keep in sync, and produce two versions of the truth when you change the title. One page, one registration record, a session field on it.

Whichever times you pick, pick ones you can defend for the audience you actually have and then keep them. A session that is always on the same weekday at the same hour becomes a habit; a session at a new time every month is a new decision every month. When the honest answer is that your audience cannot all be in one room at one time, that is a scheduling question, not a copy question.

Three to five things they will be able to do afterward.

Not an agenda. An agenda describes your hour; outcome bullets describe their afternoon. “Introduction, five common mistakes, Q&A” is a running order, and a running order is not a reason to attend anything.

Write each bullet as a capability the reader leaves with, in the plainest verb you can find. Then apply the rule that keeps the whole block honest.

Three to five, and the range matters. Fewer than three reads thin — as though the session is one idea stretched over an hour. More than five reads like a syllabus, and the reader stops weighing individual claims and starts skimming, at which point none of them land.

Specific beats superlative every time. Write the thing rather than the adjective: the artifact they will have, the decision they will be able to make, the calculation they will be able to run. Adjectives are what people write when they have not yet decided what the session actually does.

The line that costs you registrations and buys you attendance

Say who it is not for. One sentence, plainly written, immediately after the bullets. It will cost you a few registrations from people who were going to leave at minute six anyway, and it raises the quality of every question asked in the room. It also makes the rest of the page more believable, because a page that excludes someone is visibly not trying to catch everyone.

The bullets are also the spine of the session itself. If you write them well, you have most of the outline already — and the room will keep the promise the page made, which is the only reliable way to make the second session easier to fill than the first.

Credibility is what you can show, not what you claim.

Somebody deciding whether to give you an hour is asking a fair question: why you. Answer it with evidence you actually have, and answer it in one paragraph rather than a career summary.

What counts, in the order most people have it

1. 01The work itself. A teardown, a template, a spreadsheet, a number you can put on screen. Showing the artifact is stronger than any sentence about your experience with it.
2. 02Duration and context. “I have done [this specific thing] for [this specific kind of business] since [year]” is verifiable, modest and more persuasive than a superlative.
3. 03A sample of the teaching. A clip, an article, a past recording. It lets someone check the thing they are actually deciding about — whether an hour of you is useful.
4. 04Named, real proof, if you have it. Results you can substantiate and permission to cite. If you have to soften it to make it defensible, publish the softened version and nothing stronger.

What costs you more than it returns

Invented numbers. Statistics borrowed from a study nobody links. Logo bars for organisations you have no relationship with. Testimonials that do not exist. “As seen in” without the link. The practical problem is not only that these are dishonest — it is that a claim a visitor cannot verify makes every other claim on the page provisional, including the true ones you needed them to believe.

Anyone who has spent a year on the internet recognises the pattern instantly, and the detection is not conscious or fair. The page just starts reading as marketing rather than as an invitation, and the specific thing you lose is the person who was almost ready.

If you have no proof yet

Say what is true and let it be small. “I have run [this process] [n] times and I am going to show you exactly how, including the parts that did not work” is a complete and credible answer. Specific and modest beats vague and grand, and it survives contact with the session.

If you genuinely have nothing to point at, teach on the page. Two or three sentences of real, useful thinking about the problem is proof of the only kind that matters here — it demonstrates the thing they are being asked to buy an hour of.

Every extra field is a tax you pay in registrations.

Name and email is usually enough. The question is not whether a field would be interesting to have — it is whether something downstream changes because of the answer.

Run every field past one sentence: what changes because of this answer? Something in the emails, the room, the routing or the follow-up has to be different, and you have to be able to say what. “Useful to know” is not a use. Data you collect and never look at cost you registrations at the moment of collection and nothing at all afterward.

Optional fields are not free. They still add height, still add decisions, and still make the form look like a qualification exercise at a glance — which is how it is judged, because nobody reads the word “optional” before forming an impression.

Consent, and the double opt-in trade

Where a marketing consent checkbox is required, write it as a plain sentence describing what you will send, and never pre-tick it. It is a small honesty test that the visitor is running whether or not you intended to take it.

Double opt-in is a genuine trade rather than a best practice: it costs you registrations, because every additional step does, and it protects your sending reputation, which is what determines whether your reminders arrive at all. Whichever you choose, if there is a confirmation step, say so on the confirmation page in plain words — “check your email and confirm, or the reminders cannot reach you.” A silent double opt-in is an efficient way to manufacture no-shows.

The button, and what happens after it

Label the button with the action, not the mechanism. Something in the shape of “Save my seat” or “Register for [day]” restates the trade at the moment of commitment; “Submit” describes what the browser does.

Then the handoff. The confirmation page should restate the date and time in their timezone, hand over the calendar file, and say what arrives next and when. The confirmation email should do the same things, because people register on phones and add things to calendars on laptops. The copy for it is written out in the email sequence templates, and the calendar file — the single highest-leverage artifact in this whole chain — is covered in the attendance guide.

Being coy about the replay costs more than it saves.

The instinct is to stay quiet: mention a replay and people will watch the replay. What actually happens is that silence gets interpreted, in both directions, by different people, and you inherit both sets of consequences.

A visitor with a conflict is running a small risk calculation. If the page says nothing, some of them assume there is no replay and do not register, and some assume there obviously is one and register with no intention of attending. You have lost registrations at one end and gained no-shows at the other, which is precisely the trade you were trying to avoid.

Three honest policies

1. 01Everyone who registers gets the replay. The simplest, and the right default when the session’s job is reach. It lowers show-up rate and raises registrations, and you should expect and accept both.
2. 02The replay is available for a stated window. A real deadline, enforced. It keeps most of the urgency and most of the goodwill, provided the window closes when you said it would.
3. 03Live only, no replay. Legitimate when something about the session genuinely cannot be published — live review of a real business, unguarded numbers, a working session. Say the reason; a reason people believe does more than a rule they resent.

Whichever policy you choose, write it in the same words in three places: the registration page, the confirmation, and the reminder the day before. Those are the three moments the question is actually asked, and three slightly different answers is how a policy turns into a complaint.

A countdown is only useful if it counts down to something.

A timer running to a real, fixed start does a genuine job: it converts an abstract date into a felt cost, which is exactly the conversion the page is trying to make. A timer that resets is a different object entirely.

A countdown that starts again when the page reloads is a claim the visitor can disprove with one keystroke, and a meaningful number of them do exactly that — the pattern is familiar enough that checking is a reflex. The damage is not the lost urgency. It is that once one claim on a page has been caught, every other claim on it becomes provisional, including the ones that were true and load-bearing.

The same applies to a seat counter that does not correspond to an actual room ceiling, and to “registration closes in [n] hours” when it does not close. These are not aggressive marketing; they are checkable statements that fail when checked.

Scarcity you can state honestly

Social proof counters follow the same rule twice over: only if the number is real, and only if the real number helps. A badge announcing that four people have registered is worse than no badge, and the fix is to remove it rather than to change the number.

Evergreen sessions inherit all of this with more room to get it wrong, because the start time and the deadline are both generated per visitor. That is workable and honest when the session really does start at that time for that person and the deadline really is enforced — the deadline mechanics are their own subject.

A well-built page, top to bottom.

Described rather than screenshotted, because the layout is not the transferable part. The order of the answers is. Read it as the sequence a visitor needs, and hold your own page against it block by block.

1. 01The first screen. Title, one line naming who it is for, the date and start time with the timezone, the duration, and either the form or a button that reaches it. A stranger can answer what, when and what it costs without scrolling. Nothing else belongs here.
2. 02The promise, expanded. Two or three short paragraphs that name the problem in the reader’s words and say what the session does about it. This is the only block on the page where copy has to do persuasive work, and it is the block most often replaced by adjectives.
3. 03What you will be able to do. The three to five outcome bullets. Written as capabilities the reader leaves with, each one traceable to a specific stretch of the session.
4. 04Who this is for — and who it is not for. Two short lists, or two sentences. The exclusion is the one that earns its place: it costs you a handful of registrations from people who were going to leave at minute six anyway, and it raises the quality of every question asked in the room.
5. 05Who is teaching. A photograph, a first-person paragraph, and the evidence you actually have. Link the fuller bio for the people who want it rather than putting a career on the page.
6. 06The agenda, if the session is long or paid. Optional and frequently harmful. For a forty-five minute session an agenda adds weight without adding information — the outcome bullets already told them what happens. For a paid half-day, it is the thing people are buying.
7. 07The replay policy, in a sentence. Placed where it will be read rather than in a footer. Whatever the answer, it goes here in the same words used in the confirmation and the reminders.
8. 08The second call to action. Same button label, same promise, and the date and time repeated — the reader has scrolled past them and should not have to scroll back to commit.
9. 09A short FAQ, three or four entries. Only the objections that stop a registration: is it live, will it be recorded, how long is it, is there a pitch. Answer the last one plainly. “There is an offer at the end and I will tell you when it starts” costs nothing with the people who were going to buy and buys trust with everyone else.
10. 10The confirmation, which is the tenth block. The page’s job ends at submit; the visitor’s does not. The confirmation restates the date and time in their timezone, hands over the calendar file, and says what arrives next and when. A registration that lands nowhere is a registration you will lose on the day.

What to cut

The video header that autoplays, because it pushes the date below the fold and starts talking at someone who is reading. The second form halfway down that creates a second registration for the same person. The chat widget that opens itself. The logo bar you have not earned. The testimonial you do not have. Anything that animates while the reader is trying to answer three questions.

Then check the whole thing on a phone, first, before you check it anywhere else — a first screen that works on a laptop and fails on a phone is a page that fails for most of the people who will see it. Do the ten-second test again there.

One last pass, and it is the one nobody does: complete a real registration yourself, from a channel link with its source tag on it, using an address you can check. Watch the confirmation page, the confirmation email and the calendar file arrive. Every failure that costs you the most on the day is visible in that thirty seconds of testing and invisible from the editor.

One number judges the page, and it is not registrations.

Registration rate — registrations divided by registration-page visits. It judges the page and the promise on it, and nothing else, which is exactly why it is useful.

Read it per traffic source, always. Your own list converts at one rate and cold social traffic at quite another, and the blended figure is an average of two audiences that hides both. A page can look mediocre in aggregate while converting your list perfectly well and being pointed at by a channel that was never going to work.

The number that keeps this honest

A registration page can be tuned into a higher registration rate and a lower show-up rate: by being vague about the time, by implying a replay you will not send, by stripping the who-it-is-not-for line, by collecting registrations from people who were never going to attend. Every one of those changes looks like an improvement on the page report and shows up as an empty room.

So judge the page on attendees wherever you can trace it that far, and read registration rate next to show-up rate rather than on its own. Both numbers, and the four that sit around them, are defined in the pillar guide’s Measure stage.

Change one thing at a time

Between sessions, change the title, then the first screen, then the form — in that order, one per session, unless the numbers are so thin that the difference could not possibly be read. With small samples, a redesign tells you nothing except that the page is different now. A single deliberate change, repeated across three sessions, tells you something you can keep.