page-cro
Analyze and optimize individual pages for conversion performance.
What this skill does
# 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. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".