When the user wants to increase conversions on any marketing page — homepage, landing, pricing, feature, or blog; "CRO," "this page isn't converting," "low conversion rate," "bounce rate," "my landing page sucks" — or just shares a URL asking for feedback. For signup flows, see signup-flow-cro; post-signup activation, onboarding-cro; forms, form-cro; popups, popup-cro.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Analyze marketing pages and deliver actionable recommendations to improve conversion rates.
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Identify first:
Analyze these dimensions, in order of impact:
Can a visitor grasp what this is and why they should care within 5 seconds? Is the primary benefit clear, specific, differentiated, and in customer language (not company jargon)?
Common issues: feature-focused instead of benefit-focused; too vague or too clever (sacrificing clarity); saying everything instead of the most important thing.
Does it communicate the core value proposition? Specific enough to be meaningful? Does it match the traffic source's messaging?
Strong patterns:
One clear primary action, visible without scrolling, with button copy that communicates value, not just action:
Hierarchy: logical primary vs. secondary CTA structure; CTAs repeated at key decision points.
Can someone scanning get the main message? Are the most important elements visually prominent? Enough white space? Do images support or distract from the message?
Types: customer logos (especially recognizable), 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.
Common objections: price/value; "Will this work for my situation?"; implementation difficulty; "What if it doesn't work?"
Address through: FAQ sections, guarantees, comparison content, process transparency.
Too many form fields, unclear next steps, confusing navigation, required information that shouldn't be, mobile experience issues, long load times.
Homepage: clear positioning for cold visitors; quick path to most common conversion; handle both "ready to buy" and "still researching."
Landing page: message match with traffic source; single CTA (remove navigation if possible); complete argument on one page.
Pricing page: clear plan comparison; recommended plan indication; address "which plan is right for me?" anxiety.
Feature page: connect feature to benefit; use cases and examples; clear path to try/buy.
Blog post: contextual CTAs matching content topic; inline CTAs at natural stopping points.
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
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.
The English summary is being prepared. Showing the original description.
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
The English summary is being prepared. Showing the original description.
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
The English summary is being prepared. Showing the original description.
When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.
The English summary is being prepared. Showing the original description.
When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.
The English summary is being prepared. Showing the original description.
Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.
The English summary is being prepared. Showing the original description.