page-cro

Overview of page-cro skill

What page-cro is for

page-cro is a Conversion Rate Optimization skill for auditing marketing pages and turning vague “this page is not converting” concerns into prioritized, actionable recommendations. It is best suited for homepages, landing pages, pricing pages, feature pages, about pages, and conversion-oriented blog posts where the goal is signups, demos, purchases, subscriptions, downloads, or sales contact.

Best-fit users and use cases

Use the page-cro skill if you are a founder, marketer, product marketer, growth lead, copywriter, or web designer who needs a structured page review before rewriting copy or running experiments. It is especially useful when you have a live URL, HTML export, page draft, wireframe, or copied page text and want feedback on value proposition, CTA clarity, trust, friction, social proof, objection handling, and page flow.

What makes page-cro different

The skill is not just a generic “improve this landing page” prompt. Its source framework asks for page type, conversion goal, and traffic context before making recommendations, then analyzes high-impact CRO areas in order. The repository also includes scripts/conversion_audit.py, a lightweight helper for scanning HTML pages for signals such as CTAs, forms, testimonials, trust mentions, viewport metadata, and other page-level conversion elements.

When to choose another skill

Do not use page-cro for every conversion problem. For signup or registration flows, use a signup-flow CRO skill if available. For post-signup activation, onboarding, or retention, use an onboarding-focused skill. For standalone form optimization, modal behavior, or popup copy, a narrower form or popup CRO skill will usually produce more precise recommendations.

How to Use page-cro skill

page-cro install and files to inspect first

Install from the GitHub skill repository with:

npx skills add alirezarezvani/claude-skills --skill page-cro

After installation, read marketing-skill/skills/page-cro/SKILL.md first because it contains the core CRO framework and triggering rules. Then inspect scripts/conversion_audit.py if you want a more evidence-based audit from an HTML file or URL. This skill folder is intentionally small: there is no separate README.md, rules/, or references/ directory in the current tree, so SKILL.md and the script are the practical sources of truth.

Inputs that produce better page-cro usage

For strong page-cro usage, provide more than a URL. Include the page type, target audience, offer, primary CTA, traffic source, current conversion goal, and any known performance data. If the page serves multiple audiences or has multiple CTAs, say which segment and action matter most.

A weak prompt is:

“Improve this landing page for conversions.”

A stronger prompt is:

“Use page-cro for Conversion review of this B2B SaaS pricing page. Goal: increase demo requests from paid search traffic. Audience: RevOps managers at 100–500 person companies. Primary CTA: Book a demo. Current issue: high traffic but low CTA clicks. Review headline clarity, plan comparison, objections, trust signals, CTA placement, and friction. Prioritize fixes by likely impact and effort.”

Suggested workflow for a useful audit

Start by asking the model to identify the page type, primary conversion goal, and traffic context before recommending changes. Then request a prioritized audit, not a flat list. A practical sequence is:

1. Run the skill on the page copy, screenshot notes, URL, or HTML.
2. Ask for the top 5 conversion blockers ranked by impact.
3. Ask for rewritten hero copy, CTA alternatives, trust-section improvements, and objection-handling modules.
4. Turn recommendations into testable hypotheses.
5. If you have HTML, run or reference scripts/conversion_audit.py to support the qualitative review.

The script can be used as a quick pre-check with commands such as python3 conversion_audit.py --file page.html or python3 conversion_audit.py --url https://example.com.

Practical prompt pattern

Use this structure when calling page-cro:

“Use the page-cro skill to audit [page type] for [audience]. The primary goal is [conversion action]. Traffic comes from [source]. Here is the page content/URL/HTML: [input]. Focus on [business concern]. Return: conversion diagnosis, prioritized issues, recommended copy/layout changes, CTA improvements, trust gaps, and 3 experiment ideas.”

This works because the skill’s framework depends on context. A homepage for organic visitors needs different recommendations than a paid landing page for a warm retargeting audience.

page-cro skill FAQ

Is page-cro suitable for beginners?

Yes. The page-cro skill is beginner-friendly because it gives the agent a structured CRO lens rather than expecting the user to know all audit categories. Beginners should still provide the conversion goal, audience, and traffic source; without those, the output may become a broad best-practices review instead of a decision-ready audit.

Can page-cro replace analytics or A/B testing?

No. page-cro helps identify likely conversion problems and generate better test ideas, but it does not prove causality. Use it before analytics review, customer research, or A/B testing to sharpen hypotheses. If you already have funnel data, heatmaps, search terms, or session recordings, include them so the skill can distinguish evidence-backed issues from plausible guesses.

What pages does page-cro handle best?

It works best on marketing pages where one primary conversion action matters. Strong fits include SaaS landing pages, pricing pages, product feature pages, agency service pages, lead-generation pages, newsletter signup pages, and sales pages. It is less ideal for complex app workflows, checkout engineering, lifecycle email strategy, or in-product activation.

How is this better than an ordinary CRO prompt?

An ordinary prompt may produce generic advice such as “add testimonials” or “make the CTA clearer.” page-cro is more useful because it starts with conversion context, separates page-level CRO from signup, onboarding, form, and popup CRO, and emphasizes high-impact areas like value proposition clarity before lower-priority polish.

How to Improve page-cro skill

Give page-cro sharper conversion context

The fastest way to improve page-cro output is to define the conversion moment precisely. Instead of saying “increase conversions,” say “increase free trial starts from non-branded organic traffic” or “increase demo requests from enterprise visitors who arrive from LinkedIn ads.” This helps the skill judge message match, objection handling, CTA strength, and page friction against the real visitor intent.

Add evidence before asking for recommendations

Better inputs create better audits. Include page metrics such as traffic source, bounce rate, CTA click rate, form completion rate, scroll depth, conversion rate by device, or top objections from sales calls. If you lack data, say so and ask the skill to label recommendations as assumptions, qualitative issues, or test hypotheses.

Watch for common failure modes

The most common page-cro failure is over-optimization without strategy: changing button text, colors, or section order before clarifying the offer. Another failure is asking for recommendations without identifying the audience or funnel stage. A third is treating all suggestions as equally important. Ask the skill to rank fixes by impact, confidence, and implementation effort so the output becomes a usable CRO roadmap.

Iterate after the first page-cro output

After the first audit, do not stop at the recommendation list. Ask for rewrites of the hero section, above-the-fold CTA area, pricing explanation, testimonial block, FAQ objections, and final CTA. Then ask the skill to convert the strongest ideas into A/B test hypotheses with success metrics. This turns page-cro from a one-time critique into a practical conversion improvement workflow.