Landing Page CRO for CPR Training Companies

Optimizing a course page is different from optimizing a product page because the thing being sold is a seat at a time, and time is the constraint the buyer is under. That means the change that moves the number most is almost never the copy, it is showing real, bookable dates on the page itself. A student who can see Saturday at 9am and click it converts at a different rate from one who has to ask when the next class is. After that, the order of the page matters more than the words in it: eligibility, format, timing, price, then booking. We test in that order because that is the order the questions arrive in.

Start by removing the steps between reading and booking. Put live class dates in the first screen, make the booking work without leaving the page, and make sure it works on a phone, because that is where most of this traffic is. Next, answer the three objections early and plainly: whether the card is the official one their employer will accept, how long the class runs, and whether a seat is available this week. Then check that your tracking is honest before you judge anything. Most pages we look at do not have a copywriting problem, they have a friction problem and a measurement problem stacked on top of each other.

One course, not eight. A headline that names the course and the city. Live dates with an on-page booking step. The certifying body stated clearly, because a student whose employer requires a specific card will bounce rather than guess. Class length, format, and what happens on the day. Price, visible, because hiding it only filters out the people who were going to ask anyway. Location with parking detail. Proof from real reviews, ours currently sit at 4.9 from 300+ reviews. And a short answer to the deadline question. Everything else is optional, and most pages fail because they add the optional parts before finishing the required ones.

Long enough to see enough bookings, which for most training companies means weeks rather than days. The mistake is calling a test on a good Tuesday. We set a hypothesis and a stopping rule before the test starts, run one change at a time so the result is attributable, and refuse to call a result while the underlying conversion tracking is in question. If your traffic is light, we test bigger swings rather than small ones, because a page that is meaningfully different can be judged on less data than a button color can. Slower and honest beats fast and wrong, because a wrong call gets built on.

Usually both, in that order. If the current page tries to serve every course, the first move is a dedicated page for the course that gets the most paid and organic traffic, because a single-intent page is the only fair baseline to test against. From there it is improvement rather than rebuilds: one structured change a month on the page that carries the most volume. Rebuilding repeatedly feels productive and teaches you nothing, since each rebuild changes twenty variables at once. The compounding comes from a page that gets slightly better every month and never gets reset.