Content

Landing Page Hero Copy Prompt — Headline, Subhead, and CTA

Turn product positioning into above-the-fold hero copy: a headline, subheadline, primary and secondary CTA, a trust cue, an objection-handling line, and three alternative headline angles to test.

Open in Markdown Output Builder

Overview

A hero section fails when it describes the company instead of promising the visitor an outcome — and when its claims are invented to sound impressive. This prompt does neither. It takes the product, the audience, the core problem, the positioning, and whatever real proof exists, and returns above-the-fold hero copy: an outcome-led headline, a concrete subheadline, a primary and a secondary CTA, a trust cue, an objection-handling line, and three labelled alternative headline angles ready to test. Every claim traces to the positioning or proof you pasted; anything unsupported is marked [needs evidence] rather than invented — no fabricated testimonials, customer counts, awards, or guarantees. It produces ready-to-place hero copy, not a wireframe, a brand strategy, or a long-form sales page.

How to use this resource

Lead with the outcome

The headline names what the visitor gets, not what the company is — the subhead makes it concrete.
Earn the click twice

A primary CTA for the ready and a secondary for the hesitant, each an action plus its value.
Never invent proof

Trust cues use only real proof; missing proof becomes a [needs evidence] placeholder, not a fabrication.

Why This Works

Outcome-led headlines outperform company descriptions because the visitor reads for themselves, not for you
Labelling three headline angles makes the hero testable instead of a single guess
Marking unsupported claims [needs evidence] keeps the page honest and keeps you out of claims you can't back

Best for

SaaS and product landing pages
Product launch and campaign-specific pages
Service and AI-tool pages that need an above-the-fold hook
Replacing a feature-listing hero with outcome-led copy

Not for

Full page wireframes or layout — this writes copy, not structure
Brand strategy or positioning from scratch — bring the positioning in
Long-form sales pages — this is the above-the-fold hero only
Choosing between two finished variants — that's the Landing Page CTA & Hero Variant Comparison

Use cases

Writing the hero for a SaaS product landing page from its positioning
Generating three testable headline angles for a launch campaign page
Replacing a company-describing hero with an outcome-led one

FAQ

Why does the hero copy come back with [needs evidence] instead of a real trust cue?

The [needs evidence] marker appears in item 5, the TRUST CUE, when your 'known proof or constraints' block was left blank or set to 'none'. Rather than fabricate a testimonial, customer count, or award, the prompt names the proof that belongs there and flags it. Paste a real metric, integration, or named guarantee to fill it.

How are the three alternative headline angles labelled so I can A/B test them?

Item 7 returns three headlines, each tagged by angle — outcome, pain-relief, speed, or cost-of-status-quo — so every variant tests a different hook instead of a reworded near-duplicate. You paste the labelled candidates into your split-testing tool as competing hero headlines; the prompt supplies them, but running the test and picking a winner stays with you.

Which fields do I need to paste before the primary and secondary CTA come out useful?

The 'current positioning / differentiator' block matters most: it shapes the PRIMARY CTA (item 3) into an action-plus-value label like 'Start free', and the SECONDARY CTA (item 4) into a lower-commitment option such as 'See how it works'. Paste a thin positioning line and both buttons read generic; a sharp differentiator gives them something specific to promise.

Customize This Resource

Opens this setup in Markdown Output Builder. Generate to get the full markdown prompt — then adjust the sections, table rules, and consistency level.

Open in Markdown Output Builder

Inputs you need

Have these details ready before you copy or open the template.

Your product or service name and what it does in a sentence
The audience this page targets — their role and what they use today
The core problem or job-to-be-done the product addresses
Your positioning or differentiator versus the alternative
Real proof you can cite (metrics, integrations, guarantees) and any claim the copy must not invent

Prompt Template

Copy it as-is, or use Open in Markdown Output Builder to load it pre-filled and customize it with your own context.

LANDING PAGE HERO COPY

You are writing the above-the-fold hero section for a landing page. Write to the audience and offer given — do not invent product capabilities, customers, numbers, awards, or guarantees that aren't provided. Where a proof point would strengthen a line but you don't have it, mark it [needs evidence] instead of inventing it.

Paste the product or service:
[What it is, in one or two sentences]

Paste the audience:
[Who this page is for — their role, situation, and what they use today]

Paste the core problem:
[The pain or job-to-be-done this product addresses]

Paste the current positioning / differentiator:
[What makes this the right choice over the alternative — or over doing nothing]

Paste known proof or constraints:
[Real proof you can use — metrics, integrations, named guarantees — and any claim you must NOT make. Write "none" if you have none]

Paste the desired tone:
[e.g. confident and plain, technical, warm — plus any banned words]

Return:
1. HERO HEADLINE — one line, under ~10 words, naming the outcome the visitor gets (not a description of the company).
2. SUBHEADLINE — one or two lines that make the headline concrete: who it's for and how the outcome is delivered.
3. PRIMARY CTA — the single most important action as a button label (action + value, e.g. "Start free", not "Submit").
4. SECONDARY CTA — a lower-commitment option for the not-yet-ready (e.g. "See how it works").
5. TRUST CUE — one short above-the-fold reassurance line, using only real proof; if none was provided, return a [needs evidence] placeholder naming the proof that belongs here.
6. OBJECTION-HANDLING LINE — one line that pre-empts the visitor's biggest hesitation.
7. THREE ALTERNATIVE HEADLINE ANGLES — each labelled by its angle (outcome / pain-relief / speed / cost-of-status-quo) so they can be A/B tested.

Rules:
- Lead with the visitor's outcome, not the product's features or the company's story.
- Every claim must trace to the pasted positioning or proof — mark anything unsupported [needs evidence], never invent it.
- No invented testimonials, customer counts, awards, guarantees, or case studies.
- Honor the banned words and tone; cut hype adjectives that carry no information.

More resources from Markdown Output Builder

Resource

Markdown Output Prompt — Lock the Document Structure

The contract that stops AI documents from restructuring themselves: a pinned section skeleton, forced tables, and strict consistency rules.

Prompt Engineering

Resource

README Prompt Template

Overview, Installation, Usage, Examples, Configuration — the README skeleton with required, runnable code examples.

Engineering

Resource

API Documentation Prompt

Overview, Authentication, Endpoints, Error Handling, Rate Limits — endpoint docs in an identical structure, with parameter tables and runnable examples forced.

Engineering

Resources that pair well

Resource

Executive Summary Prompt

Summary, Why It Matters, What Happens Next — the executive summary contract for readers who will never open the source.

Operations

Resource

Force JSON Output from AI

Stop getting 'Sure, here is the JSON…' — the output-contract pattern that forces models to return only parseable JSON: schema, example, and a strict rule block.

Prompt Engineering

Resource

Fix Invalid JSON from AI

The JSON won't parse and you can't see why. Deterministic cause-sniffing — trailing commas, single quotes, unclosed brackets — and the repair prompt that fixes it.

Engineering

Related tools

Tool

Markdown Output Builder

Build prompts that produce documents in a fixed structure — headings, sections, and tables.

Structured Output

Projects that use this resource

Project

Build a Company Website with AI

The full path to a business website that holds together — plan the content, structure the site, design the components, write the page copy, then ship it as one coherent whole.

5 stages Websites

Workflows that use this resource

Workflow

AI Landing Page Copywriting Workflow

Write a landing page that converts, not one that just describes — sharpen the value proposition, draft the hero and benefits, answer objections at the CTA, then A/B the variants to pick the stronger.

4 steps 30–60 minutes

Tip: Save time by exploring related resources and tools that integrate with this resource.