Write conversion-focused landing page copy for [OFFER] aimed at [TARGET AUDIENCE]. The visitor should take this primary action: [PRIMARY CTA]. Use these verified details, proof, constraints, and required claims: [SOURCE MATERIAL]. The acquisition context and page constraints are: [TRAFFIC CONTEXT]. First identify the visitor’s likely situation, desired outcome, current alternative, and the main reason they may hesitate. Do not write these as generic personas; use them to make specific copy choices. Return a complete page wireframe with copy in this order: 1. Hero: a one-line outcome-led headline, supporting subhead, CTA label, and a short anxiety-reducing microcopy line. 2. Problem and cost of the current approach: 2–4 concrete points that a visitor would recognize. 3. How it works: three steps, each describing the customer’s action and resulting outcome. 4. Benefits: 3–5 benefits tied to a practical consequence, not feature labels. 5. Proof: use only supplied testimonials, numbers, customer names, certifications, or case-study facts. If proof is thin, write a clearly marked proof gap instead of making claims. 6. Objection handling: address the three most likely objections, including implementation effort, price or risk, and fit. 7. Offer details: what is included, exclusions or limits, pricing only if provided, and CTA. 8. Closing section with a distinct final headline and CTA. Keep the page between 700 and 1,000 words unless the traffic context requires less. Match the vocabulary of the target audience, avoid unsupported superlatives, and do not invent testimonials, results, urgency, integrations, or guarantees. Before answering, check that every major section moves toward one CTA and that every factual claim is traceable to my source material. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [OFFER] | Describe the product, service, promotion, or lead magnet and what the customer receives. | A 14-day trial of LedgerLoop, software that collects client receipts and categorizes expenses for small accounting firms. |
| [TARGET AUDIENCE] | Describe the visitor’s role, situation, problem, and level of awareness. | Owners of US accounting firms with 3–15 staff who spend hours chasing clients for receipts before month-end close. |
| [PRIMARY CTA] | State the one desired conversion action, such as start a trial, request a demo, or download a guide. | Start a 14-day trial |
| [SOURCE MATERIAL] | Provide verified features, prices, customer evidence, differentiators, claims, and legal or brand constraints. | Clients upload by text or email; accountants can set recurring requests; the product exports CSV files. Trial needs no card. Plans start at $149 monthly. A beta customer reduced receipt-follow-up emails from 75 to 28 monthly. Do not claim tax compliance or QuickBooks integration. |
| [TRAFFIC CONTEXT] | State where visitors come from, device or page limits, campaign message, and any secondary audience. | Traffic comes from a Google Search campaign for “client receipt collection software”; mobile is important; visitors may compare it with email reminders and shared folders. |
How to use
- Paste verified product information, including limits and proof, before asking for copy.
- Make the CTA a single action; do not ask the first-screen visitor to both book a demo and download a guide.
- Check every metric, customer statement, integration, and guarantee against your source material.
- Follow up with: “Create two alternative hero sections for visitors who currently use shared folders and email reminders.”
Variations
Waitlist page
Use this before launch to test demand without implying the product is already available.
Write a 450–650 word waitlist landing page for [UPCOMING PRODUCT] for [AUDIENCE]. The action is [CTA], and the verified product concept, expected timing, and limits are [FACTS]. Structure it as hero, problem, proposed solution, what early access includes, who it is for and not for, FAQ, and final CTA. Be explicit about what is not built or confirmed. Do not invent launch dates, customer counts, testimonials, or scarcity. Include three signup questions that help qualify demand without making the form burdensome. Before answering, check that the page does not present a concept as a finished product. Ask up to 3 questions only if required inputs are missing.
B2B demo page
Use this for a higher-consideration product where a prospect should request a sales conversation.
Draft a B2B demo-request landing page for [PRODUCT] aimed at [BUYER ROLE] in [INDUSTRY]. The desired action is [CTA]. Use only these verified features, implementation details, outcomes, and proof points: [EVIDENCE]. Produce 700–900 words with a hero, costly workflow problem, product workflow, role-specific outcomes, evidence, implementation expectations, objection handling, and form microcopy. Address security, integrations, pricing, or procurement only to the extent supported by the evidence. Do not use fabricated ROI, logos, testimonials, or compliance claims. Flag missing proof that a buyer will expect. Ask up to 3 questions only when inputs are missing.
Sales page
Use this when visitors can buy a clear product directly from the page.
Write a 900–1,200 word direct-purchase sales page for [PRODUCT] sold to [CUSTOMER]. Price, contents, delivery method, refund terms, and verified outcomes are [OFFER DETAILS]. The purchase action is [CTA]. Use a message sequence of desired result, current frustration, mechanism, what is included, who it fits, proof, objections, price framing, and final CTA. State limitations honestly, especially what the buyer must do themselves. Do not create testimonials, urgency deadlines, bonuses, or guarantees not in the offer details. Before answering, check that the price and terms appear before the final CTA and all promises are supported. Ask up to 3 questions only if required information is absent.
Tips
- Match the hero promise to the ad, email, or search query that brought the visitor there; a broad homepage headline often creates message mismatch.
- Place proof close to the claim it supports. A customer result at the bottom cannot credibly support an unsupported performance claim in the hero.
- If the offer requires implementation, explain the first customer action and time commitment before the CTA; hiding effort usually lowers downstream conversion quality.
- For search traffic, name the existing alternative the visitor recognizes, such as spreadsheets, agency retainers, or manual follow-up, rather than describing an abstract problem.
FAQ
Can AI write landing page copy without customer research?
It can structure a page, but its strongest copy needs actual customer language, objections, and proof. Supply sales calls, reviews, surveys, or support patterns when available.
How long should a landing page be?
Length should match the risk and complexity of the conversion. A low-friction download may need a few sections, while a high-cost B2B demo needs more proof and implementation detail.
Should I include pricing on the page?
Include it when transparent pricing helps the qualified buyer act and you have a clear offer. If pricing depends on scope, explain the pricing basis instead of making the visitor guess.