page-cro

Overview

What is page-cro?

page-cro is a conversion rate optimization (CRO) skill designed to analyze marketing pages and propose practical ways to increase conversions. It focuses on pages like homepages, campaign landing pages, pricing pages, feature pages, demo request pages, and even resource or blog posts that should be generating leads or signups.

Instead of vague feedback, page-cro uses a structured CRO framework. It reviews value proposition clarity, headline and messaging, calls to action (CTAs), visual hierarchy, trust signals, objections, friction points, and page-specific patterns. The output is organized into clear sections such as quick wins, high‑impact changes, and test ideas.

Who is page-cro for?

page-cro is a good fit if you:

• Own or manage marketing pages that should drive signups, demo requests, trials, purchases, or subscriptions
• Run paid traffic (e.g., Google Ads, Meta Ads) and suspect poor message match with your landing pages
• Are a marketer, founder, PM, or CRO specialist who wants structured recommendations and A/B test ideas
• Need a repeatable way to review pages across multiple products, campaigns, or markets

It is especially useful when you hear or say things like:

• "This landing page isn't converting"
• "Bounce rate is too high"
• "People leave without signing up"
• "Nobody's picking our main pricing tier"
• "Our homepage traffic is growing but conversions are flat"

What problems does page-cro solve?

page-cro helps you:

• Diagnose why a marketing page with traffic is not converting
• Turn unstructured complaints ("my landing page sucks") into a clear CRO diagnosis
• Prioritize changes by impact: quick fixes vs. deeper redesigns vs. experiments
• Generate specific headline and CTA alternatives instead of generic advice
• Brainstorm A/B tests tailored to your page type (homepage, pricing, demo request, etc.)

It is not a visual design tool or an analytics platform. Instead, it plugs into your workflow as an expert CRO reviewer that uses your existing context and traffic data to recommend changes.

When is page-cro the right skill vs. other CRO skills?

The page-cro skill is designed for individual pages whose main job is to turn visitors into leads or customers. Use it when the core problem is: "This marketing page gets traffic but not enough conversions."

Use related skills for specialized flows:

• For signup and registration flows: use signup-flow-cro
• For post-signup onboarding and activation: use onboarding-cro
• For standalone forms outside signup (e.g., contact forms): use form-cro
• For popups and modals (exit intent, lead capture overlays): use popup-cro

If you are unsure, page-cro is usually a safe default for any URL that looks like a marketing page and has a clear conversion goal.

How to Use

Installation and setup

To add page-cro to your agent or skills-enabled environment, install it from the marketingskills repository:

npx skills add https://github.com/coreyhaines31/marketingskills --skill page-cro

This pulls only the page-cro skill from the coreyhaines31/marketingskills repo, including its main configuration and supporting evaluation and reference files.

Key files for page-cro:

• SKILL.md – the core definition of the page-cro skill and its behavior
• evals/evals.json – example prompts and expected outputs to show how the skill should respond
• references/experiments.md – a structured library of CRO experiment ideas by page type

After installation, open SKILL.md first to understand the skill’s role and assumptions, then review the evals and references folders for guidance on usage and output patterns.

Core workflow: from URL to CRO recommendations

page-cro follows a consistent workflow to review a page:

1. Gather product marketing context
   If your project includes .agents/product-marketing-context.md (or .claude/product-marketing-context.md in older setups), the skill is designed to read that file first. This gives it the positioning, target audience, and messaging context before it evaluates the page.

2. Identify the page type and goal
   The skill classifies the page as one of:

   • Homepage
   • Landing page (e.g., campaign or ad-specific)
   • Pricing page
   • Feature page
   • Blog/resource page
   • About or other marketing page

   It then identifies the primary conversion goal, such as:

   • Sign up or start a free trial
   • Request a demo
   • Purchase or upgrade
   • Subscribe (newsletter, content series, etc.)
   • Download (lead magnet, whitepaper)
   • Contact sales

3. Analyze traffic context
   Using the prompt and any provided data (e.g., traffic from Google Ads, organic search, email), page-cro evaluates whether there is message match between traffic sources and on-page copy, and how that might impact conversions.

4. Run the CRO analysis framework
   From SKILL.md and the examples in evals/evals.json, page-cro applies a structured CRO lens, typically covering:

   • Value proposition clarity
   • Headline effectiveness
   • CTA copy, placement, and hierarchy
   • Visual hierarchy and focus
   • Trust signals and social proof
   • Objection handling and risk reversal
   • Friction (forms, layout, distractions)

5. Output structured recommendations
   The expected outputs (as seen in evals/evals.json) are organized into sections such as:

   • Quick Wins – low-effort changes that can be implemented immediately
   • High-Impact Changes – deeper copy, layout, or structural updates
   • Test Ideas – A/B tests and experiments tailored to your page type and traffic

   For many prompts, the skill is expected to also:

   • Call out message match issues between ads and the page
   • Provide 2–3 headline or CTA variations with rationale

Example usage patterns

The evals/evals.json file shows realistic prompts and what the skill is expected to do with them. Typical usage looks like:

• SaaS landing page with poor trial conversions
  Provide the URL, traffic details (e.g., "5,000 visitors/month from Google Ads, 1.2% trial signup"), and let page-cro:

  • Confirm page type (landing page)
  • Confirm conversion goal (free trial signup)
  • Analyze value proposition, headline, and CTA
  • Suggest quick wins, structural changes, and A/B test ideas

• Pricing page with skewed plan selection
  If one plan is over-selected or ignored, page-cro uses the pricing context plus the experiments in references/experiments.md to suggest tests around pricing presentation, highlighting a target plan, and objection handling.

• Blog or resource page that should generate leads
  For high-traffic content that doesn’t convert, page-cro will evaluate content CTAs, placement of lead forms, and alignment between topic and offer, then propose relevant experiments.

Using the experiments library

The references/experiments.md file is a curated list of CRO experiment ideas organized by page type:

• Homepage experiments (hero, trust & social proof, features, navigation)
• Pricing page experiments (plan layout, price anchoring, objection handling)
• Demo request page experiments (form friction, CTA variants, routing)
• Resource/blog experiments (content CTAs, inline vs. sidebar offers)
• Landing page experiments (message match, conversion focus, page length)
• Feature page experiments (feature presentation, conversion paths)
• Cross-page experiments (site-wide tests, navigation changes)

page-cro can draw from this library to:

• Suggest experiment themes appropriate for your specific page type
• Translate problems (e.g., nobody selects the middle plan) into targeted tests
• Provide a prioritised roadmap of experiment ideas instead of generic suggestions

When page-cro is not a good fit

Consider a different approach if:

• Your issue is primarily product onboarding after signup – use onboarding-cro instead
• You’re focused on multi-step signup or checkout flows rather than a single marketing page – use signup-flow-cro
• You want visual design critiques or component-level UI tweaks without a conversion goal – a design-specific skill may be better
• You have no traffic or baseline conversions yet – page-cro works best once there is at least some data or clear goals

FAQ

What does page-cro actually look at on my page?

page-cro focuses on conversion drivers rather than code or pixel-perfect design. Based on the skill definition and evaluation prompts, it pays particular attention to:

• How clearly the value proposition is communicated above the fold
• Whether the headline and subheadline explain who the product is for and what outcome it delivers
• The clarity, visibility, and hierarchy of CTAs
• Message match between ad or traffic source promises and on-page copy
• Placement and strength of social proof, trust badges, and testimonials
• How objections (price, effort, risk) are handled
• Friction in forms and layouts that might stop visitors from acting

Can page-cro help with Google Ads or other paid traffic campaigns?

Yes, indirectly. The evals for page-cro include scenarios with traffic from Google Ads. The skill is expected to:

• Identify the landing page as the target for paid traffic
• Compare the likely ad promise to on-page messaging
• Flag message mismatch as a potential cause of low conversion
• Suggest headline and CTA variants and experiments to better align the page with your ad campaigns

While it doesn’t manage ad accounts, it gives you page-side CRO recommendations that make your ad spend more efficient.

How is page-cro different from generic landing page advice?

page-cro is built around a defined CRO framework and concrete expectations captured in evals/evals.json. This means it:

• Always starts from page type, conversion goal, and traffic context
• Produces structured sections (Quick Wins, High-Impact Changes, Test Ideas) instead of freeform commentary
• Provides specific copy suggestions (e.g., alternative headlines and CTAs) with reasoning
• Uses a curated experiment library in references/experiments.md to suggest realistic A/B tests

This makes it more practical for ongoing CRO work than generic best-practice checklists.

Do I need existing analytics data for page-cro to be useful?

page-cro is most powerful when you provide at least basic metrics such as traffic volume, current conversion rate, and traffic sources. However, it can still:

• Review your page structure and messaging
• Infer likely friction and clarity issues
• Suggest a starting set of changes and tests

If you do have data (e.g., "60% choose the cheapest plan, 30% bounce"), the skill is designed to use it as part of its diagnosis and experiment recommendations.

Can page-cro handle different page types in the same project?

Yes. The references/experiments.md file is explicitly organized by page type, and the skill definition expects it to classify the page before recommending changes. This allows page-cro to:

• Use homepage-specific experiments for your main site
• Apply pricing-page-specific ideas to your plans page
• Suggest form and routing experiments for demo request pages
• Optimize content CTAs on blogs and resource hubs

You can reuse page-cro across multiple URLs and campaigns within the same product or across products.

How do I see more examples of expected page-cro behavior?

Open the evals/evals.json file in the page-cro directory. It contains sample prompts (like SaaS landing pages, pricing page issues, and more) together with descriptions of the expected analysis and output structure. Reviewing these examples is the fastest way to understand how to frame your own prompts and what page-cro will return.