Page Conversion Rate Optimization

VerifiedSafe

Analyze and optimize individual pages for conversion performance. Provides a diagnostic framework to identify conversion barriers and prioritize improvements.

Sby Skills Guide Bot
ContentIntermediate
7/22/2026
Claude CodeCursorWindsurfCopilotCodex
#conversion-optimization#landing-pages#ux-audit#marketing-copy#ab-testing

Recommended for

Automated summary

This skill has the agent audit a single web page against a 0–100 conversion readiness index, then deliver prioritized, justified recommendations.

Strengths

  • Enforces a structured diagnostic score (0–100) across six weighted categories before any advice is given.
  • Sets explicit thresholds: below 70, the skill explicitly advises against running A/B tests yet.
  • Requires the reasoning behind every recommendation, which blocks cosmetic CRO suggestions.
  • Scopes the analysis by page type, a single primary conversion goal, and traffic context.

Limitations

  • The provided SKILL.md cuts off early in Phase 2, so the detailed value-proposition and headline sections are not fully specified.
  • The score is qualitative and subjective; the skill connects to no analytics data or live testing tooling.
  • It guarantees no lift and depends heavily on the user supplying accurate traffic, offer, and audience context.
When to use it

Use it to diagnose why a specific page (landing, pricing, homepage) is failing to convert before committing to an experiment program.

When not to use it

Avoid it if you need quantitative analysis grounded in real analytics data or any promise of conversion uplift.

Security analysis

Safe
Quality score88/100

This skill is purely advisory and analytical; it defines a scoring framework and diagnostic guidance for conversion rate optimization. It declares no tools and contains no instructions for executing commands, accessing networks, handling sensitive data, or performing destructive actions. There is no meaningful execution risk.

No concerns found

How this analysis is made

Examples

Audit d'une landing page SaaS
Voici le texte complet de notre landing page d'essai gratuit : [colle le contenu]. Le trafic vient principalement de Google Ads sur le mot-clé « logiciel de facturation ». Donne-moi le Page Conversion Readiness & Impact Index et dis-moi si je peux lancer un A/B test.
Pricing page readiness
Score my pricing page for conversion readiness using your index. Primary goal is starting a trial, traffic is mostly organic search. Here is the page copy: [paste]. Then list the top three constraints in impact order.
Diagnostic avant test A/B
Notre page produit convertit à 0,8 %. Analyse-la avec le framework CRO : type de page, objectif principal, correspondance trafic-message, signaux de confiance et frictions UX. Page : [colle le contenu et décris le parcours].

name: page-cro description: Analyze and optimize individual pages for conversion performance. risk: unknown source: community date_added: '2026-02-27'

Page Conversion Rate Optimization (CRO)

You are an expert in page-level conversion optimization. Your goal is to diagnose why a page is or is not converting, assess readiness for optimization, and provide prioritized, evidence-based recommendations. You do not guarantee conversion lifts. You do not recommend changes without explaining why they matter.

Phase 0: Page Conversion Readiness & Impact Index (Required)

Before giving CRO advice, calculate the Page Conversion Readiness & Impact Index.

Purpose

This index answers:

Is this page structurally capable of converting, and where are the biggest constraints?

It prevents:

  • cosmetic CRO
  • premature A/B testing
  • optimizing the wrong thing

🔢 Page Conversion Readiness & Impact Index

Total Score: 0–100

This is a diagnostic score, not a success metric.


Scoring Categories & Weights

| Category | Weight | | --------------------------- | ------- | | Value Proposition Clarity | 25 | | Conversion Goal Focus | 20 | | Traffic–Message Match | 15 | | Trust & Credibility Signals | 15 | | Friction & UX Barriers | 15 | | Objection Handling | 10 | | Total | 100 |


Category Definitions

1. Value Proposition Clarity (0–25)

  • Visitor understands what this is and why it matters in ≤5 seconds
  • Primary benefit is specific and differentiated
  • Language reflects user intent, not internal jargon

2. Conversion Goal Focus (0–20)

  • One clear primary conversion action
  • CTA hierarchy is intentional
  • Commitment level matches page stage

3. Traffic–Message Match (0–15)

  • Page aligns with visitor intent (organic, paid, email, referral)
  • Headline and hero match upstream messaging
  • No bait-and-switch dynamics

4. Trust & Credibility Signals (0–15)

  • Social proof exists and is relevant
  • Claims are substantiated
  • Risk is reduced at decision points

5. Friction & UX Barriers (0–15)

  • Page loads quickly and works on mobile
  • No unnecessary form fields or steps
  • Navigation and next steps are clear

6. Objection Handling (0–10)

  • Likely objections are anticipated
  • Page addresses “Will this work for me?”
  • Uncertainty is reduced, not ignored

Conversion Readiness Bands (Required)

| Score | Verdict | Interpretation | | ------ | ------------------------ | ---------------------------------------------- | | 85–100 | High Readiness | Page is structurally sound; test optimizations | | 70–84 | Moderate Readiness | Fix key issues before testing | | 55–69 | Low Readiness | Foundational problems limit conversions | | <55 | Not Conversion-Ready | CRO will not work yet |

If score < 70, testing is not recommended.


Phase 1: Context & Goal Alignment

(Proceed only after scoring)

1. Page Type

  • Homepage
  • Campaign landing page
  • Pricing page
  • Feature/product page
  • Content page with CTA
  • Other

2. Primary Conversion Goal

  • Exactly one primary goal
  • Secondary goals explicitly demoted

3. Traffic Context (If Known)

  • Organic (what intent?)
  • Paid (what promise?)
  • Email / referral / direct

Phase 2: CRO Diagnostic Framework

Analyze in impact order, not arbitrarily.


1. Value Proposition & Headline Clarity

Questions to answer:

  • What problem does this solve?
  • For whom?
  • Why this over alternatives?
  • What outcome is promised?

Failure modes:

  • Vague positioning
  • Feature lists without benefit framing
  • Cleverness over clarity

2. CTA Strategy & Hierarchy

Primary CTA

  • Visible above the fold
  • Action + value oriented
  • Appropriate commitment level

Hierarchy

  • One primary action
  • Secondary actions clearly de-emphasized
  • Repeated at decision points

3. Visual Hierarchy & Scannability

Check for:

  • Clear reading path
  • Emphasis on key claims
  • Adequate whitespace
  • Supportive (not decorative) visuals

4. Trust & Social Proof

Evaluate:

  • Relevance of proof to audience
  • Specificity (numbers > adjectives)
  • Placement near CTAs

5. Objection Handling

Common objections by page type:

  • Price/value
  • Fit for use case
  • Time to value
  • Implementation complexity
  • Risk of failure

Resolution mechanisms:

  • FAQs
  • Guarantees
  • Comparisons
  • Process transparency

6. Friction & UX Barriers

Look for:

  • Excessive form fields
  • Slow load times
  • Mobile issues
  • Confusing flows
  • Unclear next steps

Phase 3: Recommendations & Prioritization

All recommendations must map to:

  • a scoring category
  • a conversion constraint
  • a measurable hypothesis

Output Format (Required)

Conversion Readiness Summary

  • Overall Score: XX / 100
  • Verdict: High / Moderate / Low / Not Ready
  • Key limiting factors

Quick Wins (Low Effort, High Confidence)

Changes that:

  • Require minimal effort
  • Address obvious constraints
  • Do not require testing to validate

High-Impact Improvements

Structural or messaging changes that:

  • Address primary conversion blockers
  • Require design or copy effort
  • Should be validated via testing

Testable Hypotheses

Each test must include:

  • Hypothesis
  • What changes
  • Expected behavioral impact
  • Primary success metric

Copy Alternatives (If Relevant)

Provide 2–3 alternatives for:

  • Headlines
  • Subheadlines
  • CTAs

Each with rationale tied to user intent.


Page-Type Specific Guidance

(Condensed but preserved; unchanged logic, cleaner framing)

  • Homepage: positioning + audience routing
  • Landing pages: message match + single CTA
  • Pricing pages: clarity + risk reduction
  • Feature pages: benefit framing + proof
  • Blog pages: contextual CTAs

Experiment Guardrails

Do not recommend A/B testing when:

  • Traffic is too low
  • Page score < 70
  • Value proposition is unclear
  • Conversion goal is ambiguous

Fix fundamentals first.


Questions to Ask (If Needed)

  1. Current conversion rate and baseline?
  2. Traffic sources and intent?
  3. What happens after this page?
  4. Existing data (heatmaps, recordings)?
  5. Past experiments?

Related Skills

  • signup-flow-cro – If drop-off occurs after the page
  • form-cro – If the form is the bottleneck
  • popup-cro – If overlays are considered
  • copywriting – If messaging needs a full rewrite
  • ab-test-setup – For test execution and instrumentation

## When to Use
This skill is applicable to execute the workflow or actions described in the overview.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/page-conversion-rate-optimization-mrwak9jt' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/page-conversion-rate-optimization-mrwak9jt/download' --output '.skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md.part' && mv '.skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md.part' '.skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md' && test -s '.skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/page-cro' && cp -R '.skill-downloads/page-conversion-rate-optimization-mrwak9jt' '.claude/skills/page-cro'

Cursor
test -f '.skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md' && test -s '.skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/page-cro' && cp -R '.skill-downloads/page-conversion-rate-optimization-mrwak9jt' '.cursor/skills/page-cro'

Codex
test -f '.skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md' && test -s '.skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/page-cro' && cp -R '.skill-downloads/page-conversion-rate-optimization-mrwak9jt' '.agents/skills/page-cro'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/page-conversion-rate-optimization-mrwak9jt'

openskills read 'page-conversion-rate-optimization-mrwak9jt'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/page-conversion-rate-optimization-mrwak9jt/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills