Conversion
What social proof can I show before I have customers
What 13x checks
This is rule conversion.social-proof in the public registry: Some form of social proof. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.
- Surface
- Conversion
- Score weight
- 3 of the readiness score
- Scope
- Reported as skipped when the page renders only with JavaScript
- Applies
- To every site
Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.
The fix
The same text the audit hands you when this check fails on your own site.
No testimonials, customer counts, logos or badges were found.
A brand-new product genuinely has none of this, so treat it as a prompt rather than a defect. What works before you have customers:
- The waitlist number. "412 people waiting" is social proof. - Who it is for, specifically. "Built for freelance designers who bill by project" signals more than a generic testimonial. - Your own story. Why you built it, and what you were using before. - Something verifiable. GitHub stars, a Product Hunt badge, a published changelog.
Avoid invented testimonials and placeholder logos. Both are recognisable, and getting caught costs more than having none.
Does your site have this problem?
13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.
No signup. Results in 30 seconds.
More conversion checks
- Why every launch page needs an email captureThere is a way to capture an email
- What size should an og:image beog:image is the right size
- Which analytics should I install before launchAnalytics is installed
- My page has no clear call to actionThere is a recognisable call to action
- Why I need error tracking before launchErrors are reported somewhere
- Why my site needs a contact routeThere is a way to make contact