trust-badges-generator
# trust-badges-generator The trust-badges-generator skill guides design and strategic placement of trust badges, security seals, payment logos, and social proof elements to reduce purchase anxiety and boost conversion rates. Use it when optimizing badge types like SSL certificates, payment methods, guarantees, and customer testimonials across checkout, product pages, and hero sections, or when the user specifically mentions trust signals, security badges, or "trusted by" logos.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/trust-badges-generator && cp -r /tmp/trust-badges-generator/skills/components/conversion/trust-badges ~/.claude/skills/trust-badges-generatorSKILL.md
# Components: Trust Badges Guides trust badge design and placement for conversion. Trust badges borrow authority from third-party organizations to signal legitimacy and reduce purchase anxiety. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for key partners and certifications. Identify: 1. **Site type**: E-commerce, SaaS, lead gen 2. **Available badges**: Security, payment, reviews, guarantees 3. **Placement goals**: Hero, checkout, product pages ## Badge Types & Impact | Type | Best Placement | Conversion Impact | |------|----------------|-------------------| | **Security** (SSL, Norton, McAfee) | Checkout, payment forms | +15–10% for unfamiliar brands | | **Payment logos** (Visa, PayPal, Stripe) | Checkout, cart | +8→2% trust | | **Money-back guarantee** | Product, checkout | +6–10% | | **Reviews/ratings** (Trustpilot, BBB) | Product, hero | +12→8% | | **Privacy/compliance** (GDPR, CCPA) | Forms, checkout | Data-sensitive transactions | **"Trusted by" logos**: Client/customer logos in hero or footer; social proof for B2B. **"As Seen In"** (press coverage): Publication logos; see **press-coverage-page-generator** for media mentions aggregation. ## Best Practices ### Quantity - **3→ badge types max**; more can cause "badge bloat" and reduce conversions by 5→% - Quality over quantity; use only legitimate, verifiable badges ### Placement - **Highest leverage**: Cart and checkout (near payment fields) - **Product pages**: Near add-to-cart button - **Hero**: "Trusted by" logos for brand credibility - **Footer**: Secondary trust signals ### Authenticity - Use only real, verifiable badges - Fake or irrelevant badges create skepticism - Link to verification where appropriate ## Design Guidelines - Consistent size and style; don't mix clashing visuals - **Image optimization**: Alt text, format—see **image-optimization** - Adequate spacing; avoid clutter - Grayscale or muted for "Trusted by" logos (don't compete with primary content) - Ensure badges are recognizable at display size ## Accessibility - Provide `alt` text for badge images (e.g., "Norton Secured") - Don't rely on badges alone for critical information ## Output Format - **Badge recommendations** by type and placement - **Placement map** (hero, product, checkout) - **Quantity** guidance (avoid bloat) ## Related Skills - **landing-page-generator**: Trust signals as step 2 (earn trust) in landing page flow - **hero-generator**: "Trusted by" often in hero - **testimonials-generator**: Complementary social proof - **cta-generator**: Badges near CTAs increase conversion - **pricing-page-generator**: Trust badges on pricing pages - **image-optimization**: Badge image optimization (alt, format) - **press-coverage-page-generator**: "As Seen In" publication logos; similar visual treatment; distinct (press = media coverage; trust-badges = security, payment, reviews) - **brand-protection**: "Official website" badges to distinguish from impersonation sites
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.