The hero headline and its immediately following supporting text are read as a unit — visitors process them together in their first pass. When the supporting text introduces a different topic than the headline, visitors receive two half-messages instead of one complete one. Neither registers clearly. For example, a headline about speed ("Ship faster") followed by sub-text about security ("Enterprise-grade security for your team") leaves the visitor unsure which of the two attributes is the actual value proposition. The dissonance also signals inconsistency in how the product thinks about itself — a subtle trust signal. The sub-headline's job is to answer the question the headline raises, not to pivot to a new claim.
Low because a mismatched headline and sub-text reduces hero clarity without preventing visitors from understanding the product entirely — the failure is inefficiency rather than a blocking confusion.
Read the headline and sub-text together and ask: can you summarize both in one sentence? If not, rewrite the sub-text to amplify or specify what the headline already started.
Paired examples:
Headline: "Ship faster"
Weak sub-text: "Enterprise-grade security for your team." ← different topic
Strong sub-text: "Deploy to production in one click — no CI pipeline to configure."
Headline: "Never lose a customer again"
Weak sub-text: "Our platform leverages advanced ML to power your workflow."
Strong sub-text: "Predict churn 30 days early and automate retention outreach."
The sub-text's structure should be: [verb or result] + [mechanism or specificity]. In app/page.tsx or components/HeroSection.tsx, locate the <p> or sub-headline element immediately below the <h1> and update it to answer the question the headline raises.
ID: marketing-content-quality.value-proposition.hero-subtext-reinforces-headline
Severity: low
What to look for: Count all relevant instances and enumerate each. Read the hero <h1> headline and the immediately following supporting text (sub-headline, descriptor paragraph, or tagline). Determine whether the supporting text amplifies, explains, or specifies the headline's message — making the two form a coherent, single message that a reader could summarize in one sentence. Check whether the supporting text introduces a topic, benefit, or audience that the headline does not imply.
Pass criteria: The sub-headline or supporting text directly expands on the headline's message. Together, headline + supporting text answer: what does this product do, for whom, and what outcome do they get? The two are about the same topic.
Fail criteria: The supporting text introduces a different topic, benefit, or audience than the headline implies. Example: headline says "Ship faster" but sub-text says "Enterprise-grade security for your team" — the headline is about speed, the sub-text is about security. Or the supporting text merely restates the headline in different words without adding new information (e.g., headline: "The best analytics tool" → sub-text: "An analytics tool that's the best").
Skip (N/A) when: No hero section detected, or the hero has only a headline with no supporting text element (no <p>, no sub-headline, no descriptor below the <h1>).
Detail on fail: Quote both the headline and supporting text and name the mismatch. Example: "Headline: 'Ship faster' — Sub-text: 'Enterprise-grade security for your team.' Headline is about speed; sub-text is about security. No coherent single message." Keep under 250 chars.
Remediation: When headline and supporting text are about different things, visitors get two half-messages instead of one complete one. Neither lands.
Write the sub-headline to answer the question the headline raises:
The test: can you combine headline + sub-text into one coherent sentence? If not, they're not reinforcing each other.
Review the configuration in src/ or app/ directory for implementation patterns.
Cross-reference: For related patterns and deeper analysis, see the corresponding checks in other AuditBuffet audits covering this domain.