| name | page-cro |
| platforms | ["cowork","claude-code"] |
| description | Audit and improve conversion performance on Tiger Data marketing pages, including homepage, landing pages, pricing pages, feature pages, and blog posts. Use this skill when the user asks for CRO, landing page feedback, conversion advice, CTA improvements, hero rewrites, bounce or drop-off analysis, or wants recommendations based on Clarity exports, screenshots, or a live page URL. Also trigger when the user mentions 'conversion rate,' 'page performance,' 'why isn't this page converting,' 'CTA audit,' 'hero section feedback,' 'friction analysis,' 'landing page review,' or 'page optimization.' For signup or registration flow issues, use a dedicated signup-flow-cro skill if one exists. For production edits, hand off to website-content-editor or page-mockup-builder. |
| references | ["product-marketing-context","brand-voice-guide"] |
Page CRO
Audit and improve conversion performance on Tiger Data marketing pages. Combines page review, messaging analysis, friction analysis, and optional Clarity behavioral evidence to produce prioritized recommendations: copy fixes, structural changes, and test ideas.
When to use this skill
- When the user asks for CRO, conversion advice, or landing page feedback
- When the user wants CTA improvements, hero rewrites, or friction analysis
- When the user shares a page URL, screenshot, or Clarity CSV and asks "what would you change?"
- When the user mentions bounce rates, drop-off, or conversion issues on a specific page
- When the user asks "why isn't this page converting?" or "how do I improve this page?"
Scope
Included: Homepage, product pages, feature pages, campaign landing pages, pricing pages, blog CTA strategy.
Optional inputs: Screenshots, page URLs, Clarity CSVs, notes on traffic source and conversion goal.
Excluded: Signup flow internals, product onboarding, in-app modals (unless the modal is the primary conversion mechanism on the page).
Step 0: Pre-flight check
Invoke the marketing-preflight skill via the Skill tool, passing this skill's name: field value (page-cro) as the args. Do not proceed until it completes successfully. If it stops with an error, follow its instructions and stop.
If marketing-preflight returned a stale-connector footer note, append it verbatim at the end of your final response to the user.
Once Tiger Den is confirmed, fetch this skill's reference docs:
get_marketing_context(slugs: ["product-marketing-context", "brand-voice-guide"])
If Clarity CSVs are provided: Before proceeding to Step 1, invoke the clarity-analyzer skill to process the CSV data. Use those findings as behavioral evidence throughout the audit.
Step 1: Classify the page
Determine the page type and primary conversion goal. Ask the user to confirm if ambiguous.
| Page type | Typical primary goal |
|---|
| Homepage | Navigate to product page or start trial |
| Product / feature page | Start trial or request demo |
| Pricing page | Select plan and start trial |
| Campaign landing page | Single CTA (demo, download, signup) |
| Blog post | Read related content, start trial, or subscribe |
| Comparison page | Choose Tiger Data over alternative |
Also identify:
- Traffic source assumptions — Where are visitors likely coming from? (organic search, paid ads, email, social, direct) This shapes intent expectations.
- Visitor intent — What problem are they trying to solve? What stage of evaluation are they in?
If the user provides traffic source or goal information, use it. If not, infer from the page type and content, and state your assumptions.
Step 2: Audit the page
Work through each dimension in the CRO checklist (see references/cro-checklist.md). For each dimension, assess the current state and note specific issues.
The six audit dimensions:
- Value proposition clarity — Is it obvious what Tiger Data does and why it matters, within 5 seconds? Is the headline specific and benefit-driven, or vague and feature-first?
- CTA hierarchy — Is there one clear primary CTA? Are secondary CTAs visually subordinate? Is the CTA copy action-oriented and specific ("Start your free trial" not "Get started")?
- Trust and proof — Are there customer logos, case studies, metrics, testimonials, or third-party validation? Is the proof relevant to the visitor's likely concerns?
- Objection handling — Does the page preemptively address common hesitations (pricing, migration difficulty, vendor lock-in, performance at scale)? Are answers specific or hand-wavy?
- Scannability and structure — Can a visitor who skims get the core message? Are headings descriptive? Is the visual hierarchy working? Is there too much text before the first CTA?
- Friction and cognitive load — Are there unnecessary form fields, confusing navigation choices, competing CTAs, jargon without context, or dead ends? Is the path from "interested" to "acting" as short as possible?
Folding in behavioral evidence
If Clarity data was processed in Step 0, integrate those findings into the relevant dimensions:
- Scroll depth data → Scannability (where do visitors stop reading?), CTA hierarchy (is the primary CTA above the scroll drop-off?)
- Click data → CTA hierarchy (what are visitors actually clicking?), Friction (are they clicking non-clickable elements or ignoring the primary CTA?)
- Rage clicks or dead clicks → Friction (broken expectations, confusing UI)
Don't just list the behavioral data separately. Weave it into the dimensional analysis as supporting evidence.
Step 3: Assess messaging alignment
Using product-marketing-context and brand-voice-guide, check:
- Positioning match — Does the page lead with the problem Tiger Data solves, not just features? Does it align with current positioning?
- Terminology — Are product names, feature names, and technical terms correct per the glossary?
- Voice — Does the copy sound like Tiger Data? Flag AI slop, marketing fluff, passive voice, em dashes, or generic developer-tool language.
- Competitive framing — If the page references competitors, does it follow the guardrails in product-marketing-context?
Keep this section focused on issues that affect conversion, not a full brand audit. If the messaging is generally on-brand, say so and move on.
Step 4: Produce the audit report
Structure the output as follows:
Executive summary
2-3 sentences. What's the page doing well? What's the biggest conversion risk?
Top conversion blockers
The 2-3 most critical issues preventing conversions. Each should include:
- What the problem is
- Why it matters (impact on conversion)
- Where on the page it occurs
Quick wins
Changes that are low-effort and high-confidence. These should be implementable in under an hour:
- Copy tweaks (headline rewrites, CTA label changes)
- Removing friction (unnecessary fields, confusing microcopy)
- Adding missing trust signals in obvious spots
High-impact changes
Changes that require more effort but would meaningfully improve conversion:
- Structural reorganization (section reordering, adding/removing sections)
- New content blocks (case study section, comparison table, objection-handling FAQ)
- Visual hierarchy fixes (CTA prominence, above-fold content)
Test ideas
A/B or multivariate test hypotheses. Consult references/experiments.md for a menu of experiments organized by page type -- pick tests that address the specific issues found in the audit, don't just list generic tests. Each test idea should include:
- What to test (control vs. variant)
- What you expect to happen and why
- What metric to watch
Optional: Rewritten hero / CTA set
If the user asks for it, or if the hero or CTAs are the primary conversion blocker, provide:
- A rewritten headline and subheadline
- Rewritten primary CTA (button copy + supporting text)
- Brief rationale for each change
Write these in Tiger Data's brand voice using the brand-voice-guide.
Step 5: Offer next steps
After delivering the audit, ask whether the user wants:
- A deeper dive on any specific dimension
- Help rewriting specific sections (hand off to brand-voice-writer)
- A visual mockup of recommended changes (hand off to page-mockup-builder)
- To implement changes on the live site (hand off to website-content-editor)
- A re-audit after changes are made
- Clarity data analyzed if they have CSVs but didn't provide them initially (hand off to clarity-analyzer)
Dependencies
- Required: Tiger Den connector (for product-marketing-context and brand-voice-guide)
- Optional: Clarity CSV exports (processed via clarity-analyzer skill), screenshots or page URLs for visual review
