Complete firstPage
Document target segment, value proposition, primary CTA, qualified follow-up action, traffic source, observation window, and decision threshold in advance.
Test one value proposition or one clearly named variant at a time.
Method guideProduct Discovery
Landing Page Test
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityMedium
Time1-5 Tage
ParticipantsNutzertraffic
FormatAsync
MaturityEstablished
01
Prerequisite
What needs to be finished first
Complete firstExperiment
Reduce the page to one value proposition and one primary action. Trigger analytics in test mode, inspect mobile rendering, and preserve the source for each visit.
Make the next action available and treat interested people transparently.
02
Preparation
What needs to be ready before start
Materials
Value proposition hypothesis, landing-page draft, one primary CTA, analytics with tested events, documented traffic source, and privacy copy.
People / roles
Experiment owner · content/design · analytics · channel owner · decision owner
Pre-read
Document target segment, value proposition, primary CTA, qualified follow-up action, traffic source, observation window, and decision threshold in advance.
Time needed
3–10 days for design, traffic collection, and analysis; 60–120 minutes for the hypothesis and measurement plan.
Setup
Reduce the page to one value proposition and one primary action. Trigger analytics in test mode, inspect mobile rendering, and preserve the source for each visit.
03
Core question
The one question this method answers
Which variant produces the predefined action more often for the same audience?
04
Flow
Phases with goal, actions, output and pitfall
A Landing Page Test translates a concrete value assumption into a page, brings a relevant audience to it, and measures a predefined action. Evidence depends on audience, traffic source, offer, and measurement rule together.
Landing page test plan
Fictional example
Fictional test of a maintenance offer with one explicit funnel.
Hypothesis
For which segment should which value proposition lead to which action?
Small workshops are more likely to book a 15-minute maintenance call when predictable downtime leads the message.
Page and CTA
Which message, evidence, and primary CTA does the audience see?
Predictable-downtime headline, three proof points, 'Check a maintenance window' CTA; no purchase promise yet.
Funnel and threshold
Which events, sources, and rules are measured?
LinkedIn campaign → page view → CTA → appointment request. Pre-set rule: at least 10 qualified requests from 500 relevant visits.
Result and decision
What was observed, what remains uncertain, and what follows?
480 visits, 31 CTA clicks, 7 requests. Threshold missed; interviews investigate pricing and timing barriers.
The numbers are fictional.
- 1
Value
Focus hypothesis
Goal
Value: State one value proposition and audience precisely enough for a page to test.
Inputs for this step
- Document target segment, value proposition, primary CTA, qualified follow-up action, traffic source, observation window, and decision threshold in advance.
Actions
- State one value proposition and audience precisely enough for a page to test.
Output
Value
Value
Quality check
Does the hypothesis name one segment, one value proposition, and an observable action?
Pitfall
The page tries to test problem, price, brand, and several audiences at once. Return to “Focus hypothesis” and repeat this method step: State one value proposition and audience precisely enough for a page to test.
Timing: 45–60 minutes
- 2
Variant
Build page
Goal
Published test page: Change only the tested variable; keep CTA, audience, and metric rule stable.
Inputs for this step
- Value
Actions
- Change only the tested variable; keep CTA, audience, and metric rule stable.
Output
Published test page
Published test page
Quality check
Is the primary CTA unambiguous and functional on desktop and mobile?
Pitfall
Variants change CTA, copy, and audience together, leaving no clear learning target. Return to “Build page” and repeat this method step: Change only the tested variable; keep CTA, audience, and metric rule stable.
Timing: 0.5–2 days
- 3
Exposure
Assign traffic
Goal
Traceable exposure: Assign relevant visitors to variants randomly or by one predeclared rule.
Inputs for this step
- Published test page
Actions
- Assign relevant visitors to variants randomly or by one predeclared rule.
Output
Traceable exposure
Traceable exposure
Quality check
Do audience, channel, and assignment rule remain stable during the observation window?
Pitfall
Organic, paid, and internal traffic are combined without labels. Return to “Assign traffic” and repeat this method step: Assign relevant visitors to variants randomly or by one predeclared rule.
Timing: 2–7 days
- 4
Measurement
Capture action
Goal
Verified conversion funnel: Record CTA clicks and qualified follow-up by source, period, and variant.
Inputs for this step
- Traceable exposure
Actions
- Record CTA clicks and qualified follow-up by source, period, and variant.
Output
Verified conversion funnel
Verified conversion funnel
Quality check
Can page view, CTA, and qualified follow-up action be measured separately?
Pitfall
Analytics counts internal tests, bots, or repeated events as real conversions. Return to “Capture action” and repeat this method step: Record CTA clicks and qualified follow-up by source, period, and variant.
Timing: 30–60 minutes
- 5
Readout
Decide next experiment
Goal
Experiment decision: Review result, sample, uncertainty, and next hypothesis together.
Inputs for this step
- Verified conversion funnel
Actions
- Review result, sample, uncertainty, and next hypothesis together.
Output
Experiment decision
Experiment decision
Quality check
Does the decision account for traffic quality, sample size, and plausible alternative explanations?
Pitfall
The higher click rate is declared the winner although qualified follow-up actions did not improve. Return to “Decide next experiment” and repeat this method step: Review result, sample, uncertainty, and next hypothesis together.
Timing: 30–45 minutes
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Versioned landing page plus experiment log containing hypothesis, screenshot, traffic, funnel, uncertainty, and decision.
Versioning / ownership
Version the experiment decision with date, owner, source state, and review date. Preserve earlier observations and append changes with their reason.
Tool alternatives
- Landing-page builder or CMS with a mobile-checked draft
- Analytics or tag manager for page view, CTA, and follow-up action
- Versioned experiment log with screenshot and traffic source
landing-page-test-working-template.md
Plan the hypothesis, setup, real run, and analysis with clear ownership.
Landing Page Test: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Whole initiative Time: 3–10 days for design, traffic collection, and analysis; 60–120 minutes for the hypothesis and measurement plan.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Value proposition hypothesis, landing-page draft, one primary CTA, analytics with tested events, documented traffic source, and privacy copy.
- Roles: Experiment owner · content/design · analytics · channel owner · decision owner
- Advance information: Document target segment, value proposition, primary CTA, qualified follow-up action, traffic source, observation window, and decision threshold in advance.
- Overall time needed: 3–10 days for design, traffic collection, and analysis; 60–120 minutes for the hypothesis and measurement plan.
- Setup: Reduce the page to one value proposition and one primary action. Trigger analytics in test mode, inspect mobile rendering, and preserve the source for each visit.
Prepare for the work steps
Value: Focus hypothesis
- Document target segment, value proposition, primary CTA, qualified follow-up action, traffic source, observation window, and decision threshold in advance.
Variant: Build page
- Value
Exposure: Assign traffic
- Published test page
Measurement: Capture action
- Traceable exposure
Readout: Decide next experiment
- Verified conversion funnel
Landing page test plan
Hypothesis
For which segment should which value proposition lead to which action?
...
Page and CTA
Which message, evidence, and primary CTA does the audience see?
...
Funnel and threshold
Which events, sources, and rules are measured?
...
Result and decision
What was observed, what remains uncertain, and what follows?
...
Complete hypothesis, CTA, funnel, and threshold before publishing.
Strategyzer · original teaching example
Value: Focus hypothesis
Expected artifact: Value
Value
Entry:
...
- Does the hypothesis name one segment, one value proposition, and an observable action?
Variant: Build page
Expected artifact: Published test page
Published test page
Entry:
...
- Is the primary CTA unambiguous and functional on desktop and mobile?
Exposure: Assign traffic
Expected artifact: Traceable exposure
Traceable exposure
Entry:
...
- Do audience, channel, and assignment rule remain stable during the observation window?
Measurement: Capture action
Expected artifact: Verified conversion funnel
Verified conversion funnel
Entry:
...
- Can page view, CTA, and qualified follow-up action be measured separately?
Readout: Decide next experiment
Expected artifact: Experiment decision
Experiment decision
Entry:
...
- Does the decision account for traffic quality, sample size, and plausible alternative explanations?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/landing-page-test/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
landing-page-test-beispiel.md
Concrete filled scenario, fictional example
Fictional teaching example: Landing page test plan
Hypothesis
Small workshops are more likely to book a 15-minute maintenance call when predictable downtime leads the message.
Page and CTA
Predictable-downtime headline, three proof points, 'Check a maintenance window' CTA; no purchase promise yet.
Funnel and threshold
LinkedIn campaign → page view → CTA → appointment request. Pre-set rule: at least 10 qualified requests from 500 relevant visits.
Result and decision
480 visits, 31 CTA clicks, 7 requests. Threshold missed; interviews investigate pricing and timing barriers.
The numbers are fictional.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Focus hypothesisThe page tries to test problem, price, brand, and several audiences at once.View in phase
- Build pageVariants change CTA, copy, and audience together, leaving no clear learning target.View in phase
- Assign trafficOrganic, paid, and internal traffic are combined without labels.View in phase
- Capture actionAnalytics counts internal tests, bots, or repeated events as real conversions.View in phase
- Decide next experimentThe higher click rate is declared the winner although qualified follow-up actions did not improve.View in phase
Trap
Focus hypothesis
Symptom
The page tries to test problem, price, brand, and several audiences at once.
What to do
Return to “Focus hypothesis” and repeat this method step: State one value proposition and audience precisely enough for a page to test.
Trap
Build page
Symptom
Variants change CTA, copy, and audience together, leaving no clear learning target.
What to do
Return to “Build page” and repeat this method step: Change only the tested variable; keep CTA, audience, and metric rule stable.
Trap
Assign traffic
Symptom
Organic, paid, and internal traffic are combined without labels.
What to do
Return to “Assign traffic” and repeat this method step: Assign relevant visitors to variants randomly or by one predeclared rule.
Trap
Capture action
Symptom
Analytics counts internal tests, bots, or repeated events as real conversions.
What to do
Return to “Capture action” and repeat this method step: Record CTA clicks and qualified follow-up by source, period, and variant.
Trap
Decide next experiment
Symptom
The higher click rate is declared the winner although qualified follow-up actions did not improve.
What to do
Return to “Decide next experiment” and repeat this method step: Review result, sample, uncertainty, and next hypothesis together.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Pause or return to the previous step when this check is not satisfied: Does the hypothesis name one segment, one value proposition, and an observable action?
Pause or return to the previous step when this check is not satisfied: Is the primary CTA unambiguous and functional on desktop and mobile?
Pause or return to the previous step when this check is not satisfied: Do audience, channel, and assignment rule remain stable during the observation window?
Pause or return to the previous step when this check is not satisfied: Can page view, CTA, and qualified follow-up action be measured separately?
Pause or return to the previous step when this check is not satisfied: Does the decision account for traffic quality, sample size, and plausible alternative explanations?
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.