Generic claims — "fast", "the best", "easy integration", "trusted by teams" — have been used on so many product pages that visitors filter them out on sight. They create no credibility because they cannot be verified and no competitor would dispute them. Specific claims — "average response time: 45ms", "2,400 SaaS teams", "connects to Slack in 2 clicks" — create credibility precisely because they can be verified and could be wrong. A visitor reading specific claims perceives that the company is confident enough to commit to a checkable statement. When more than 40% of a page's claims are generic, the page loses its signal-to-noise ratio: the specific claims get buried under the generic ones.
High because a majority of generic, unverifiable claims across the home page erodes credibility at the moment of evaluation — visitors who are comparing options rely on claims to differentiate, and generic claims provide no signal.
Audit your home page for its 5-7 most prominent claims. For each, classify it: does it include a number, a named entity, a concrete mechanism, or a verifiable outcome? If not, either make it specific or remove it.
Transformation patterns:
"Fast" → "Average response time: 45ms"
"Trusted by many teams" → "Used by 2,400 SaaS teams"
"Easy integration" → "Connects to Slack in 2 clicks"
"Works with any tool" → "Works with GitHub, Linear, and Notion"
"Secure" → "SOC 2 Type II certified, AES-256 encrypted at rest"
If you cannot make a claim specific because the evidence doesn't exist yet, remove it. Three specific claims are more persuasive than three specific claims buried under five generic ones. Update the claims in whichever component renders the hero and features sections — typically app/page.tsx, components/HeroSection.tsx, or a features data array.
ID: marketing-content-quality.value-proposition.claims-specific-not-generic
Severity: high
What to look for: Identify the top 3-5 claims on the home page. A "claim" is any statement asserting a capability, benefit, result, or advantage — e.g., "Works with any AI tool", "Reduces churn by 30%", "The fastest way to ship." For each claim, classify it as specific (contains a number, a named entity, a concrete mechanism, or a verifiable outcome) or generic (uses unsubstantiated superlatives like "best" or "fastest" without evidence, vague promises like "improve your workflow", or category-level descriptions any competitor could make verbatim without modification). Report: "X of Y claims are specific."
Pass criteria: At least 60% of the identified claims are specific. Report the ratio: "X of Y claims are specific." A claim counts as specific if it includes at least one of: a number ("2,000+ checks"), a named entity ("works with Slack and GitHub"), a concrete mechanism ("uses SHA-256 hashing"), or a verifiable outcome ("reduce churn by 30%").
Fail criteria: More than 40% of claims are generic — they could appear on any competitor's site without modification. Report the ratio and quote an example generic claim. Example: "2 of 5 claims are specific (40%). Generic examples: 'The best solution for your team', 'Improve your workflow instantly.'"
Skip (N/A) when: No home page or marketing content detected. Signal: API-only project with no public-facing marketing routes.
Detail on fail: Report the ratio and quote 1-2 generic claims. Example: "2 of 5 claims are specific (40%). Generic: 'The best tool for modern teams' — any product could say this."
Remediation: Generic claims are invisible — visitors have seen them on every other product page. Specific claims create credibility because they can be verified.
Make each claim concrete:
If you can't make a claim specific because the evidence doesn't exist yet, remove the claim. A page with 3 specific claims is more credible than a page with 3 specific and 5 generic ones.
Review the configuration in src/ or app/ directory for implementation patterns.