A/B Testing Your Financial Planning Website's Booking Page
Most financial planning websites get redesigned every few years, with everyone hoping the new version books more first meetings. But a full redesign changes ten things at once — you never learn which one actually helped, and which ones quietly hurt. 💖 Testing one element at a time gives you real answers instead of guesses.
What most practices get wrong: testing cosmetic changes (font, colour, stock photos) instead of the things that actually influence a decision to book — trust signals, the clarity of what the first meeting involves, and how much information the form asks for upfront.
The Booking Page Test Priority List
- Test first: the headline above your booking calendar ('Book Your First Meeting' vs 'Book a Free, No-Obligation Chat')
- Test second: how much you ask for before someone can book (name and email only, vs a longer qualifying form)
- Test third: adding a short trust element near the button — a credential, an AFSL detail, or a one-line note on what the meeting actually covers
- Run each test for at least two full weeks before comparing results
How to run it without enterprise tools
If your booking software (Calendly, Acuity, or similar) supports it, you can often run a simple test by sending half your traffic to one page variant via your ad platform or email campaigns. For organic website traffic, many website builders now include basic split-testing tools built in — check before assuming you need to buy something separate.
Mistakes to avoid
- Testing surface-level design changes instead of the copy and friction points that actually affect decisions.
- Only tracking bookings, not attended meetings — a form-start win that increases no-shows isn't a real win.
- Running a test during an unusually busy or quiet period (e.g. just after a market downturn) and treating the result as normal.
- Changing the booking software itself mid-test, which resets all your data.
Frequently asked questions
What if we don't have enough website traffic to test?
Below a few hundred visits a month to the booking page, formal testing will take too long — make one confident, well-reasoned change at a time instead and track the trend over a full quarter.
Should we test our fee disclosure wording too?
You can, but treat it carefully — it needs to stay compliant with your AFSL's requirements regardless of which version books better, so run any wording changes past compliance first.
How long should each test run?
A minimum of two weeks, ideally until each version has at least 50–100 people reach the page, to avoid drawing conclusions from a handful of unusually behaved visitors.
Honestly, will this fix low enquiry numbers on its own?
No — if your traffic volume is the real problem, optimising the booking page won't create visitors who aren't showing up in the first place. Fix the traffic source before micro-optimising the page.
Keep reading 🤍
I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.
Work with me ✦