a builder's codex
codex · playbooks · Landing page CRO rubric playbook

Landing page CRO rubric playbook

Scoring rubric · 7 sections, weighted

The LP Audit System

High weight
Hero · 25%headline clarity, CTA above fold, trust signal visible
Value proposition · 20%outcome-specific, differentiates from alternatives, matches buyer language
If hero scores 1 on any dimension: automatic BLOCK regardless of weighted score.
Mid weight
Social proof · 15%specificity of testimonials, logo trust, review count + recency
Objection handling · 15%top 3 objections addressed, FAQ quality, pricing transparency
CTA clarity · 10%button copy outcome-led (not "Submit"), placement, repetition
Lower weight
Trust + risk reversal · 10%security badges, guarantees, privacy commitment
Page mechanics · 5%load-speed signals, mobile readiness, form-friction count
Gate: weighted score < threshold = BLOCK with prioritized fix list. Ship = ≥ 3.5–4.0 by page type.

A section-by-section audit of a landing-page draft that produces weighted scores, a prioritized fix list, and a ship/block decision. Use as a gate inside the LP ship workflow, runs after voice enforcement, before any synthetic-audience or live test.

Source synthesis: Peep Laja (Wynter, quantified message testing), Craig Sullivan (CRO audit framework), Joanna Wiebe (above-the-fold copy), Brian Massey (Conversion Sciences rubric), and the ai-marketing-claude market-landing 7-point framework.

When to use

The 7-section rubric

Each section scored 1–5 with rationale. Weights reflect conversion impact.

SectionWeightScoring focus
1. Hero25%Headline clarity, CTA above fold, visual relevance, trust signal visible
2. Value proposition20%Outcome-specific, differentiates from alternatives, matches buyer language
3. Social proof15%Specificity of testimonials, logo trust, review count and recency
4. Objection handling15%Top 3 objections addressed, FAQ quality, pricing transparency
5. CTA clarity10%Button copy outcome-led (not "Submit"), placement, repetition
6. Trust and risk reversal10%Security badges, guarantees, refund policy, privacy commitment
7. Page mechanics5%Load-speed signals, mobile readiness, form-friction count

Page-type thresholds

Page typePrimary goalThreshold (weighted)
SaaS trial signupFree trial start≥ 3.8
Demo requestMeeting booked≥ 3.5
Lead captureEmail / form submit≥ 3.5
Pricing pagePlan selection≥ 3.8 (CTA + objection weights doubled)
Feature comparisonAlternative displacement≥ 4.0

Process

  1. Identify page type, or infer from asset content.
  2. Score each section 1–5 with rationale.
  3. Compute weighted score.
  4. Identify the weakest section (lowest weighted contribution).
  5. Generate prioritized fix list: top 3 specific changes, highest impact first.
  6. Gate: if weighted < threshold, BLOCK with fix list. If hero scores 1 on any dimension, automatic BLOCK regardless of weighted score.
  7. Log the audit.

Output template

PASS / BLOCK — weighted score: X.X / 5.0

Section scores:
  Hero              (25%): N/5 — [key finding]
  Value proposition (20%): N/5 — [key finding]
  Social proof      (15%): N/5 — [key finding]
  Objection handling(15%): N/5 — [key finding]
  CTA clarity       (10%): N/5 — [key finding]
  Trust/risk reversal(10%): N/5 — [key finding]
  Page mechanics     (5%): N/5 — [key finding]

Weakest section: [name]
Priority fixes:
1. [Hero fix]
2. [Value-prop fix]
3. [Weakest-section fix]

Gates

Composes with

Common failure modes

Open the interactive view →