Product differentiation is stated somewhere on the home page
Why it matters
Visitors who are genuinely interested in your product are also considering alternatives. If nothing on your home page answers "why you and not the other option?", the comparison happens entirely in the visitor's head, with no data you've provided. Generic positioning — "We're the best", "High-quality solution", "Built with passion" — is indistinguishable from your competitors' copy and provides no decision-making signal. Specific differentiation ("The only tool that works without a backend", "Built for indie developers, not enterprise teams", "Teams using this ship 2x more features per sprint on average") gives the visitor something concrete to evaluate. The specificity itself signals confidence and honesty — only a company that believes its claim would make it.
Severity rationale
Medium because without specific differentiation, the home page leaves comparison-stage visitors with no signal to choose this product over alternatives — a gap that coexists with otherwise clear messaging but costs conversion among considered buyers.
Remediation
Add at least one differentiation statement to the home page — a sentence specific enough that a competing product could not use it verbatim without lying.
Approaches that work:
// Audience specificity (excludes rather than includes)
"Built for indie developers, not enterprise teams"
// Distinct technical approach
"We store nothing server-side — your data never leaves your device"
// Measurable outcome claim
"Teams using [product] ship 2x more features per sprint on average"
// Named constraint
"The only [category] that works without a database"
Place the differentiation statement in the hero section (sub-headline or below the CTA), in a dedicated "Why us" section, or as a callout in the features section. In the codebase, locate the hero copy in app/page.tsx or components/HeroSection.tsx and add the statement where it is visible above or near the fold without scrolling.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Content Quality Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from marketing-content-quality·automated