P

page-cro

Verified

by coreyhaines31 · Updated Apr 16, 2026

opus
1.0Kin7.4Kout
$0.763m 21s

When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

cromarketinglanding-pagescopywritingconversion-optimizationwebsite-audit

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. paid search goes live this afternoon — can you audit doany.ai homepage and give me the biggest CRO fixes to boost demo requests

Let me start by exploring the codebase and fetching the live homepage.

Now I have the full picture. This is a critical situation — the April 7 messaging refresh dropped conversions from 3.2% to 1.8%, and with paid search at $1,200/day launching today, every unconverted click costs $8-14. Here's the audit.


CRO Audit: doany.ai Homepage

The core problem: The April 7 messaging refresh traded specificity for aspirational fluff. The old headline told visitors what they get and what pain goes away. The new one says nothing actionable. Combined with weak CTAs, this explains the 44% conversion drop.


Quick Wins (Implement Before Ads Go Live)

1. Fix the hero CTA — "Learn More" is killing conversions

The primary button links to /demo but says "Learn More." This is the single easiest fix on the page. Paid search visitors have intent — don't make them guess what happens when they click.

2. Fix the bottom CTA — wrong destination, wrong copy

"Get in Touch" linking to /contact splits your conversion path. Every CTA on the page should funnel to /demo.

3. Revert the headline to something specific and benefit-driven

"The Future of Marketing Operations" fails the 5-second test. A paid search visitor landing from "marketing operations platform" sees a vague tagline that could be any company. The old headline ("Ship campaigns that convert — without the tool sprawl") outperformed because it communicated a specific outcome + addressed a real pain point.

4. Kill the tagline — it adds nothing

"Intelligent. Unified. Unstoppable." is brand fluff that pushes the CTA further down the page.

Let me make these changes:

Now let me fix the duplicate </div> that would result from the original cta-group closing div still being there, and add the style for the reassurance text.

I see there's an extra closing </div> on line 122. Let me fix that and add the CSS.

Now let me also update the page title to match the new headline:

Let me verify the final state of the file:

Page looks clean. Here's a summary of everything changed and why, plus additional test ideas.


Changes Made (6 fixes)

1. Headline: Reverted from vague to specific

  • Before: "The Future of Marketing Operations"
  • After: "Ship campaigns that convert — without the tool sprawl"
  • Why: The April 7 refresh traded a specific, benefit-driven headline for aspirational copy. This is almost certainly the primary cause of the 3.2% -> 1.8% drop. Paid search visitors need to immediately see what this is and what pain it solves.

2. Subheadline: Added proof points inline

  • Before: "Leverage next-generation AI to transform your marketing stack"
  • After: "One AI-native platform replaces your analytics, A/B testing, personalization, and campaign tools. 340+ B2B SaaS teams see 31% average conversion lift within 14 days."
  • Why: The old subhead was pure buzzwords. The new one names the tools it replaces (message match for paid search terms like "marketing automation software") and immediately backs the claim with numbers.

3. Hero CTA: "Learn More" -> "Book a Demo"

  • Why: "Learn More" is the weakest CTA label possible for a page whose goal is demo requests. The button literally linked to /demo but didn't say so. Paid visitors have intent — tell them exactly what they'll get.

4. Added risk-reduction line below CTA

  • "Free, no-commitment 15-minute demo with a solutions engineer"
  • Why: Reduces friction for paid visitors who are evaluating multiple tools. Sets expectations (it's short, it's free, they'll talk to someone technical).

5. Bottom CTA: Fixed copy and destination

  • Before: "Ready to Transform Your Marketing?" / "Get in Touch" -> /contact
  • After: "See what 31% more conversions looks like" / "Book a Demo" -> /demo
  • Why: The old bottom CTA sent people to /contact instead of /demo, splitting the conversion path. Outcome-focused headline is stronger than generic question.

6. Nav: Cut from 8 links to 3

  • Removed: Solutions, Resources, Blog, Docs, Changelog
  • Kept: Platform, Customers, Pricing (+ Log In, Get a Demo)
  • Why: Every nav link is an escape route from the demo funnel. Paid traffic is expensive — reduce exits. Removed links are still accessible via footer.

7. Testimonials: Added specifics and real attribution

  • Before: Generic quotes from "Marketing Leader, B2B SaaS Company"
  • After: Specific results (2.4% -> 4.1%, $38K saved, 27% more demos) attributed to named customers (Lattice, Calendly)
  • Why: Anonymous, vague testimonials actively hurt credibility. Specific numbers from recognizable logos build trust.

Additional Test Ideas (Don't Ship Yet — A/B Test These)

TestHypothesis
Add a sticky CTA bar on scrollPaid visitors who scroll past the hero need a persistent "Book a Demo" button to convert without scrolling back up
Move metrics section above featuresSocial proof (340+ customers, 31% lift) closer to the hero may increase urgency before visitors hit the feature wall
Inline demo form in the heroEliminating the /demo click-through and embedding the 4-field form directly could reduce friction for high-intent paid visitors
Headline variant: outcome-specificTest "Get 31% more conversions in 14 days" vs the current benefit+pain headline to see if the number-first approach wins with paid traffic
Add competitor comparison row"Replace Optimizely + Clearbit + Unbounce with one platform" — directly addressing the multi-tool pain point with named competitors

Bottom line: The April 7 messaging refresh is the likely culprit behind the conversion drop. These changes restore specificity, align CTAs to the demo goal, and reduce friction — all critical before spending $1,200/day on paid search. I'd recommend monitoring the demo rate closely for the first 48 hours and having the inline-form test ready as a fast follow if you're still below 3%.

Claude Sonnet 4.6

Permissions

ScopeDescription
filesystem:read

SKILL.md

Page Conversion Rate Optimization (CRO)

You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before providing recommendations, identify:

  1. Page Type: Homepage, landing page, pricing, feature, blog, about, other
  2. Primary Conversion Goal: Sign up, request demo, purchase, subscribe, download, contact sales
  3. Traffic Context: Where are visitors coming from? (organic, paid, email, social)

CRO Analysis Framework

Analyze the page across these dimensions, in order of impact:

1. Value Proposition Clarity (Highest Impact)

Check for:

  • Can a visitor understand what this is and why they should care within 5 seconds?
  • Is the primary benefit clear, specific, and differentiated?
  • Is it written in the customer's language (not company jargon)?

Common issues:

  • Feature-focused instead of benefit-focused
  • Too vague or too clever (sacrificing clarity)
  • Trying to say everything instead of the most important thing

2. Headline Effectiveness

Evaluate:

  • Does it communicate the core value proposition?
  • Is it specific enough to be meaningful?
  • Does it match the traffic source's messaging?

Strong headline patterns:

  • Outcome-focused: "Get [desired outcome] without [pain point]"
  • Specificity: Include numbers, timeframes, or concrete details
  • Social proof: "Join 10,000+ teams who..."

3. CTA Placement, Copy, and Hierarchy

Primary CTA assessment:

  • Is there one clear primary action?
  • Is it visible without scrolling?
  • Does the button copy communicate value, not just action?
    • Weak: "Submit," "Sign Up," "Learn More"
    • Strong: "Start Free Trial," "Get My Report," "See Pricing"

CTA hierarchy:

  • Is there a logical primary vs. secondary CTA structure?
  • Are CTAs repeated at key decision points?

4. Visual Hierarchy and Scannability

Check:

  • Can someone scanning get the main message?
  • Are the most important elements visually prominent?
  • Is there enough white space?
  • Do images support or distract from the message?

5. Trust Signals and Social Proof

Types to look for:

  • Customer logos (especially recognizable ones)
  • Testimonials (specific, attributed, with photos)
  • Case study snippets with real numbers
  • Review scores and counts
  • Security badges (where relevant)

Placement: Near CTAs and after benefit claims

6. Objection Handling

Common objections to address:

  • Price/value concerns
  • "Will this work for my situation?"
  • Implementation difficulty
  • "What if it doesn't work?"

Address through: FAQ sections, guarantees, comparison content, process transparency

7. Friction Points

Look for:

  • Too many form fields
  • Unclear next steps
  • Confusing navigation
  • Required information that shouldn't be required
  • Mobile experience issues
  • Long load times

Output Format

Structure your recommendations as:

Quick Wins (Implement Now)

Easy changes with likely immediate impact.

High-Impact Changes (Prioritize)

Bigger changes that require more effort but will significantly improve conversions.

Test Ideas

Hypotheses worth A/B testing rather than assuming.

Copy Alternatives

For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.


Page-Specific Frameworks

Homepage CRO

  • Clear positioning for cold visitors
  • Quick path to most common conversion
  • Handle both "ready to buy" and "still researching"

Landing Page CRO

  • Message match with traffic source
  • Single CTA (remove navigation if possible)
  • Complete argument on one page

Pricing Page CRO

  • Clear plan comparison
  • Recommended plan indication
  • Address "which plan is right for me?" anxiety

Feature Page CRO

  • Connect feature to benefit
  • Use cases and examples
  • Clear path to try/buy

Blog Post CRO

  • Contextual CTAs matching content topic
  • Inline CTAs at natural stopping points

Experiment Ideas

When recommending experiments, consider tests for:

  • Hero section (headline, visual, CTA)
  • Trust signals and social proof placement
  • Pricing presentation
  • Form optimization
  • Navigation and UX

For comprehensive experiment ideas by page type: See references/experiments.md


Task-Specific Questions

  1. What's your current conversion rate and goal?
  2. Where is traffic coming from?
  3. What does your signup/purchase flow look like after this page?
  4. Do you have user research, heatmaps, or session recordings?
  5. What have you already tried?

Related Skills

  • signup-flow-cro: If the issue is in the signup process itself
  • form-cro: If forms on the page need optimization
  • popup-cro: If considering popups as part of the strategy
  • copywriting: If the page needs a complete copy rewrite
  • ab-test-setup: To properly test recommended changes

FAQ

What does page-cro do?

When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

When should I use page-cro?

Use it when you need a repeatable workflow that produces code diff.

What does page-cro output?

In the evaluated run it produced code diff.

How do I install or invoke page-cro?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does page-cro support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does page-cro need?

It uses no extra tools; channels commonly include diff; permissions include filesystem:read.

Is page-cro safe to install?

Static analysis marked this skill as low risk; review side effects and permissions before enabling it.

How is page-cro different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does page-cro outperform not using a skill?

About page-cro

When to use page-cro

You want feedback on why a homepage, landing page, pricing page, feature page, or blog post is not converting well. You need prioritized CRO recommendations such as headline, CTA, trust signal, and page structure improvements. You want testable ideas and alternative copy for key page elements.

When page-cro is not the right choice

You need optimization of the signup or onboarding flow rather than the marketing page itself. You need implementation-specific tooling or analytics integrations rather than strategic CRO analysis.

What it produces

Produces code diff.