Compare competitor landing pages with your own
Collect current page screenshots and ask an assistant to identify differences worth investigating.
How this works
Collect current page screenshots and ask an assistant to identify differences worth investigating. Landing-page comparison can reveal differences worth testing, but a screenshot does not show conversion rates or explain why one design works. The useful output separates observable page choices from hypotheses about their effect.
Capture comparable pages and review them against explicit messaging, layout, trust, and conversion-path criteria. Include your own page as the reference. Turn differences into specific experiments rather than copying a competitor's design or declaring a winner.
Before you start
Comparison goal
Choose the visitor task and conversion action being studied.
Page set
Select relevant competitors and comparable offers.
Capture conditions
Use consistent device size, locale, and access state.
Prepare the inputs
- page_references
- Required
Own and competitor pages
Record retrieval date and any access limits.
- screenshots
- Required
Comparable captures
Keep viewport dimensions and page state.
- page_text
- Required
Visible copy
Preserve important claims and calls to action.
- review_criteria
- Required
Defined dimensions
Separate messaging, hierarchy, trust, and interaction.
- own_constraints
- Required
Brand and product limits
Avoid proposing unavailable features.
Implementation, step by step
Choose comparable journeys
- Identify the offer and action on each page.
- Exclude or label pages serving a materially different buyer or funnel stage.
Checkpoint: A comparison scope.
Capture current evidence
- Record screenshots and readable text at the agreed viewport.
- Note hidden content, consent banners, and interactions not observed.
Checkpoint: A dated page evidence set.
Describe observable choices
- Compare headline promise, information order, proof, form effort, and action visibility.
- Use concrete observations rather than aesthetic verdicts without reasons.
Checkpoint: A criterion-based comparison table.
Identify likely friction
- Connect differences to the visitor's task and your own page's stated goal.
- Label effects as hypotheses because competitor conversion data is unknown.
Checkpoint: A friction and opportunity shortlist.
Design original tests
- Propose bounded changes to your own page using approved product facts and brand rules.
- Specify the changed variable and the result to observe.
Checkpoint: A test-ready recommendation set.
Review and prioritize
- Check feasibility and avoid bundling several untested changes into one vague redesign.
- Deliver evidence and experiment options for the page owner.
Checkpoint: A focused comparison brief.
Decisions along the way
Competitor page targets a different segment
Treat it as inspiration only and note the mismatch.
A dynamic interaction cannot be observed
Mark it unknown rather than infer behavior from the screenshot.
A competitor makes an unsupported claim
Do not import the claim into your own page.
What you will produce
landing-page-comparison.csv
CSVSeparates facts from interpretation.
Include: page · criterion · observation · evidence · hypothesis
page-experiment-brief.md
MarkdownSupports original improvement tests.
Include: problem · proposed_change · variable · measure · constraints
Check the result
- Verify every observation against the captured page.
- Keep viewport and page-state differences visible.
- Check proposed copy against own product facts.
- Ensure no claim about competitor conversion or revenue appears without evidence.
When something goes wrong
Screenshot captures a loading state
Recapture or mark the evidence incomplete.
The assistant recommends copying a distinctive layout
Translate the underlying usability principle into an original design.
Several changes cannot be evaluated separately
Prioritize or design a clearly bounded combined experiment.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Compare signup pages for a business dashboard.
Inputs
Synthetic example. Synthetic own page has a 10-field form; a comparable competitor shows a 3-field first step. Conversion rates are unavailable.
Expected result
Synthetic expected result. Propose testing a shorter first step if required data can be collected later. Do not claim the competitor converts better.
Run a small pilot
Start small
Your page and a few directly comparable alternatives.
Record the baseline
Record review time and the usefulness of proposed tests.
Agree success criteria
Agree observation accuracy and testability with the page owner.
Stop or revise
Stop conclusions based on inaccessible states or incomparable offers.
Keep the scope clear
- Public design evidence is not permission to copy assets or wording.
- The comparison does not authorize changing or publishing your page.
Check before using
Check screenshots and context; a competitor’s design does not prove effectiveness.
Business activities
- Run advertising and acquisition tests
- Research customers and markets
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Competitor page list · Your landing page · Review criteria
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow