CRO-Optimized Example Prompts

Here are real-world example prompts for common CRO experiments. Each example includes the prompt text, the hypothesis behind it, and important considerations.

1. Adding Trust Signals to Product Pages

Prompt:

"Add trust badges (free shipping, secure checkout, money-back guarantee) directly above the add-to-cart button. Style them to be subtle but visible, using small icons with text. Make sure the add-to-cart button functionality is preserved and the product price remains dynamic."

CRO Hypothesis: Trust signals near the primary CTA reduce purchase anxiety and increase conversion rates. Research shows trust badges within 200px of checkout CTAs can increase conversions by 7-15%.

Considerations:

• Ensure the price is dynamic, not hardcoded
• Preserve add-to-cart button functionality
• Test on mobile to ensure badges don't clutter the interface

2. Optimizing CTA Button Copy and Styling

Prompt:

"Replace the main call-to-action button in the hero section. Change the text from 'Learn More' to 'Start Your Free Trial' and make it use the primary brand color (the blue from the logo). Increase the button size slightly and add a subtle hover effect that makes it slightly darker. Ensure it links to the same destination."

CRO Hypothesis: Action-oriented, benefit-focused CTAs with clear value propositions (like "free trial") convert better than vague CTAs. Visual prominence through color and size draws attention to the primary action.

Considerations:

• Proxy click events if replacing an interactive button
• Match the brand's existing color palette
• Test button contrast for accessibility

3. Adding Social Proof Near CTAs

Prompt:

"Add a social proof section immediately after the hero section. Include a headline like 'Join 10,000+ happy customers' and display 3-4 customer logos in a row. Style it to be clean and professional, matching the page's existing design. On mobile, stack the logos vertically."

CRO Hypothesis: Social proof (customer counts, logos, testimonials) reduces perceived risk and builds credibility. Placing it early on the page, near the hero, leverages the goal-gradient effect—users feel they're joining a community.

Considerations:

• Use actual customer counts if available, or use placeholders like "[CUSTOMER_COUNT]"
• Ensure logos are properly sized and don't break on mobile
• Don't invent customer names or companies

4. Adding Urgency/Scarcity Messaging

Prompt:

"Add a limited-time offer banner above the pricing section. Display text like 'Limited time: Save 20% on annual plans' with a countdown timer showing days remaining. Style it with a subtle background color that matches the brand, and make it dismissible with a small X button. Only show this if there's evidence of a current promotion on the page."

CRO Hypothesis: Scarcity and urgency messaging can increase conversions by creating FOMO (fear of missing out), but only when authentic. Loss aversion makes users act faster when they perceive limited availability.

Considerations:

• Only use if there's actual evidence of a promotion—never invent discounts or sale prices
• Ensure the countdown timer is functional (may require JavaScript)
• Make it dismissible to avoid annoying returning visitors
• Test that it doesn't conflict with existing promotional messaging

5. Reordering Sections for Better Hierarchy

Prompt:

"Move the customer testimonials section to appear immediately after the hero section, before the features section. On mobile, ensure the testimonials are still readable and don't create too much scrolling before the main CTA."

CRO Hypothesis: Placing social proof and trust signals early (above the fold or immediately after the hero) builds credibility before users evaluate features. This follows the principle of establishing trust before asking for commitment.

Considerations:

• Test on both mobile and desktop to ensure layout doesn't break
• Consider the page's existing flexbox or grid structure
• Ensure the section maintains its styling and functionality after moving

6. Optimizing SaaS Landing Page Hero

Prompt:

"Redesign the hero section headline to focus on the primary pain point our ideal customer faces. Change the subheadline to be more benefit-focused, emphasizing time savings. Make the primary CTA button more prominent by increasing its size and using a contrasting color. Add a short value proposition line directly above the CTA."

CRO Hypothesis: Headlines that address specific pain points resonate more with target audiences. Benefit-focused messaging (time savings, efficiency) converts better than feature-focused messaging. Prominent CTAs with clear value props reduce friction.

Considerations:

• Maintain brand voice and tone
• Ensure the CTA remains functional
• Test headline length on mobile (shorter may be needed)
• Keep the value proposition concise (one sentence)

7. Emphasizing Preferred Plan in Pricing Table

Prompt:

"Make the middle pricing tier (the 'Professional' plan) more visually prominent by increasing its size slightly, adding a subtle border or background color, and placing a 'Most Popular' badge at the top. Ensure all pricing information remains dynamic and accurate—don't hardcode any prices."

CRO Hypothesis: The decoy effect and anchoring work together: highlighting a preferred plan makes it the "anchor" that other plans are compared against. Visual prominence (size, color, badges) draws attention to the recommended option.

Considerations:

• Critical: Never hardcode prices—they must remain dynamic
• Don't invent "Most Popular" badges if there's no evidence this plan is actually preferred
• Ensure the pricing table remains functional and all CTAs work
• Test that the visual changes don't break the table layout on mobile

8. Mobile-Specific Optimizations

Prompt:

"On mobile only, make the main CTA button full-width and increase its size. Move it to a sticky position at the bottom of the screen after the user scrolls past the hero section. Ensure the button text is large enough to read easily and maintains good contrast."

CRO Hypothesis: Mobile users have limited screen space and shorter attention spans. Sticky CTAs ensure the primary action is always accessible, reducing friction. Full-width buttons are easier to tap on mobile devices.

Considerations:

• Specify "on mobile only" clearly in the prompt
• Test that the sticky behavior doesn't interfere with page content
• Ensure the button doesn't cover important content when sticky
• Verify touch target size meets accessibility guidelines (minimum 44x44px)

Common Improve Flow Prompts

For prompts to fix common styling and layout issues when iterating on existing variants, see Common Improve Flow Prompts. This guide covers alignment issues, margin and spacing problems, container constraints, flex flow issues, grid column spanning, z-index layering, and sticky positioning.

Building on Examples

These examples are starting points. Combine techniques (e.g., add trust badges + optimize CTA copy) for more comprehensive experiments. Always test one change at a time initially, then iterate based on results.