Subheadline
A subheadline is the secondary line directly below the headline that expands on the main promise with added context, proof, or a how.
Key takeaways
- The subheadline is read second, so it explains rather than competes with the headline.
- It carries the mechanism, the audience qualifier or the effort the headline had to omit.
- Words repeated from the headline are wasted; overlap is the most common weakness.
- Naming question count and time required lowers perceived risk before the first click.
- A page with an already complete headline may need no subheadline at all.
In depth
A subheadline is read second, and only if the headline earned it. That sequence defines its job: it does not restate the promise, it makes the promise plausible by adding the piece the headline had to leave out. That piece is usually the mechanism, meaning how the result is produced, the qualifier naming who it applies to, or the cost in time and effort. Set in smaller, lighter type, it reads as explanation rather than as a second competing claim.
The line works better the more it removes rather than adds. Naming the number of questions, the minutes required, or the fact that no payment details are needed lowers perceived risk at the moment the reader is deciding. What weakens it is overlap: every word repeated from the headline is spent for nothing, and a second line written in the same register forces the eye to read two claims and choose between them. Length is the practical ceiling.
Teams draft the subheadline immediately after the headline is fixed, then check the pair by reading the two aloud in sequence. If the second line could be deleted with nothing lost, it is not doing any work and should be rewritten. On a scorecard funnel page it usually carries the format and the payoff: how many questions, how long they take, and what the result page returns, so the visitor understands the trade before clicking rather than discovering it mid-quiz.
Not every page needs one. When the headline is already complete and the offer is familiar, a subheadline adds a line the reader must process for no gain. It also cannot rescue a headline that failed, because a reader who rejected the first line never reaches the second. On pages where a visual carries the explanation, such as a screenshot showing the product in use, the supporting line often duplicates what the image already said.
Example in practice
How to measure it
Because the subheadline rarely moves a metric alone, test it as part of the pair. Hold the headline constant and vary only the second line, then read the click rate on the primary action. If the rate moves, the added specifics were doing real work. If nothing moves across several genuinely different variants, the friction sits somewhere else on the page.
Attention data helps more here than conversion data. Session recordings show whether the second line is read at all, and a subheadline that is consistently skipped is usually too long or too close in wording to the line above. Watch completion as well: if starts stay flat but drop-off falls, the line set expectations more accurately than before.
Common mistakes
The usual failure is paraphrase: the headline promises a result and the subheadline says the same thing in longer words. The reader gains no information and the eye slows for nothing. Test it by deleting the line. If the page loses nothing, rewrite it to add one of the three things a headline cannot carry: the mechanism, the audience qualifier, or the effort the visitor is being asked for.
The second is treating the subheadline as an overflow area for everything that did not fit, which produces a paragraph in smaller type. At that size and position it will be skimmed rather than read, so a long block simply pushes the button further down the screen. Keep it to one or two lines, put a single idea in it, and move remaining detail into the section that follows.
Frequently asked questions
How is a subheadline different from benefit bullets?
A subheadline is one continuous sentence that supports the headline, while benefit bullets are a scannable list of separate advantages. The subheadline frames the offer, the bullets enumerate its payoffs.
What should a subheadline actually say?
One of three things the headline could not fit: how the result is produced, who it applies to, or what it costs in time and effort. Choose whichever is the largest open question after the headline. Covering all three produces a paragraph that gets skimmed, and the reader takes nothing precise away from any of them.
Does every landing page need a subheadline?
No. When the headline is already specific and the audience knows the category, a second line adds processing work without adding information. Subheadlines earn their place when the offer is unfamiliar, when the headline had to drop an important qualifier, or when the visitor needs reassurance about effort before committing to a first click.
How long should a subheadline be?
One or two lines at mobile width, generally under about twenty-five words. It sits in smaller type in a position readers skim, so length works directly against it. If the idea does not fit, the leftover material belongs in the section below the hero, where it has room and the reader has already decided to keep going.
Should the subheadline repeat keywords for SEO?
It can carry a natural variant of the target phrase, but stuffing it damages the one thing it exists to do. Heading structure and body content handle most of the search work; the subheadline's job is persuasion at the moment of decision. A line that reads as written for a crawler undermines the credibility the headline just built.
How is a subheadline different from a tagline?
A tagline is a brand-level line, stable across pages and campaigns, saying what the company stands for. A subheadline is page-level, changes with the offer and the traffic source, and supports one specific claim. Putting a tagline in the subheadline position wastes the slot, since brand statements rarely answer the visitor's open question.
Where should the subheadline sit relative to the button?
Directly between the headline and the primary action, so the reading path runs claim, support, act with no detour. Placing it below the button breaks the sequence, because the reader meets the decision before the reassurance that would make it easy. Any further detail belongs after the button, where it catches the people who need more.