TrustSignalPlacement [rule] v1.0.0

Place each trust signal at the moment it addresses a specific conversion objection — not wherever it fits visually. Each trust component type appears once, in one position.

Meta

• License: Apache-2.0
• License Provenance: package-authorship-claim

Applies To

• Landing pages
• Product marketing pages
• Pricing pages
• Any page where conversion is a goal

TrustSignalPlacement [rule] v1.0.0

Place each trust signal at the moment it addresses a specific conversion objection — not wherever it fits visually. Each trust component type appears once, in one position.

Meta

• License: Apache-2.0
• License Provenance: package-authorship-claim

Applies To

• Landing pages
• Product marketing pages
• Pricing pages
• Any page where conversion is a goal

Examples

• Hero CTA → Trust badge row ('Is this legit?')
• Below fold → Logo strip ('Who else uses this?')
• After features → Social proof numbers ('How big is this really?')
• Beside pricing → Testimonial micro-quote ('Has someone like me succeeded?')
• Page bottom → Security certifications ('Is my data safe?')

Relations

related: [@community/pattern-trust-badge-row, @community/pattern-trust-logo-strip, @community/pattern-trust-social-proof-numbers, @community/pattern-trust-testimonial-micro, @community/pattern-trust-security-cert, @community/rule-trust-signal-critical, @community/anti-pattern-fake-trust-signals]

Rationale

Trust signals that appear repeatedly across multiple sections suffer from signal fatigue and lose their meaning. Each trust component is most persuasive when it directly answers the specific objection a visitor has at that point in the page scroll.

Meta

• License: Apache-2.0
• License Provenance: package-authorship-claim

Applies To

• Landing pages
• Product marketing pages
• Pricing pages
• Any page where conversion is a goal