Splitlab home

Book a Demo

Splitlab home

Book a Demo

Splitlab home
The splitlab.io features page in a desktop browser, between a grid of ten checklist groups, a pass-or-fail checklist card and the splitlab.io integrations page

November 17, 2026

By

Bishal Katuwal

·

13 min

read

Landing Page CRO Checklist: 40 Checks Before You Launch or Test

November 17, 2026

By

Bishal Katuwal

·

13 min

read

Landing Page CRO Checklist: 40 Checks Before You Launch or Test

In the ever-evolving business environment, achieving a competitive edge demands innovative solutions beyond conventional methods. Organizations require smart systems that can optimize workflows, enhance customer interactions, and reveal new avenues for growth. Enter Biotix, the cutting-edge AI-powered CRM management tool.

Forty pass-or-fail checks I run on a landing page before it goes live and before I test anything on it, each with the reason it matters. Fix the fails, then test what’s left.

Bishal Katuwal

Bishal Katuwal

Splitlab Founder

The splitlab.io features page in a desktop browser, between a grid of ten checklist groups, a pass-or-fail checklist card and the splitlab.io integrations page
The splitlab.io features page in a desktop browser, between a grid of ten checklist groups, a pass-or-fail checklist card and the splitlab.io integrations page

A landing page CRO checklist is a list of pass-or-fail checks you run on a page before you launch it and before you A/B test it. This one has 40 checks in 10 groups: message match, the first screen, copy and offer, proof and trust, the call to action, the form, mobile, speed, tracking and test readiness. Each check comes with the reason it matters, because a check you don’t understand is easy to skip. Fix anything that fails. Then test the things that pass but could be better.

Most CRO checklists stop at the page. I add two groups at the end, tracking and test readiness, because they’re where most tests quietly go wrong. A page can pass every design check and still give you a wrong answer if the revenue isn’t tracked or the test is too small to read.

If you want the bigger picture behind these checks, it’s in my guide to landing page optimization best practices. This post is the working version: open your page, go down the list, and mark each line.

Key takeaways

  • Run it twice: once before launch and once before every test.

  • Fails first, tests second. A broken form or missing tracking isn’t something to A/B test. It’s something to fix.

  • The first screen carries the page. Nielsen Norman Group found 57% of viewing time is spent above the fold.

  • Message match decides whether people stay. The page has to repeat what the ad, post or email promised.

  • Tracking is part of CRO. If you can’t see revenue per visitor by variant, you can’t tell a winner from a page that just got more sign-ups.

How to use this checklist

Go through each group and mark every check pass or fail. Be strict: “sort of” is a fail.


The landing page CRO checklist at a glance: 10 groups of 4 checks each (traffic and message match, the first screen, copy and offer, proof and trust, call to action, form and checkout, mobile, speed and technical, tracking and attribution, test readiness), with form and checkout, speed and technical, and tracking and attribution marked fix first

Then work through the fails in this order:

  1. Anything broken: tracking, the form, the checkout, a page that loads slowly on a phone. These cost you every visitor, every day.

  2. Message match and the first screen. Cheap to change, and they decide whether people stay at all.

  3. Everything else, as A/B tests, starting with the page that gets the most traffic.

1. Traffic and message match

Message match means the page keeps the promise the visitor clicked on. Say someone taps an Instagram post that reads “Get 50 booked calls a month without cold DMs”. The page should open with that same promise, not “Welcome to Acme Coaching”. The same goes for a Meta ad, a Google ad or a link in your newsletter. When the words change, people assume they’re in the wrong place and go back.

  • The headline repeats the ad. Pass if the promise from the ad, post or email appears in the headline, in similar words. Why: people decide in a few seconds whether they’re in the right place, and the fastest proof is seeing the words they just clicked on.

  • The page matches the visitor. Pass if cold traffic gets more explanation than your email list does. Why: a stranger from a Facebook ad doesn’t know you yet and needs the what, who and why. Your list already does, and a long explanation only slows them down.

  • One audience per page. Pass if you aren’t sending two very different audiences to the same page. Why: a page written for beginners and experts at once speaks clearly to neither. Separate pages let each one match its own ad.

  • Links don’t leak. Pass if the page has no main navigation or footer links that pull people away from the offer. Why: every extra link is an exit. On a page you paid to send people to, the only way forward should be the offer.


Message match example: a mock Facebook ad from Splitlab, tagged EXAMPLE, says “Stop guessing which page makes money. See revenue per variant.” and the live splitlab.io headline it lands on says “Optimize for revenue, not just conversion rates.” Both make the same promise: revenue

2. The first screen

The first screen is the only part of the page every visitor sees. In Nielsen Norman Group’s eyetracking research, 57% of viewing time went to the area above the fold and 74% to the first two screenfuls. If the first screen fails, most visitors never see the rest.

  • It says what they get. Pass if a headline plus one supporting sentence explain it, with no jargon and no scrolling. Why: people don’t scroll to find out what a page is about. If the top doesn’t tell them, they leave.

  • One main button. Pass if one clear action is visible without scrolling. Why: two equal buttons make people choose, and every choice is a chance to do nothing.

  • The button says the result. Pass if it reads like “Get my free guide”, not “Submit”. Why: a label that names the outcome reminds people what they get for clicking. “Submit” only reminds them they’re giving something away.

  • A risk reducer sits by the button. Pass if a guarantee, “No card needed” or “Cancel anytime” sits right under or beside it. Why: the moment of most doubt is just before the click. A line that removes the risk answers the last worry exactly where it happens, instead of in an FAQ nobody reaches. On our homepage it’s “We’ll increase your conversion rate by 30% or you don’t pay”, right above the button.


The splitlab.io first screen on a phone passing four checks: 1 the headline says what you get, revenue not just conversion rates; 2 a risk reducer, “30% or you don’t pay”, sits right above the button; 3 one main Book a Demo button, with Book a Demo as a softer link; 4 proof from a live purchases card

3. Copy and offer

This is where people decide whether the offer is for them, so clear beats clever. Unbounce’s 2024 benchmark report found pages written at a 5th to 7th-grade level converted at 11.1%, against 5.3% for professional-level writing.

  • Easy to read. Pass if a free readability checker scores it at 9th grade or below. Why: hard words slow people down, and every extra second of effort is a reason to leave.

  • Outcomes before features. Pass if each section opens with what the visitor gets, then how. Why: people buy the result. A feature only matters once they can see what it does for them.

  • The main objection is answered. Pass if price, time or trust, whichever your sales calls hear most, has a direct answer on the page. Why: visitors who read but don’t act have a reason. If the page never answers it, they leave to think it over, and most don’t come back.

  • The offer is clear. Pass if price, what’s included and what happens after they act are all stated plainly. Why: uncertainty feels like risk. If people can’t tell what they’ll get or what happens next, they wait.

4. Proof and trust

Proof answers “does this work for people like me?” Trust answers “is it safe to pay here?” Both work best right where people decide, not in a testimonials section at the bottom.

  • Proof sits near the button. Pass if your strongest testimonial, result or review is within a scroll of the main call to action, ideally with a star rating and review count right under the button. Why: someone hesitating at the button won’t scroll to the bottom to look for testimonials. The proof has to be where the doubt is.

  • The proof is specific. Pass if it uses names, numbers, screenshots or a real look at the product, not “customers love us”. Why: specific proof is believable because it could be checked. “Booked 14 calls in the first week” beats “Great program!”

  • Recent activity is visible. Pass if real purchases or sign-ups show up as a small proof pop-up, like “Mary from Massachusetts just purchased”. Why: seeing other people buy right now makes the decision feel normal and safe. Only show real activity. Made-up names are easy to spot and cost you more trust than they win.

  • Trust basics are there. Pass if contact details, refund terms and a privacy link are easy to find, and the checkout shows a money-back guarantee, a secure-checkout badge people recognize (such as Norton or McAfee) and the cards you accept (Visa, Mastercard, Discover, Amex). Why: in Baymard Institute’s research, 19% of US shoppers who abandoned an order said they didn’t trust the site with their card details. These signals answer that at the moment of payment.


Example mockup on splitlab.io around the Book a Demo button, tagged EXAMPLE: 1 a five-star rating line, 4.9 from 212 reviews, right under the button; 2 a small proof pop-up, Jordan from Austin, TX just started a revenue test, verified 4 minutes ago; 3 a row of Secure checkout, Visa, Mastercard and Amex badges. The rating, pop-up and badges are illustrations of the technique, not live on the site

5. Call to action

The call to action is where attention turns into a result, so it has to be obvious, consistent and working.

  • One page, one job. Pass if every button on the page leads to the same action. Why: different buttons split attention. One action, repeated, is easier to say yes to.

  • It repeats down the page. Pass if the same call to action appears after each major section. Why: people decide at different points. Whoever is convinced halfway down should find the button right there, not have to scroll back up.

  • It looks clickable. Pass if it’s high contrast, button-shaped and easy to find in a second. Why: if people have to hunt for the button, some won’t bother.

  • It works. Pass if you clicked it yourself today, on desktop and on a phone. Why: broken buttons and dead links are more common than anyone admits, and they cost you every visitor without showing up anywhere.

6. Form and checkout

Baymard Institute finds most checkouts need only 8 form fields, but the average in 2024 had 11.3. Its average documented cart abandonment rate, across 50 studies, is 70.22%.

  • Only the fields you need. Pass if every field is needed for the next step. Why: every field is a small reason to stop. You can collect the rest later, once they’re a lead or a customer.

  • Labels stay visible. Pass if labels sit above fields, not only inside them as placeholder text. Why: placeholder text disappears as soon as people type, so they forget what the field was for, especially on a phone.

  • Errors are helpful. Pass if a wrong entry shows a clear message next to the field, and nothing typed is lost. Why: a form that wipes everything after one mistake loses a lot of people on the spot.

  • Checkout is short. Pass if there’s no forced account creation and as few steps as you can manage. Why: in Baymard’s data, 18% of shoppers who abandoned an order left because the site wanted them to create an account, and 17% because checkout was too long or complicated.

7. Mobile

For most funnels, the phone is where the traffic is. In the paid-ad funnels I run it’s often 90% or more, and the buying starts on the phone, not on a desktop later. So check every page on a phone first, then on a laptop.

  • The promise fits the phone screen. Pass if the headline, one sentence and the button show before any scrolling. Why: a phone’s first screen is small. If the promise doesn’t fit, most people never reach the button.

  • Thumb-friendly. Pass if buttons and fields are big enough to tap without zooming. Why: missed taps feel like a broken page. People don’t zoom in to buy. They leave.

  • Nothing covers the offer. Pass if no pop-up or cookie banner hides the first screen. Why: on a phone a pop-up often covers the whole screen, and if the first thing people see is a close button, many leave instead.

  • Forms work on a phone. Pass if the right keyboard appears for email and phone fields, and autofill works. Why: typing on a phone is slow. The right keyboard and autofill turn a one-minute form into a few seconds.


The splitlab.io features page on a 390px phone screen with four passing checks: the promise fits the screen, the Book a Demo button is thumb-sized, Book a Demo is a softer text link, and nothing covers the offer

8. Speed and technical

  • Main content loads fast. Pass if Largest Contentful Paint is 2.5 seconds or less in PageSpeed Insights, on mobile. Why: people judge a page before it finishes loading, and a blank screen on mobile data is the fastest way to waste a paid click.

  • The page responds quickly. Pass if Interaction to Next Paint is 200 milliseconds or less. Why: if a tap does nothing for a moment, people tap again or give up, often on the buy button itself.

  • Nothing jumps around. Pass if Cumulative Layout Shift is 0.1 or less. Why: when the layout shifts, people tap the wrong thing or lose their place, and the page feels broken.

  • Heavy items are trimmed. Pass if images are compressed, video loads only when played, and unused scripts are removed. Why: these are the usual causes of a slow funnel page, and they’re cheap to fix.

These are Google’s “good” thresholds for Core Web Vitals. Speed matters for conversions too: in Portent’s 2022 analysis of 20 sites, B2B pages that loaded in 1 second converted 3x better than pages that took 5 seconds.

9. Tracking and attribution

This is the group most CRO checklists skip, and it decides whether you can trust anything you learn from the page.

  • The goal is tracked. Pass if the form submit or purchase fires a conversion event, and you’ve tested it with a real submission. Why: if the goal isn’t tracked, every decision after it is a guess.

  • Revenue is tracked. Pass if order value is recorded, including upsells and order bumps where you have them. Why: conversion rate alone can’t tell a page that sells more from a page that gets more cheap sign-ups.

  • Refunds come off. Pass if refunded orders are subtracted, so revenue isn’t overstated. Why: a page that sells harder can also get refunded more. Without refunds, it looks like a winner when it isn’t.

  • You can split it. Pass if you can see results by traffic source and by device. Why: a page can work for your email list and fail for cold ads, and blended numbers hide that.

If your checkout lives on another platform, the visitor’s test variant has to follow them there, or the sale is credited to nobody. In Splitlab that’s what the integrations do: they connect your funnel builder, store or booking tool, so every order, upsell, won deal and booking is credited to the variant the visitor saw.


The splitlab.io integrations page on desktop: every order, upsell, won deal and booking is credited to the variant the visitor saw, with ClickFunnels 2.0, ClickFunnels Classic and GoHighLevel listed. Below, the flow: a visitor sees variant B, buys plus an upsell in ClickFunnels, HighLevel or your store, and the Splitlab integration credits the order to variant B

10. Test readiness

  • You have a baseline. Pass if you know the last 30 days’ conversion rate and revenue per visitor for this page. Why: without a starting number, you can’t tell whether a change helped.

  • The main metric is picked. Pass if it’s chosen before the test starts: revenue per visitor for pages that sell. Why: picking the metric after you see the results makes it easy to call whatever moved a win.

  • The hypothesis is written. Pass if “Because X, changing Y will raise Z” is written down before launch. Why: a written reason tells you what you learned, even when the test loses.

  • There’s enough traffic. Pass if you can reach enough visitors in a few weeks to read the result. If not, test a bigger change. Why: small tweaks on small traffic end in noise, while bold changes show up faster.

For a sense of scale: at a 2% conversion rate, you need about 750 visitors per version just to know the true rate is somewhere between 1% and 3%. Telling 2.0% from 2.5% takes thousands. That’s why small pages should test bold changes, like a new offer or headline, not small tweaks.


The Splitlab test setup Metrics step listing Revenue per Visitor (RPV), Average Order Value (AOV) and Conversion Rate (CVR): revenue per visitor is the main metric for pages that sell, conversion rate (unique buyers divided by unique visitors) sits beside it, and you star any metric to make it the primary

In Splitlab, revenue per visitor, average order value and conversion rate are available on every test, and you star one to make it the main metric before you start. I explain why I pick revenue per visitor in revenue per visitor vs conversion rate.

What to do after the checklist

When everything that’s broken is fixed, the remaining “could be better” items become your test list. Rank them by how many visitors they affect and how cheap they are to change, then test one at a time.

If you aren’t sure where your page loses people, start with my guide on how to increase landing page conversion rate. And if the page sells something, check your numbers against these sales page conversion rate benchmarks before you decide it’s underperforming.

How Splitlab helps

Splitlab runs A/B, multivariate and multi-armed bandit tests on funnel pages, including pages built in ClickFunnels and HighLevel. It connects each visitor to the purchase they make later and reports revenue per visitor next to conversion rate, so groups 9 and 10 of this checklist are covered from the first test. See the features or book a demo.

FAQ

What should a landing page CRO checklist include?

Checks for message match, the first screen, copy and offer, proof and trust, the call to action, forms, mobile, speed, tracking and test readiness, each with a reason. The last two groups are often missing, and they decide whether your test results can be trusted.

How often should I run a CRO checklist on my landing page?

Before launch, before every A/B test, and whenever you change traffic sources. A page that works for your email list may fail the message-match checks for cold ads.

Should I fix everything on the checklist before testing?

Fix anything broken first: tracking, forms, checkout and speed. Items that work but could be better are better tested than changed blindly, because some “improvements” lose money.

What is the most important item on a landing page CRO checklist?

Message match on the first screen. Whatever the visitor saw before clicking, an Instagram post, a Meta ad, a Google ad or an email, the headline should repeat that promise. If it doesn’t, many people leave before they read anything else.

My final thoughts

This checklist is long on purpose, but you don’t need a perfect score. You need zero fails in the places that cost you every visitor: message match, the first screen, a working form and tracking you can trust.

Fix the fails first, then test the weak spots one at a time. I run it before every launch and again before every test, because pages drift. A new pop-up, a slower script, a broken link in the checkout.

And don’t skip group 9. If you can’t see revenue by version, you can’t tell a real winner from a page that just collected more sign-ups. That’s the gap Splitlab closes. Book a demo to see it on your funnel.

Fix what’s broken. Test what’s uncertain. Keep what makes money.

Built for revenue

Test for revenue, not just clicks.

Run A/B, multivariate, and multi-armed bandit experiments — with real revenue tied to every variation.

We’ll increase your conversion rate by 30% or you don’t pay. Terms apply.

✓

Revenue per variation

✓

A/B & MVT

✓

Multi-armed bandit

Test for revenue, not just clicks.

A/B, multivariate and multi-armed bandit experiments, with real revenue tied to every variation.


Start optimizing for revenue today not just conversion rates.

Run experiments, track revenue per variation, and scale what actually makes you money.

We’ll increase your conversion rate by 30% or you don’t pay. Terms apply.


Start optimizing for revenue today not just conversion rates.

Run experiments, track revenue per variation, and scale what actually makes you money.

We’ll increase your conversion rate by 30% or you don’t pay. Terms apply.


Start optimizing for revenue today not just conversion rates.

Run experiments, track revenue per variation, and scale what actually makes you money.

We’ll increase your conversion rate by 30% or you don’t pay. Terms apply.