Every tour, preview page and advert you run leads to one place: the join page. It is where a visitor finally decides whether to become a member, and it is surprisingly easy to lose them here. A confusing plan list, a form that asks for too much, or a page that looks different from the rest of the site can be enough to send someone away at the last step.
This checklist walks through what a good join page includes, which checks to ask for and why payment should be handled by your billing processor rather than by your own site. It is general guidance for website owners, not legal advice. The rules on age checks, terms, cancellations and consumer rights vary, so always check what applies in your country and what your billing processor requires.
Make it look like part of the site
Visitors arrive at the join page from your tour. If it suddenly looks different, with a new layout, different colours or no logo, it can feel like they have been sent somewhere untrustworthy. A join page should use the same design, logo and tone of voice as the tour, so the visitor feels they are still on the site they liked.
- Use the same header, logo and colours as the tour.
- Keep the page focused: no long menus, no unrelated links, no adverts for other things.
- Make the logo link back to the site's home page, for visitors who want another look first.
- Check the page on a phone. Many visitors will join from one.
Remind visitors what they are getting
By the time someone reaches the join page they are interested, but a short reminder of the benefits helps them commit. A brief list is enough:
- What kind of content is inside, such as photo sets, videos and stories.
- How much of it there is, or how often it is updated, if that is true and you can keep to it.
- Anything else members get, such as full-size downloads.
Next to the benefits, show the plan and price clearly. Visitors should be able to see exactly what they will pay, how often and for what, before they type anything. If you offer several plans, keep the choice simple and make the differences obvious. Hidden or vague pricing is one of the quickest ways to lose trust.
Ask only for what you need
Every extra field on a form is another reason to give up. A join page normally needs very little from the visitor, because the billing processor's checkout collects the payment details. A typical form only needs:
- An email address. This is where login details and receipts go.
- The email address again. Typing it twice catches typos, which would otherwise leave a new member without their login.
- An age confirmation where your content requires it.
- Agreement to your terms, with a link to the terms themselves.
Check that both email boxes match, and that the required boxes are ticked, before the visitor moves on. Show a friendly message beside the field that needs attention rather than a vague error at the top of the page.
Which checks, wording and links your join page needs depends on where you and your members are, and on your billing processor's rules. Check what applies in your country and with your processor before you go live, and keep your terms and policies up to date.
Let the billing processor take payment
Your join page should never collect card details itself. Handling card numbers on your own server brings security responsibilities and risks that most site owners do not want. Billing processors run checkouts built for exactly this job, and they deal with the payment, the receipt and the membership account.
The join page's job is simply to hand the visitor over to the processor's checkout, ideally with the email address already filled in so they do not have to type it a third time. After payment, the processor or your members script creates the login, and the member signs in to the members area in the usual way. Our guide to members area login methods explains how that login is then recognised.
| Part of joining | Handled by |
|---|---|
| Benefits, plan details, email and checks | Your join page |
| Card details and payment | Your billing processor's checkout |
| Membership account and password | Your billing processor or members script |
| Showing content to the new member | Your members area |
Quick pre-launch checklist
- The page matches the tour's design and works on a phone.
- Benefits and the plan and price are visible without scrolling far.
- The form asks for email, confirm email, age confirmation where needed and terms agreement, and nothing more.
- Mismatched emails and unticked boxes are caught with a clear message.
- The button sends the visitor to the processor's checkout, with the email filled in.
- No card details are ever entered on your site.
- You have tested a full sign-up from tour to members area.
Every route into the join page matters too. Our guide to set preview pages that turn visitors into members covers the pages that send visitors here.
How Members CMS handles this
Members CMS includes a ready join page as part of each website's tour. It uses the same design as the tour pages and shows a benefits list and a plan and price card, followed by email and confirm email fields and boxes for the 18+ age confirmation and your terms. Once those are filled in, the visitor is sent to your billing processor's checkout with their email already filled in. No card details are ever taken on the site.
All the tour wording, including the join page text, lives in one tour-config.php file, so you can adjust it to match your plans and your processor's requirements. An optional age warning box with your own legal links is also available where your content requires it. Members CMS does not handle billing, payments or member accounts; those stay with your billing processor or members script, which keeps payment where it belongs.
Frequently asked questions
Should my site collect card details itself?
No. Let the billing processor's checkout take payment. Your join page only needs to send the visitor there, which keeps card data off your server.
Why ask for the email twice?
Typing it twice catches mistakes, so the member gets their login details and receipts.
What checks should a join form include?
At least confirmation of the visitor's age where your content requires it and agreement to your terms, checked before the visitor is sent to checkout.
