How to Test a Landing Page When You Have No Traffic Yet

You cannot A/B test a landing page with no traffic, and you shouldn’t try. With zero visitors the useful question isn’t “which variant wins” but “where does a first-time reader stop understanding me”, and that question can be answered by four methods that need no traffic at all: a structured cold read, five friendly humans, a paid human panel, or a synthetic buyer panel. Do the diagnosis now, save the A/B testing for when you have thousands of visitors a month.

Most advice about improving a landing page silently assumes you already have an audience. Test your headline. Test your CTA. Let the data decide. It’s decent advice for a page doing 40,000 sessions a month. For a page that launches next Tuesday and has been seen by you, your co-founder and your mum, it’s useless.

So let’s do the thing nobody does, which is actually work out how much traffic A/B testing requires.

The trap: run the numbers before you take the advice

Say your page will do 100 visitors a month once you switch the ads on. You’d like a 3% signup rate, which is a reasonable target for a decent B2B page. You want to know whether a new headline lifts you 20% relative, from 3.0% to 3.6%.

Here’s the standard two-proportion sample size calculation. It’s the same one every A/B calculator runs under the bonnet:

n per variant = (Z_α/2 + Z_β)² × [ p₁(1−p₁) + p₂(1−p₂) ] ÷ (p₂ − p₁)²

With a two-sided test at 95% significance and 80% power, Z_α/2 = 1.96 and Z_β = 0.8416, so the leading constant is (1.96 + 0.8416)² = 7.85. Plugging in p₁ = 0.030 and p₂ = 0.036:

• p₁(1−p₁) = 0.030 × 0.970 = 0.0291
• p₂(1−p₂) = 0.036 × 0.964 = 0.034704
• sum = 0.063804
• (p₂ − p₁)² = 0.006² = 0.000036
• n = 7.85 × 0.063804 ÷ 0.000036 = 13,911 per variant

Two variants, so 27,822 visitors for one conclusive test. At 100 visitors a month that is 278 months. Roughly 23 years for a single headline test. Check the arithmetic yourself; every step is above.

Even at ten times the traffic, 1,000 visitors a month, you’re waiting 28 months for one answer. You will have pivoted, run out of money, or both.

There’s a second problem that’s easier to feel. At 100 visitors and a 3% rate you collect about three signups a month across the whole page. Split the traffic in half and each variant gets roughly 1.5. One extra signup landing in variant B looks like a 33% lift and means nothing whatsoever. You would be reading tea leaves with a dashboard.

This isn’t an argument that A/B testing is broken. It’s a scale mismatch. If you want the full sample size table across several baselines, I’ve worked it out in How Many Visitors Do You Need to A/B Test?.

What you actually need at this stage

The A/B test answers a comparison question: given two things I already believe in, which performs better? That question only becomes interesting once your page is basically working.

Before launch, your page has a different failure mode. It isn’t losing a close race against a slightly better headline. It’s losing readers in the first eight seconds because they can’t tell what category of thing you sell, or in the middle because a claim arrived without evidence, or at the bottom because the CTA asks for a 30-minute call from someone who arrived four paragraphs ago.

The pre-launch question is: where does a first-time reader stop understanding me?

That’s a comprehension and friction question, and comprehension problems are visible in a sample of five. You don’t need statistical power to discover that nobody knows what your product does. You need one honest stranger.

The awkward part is that you are structurally incapable of being that stranger about your own page. You know what the product does, so your copy reads as obvious to you. This is the curse of knowledge, and no amount of careful re-reading fixes it. Which is why the methods below all involve getting a perspective that isn’t yours.

Four things you can do with zero traffic

Ranked from cheapest to strongest signal. The honest answer is that you should do more than one.

Method	Cost	Time to result	Best at	Weakest at
Structured cold read	Free	30 minutes	Catching obvious gaps you’d notice if you slowed down	Anything you’re blind to
Five friendly humans	Favours	2–4 days	Real comprehension failures, genuine confusion	Politeness bias, wrong audience
Paid human panel	Hundreds to low thousands	3–10 days	Emotional reaction, true stranger behaviour	Cost, recruitment lag, small n
Synthetic buyer panel	Free to ~$49/mo	Minutes	Structural friction across many buyer types at once	Emotional nuance, exact price sensitivity

1. Read it cold, with a protocol

Free, and better than nothing if you impose rules on yourself. Unstructured re-reading is worthless; a protocol is not.

1. Open the page, look at it for five seconds, close the tab. Write down what the product does, who it’s for, and what you’re meant to do next. If you can’t answer all three from memory, a stranger has no chance.
2. Read it as your most sceptical buyer, not your champion. The CFO. The engineer who has been burned. Where do they stop?
3. Walk top to bottom listing every question the page raises but doesn’t answer before the CTA. Pricing, integrations, “is this for someone my size”, “what’s the catch”.
4. For every superlative, look immediately to its right. Is there evidence within one screen? A claim with no proof next to it is friction.
5. At the CTA, ask whether the size of the ask matches the trust you’ve earned by that point on the page.

This surfaces maybe half the problems. The half it misses is the half you’re blind to, which is unfortunately the important half.

2. Five friendly humans

Send the URL to five people who resemble your buyer. Don’t ask “what do you think” — that produces compliments. Ask them to narrate: what do you think this does, what would you want to know before signing up, at what point did you lose interest.

Real strangers are better than friends because friends fill in gaps out of goodwill. If you can get five people who genuinely don’t know what you’re building, take that over ten who do. The tradeoff is speed: this takes days, and people are slow to reply.

3. A paid human panel

Recruited testers reading your page on camera, thinking aloud. This is the highest-fidelity option and it’s genuinely good. It also costs real money, takes the better part of a week to recruit and run, and gives you five to eight people, which means you’ll catch big comprehension failures and miss anything subtler. Worth it before a launch you’ve spent six months on. Overkill for a page you’re iterating on twice a week.

4. A synthetic buyer panel

This is what Buyer Clone does. You paste a URL, and a panel of AI buyer-persona agents moves through the page the way distinct customer types would: the economic buyer, the technical evaluator, the sceptic, the person who’s already comparing you to two competitors. Each one reports where it stalled, what it doubted, where it bounced or converted, and you get a ranked conversion brief pointing at the highest-cost friction first.

Under ten minutes. No snippet to install, no traffic, nobody to recruit. The model tracks an attention budget per persona that drains when the page makes them work and refills when something lands clearly, which is what turns “this section is a bit wordy” into “this section is where the CFO stopped reading”.

There’s a live sample report at /sample if you’d rather see the output than read a description of it, and the free tier is $0 if you want to run your own page through it before deciding anything. Paid plans start at $19/mo, with Growth at $49 and Pro at $149.

The natural move at this stage is to run the synthetic panel first, because it’s fast and cheap enough to do on a draft, then spend your human research budget on whatever it flagged that you didn’t already know.

Where each method falls down, including ours

Every one of these has a real weakness, and pretending otherwise would make this a worse article.

The cold read is limited by your own knowledge. You will read past the sentence that confuses everyone else, because to you it isn’t confusing. Protocols narrow this gap; they don’t close it.

Five friendly humans are biased toward encouragement. People who like you soften their feedback, and people who aren’t your buyer will confidently tell you things that don’t apply. You’re also getting five data points, which is fine for comprehension and hopeless for anything requiring a rate.

Paid human panels give you excellent depth on a tiny sample, slowly and expensively. They’re also subject to the observer effect: someone being paid to examine your page examines it far more carefully than a visitor who wandered in from an ad.

Synthetic buyer panels, ours included, have specific limits worth stating plainly. We’re strong on structural friction: unclear copy, missing proof, weak or mistimed CTAs, pricing opacity, claims that arrive without evidence. Those are the failures that dominate pre-launch pages, and they’re the ones that are legible from the page itself.

We’re directional only on emotional nuance and on exact pricing sensitivity. If a persona says the $49 tier feels expensive, treat that as “price is doing work on this page” and not as a demand-curve estimate. And once you have real traffic, this is not a replacement for real user research or for measurement. It’s the thing you do when measurement isn’t available yet.

An agent also can’t tell you whether the market wants the product. It can tell you whether the page explains it.

The pre-launch protocol

Here’s the sequence, in the order that wastes the least of your time. It assumes you have a built page and roughly a week.

1. Do the cold read first. Thirty minutes, using the five steps above. Fix everything you catch. This is free and it removes the noise that would otherwise dominate everyone else’s feedback.
2. Run a synthetic buyer panel on the fixed draft. You want the structural pass done before you spend anyone’s attention. Look for the friction that repeats across multiple personas, because agreement across buyer types is your strongest signal.
3. Fix in ranked order, one pass. Take the top three items. Resist the urge to rewrite the whole page, because you want to know which change did what.
4. Re-run and compare. The friction you fixed should stop appearing. If a persona still stalls in the same place, your fix addressed the symptom rather than the cause. This loop is why the fast, cheap method is worth having: you can afford to do it four times in an afternoon.
5. Now spend the human budget. Five real people, or a paid panel if the stakes justify it. Send them the version that has already survived steps 1 to 4, so their attention goes to the subtle problems rather than the obvious ones.
6. Fix what humans found that the agents didn’t. Usually emotional register, tone, trust in the brand itself, whether the offer feels fair. That’s where humans earn their cost.
7. Launch, and instrument it. Analytics, session recording, and a clear definition of what counts as a conversion. You want the measurement running from visitor number one.

That’s four to six days including waiting on humans, and most of it is you rewriting copy rather than buying anything.

When traffic arrives, A/B testing becomes valid

Once you’re actually getting visitors, the maths changes and testing becomes the right tool.

Work out your own threshold before you start, using the formula at the top of this article. A rough guide from the same calculation: at a 5% baseline chasing a 20% relative lift, you need about 8,155 visitors per variant. At a 10% baseline chasing the same relative lift, about 3,838. The higher your conversion rate and the bigger the change you’re willing to make, the sooner testing becomes affordable.

Three rules that will save you from the most common way test programmes go wrong:

• Fix the diagnosed friction before you test. Structural problems dwarf anything you’d A/B, and testing two variants of a page nobody understands just tells you which confusing page is marginally less confusing.
• Decide the sample size in advance and don’t peek. Checking daily and stopping when the green banner appears is the single most reliable way to manufacture fake winners. There’s more on that in Your A/B Test ‘Winner’ Might Be a Coin Flip.
• Test genuine trade-offs, not tweaks. If two directions are both defensible and you honestly can’t reason your way to an answer, that’s an A/B test. Everything else is a decision you should just make.

And if traffic arrives but conversions don’t, that’s a different diagnosis again: start with Getting Traffic but No Conversions or the symptom-by-symptom walk in Why Nobody’s Signing Up From Your Landing Page.

The short version: before launch, diagnose. After launch, measure. A/B testing sits at the far end of that sequence, and reaching for it on day one costs you the two weeks you should have spent making the page comprehensible.

Frequently asked questions

Can I A/B test a landing page with 100 visitors a month?

No. Detecting a 20% relative lift from a 3% baseline requires roughly 13,900 visitors per variant at 95% significance and 80% power, or about 27,800 in total. At 100 visitors a month that’s over 23 years. Diagnose friction instead, and revisit testing when you’re consistently doing thousands of visitors a month.

How many people do I need to find problems on a landing page?

Far fewer than you need to measure a conversion rate. Comprehension failures show up in a handful of readers, because if three of five people can’t tell what your product does, that’s the finding. The large numbers are only needed to detect small differences between two versions, which is a completely different job from spotting that something is broken.

Is AI feedback on a landing page actually reliable?

It’s reliable for structural friction: unclear value propositions, claims without proof, pricing opacity, CTAs that ask too much too early. Those are readable from the page itself, which is why agents do well on them. Treat emotional reactions and price sensitivity as directional signals to investigate rather than measurements, and validate against real people once you have them.

Should I just launch and learn from real traffic instead?

You should launch, but not instead. Paid traffic against an unclear page is the most expensive way to discover that it’s unclear, and the analytics will tell you people left without telling you why. Spend the week before launch on diagnosis so that your first ad dollars land on a page that at least explains itself.

What if I don’t have a landing page yet, only an idea?

Then these methods are premature. Build the page first, even a rough one, because all four techniques above test comprehension of a specific artefact rather than the appeal of a concept. A one-page draft with a real headline, a real offer and a real CTA is enough to start; it doesn’t need to be designed.