How to Write a High-Converting Headline

June 19, 2026 · 10 min read · How-to

Visitors decide in seconds whether your page is for them. The headline is the highest-leverage copy on a static landing page—no backend A/B framework required to get it right the first time, but you must be specific. This how-to teaches a repeatable process indie hackers use to write headlines that drive waitlist signups and demo clicks, grounded in clarity-first conversion principles rather than vague buzzwords.

Start with the visitor outcome, not your product category

Weak headlines describe what you built ("AI-powered analytics platform"). Strong headlines describe what changes for the reader ("See which feature launches actually drive retention"). Write one sentence completing: After using my product, my customer can ___ without ___. That sentence becomes the raw material for your H1. If you cannot finish it, your positioning is not ready for public traffic.

Use the clarity formula

A reliable static-page pattern is: [Who] + [desired outcome] + [time or friction reducer]. Example: "Indie hackers ship privacy-friendly analytics in ten minutes." Another: "Turn Figma comments into Jira tasks without copying screenshots." Avoid stacking three adjectives. One concrete verb beats "innovative, seamless, cutting-edge."

Match the headline to traffic temperature

Cold traffic from social ads needs more context in the subheadline because the H1 cannot carry every detail. Warm traffic from your newsletter can use insider language and shorter H1s. Search traffic should mirror intent keywords naturally—"static site deployment checklist" belongs in an H1 for that query, not "Launch faster than ever." Align hero copy with the meta title tag for SEO, but do not duplicate them word-for-word.

Add proof without cluttering the H1

Social proof rarely belongs inside the H1 itself; it works better directly beneath as a one-line eyebrow or microcopy. Examples: "Trusted by 2,400 Shopify merchants" or "Built by ex-Stripe billing engineers." Only use numbers you can substantiate. Pre-launch? Replace vanity metrics with process proof: "No account required to try the demo" or "Open-source template—MIT licensed."

Draft five variants before you pick one

Open a blank document and write five H1 options using different angles: outcome, pain removal, speed, risk reversal, and audience call-out. Read them aloud. The winner should be understandable to a smart friend outside your industry. If you need to explain the H1 verbally for more than one sentence, simplify. Screenshot all five for later testing—even manual weekly swaps on a static page teach something.

<!-- Hero structure in static HTML -->
<p class="eyebrow">For DevOps teams tired of YAML drift</p>
<h1>Promote config changes with one audited click</h1>
<p class="section-lead">Connect your repo, preview diffs, roll back in seconds—no cluster SSH.</p>

Pair the headline with one obvious action

High-converting headlines set up a single primary CTA. If the H1 promises a waitlist, the button says "Join the waitlist," not "Learn more." Mismatch kills trust. Secondary links can point to docs, but visually subordinate them. On mobile, keep the H1 under roughly 12 words so it does not wrap into a four-line wall.

Edit for scanners and accessibility

Use sentence case for readability. Avoid ALL CAPS except acronyms. Ensure color contrast between H1 and background meets WCAG AA (4.5:1 for body context; large text has slightly looser thresholds). There should be only one h1 per page—supporting lines belong in p or h2. Screen reader users hear the H1 first; make it meaningful without surrounding visual design.

Measure and iterate without fancy tooling

Track waitlist conversion rate = signups / unique visitors for the landing URL. Use Umami or similar with a custom event on the submit button. Change one variable per week—headline, then CTA, then hero image. Keep a changelog in your repo commit messages so you can correlate spikes with copy changes. Even static sites benefit from disciplined iteration.

Examples by page type

For a developer tool, lead with the workflow saved: "Ship Postgres migrations from pull requests." For a newsletter, quantify the promise: "One email each Friday with three bootstrapped revenue teardowns." For a mobile app waitlist, name the platform and benefit: "Offline habit tracking for iOS—no account required in beta." Swap jargon your audience uses daily; indie hackers respond to specificity more than corporate abstraction.

Common mistakes to delete

Delete headlines that are only motivational ("Build the future"), only feature lists ("Dashboards, alerts, API"), or vague superlatives ("The smartest way to…"). Replace them with a who-and-outcome line. If your subheadline repeats the H1, rewrite one of them—the subhead should add mechanism or proof, not paraphrase. Read the pair as a stranger: within five seconds you should know what the product does and who it is for.

Localize without losing clarity

Translating headlines for /de/ or /es/ paths requires more than machine translation. Idioms that convert in English may confuse German B2B buyers. Keep value propositions equivalent, not literal. Pair localized H1s with hreflang tags and canonical rules documented in your SEO guide. Test with a native speaker when spend justifies it—a confused headline costs more than translation fees.

Screenshot your hero before and after headline changes and file them in a /docs/marketing/ folder. Visual history prevents accidental regressions when you A/B test during fast launch weeks.

When in doubt, ask five people in your target audience to paraphrase the headline after a three-second glance. If answers diverge wildly, the copy is still too vague.

Related: SaaS landing template Waitlist conversion tips Set up Umami analytics Waitlist template