"AI-powered survey platform with 50+ integrations" describes what the product is. "Get answers from real buyers in 24 hours" describes what the buyer experiences. These are not the same statement. One leads with engineering capability; the other leads with buyer outcome. Visitors scan landing pages to answer one question: what changes for me if I use this? Feature-led headlines make them work to find the answer. Benefit-led headlines hand it to them. This is the long version of PageLint check VA-6: Benefit-led, not feature-led headlines.
What Ogilvy actually prescribed
Ogilvy was specific about this in Ogilvy on Advertising (1983): the headline must promise a benefit to the reader.
The headline is the most important element in most advertisements. It is the telegram which decides whether the reader will read the copy. On the average, five times as many people read the headline as read the body copy.
The operative word in Ogilvy's framing is "telegram" — a compressed message that must stand alone. A telegram about features tells the recipient what the product has. A telegram about benefits tells the recipient what they get. The reader's interest is in themselves, not in the product's architecture.
Ogilvy's prescription in the same chapter: "Your headline should telegraph what you want to say — and say it in simple language." The "what you want to say" is always the benefit. Not the mechanism that produces it.
Features vs benefits — the actual distinction
A feature is a property of the product. A benefit is a change in the buyer's world.
Features: 50+ integrations, AI-powered, real-time sync, drag-and-drop editor, SSO support, 99.9% uptime SLA.
Benefits: invoices paid 11 days faster, no more chasing clients for payment, audit results in 30 seconds, find the exact line losing you conversions.
The distinction matters because buyers don't buy features. They buy changes in their situation. A "50+ integrations" headline requires the visitor to infer: integration with what? For what purpose? Saving me how much time? The buyer's brain has to do the translation work that the copywriter failed to do.
Visitors scan to answer one question: what changes for me? Feature headlines make them work for it.
Why features appear in headlines anyway
Three reasons features dominate SaaS landing pages:
1. Engineers write or approve the copy. Features are concrete, verifiable, and defensible. "50+ integrations" is a fact. "Get answers in 24 hours" requires evidence. Features feel honest; benefits feel like marketing.
2. Benefits are harder to write specifically. "Faster" is a benefit but a weak one. "11 days faster invoice payment" is a benefit with enough specificity to be persuasive. The work of finding the specific benefit is harder than listing features.
3. Competitive anxiety. Founders list features because they're worried about objections — "does it have X integration?" — before the visitor has decided they want the product. This answers a later question before answering the first one.
The rewrite formula
The formula: [specific role] [specific action] [specific outcome] [specific timeframe or condition]
Not all four components are always needed. But the more specifics present, the stronger the headline.
The "so what?" test
Every feature headline can be tested with the "so what?" question. "AI-powered survey platform." So what? "You get faster responses." So what? "You make decisions in days instead of weeks." So what? "Your product ships with evidence instead of assumptions."
The last answer is usually the headline. Writers stop too early — at the feature or the immediate benefit — and don't follow the chain to the outcome the buyer actually cares about.
When feature copy is appropriate
Features work in a specific context: the visitor already knows they want the product and is now evaluating capabilities. This is product-aware traffic (Schwartz's fourth state). For these visitors — comparison shoppers, people evaluating specific integrations — feature copy is the right language.
The error is using feature copy for awareness-stage traffic — visitors who are still deciding whether they need this category of product at all. Those visitors need benefit framing to translate the features into outcomes they care about.
On a landing page designed for paid or SEO traffic, the audience is typically problem-aware or solution-aware, not product-aware. Benefit framing is correct for this traffic.
How PageLint detects this
VA-6 is an LLM check. The engine evaluates the H1 and subhead against a two-part test:
-
Outcome presence: Does the headline describe a change in the buyer's world? Words like "get", "save", "find", "stop", "close", "ship" signal outcomes. Words that describe product properties (AI-powered, automated, intelligent, next-generation) signal features.
-
Specificity level: A benefit without specificity ("faster", "better", "easier") is scored lower than a benefit with specificity ("11 days faster", "close 23% more deals", "ship in 30 seconds").
A headline that names a specific outcome scores High confidence pass. A headline that names only features scores fail. A headline with a generic benefit ("better results") scores Low confidence warning.
Severity: Critical. This check runs on the H1, which Ogilvy established carries 80% of the advertising value. A feature-led H1 is the most expensive single copy error on a page.
Sources cited
Primary:
- Ogilvy, David. Ogilvy on Advertising. Crown Publishers, 1983. Ch. 7: "How to write potent copy."
- Ogilvy, David. Confessions of an Advertising Man. Atheneum, 1963. Ch. VI.
Secondary:
- CXL Institute. Benefit vs feature headline testing. Peep Laja public writing on clarity > persuasion.
- Hopkins, Claude. Scientific Advertising. Lord & Thomas, 1923. Ch. 6: "Being Specific." (foundational source Ogilvy cites for specificity prescription)