Page CRO
Production-grade conversion rate optimization framework for marketing pages. Covers the 7-dimension analysis framework, page-type-specific playbooks, copy alternatives methodology, above-the-fold engineering, social proof hierarchy, objection handling patterns, and structured A/B test design.
Table of Contents
Clarify First
Before optimizing the page, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the audit.
Initial Assessment
Required Context
| Question |
Why It Matters |
| What page type? (homepage, landing page, pricing, feature, blog) |
Determines the CRO framework to apply |
| What is the primary conversion goal? |
Focuses the analysis |
| Where is traffic coming from? (organic, paid, email, social) |
Drives message-match requirements |
| What is the current conversion rate? |
Establishes the baseline |
| What does the post-click flow look like? |
The page may convert fine but the next step fails |
| Do you have heatmaps or session recordings? |
Behavioral data reveals what analytics cannot |
| What have you already tried? |
Avoids re-testing failed experiments |
The 7-Dimension CRO Framework
Analyze every marketing page across these 7 dimensions, in order of typical impact.
Dimension 1: Value Proposition Clarity (Highest Impact)
The 5-second test: Can a first-time visitor understand what this is, who it is for, and why they should care within 5 seconds?
| Signal |
Pass |
Fail |
| Primary benefit is stated explicitly |
"Save 10 hours/week on reporting" |
"Next-generation analytics platform" |
| Written in customer language |
"See which campaigns drive revenue" |
"Multi-touch attribution solution" |
| Differentiator is clear |
"The only CRM built for agencies" |
"A better CRM" |
| Specificity |
Includes numbers, timeframes, outcomes |
Vague superlatives ("powerful", "innovative") |
Dimension 2: Headline Effectiveness
Headline scoring rubric:
| Criteria |
Score 0 |
Score 1 |
Score 2 |
| Communicates core value |
No |
Partially |
Clearly |
| Specific (numbers, outcomes) |
Generic |
Somewhat specific |
Very specific |
| Addresses target audience |
Generic |
Implied |
Explicit |
| Matches traffic source |
No connection |
Loose match |
Exact message match |
| Emotional or logical hook |
Neither |
One |
Both |
Total: 0-10. Score < 6 = rewrite needed.
Dimension 3: CTA Hierarchy and Placement
| Check |
Pass |
Fail |
| One clear primary CTA |
Single, prominent action |
Multiple competing CTAs |
| CTA visible without scrolling |
Above the fold |
Below the fold only |
| CTA copy communicates value |
"Start Free Trial" |
"Submit" |
| CTA repeated at decision points |
After benefits, after social proof, at bottom |
Only at top or only at bottom |
| Secondary CTA is clearly secondary |
Smaller, different color, text link |
Same visual weight as primary |
Dimension 4: Visual Hierarchy and Scannability
| Check |
Pass |
Fail |
| Most important element is most prominent |
Headline + CTA dominate |
Navigation or image dominates |
| Scannable in 10 seconds |
Key points visible via headings, bold, bullets |
Wall of text |
| Adequate white space |
Breathing room between sections |
Cluttered, dense layout |
| Images support the message |
Product screenshots, relevant imagery |
Stock photos, decorative graphics |
| F-pattern or Z-pattern layout |
Content follows natural eye flow |
Random placement |
Dimension 5: Social Proof and Trust
| Check |
Pass |
Fail |
| Customer logos visible |
Recognizable logos above the fold |
No logos or unknown companies |
| Testimonials are specific |
"Increased revenue by 40%" |
"Great product!" |
| Testimonials are attributed |
Full name, title, company, photo |
Anonymous or first-name-only |
| Trust badges present (where relevant) |
Security, compliance, awards |
No trust indicators |
| Numbers-based proof |
"10,000+ teams use..." |
No scale indicators |
Dimension 6: Objection Handling
| Check |
Pass |
Fail |
| Price/value objection addressed |
ROI calculation, "starts at $X" |
No pricing context |
| "Will this work for me?" answered |
Use cases, industry examples |
Generic positioning only |
| Risk reduction offered |
Free trial, guarantee, no CC required |
No risk reversal |
| Implementation concern addressed |
"Set up in 5 minutes" |
No setup/complexity context |
| FAQ section present |
Addresses top 5 objections |
No FAQ or irrelevant questions |
Dimension 7: Friction Points
| Check |
Pass |
Fail |
| Form is optimized |
Minimal fields, clear labels |
Too many fields, unclear purpose |
| Next step is clear |
Obvious path forward from every section |
Confusing navigation or dead ends |
| Mobile experience |
Fully responsive, touch-friendly |
Desktop-only design |
| Load time |
< 3 seconds |
> 5 seconds |
| No distracting elements |
Clean, focused design |
Popups, auto-play video, chat widget on load |
Above-the-Fold Engineering
The above-the-fold area is the most valuable real estate on any page. It determines whether visitors scroll or bounce.
Required Elements (Above the Fold)
┌──────────────────────────────────────────┐
│ [Nav: Logo + 3-5 links + Primary CTA] │
├──────────────────────────────────────────┤
│ │
│ HEADLINE: Primary value proposition │
│ │
│ SUBHEADLINE: Supporting detail │
│ │
│ [PRIMARY CTA BUTTON] │
│ [Secondary CTA: text link] │
│ │
│ [Social proof: logos or stat] │
│ │
│ [Hero image or product screenshot] │
│ │
└──────────────────────────────────────────┘
Above-the-Fold Rules
- Headline is the largest text on the page
- CTA button is the most visually prominent interactive element
- Social proof appears above the fold (even just logo strip)
- Hero image shows the product in use (not abstract graphics)
- No auto-play video or animation that distracts from the CTA
- Navigation is minimal (3-5 items max, CTA in nav)
Social Proof Hierarchy
Not all social proof is equal. Use the right type at the right location.
Social Proof Power Ranking
| Rank |
Type |
Strength |
Best Placement |
| 1 |
Case study with metrics |
"Company X increased revenue 40% in 3 months" |
Mid-page, after benefits section |
| 2 |
Named testimonial with photo |
Full name, title, company, headshot |
Near CTA, after objection handling |
| 3 |
Aggregate numbers |
"10,000+ teams" or "4.8/5 on G2" |
Above the fold, near headline |
| 4 |
Customer logos |
Recognizable brand logos |
Above the fold, logo strip |
| 5 |
Awards/badges |
"G2 Leader 2026", "SOC2 Certified" |
Footer or near CTA |
| 6 |
Generic testimonial |
"Great product!" -- no specifics |
Do not use (no credibility) |
Placement Rules
- Logo strip: Above the fold, below the CTA
- Testimonials: After the section that makes the claim they validate
- Case studies: Mid-page, as their own section
- Numbers: Inline with headline or subheadline
- Trust badges: Near the primary CTA and near the form
Objection Handling Architecture
The 5 Universal Objections
Every product page must address these five objections. If the page does not, conversions leak.
| Objection |
How to Address |
Page Element |
| "Is this worth the money?" |
ROI calculator, pricing comparison, "saves X hours" |
Benefits section + pricing context |
| "Will this work for my situation?" |
Industry examples, use case sections, persona targeting |
"Who uses this" section |
| "Is this hard to set up?" |
"Set up in 5 minutes", onboarding preview, integration logos |
Feature section or FAQ |
| "What if it doesn't work?" |
Free trial, money-back guarantee, no CC required |
Near CTA |
| "Why this over alternatives?" |
Comparison table, differentiators, switcher testimonials |
Mid-page or FAQ |
FAQ Design for Objection Handling
The FAQ section should be the last defense before conversion. Structure it to address the 5 objections:
- "How long does setup take?" (complexity objection)
- "Can I cancel anytime?" (commitment objection)
- "What's included in the free trial?" (value objection)
- "Do you integrate with [popular tool]?" (compatibility objection)
- "How is this different from [competitor]?" (alternatives objection)
Page-Type Playbooks
Homepage
| Element |
Best Practice |
| Audience |
Cold visitors who may not know you |
| Headline |
Position the company, not a single feature |
| CTA split |
Primary: "Start Free Trial" / Secondary: "See Demo" or "Learn More" |
| Content |
Overview of benefits, social proof, feature highlights, use cases |
| Navigation |
Full site navigation (unlike landing pages) |
Landing Page (Paid Traffic)
| Element |
Best Practice |
| Navigation |
Remove or minimize (no escape routes) |
| Headline |
Message-match with the ad that drove the click |
| CTA |
Single action, repeated 2-3 times down the page |
| Content |
Complete argument on one page: problem > solution > proof > CTA |
| Social proof |
Directly relevant to the ad audience |
Pricing Page
| Element |
Best Practice |
| Plan presentation |
Good-Better-Best with recommended plan highlighted |
| Toggle |
Annual/Monthly with savings percentage shown |
| Feature comparison |
Full table below the fold |
| FAQ |
"Which plan is right for me?" as first question |
| CTA |
Per-plan CTA with plan-specific copy |
| Social proof |
Logos and testimonials relevant to each tier |
Feature Page
| Element |
Best Practice |
| Headline |
Benefit of the feature, not the feature name |
| Content |
Use cases > technical capabilities |
| Demo |
Screenshot, GIF, or interactive demo |
| CTA |
"Try this feature" or "Start Free Trial" |
| Internal links |
Link to related features and pricing |
Blog Post
| Element |
Best Practice |
| CTA type |
Contextual inline CTA matching the content topic |
| Placement |
After introduction, at natural breaks, at end |
| CTA style |
Inline banner or text link, not aggressive popup |
| Content CTA |
Offer a related resource (template, checklist, tool) |
Copy Alternatives Methodology
When recommending copy changes, always provide 2-3 alternatives with reasoning.
Alternative Generation Framework
For each key element (headline, subheadline, CTA), generate variants across these axes:
| Axis |
Variant A |
Variant B |
Variant C |
| Benefit focus |
Outcome-focused |
Problem-focused |
Feature-focused |
| Specificity |
Numbers and data |
Customer quote |
Use case scenario |
| Tone |
Direct and assertive |
Conversational |
Aspirational |
Example
Current headline: "Marketing Automation Software"
| Variant |
Copy |
Rationale |
| A (outcome) |
"Generate 3X More Qualified Leads Without Adding Headcount" |
Specific outcome + pain point |
| B (problem) |
"Stop Losing Leads Because Your Team Can't Follow Up Fast Enough" |
Addresses the pain directly |
| C (social proof) |
"How 2,000+ Marketing Teams Hit Their Pipeline Targets" |
Authority + specificity |
Recommendation: Test A first (most specific), B if A does not outperform current (different psychological angle).
Traffic Source Matching
Different traffic sources require different page optimization strategies.
| Source |
Visitor State |
Page Must Do |
| Paid search (brand) |
Knows you, high intent |
Fast path to action, minimal education |
| Paid search (non-brand) |
Problem-aware, solution-seeking |
Prove you solve their specific problem |
| Paid social |
Interrupted, low intent |
Hook attention, educate, build interest |
| Organic search |
Research-mode |
Comprehensive content, gradual conversion |
| Email |
Already engaged |
Deliver on the email promise, reduce friction |
| Referral |
Pre-sold by referrer |
Validate referrer's recommendation, fast CTA |
Message Match Audit
For paid traffic: Compare the ad copy with the landing page headline. They must share:
- The same language/terminology
- The same promise
- The same offer
- Visual consistency (if display ad)
Mismatch = wasted ad spend. Users who click an ad about "free SEO audit" and land on a generic homepage will bounce.
A/B Test Framework
Test Priority Matrix
| Priority |
What to Test |
Expected Impact |
| 1 |
Headline copy |
10-30% conversion lift |
| 2 |
CTA copy and color |
5-20% conversion lift |
| 3 |
Social proof placement |
5-15% conversion lift |
| 4 |
Above-the-fold layout |
5-20% conversion lift |
| 5 |
Form field reduction |
5-10% completion lift |
| 6 |
Hero image vs video |
2-10% lift (variable) |
Test Design Rules
- One variable per test (unless running a multivariate test with sufficient traffic)
- Minimum 200 conversions per variant before declaring a winner
- Run for full business cycles (minimum 2 weeks)
- Track downstream metrics (not just page conversion, but lead quality / revenue)
Fix vs Test Decision
| Situation |
Action |
| Obvious UX problem (broken form, missing CTA) |
Fix immediately, no test needed |
| Missing social proof |
Add it, no test needed |
| Headline copy alternative |
A/B test |
| Layout change |
A/B test |
| Removing page elements |
A/B test |
| Adding a new section |
A/B test |
Metrics and Benchmarks
Conversion Rate Benchmarks
| Page Type |
Below Average |
Average |
Good |
Excellent |
| SaaS homepage |
< 2% |
2-4% |
4-7% |
> 7% |
| Landing page (paid) |
< 5% |
5-10% |
10-20% |
> 20% |
| Pricing page |
< 3% |
3-5% |
5-10% |
> 10% |
| Blog post (to email) |
< 1% |
1-3% |
3-5% |
> 5% |
| Feature page |
< 2% |
2-5% |
5-8% |
> 8% |
Key Metrics
| Metric |
What It Tells You |
| Bounce rate |
Is the page meeting visitor expectations? |
| Scroll depth |
How much of the page are visitors seeing? |
| Time on page |
Are visitors reading or immediately leaving? |
| CTA click rate |
Is the CTA compelling and visible? |
| Form start rate |
Are visitors beginning the conversion process? |
| Form completion rate |
Are they finishing it? |
Output Artifacts
| Artifact |
Format |
Description |
| CRO Audit Report |
7-dimension analysis |
Per-dimension assessment with severity ratings |
| Quick Wins List |
Bullet list (max 5) |
Implementable today with expected impact |
| High-Impact Recommendations |
Structured list |
Each with rationale, effort estimate, and success metric |
| Copy Alternatives |
Side-by-side table |
2-3 variants per key element with reasoning |
| A/B Test Plan |
Prioritized table |
Hypothesis, variant, success metric, priority |
| Traffic Source Matching Audit |
Source x page element table |
Message match assessment per traffic source |
Related Skills
- form-cro -- Use when the form on the page is the specific bottleneck (field optimization, validation, mobile form UX).
- signup-flow-cro -- Use when users convert on the page but drop off during the signup/registration process.
- popup-cro -- Use when considering a popup as an additional conversion layer on the page.
- onboarding-cro -- Use when post-conversion activation is the real problem and the page itself converts adequately.
- pricing-strategy -- Use when the pricing page needs structural redesign (tier structure, value metric), not just CRO tweaks.
Tool Reference
1. page_cro_scorer.py
Purpose: Score a marketing page across the 7 CRO dimensions and generate an audit report with severity ratings.
python scripts/page_cro_scorer.py page_audit.json
python scripts/page_cro_scorer.py page_audit.json --json
| Flag |
Required |
Description |
page_audit.json |
Yes |
JSON file with page elements and dimension checks |
--json |
No |
Output results as JSON |
2. headline_scorer.py
Purpose: Score headline effectiveness against the 5-criteria rubric and generate copy alternatives.
python scripts/headline_scorer.py --headline "Marketing Automation Software" --audience "B2B marketers" --traffic-source paid-search
python scripts/headline_scorer.py --headline "Marketing Automation Software" --json
| Flag |
Required |
Description |
--headline |
Yes |
The headline text to score |
--audience |
No |
Target audience description (default: "general") |
--traffic-source |
No |
Primary traffic source: organic, paid-search, paid-social, email, referral (default: organic) |
--json |
No |
Output results as JSON |
3. conversion_benchmark_calculator.py
Purpose: Calculate conversion rate benchmarks for a given page type, traffic source, and industry, and assess current performance.
python scripts/conversion_benchmark_calculator.py --page-type landing-page --traffic paid --current-rate 8.5
python scripts/conversion_benchmark_calculator.py --page-type homepage --traffic organic --current-rate 3.0 --json
| Flag |
Required |
Description |
--page-type |
Yes |
Page type: homepage, landing-page, pricing, feature, blog |
--traffic |
Yes |
Traffic source: organic, paid, email, social, referral |
--current-rate |
Yes |
Current conversion rate as percentage |
--industry |
No |
Industry for benchmarks: saas, ecommerce, fintech, healthcare, education (default: saas) |
--json |
No |
Output results as JSON |
Troubleshooting
| Problem |
Likely Cause |
Solution |
| High bounce rate (>70%) on landing page |
Message mismatch with traffic source or poor above-the-fold |
Audit message match: compare ad copy with landing page headline; ensure value proposition is visible in first 5 seconds |
| Page converts on desktop but not mobile |
Mobile UX not optimized |
Check touch targets (44px+), form field count on mobile, CTA visibility without scrolling; score with page_cro_scorer.py |
| CTA click rate below 2% |
CTA is generic, below the fold, or visually weak |
Replace "Submit" with value-specific copy; ensure CTA is visible above fold and repeated after key sections |
| High scroll depth but low conversion |
Visitors read but are not convinced to act |
Add social proof near CTA positions; address objections in FAQ; add risk reversal (free trial, no CC) |
| A/B test shows no significant winner after 4 weeks |
Change too small to detect or insufficient traffic |
Use ab_test_calculator.py from form-cro to validate sample size; test bigger changes (headline rewrite vs word swap) |
| Paid traffic converts worse than organic |
Landing page not tailored to paid traffic intent |
Create dedicated landing pages for paid campaigns with message match; remove navigation on paid landing pages |
| Social proof section is ignored |
Generic testimonials or poor placement |
Use specific, attributed testimonials with metrics; place after the section that makes the claim they validate |
Success Criteria
- Page CRO score of 70+ across the 7-dimension framework (scored by page_cro_scorer.py)
- Headline scores 7+ on the 10-point rubric (scored by headline_scorer.py)
- Conversion rate at or above industry benchmark for page type (verified by conversion_benchmark_calculator.py)
- Above-the-fold contains: headline, CTA, and at least one social proof element
- Message match verified for all paid traffic campaigns (ad copy matches landing page headline)
- Mobile conversion rate within 20% of desktop rate
- Every page addresses at least 3 of the 5 universal objections
Scope & Limitations
- In scope: Page-level conversion optimization, headline effectiveness, CTA hierarchy, social proof placement, objection handling, traffic source matching, A/B test prioritization
- Out of scope: Form optimization (use form-cro), signup flow optimization (use signup-flow-cro), popup optimization (use popup-cro), pricing structure changes (use pricing-strategy)
- Page speed: This skill covers CRO elements, not technical performance; pages loading >3 seconds need technical optimization first
- Traffic minimum: A/B testing recommendations require 200+ conversions per variant; low-traffic pages should implement best practices without testing
- Qualitative input: Heatmaps and session recordings provide critical behavioral data that analytics alone cannot reveal; consider investing in these tools
Integration Points
- form-cro -- When the form on the page is the bottleneck (field optimization, validation UX, mobile form experience)
- signup-flow-cro -- When users convert on the page but drop off during the signup/registration process
- popup-cro -- When considering a popup as an additional conversion layer on top of the page
- onboarding-cro -- When post-conversion activation is the real problem and the page itself converts adequately
- pricing-strategy -- When the pricing page needs structural redesign (tier structure, value metric), not just CRO tweaks
- competitive-teardown -- When comparison pages need competitive data to build credible content
1---2name: page-cro-33description: Landing page and marketing page conversion rate optimization covering value proposition clarity, headline effectiveness, CTA hierarchy, visual flow, social proof placement, objection handling, and structured A/B testing.4license: MIT + Commons Clause5---6# Page CRO
7
8Production-grade conversion rate optimization framework for marketing pages. Covers the 7-dimension analysis framework, page-type-specific playbooks, copy alternatives methodology, above-the-fold engineering, social proof hierarchy, objection handling patterns, and structured A/B test design.
9
10---
11
12## Table of Contents
13
14- [Initial Assessment](#initial-assessment)
15- [The 7-Dimension CRO Framework](#the-7-dimension-cro-framework)
16- [Above-the-Fold Engineering](#above-the-fold-engineering)
17- [Social Proof Hierarchy](#social-proof-hierarchy)
18- [Objection Handling Architecture](#objection-handling-architecture)
19- [Page-Type Playbooks](#page-type-playbooks)
20- [Copy Alternatives Methodology](#copy-alternatives-methodology)
21- [Traffic Source Matching](#traffic-source-matching)
22- [A/B Test Framework](#ab-test-framework)
23- [Metrics and Benchmarks](#metrics-and-benchmarks)
24- [Output Artifacts](#output-artifacts)
25- [Related Skills](#related-skills)
26
27---
28
29## Clarify First
30
31Before optimizing the page, confirm these inputs. If any is unknown or vague, ASK — do not assume:
32
33- [ ] **Page type** — homepage, landing page, pricing, feature, or blog (selects the page-type playbook and benchmark)
34- [ ] **Traffic source** — organic, paid, email, or social (drives message-match requirements)
35- [ ] **Primary conversion goal + current rate** — focuses the 7-dimension analysis and sets the baseline
36- [ ] **Behavioral data available** — heatmaps / session recordings (reveals friction that analytics alone cannot)
37
38Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the audit.
39
40## Initial Assessment
41
42### Required Context
43
44| Question | Why It Matters |
45|----------|---------------|
46| What page type? (homepage, landing page, pricing, feature, blog) | Determines the CRO framework to apply |
47| What is the primary conversion goal? | Focuses the analysis |
48| Where is traffic coming from? (organic, paid, email, social) | Drives message-match requirements |
49| What is the current conversion rate? | Establishes the baseline |
50| What does the post-click flow look like? | The page may convert fine but the next step fails |
51| Do you have heatmaps or session recordings? | Behavioral data reveals what analytics cannot |
52| What have you already tried? | Avoids re-testing failed experiments |
53
54---
55
56## The 7-Dimension CRO Framework
57
58Analyze every marketing page across these 7 dimensions, in order of typical impact.
59
60### Dimension 1: Value Proposition Clarity (Highest Impact)
61
62**The 5-second test:** Can a first-time visitor understand what this is, who it is for, and why they should care within 5 seconds?
63
64| Signal | Pass | Fail |
65|--------|------|------|
66| Primary benefit is stated explicitly | "Save 10 hours/week on reporting" | "Next-generation analytics platform" |
67| Written in customer language | "See which campaigns drive revenue" | "Multi-touch attribution solution" |
68| Differentiator is clear | "The only CRM built for agencies" | "A better CRM" |
69| Specificity | Includes numbers, timeframes, outcomes | Vague superlatives ("powerful", "innovative") |
70
71### Dimension 2: Headline Effectiveness
72
73**Headline scoring rubric:**
74
75| Criteria | Score 0 | Score 1 | Score 2 |
76|----------|---------|---------|---------|
77| Communicates core value | No | Partially | Clearly |
78| Specific (numbers, outcomes) | Generic | Somewhat specific | Very specific |
79| Addresses target audience | Generic | Implied | Explicit |
80| Matches traffic source | No connection | Loose match | Exact message match |
81| Emotional or logical hook | Neither | One | Both |
82
83**Total: 0-10. Score < 6 = rewrite needed.**
84
85### Dimension 3: CTA Hierarchy and Placement
86
87| Check | Pass | Fail |
88|-------|------|------|
89| One clear primary CTA | Single, prominent action | Multiple competing CTAs |
90| CTA visible without scrolling | Above the fold | Below the fold only |
91| CTA copy communicates value | "Start Free Trial" | "Submit" |
92| CTA repeated at decision points | After benefits, after social proof, at bottom | Only at top or only at bottom |
93| Secondary CTA is clearly secondary | Smaller, different color, text link | Same visual weight as primary |
94
95### Dimension 4: Visual Hierarchy and Scannability
96
97| Check | Pass | Fail |
98|-------|------|------|
99| Most important element is most prominent | Headline + CTA dominate | Navigation or image dominates |
100| Scannable in 10 seconds | Key points visible via headings, bold, bullets | Wall of text |
101| Adequate white space | Breathing room between sections | Cluttered, dense layout |
102| Images support the message | Product screenshots, relevant imagery | Stock photos, decorative graphics |
103| F-pattern or Z-pattern layout | Content follows natural eye flow | Random placement |
104
105### Dimension 5: Social Proof and Trust
106
107| Check | Pass | Fail |
108|-------|------|------|
109| Customer logos visible | Recognizable logos above the fold | No logos or unknown companies |
110| Testimonials are specific | "Increased revenue by 40%" | "Great product!" |
111| Testimonials are attributed | Full name, title, company, photo | Anonymous or first-name-only |
112| Trust badges present (where relevant) | Security, compliance, awards | No trust indicators |
113| Numbers-based proof | "10,000+ teams use..." | No scale indicators |
114
115### Dimension 6: Objection Handling
116
117| Check | Pass | Fail |
118|-------|------|------|
119| Price/value objection addressed | ROI calculation, "starts at $X" | No pricing context |
120| "Will this work for me?" answered | Use cases, industry examples | Generic positioning only |
121| Risk reduction offered | Free trial, guarantee, no CC required | No risk reversal |
122| Implementation concern addressed | "Set up in 5 minutes" | No setup/complexity context |
123| FAQ section present | Addresses top 5 objections | No FAQ or irrelevant questions |
124
125### Dimension 7: Friction Points
126
127| Check | Pass | Fail |
128|-------|------|------|
129| Form is optimized | Minimal fields, clear labels | Too many fields, unclear purpose |
130| Next step is clear | Obvious path forward from every section | Confusing navigation or dead ends |
131| Mobile experience | Fully responsive, touch-friendly | Desktop-only design |
132| Load time | < 3 seconds | > 5 seconds |
133| No distracting elements | Clean, focused design | Popups, auto-play video, chat widget on load |
134
135---
136
137## Above-the-Fold Engineering
138
139The above-the-fold area is the most valuable real estate on any page. It determines whether visitors scroll or bounce.
140
141### Required Elements (Above the Fold)
142
143```
144┌──────────────────────────────────────────┐
145│ [Nav: Logo + 3-5 links + Primary CTA] │
146├──────────────────────────────────────────┤
147│ │
148│ HEADLINE: Primary value proposition │
149│ │
150│ SUBHEADLINE: Supporting detail │
151│ │
152│ [PRIMARY CTA BUTTON] │
153│ [Secondary CTA: text link] │
154│ │
155│ [Social proof: logos or stat] │
156│ │
157│ [Hero image or product screenshot] │
158│ │
159└──────────────────────────────────────────┘
160```
161
162### Above-the-Fold Rules
163
164- Headline is the largest text on the page
165- CTA button is the most visually prominent interactive element
166- Social proof appears above the fold (even just logo strip)
167- Hero image shows the product in use (not abstract graphics)
168- No auto-play video or animation that distracts from the CTA
169- Navigation is minimal (3-5 items max, CTA in nav)
170
171---
172
173## Social Proof Hierarchy
174
175Not all social proof is equal. Use the right type at the right location.
176
177### Social Proof Power Ranking
178
179| Rank | Type | Strength | Best Placement |
180|------|------|----------|----------------|
181| 1 | Case study with metrics | "Company X increased revenue 40% in 3 months" | Mid-page, after benefits section |
182| 2 | Named testimonial with photo | Full name, title, company, headshot | Near CTA, after objection handling |
183| 3 | Aggregate numbers | "10,000+ teams" or "4.8/5 on G2" | Above the fold, near headline |
184| 4 | Customer logos | Recognizable brand logos | Above the fold, logo strip |
185| 5 | Awards/badges | "G2 Leader 2026", "SOC2 Certified" | Footer or near CTA |
186| 6 | Generic testimonial | "Great product!" -- no specifics | Do not use (no credibility) |
187
188### Placement Rules
189
190- Logo strip: Above the fold, below the CTA
191- Testimonials: After the section that makes the claim they validate
192- Case studies: Mid-page, as their own section
193- Numbers: Inline with headline or subheadline
194- Trust badges: Near the primary CTA and near the form
195
196---
197
198## Objection Handling Architecture
199
200### The 5 Universal Objections
201
202Every product page must address these five objections. If the page does not, conversions leak.
203
204| Objection | How to Address | Page Element |
205|-----------|---------------|--------------|
206| "Is this worth the money?" | ROI calculator, pricing comparison, "saves X hours" | Benefits section + pricing context |
207| "Will this work for my situation?" | Industry examples, use case sections, persona targeting | "Who uses this" section |
208| "Is this hard to set up?" | "Set up in 5 minutes", onboarding preview, integration logos | Feature section or FAQ |
209| "What if it doesn't work?" | Free trial, money-back guarantee, no CC required | Near CTA |
210| "Why this over alternatives?" | Comparison table, differentiators, switcher testimonials | Mid-page or FAQ |
211
212### FAQ Design for Objection Handling
213
214The FAQ section should be the last defense before conversion. Structure it to address the 5 objections:
215
2161. "How long does setup take?" (complexity objection)
2172. "Can I cancel anytime?" (commitment objection)
2183. "What's included in the free trial?" (value objection)
2194. "Do you integrate with [popular tool]?" (compatibility objection)
2205. "How is this different from [competitor]?" (alternatives objection)
221
222---
223
224## Page-Type Playbooks
225
226### Homepage
227
228| Element | Best Practice |
229|---------|---------------|
230| Audience | Cold visitors who may not know you |
231| Headline | Position the company, not a single feature |
232| CTA split | Primary: "Start Free Trial" / Secondary: "See Demo" or "Learn More" |
233| Content | Overview of benefits, social proof, feature highlights, use cases |
234| Navigation | Full site navigation (unlike landing pages) |
235
236### Landing Page (Paid Traffic)
237
238| Element | Best Practice |
239|---------|---------------|
240| Navigation | Remove or minimize (no escape routes) |
241| Headline | Message-match with the ad that drove the click |
242| CTA | Single action, repeated 2-3 times down the page |
243| Content | Complete argument on one page: problem > solution > proof > CTA |
244| Social proof | Directly relevant to the ad audience |
245
246### Pricing Page
247
248| Element | Best Practice |
249|---------|---------------|
250| Plan presentation | Good-Better-Best with recommended plan highlighted |
251| Toggle | Annual/Monthly with savings percentage shown |
252| Feature comparison | Full table below the fold |
253| FAQ | "Which plan is right for me?" as first question |
254| CTA | Per-plan CTA with plan-specific copy |
255| Social proof | Logos and testimonials relevant to each tier |
256
257### Feature Page
258
259| Element | Best Practice |
260|---------|---------------|
261| Headline | Benefit of the feature, not the feature name |
262| Content | Use cases > technical capabilities |
263| Demo | Screenshot, GIF, or interactive demo |
264| CTA | "Try this feature" or "Start Free Trial" |
265| Internal links | Link to related features and pricing |
266
267### Blog Post
268
269| Element | Best Practice |
270|---------|---------------|
271| CTA type | Contextual inline CTA matching the content topic |
272| Placement | After introduction, at natural breaks, at end |
273| CTA style | Inline banner or text link, not aggressive popup |
274| Content CTA | Offer a related resource (template, checklist, tool) |
275
276---
277
278## Copy Alternatives Methodology
279
280When recommending copy changes, always provide 2-3 alternatives with reasoning.
281
282### Alternative Generation Framework
283
284For each key element (headline, subheadline, CTA), generate variants across these axes:
285
286| Axis | Variant A | Variant B | Variant C |
287|------|-----------|-----------|-----------|
288| Benefit focus | Outcome-focused | Problem-focused | Feature-focused |
289| Specificity | Numbers and data | Customer quote | Use case scenario |
290| Tone | Direct and assertive | Conversational | Aspirational |
291
292### Example
293
294**Current headline:** "Marketing Automation Software"
295
296| Variant | Copy | Rationale |
297|---------|------|-----------|
298| A (outcome) | "Generate 3X More Qualified Leads Without Adding Headcount" | Specific outcome + pain point |
299| B (problem) | "Stop Losing Leads Because Your Team Can't Follow Up Fast Enough" | Addresses the pain directly |
300| C (social proof) | "How 2,000+ Marketing Teams Hit Their Pipeline Targets" | Authority + specificity |
301
302**Recommendation:** Test A first (most specific), B if A does not outperform current (different psychological angle).
303
304---
305
306## Traffic Source Matching
307
308Different traffic sources require different page optimization strategies.
309
310| Source | Visitor State | Page Must Do |
311|--------|-------------|-------------|
312| Paid search (brand) | Knows you, high intent | Fast path to action, minimal education |
313| Paid search (non-brand) | Problem-aware, solution-seeking | Prove you solve their specific problem |
314| Paid social | Interrupted, low intent | Hook attention, educate, build interest |
315| Organic search | Research-mode | Comprehensive content, gradual conversion |
316| Email | Already engaged | Deliver on the email promise, reduce friction |
317| Referral | Pre-sold by referrer | Validate referrer's recommendation, fast CTA |
318
319### Message Match Audit
320
321For paid traffic: Compare the ad copy with the landing page headline. They must share:
322- The same language/terminology
323- The same promise
324- The same offer
325- Visual consistency (if display ad)
326
327**Mismatch = wasted ad spend.** Users who click an ad about "free SEO audit" and land on a generic homepage will bounce.
328
329---
330
331## A/B Test Framework
332
333### Test Priority Matrix
334
335| Priority | What to Test | Expected Impact |
336|----------|-------------|-----------------|
337| 1 | Headline copy | 10-30% conversion lift |
338| 2 | CTA copy and color | 5-20% conversion lift |
339| 3 | Social proof placement | 5-15% conversion lift |
340| 4 | Above-the-fold layout | 5-20% conversion lift |
341| 5 | Form field reduction | 5-10% completion lift |
342| 6 | Hero image vs video | 2-10% lift (variable) |
343
344### Test Design Rules
345
346- One variable per test (unless running a multivariate test with sufficient traffic)
347- Minimum 200 conversions per variant before declaring a winner
348- Run for full business cycles (minimum 2 weeks)
349- Track downstream metrics (not just page conversion, but lead quality / revenue)
350
351### Fix vs Test Decision
352
353| Situation | Action |
354|-----------|--------|
355| Obvious UX problem (broken form, missing CTA) | Fix immediately, no test needed |
356| Missing social proof | Add it, no test needed |
357| Headline copy alternative | A/B test |
358| Layout change | A/B test |
359| Removing page elements | A/B test |
360| Adding a new section | A/B test |
361
362---
363
364## Metrics and Benchmarks
365
366### Conversion Rate Benchmarks
367
368| Page Type | Below Average | Average | Good | Excellent |
369|-----------|-------------|---------|------|-----------|
370| SaaS homepage | < 2% | 2-4% | 4-7% | > 7% |
371| Landing page (paid) | < 5% | 5-10% | 10-20% | > 20% |
372| Pricing page | < 3% | 3-5% | 5-10% | > 10% |
373| Blog post (to email) | < 1% | 1-3% | 3-5% | > 5% |
374| Feature page | < 2% | 2-5% | 5-8% | > 8% |
375
376### Key Metrics
377
378| Metric | What It Tells You |
379|--------|------------------|
380| Bounce rate | Is the page meeting visitor expectations? |
381| Scroll depth | How much of the page are visitors seeing? |
382| Time on page | Are visitors reading or immediately leaving? |
383| CTA click rate | Is the CTA compelling and visible? |
384| Form start rate | Are visitors beginning the conversion process? |
385| Form completion rate | Are they finishing it? |
386
387---
388
389## Output Artifacts
390
391| Artifact | Format | Description |
392|----------|--------|-------------|
393| CRO Audit Report | 7-dimension analysis | Per-dimension assessment with severity ratings |
394| Quick Wins List | Bullet list (max 5) | Implementable today with expected impact |
395| High-Impact Recommendations | Structured list | Each with rationale, effort estimate, and success metric |
396| Copy Alternatives | Side-by-side table | 2-3 variants per key element with reasoning |
397| A/B Test Plan | Prioritized table | Hypothesis, variant, success metric, priority |
398| Traffic Source Matching Audit | Source x page element table | Message match assessment per traffic source |
399
400---
401
402## Related Skills
403
404- **form-cro** -- Use when the form on the page is the specific bottleneck (field optimization, validation, mobile form UX).
405- **signup-flow-cro** -- Use when users convert on the page but drop off during the signup/registration process.
406- **popup-cro** -- Use when considering a popup as an additional conversion layer on the page.
407- **onboarding-cro** -- Use when post-conversion activation is the real problem and the page itself converts adequately.
408- **pricing-strategy** -- Use when the pricing page needs structural redesign (tier structure, value metric), not just CRO tweaks.
409
410---
411
412## Tool Reference
413
414### 1. page_cro_scorer.py
415
416**Purpose:** Score a marketing page across the 7 CRO dimensions and generate an audit report with severity ratings.
417
418```bash
419python scripts/page_cro_scorer.py page_audit.json
420python scripts/page_cro_scorer.py page_audit.json --json
421```
422
423| Flag | Required | Description |
424|------|----------|-------------|
425| `page_audit.json` | Yes | JSON file with page elements and dimension checks |
426| `--json` | No | Output results as JSON |
427
428### 2. headline_scorer.py
429
430**Purpose:** Score headline effectiveness against the 5-criteria rubric and generate copy alternatives.
431
432```bash
433python scripts/headline_scorer.py --headline "Marketing Automation Software" --audience "B2B marketers" --traffic-source paid-search
434python scripts/headline_scorer.py --headline "Marketing Automation Software" --json
435```
436
437| Flag | Required | Description |
438|------|----------|-------------|
439| `--headline` | Yes | The headline text to score |
440| `--audience` | No | Target audience description (default: "general") |
441| `--traffic-source` | No | Primary traffic source: organic, paid-search, paid-social, email, referral (default: organic) |
442| `--json` | No | Output results as JSON |
443
444### 3. conversion_benchmark_calculator.py
445
446**Purpose:** Calculate conversion rate benchmarks for a given page type, traffic source, and industry, and assess current performance.
447
448```bash
449python scripts/conversion_benchmark_calculator.py --page-type landing-page --traffic paid --current-rate 8.5
450python scripts/conversion_benchmark_calculator.py --page-type homepage --traffic organic --current-rate 3.0 --json
451```
452
453| Flag | Required | Description |
454|------|----------|-------------|
455| `--page-type` | Yes | Page type: homepage, landing-page, pricing, feature, blog |
456| `--traffic` | Yes | Traffic source: organic, paid, email, social, referral |
457| `--current-rate` | Yes | Current conversion rate as percentage |
458| `--industry` | No | Industry for benchmarks: saas, ecommerce, fintech, healthcare, education (default: saas) |
459| `--json` | No | Output results as JSON |
460
461---
462
463## Troubleshooting
464
465| Problem | Likely Cause | Solution |
466|---------|-------------|----------|
467| High bounce rate (>70%) on landing page | Message mismatch with traffic source or poor above-the-fold | Audit message match: compare ad copy with landing page headline; ensure value proposition is visible in first 5 seconds |
468| Page converts on desktop but not mobile | Mobile UX not optimized | Check touch targets (44px+), form field count on mobile, CTA visibility without scrolling; score with page_cro_scorer.py |
469| CTA click rate below 2% | CTA is generic, below the fold, or visually weak | Replace "Submit" with value-specific copy; ensure CTA is visible above fold and repeated after key sections |
470| High scroll depth but low conversion | Visitors read but are not convinced to act | Add social proof near CTA positions; address objections in FAQ; add risk reversal (free trial, no CC) |
471| A/B test shows no significant winner after 4 weeks | Change too small to detect or insufficient traffic | Use ab_test_calculator.py from form-cro to validate sample size; test bigger changes (headline rewrite vs word swap) |
472| Paid traffic converts worse than organic | Landing page not tailored to paid traffic intent | Create dedicated landing pages for paid campaigns with message match; remove navigation on paid landing pages |
473| Social proof section is ignored | Generic testimonials or poor placement | Use specific, attributed testimonials with metrics; place after the section that makes the claim they validate |
474
475---
476
477## Success Criteria
478
479- Page CRO score of 70+ across the 7-dimension framework (scored by page_cro_scorer.py)
480- Headline scores 7+ on the 10-point rubric (scored by headline_scorer.py)
481- Conversion rate at or above industry benchmark for page type (verified by conversion_benchmark_calculator.py)
482- Above-the-fold contains: headline, CTA, and at least one social proof element
483- Message match verified for all paid traffic campaigns (ad copy matches landing page headline)
484- Mobile conversion rate within 20% of desktop rate
485- Every page addresses at least 3 of the 5 universal objections
486
487---
488
489## Scope & Limitations
490
491- **In scope:** Page-level conversion optimization, headline effectiveness, CTA hierarchy, social proof placement, objection handling, traffic source matching, A/B test prioritization
492- **Out of scope:** Form optimization (use form-cro), signup flow optimization (use signup-flow-cro), popup optimization (use popup-cro), pricing structure changes (use pricing-strategy)
493- **Page speed:** This skill covers CRO elements, not technical performance; pages loading >3 seconds need technical optimization first
494- **Traffic minimum:** A/B testing recommendations require 200+ conversions per variant; low-traffic pages should implement best practices without testing
495- **Qualitative input:** Heatmaps and session recordings provide critical behavioral data that analytics alone cannot reveal; consider investing in these tools
496
497---
498
499## Integration Points
500
501- **form-cro** -- When the form on the page is the bottleneck (field optimization, validation UX, mobile form experience)
502- **signup-flow-cro** -- When users convert on the page but drop off during the signup/registration process
503- **popup-cro** -- When considering a popup as an additional conversion layer on top of the page
504- **onboarding-cro** -- When post-conversion activation is the real problem and the page itself converts adequately
505- **pricing-strategy** -- When the pricing page needs structural redesign (tier structure, value metric), not just CRO tweaks
506- **competitive-teardown** -- When comparison pages need competitive data to build credible content
majiayu000