How to Write a Subheadline That Earns the Scroll

The most underrated sentence on any homepage is the second one. The headline gets all the attention, in meetings and in essays like the ones I write, and the subheadline gets written in the last five minutes before launch. This is backwards. The headline is a few words and can only do one thing: make a claim compressed enough to read at a glance. The subheadline is a full sentence, sometimes two, and it’s the first real writing a visitor encounters. It’s where the page stops shouting and starts talking. Whether the visitor scrolls is largely decided right there.

To write a good one you have to know its job, and its job is defined by what the headline left undone. A headline compresses, and compression loses information. “Bookkeeping without the busywork” is a decent headline, but it leaves open who it’s for, how it works, and whether “without the busywork” is a poetic exaggeration or a literal description. The subheadline is where you pay that debt. “Connect your bank account and we categorize every transaction automatically; you review ten minutes a month instead of an evening a week.” Now the poetic claim has mechanics under it. The reader can picture the thing. Headline makes the promise, subheadline makes it believable. That’s the division of labor, and once you see it you can diagnose almost every bad subheadline as a violation of it.

The most common violation is the echo. The headline says “Ship faster,” and the subheadline says “Accelerate your development velocity and reduce time to market.” That’s the same claim in worse clothes. The visitor has now read two sentences and learned one thing, and the subheadline, the best-positioned sentence on the page, transmitted zero new information. If your subheadline could be deleted without a stranger losing anything, it’s an echo, and the test is exactly that: delete it, and ask what a stranger no longer knows.

The second violation is the swerve, where the subheadline answers a question nobody has yet. The headline announces what the product is, and the subheadline immediately says “SOC 2 compliant with 24/7 support and flexible pricing tiers.” Those facts matter, but they’re objections from the middle of a decision, and the visitor is at the beginning of one. They’re still asking “what is this and is it for me?” and the page is answering “here are our certifications.” Sequencing is part of clarity. The right information in the wrong order reads like the wrong information.

The third violation is the mission statement, where the subheadline retreats to values. “We believe every business deserves financial clarity.” Beliefs are fine, but a stranger can’t use them. They can’t picture your beliefs, evaluate them, or distinguish them from any other company’s, because every company believes its customers deserve good things. The subheadline slot is too valuable to spend on statements the reader can’t act on.

So what does the working version look like? My method is to write the headline first, then interrogate it as a skeptical stranger would, and make the subheadline the answer to the loudest question. If the headline is abstract, the loudest question is “concretely, what is it?” and the subheadline should be mechanical: what it does, for whom, roughly how. If the headline is concrete, “Inventory software for auto parts stores”, the loudest question becomes “why this one?” and the subheadline should carry the differentiator: what it does that the incumbent doesn’t, or what pain it removes. The headline and subheadline are a pair, and the subheadline’s content isn’t fixed; it’s whatever the headline made most urgent to say next.

A few craft rules I’ve settled on. Use a number if you honestly have one, because numbers are the fastest way to convert a claim into a picture, and one real number outweighs three adjectives. Name the reader if you can, because “for one-person shops” does more filtering work than a paragraph of positioning. Keep it under about twenty-five words, not because of any law, but because past that length it stops being read as a subtitle and starts being read as a paragraph, and paragraphs get skipped by people who haven’t yet decided to read. And write it last, after the rest of the page exists, because the subheadline is a summary of your best material, and you can’t summarize material you haven’t written.

I’ll admit why I care about this particular sentence so much. When I audit sites with GazeSite, the subheadline is where the diagnosis usually happens. Headlines fail in a handful of predictable ways, but subheadlines fail in ways that reveal what the company itself doesn’t know: an echo means they have one idea and are stretching it; a swerve means they don’t know what order their buyers think in; a mission statement means they haven’t yet figured out what’s concretely different about what they’ve built. The sentence is small but the confusion it exposes is not. Which is also the encouraging part. Fixing a subheadline takes an hour, and it forces exactly the thinking, who is this for, what does it actually do, why this one, that improves everything else you’ll ever write about the product. The scroll is earned one sentence at a time, and this is the sentence that does most of the earning.