TL;DR: The best AI prompts for landing page copy are not one universal template. A SaaS trial page, a webinar registration page, and a local service page ask the reader to do completely different things, so the hero, objections, and CTA need different prompts. Below are 30, organized by eight page types, not by section.
What are the best AI prompts for landing page copy?
The best AI prompts for landing page copy name the specific page type before they name anything else, because the reader's decision is different on every one. A prompt template written for a SaaS free trial page will produce good copy for a SaaS free trial page and mediocre copy for a webinar page, even with the same product and the same model, because the two pages are answering different questions. Trial pages answer "what happens if I try this." Webinar pages answer "why do I need to be there, live, on this exact date." Waitlist pages answer a question nobody enjoys answering: "why should I wait, with no promise of when."
The free landing page copy prompt generator covers this for one page at a time: an input sheet plus nine section prompts running hero through FAQ. This post assumes that structure exists and adds the layer underneath it, which sections carry the real risk on which kind of page, and a working prompt for each, organized by eight page types instead of by section. If you want the channel-based version instead, matching prompts across email subject lines, ad copy, and landing pages, 45 AI prompts for email, ads and landing pages covers that ground. This post stays inside the landing page and organizes by who is landing on it.
Fill in every [bracketed] field before you run anything below. An empty field does not produce a blank space in the output, it produces a guess, and the guess is always the category average. That average is the reason a generic "write me landing page copy" prompt reads fine on a screen and converts nowhere: it has no page type to be specific about, so it writes toward whichever page type appears most often in its training data, which tends to be a SaaS product page whether or not that is what you are building.
How does landing page copy differ by page type?
Nine sections show up on nearly every landing page: hero, subhead, problem, mechanism, proof, objections, offer, CTA, and FAQ. What changes by page type is which of those nine is doing the real work, and what a wrong answer there actually costs you.
A SaaS trial page lives or dies on the objection about being charged without warning, and on the CTA microcopy sitting under the button. A webinar page lives or dies on the hero, because someone deciding whether to block 45 minutes on a specific Thursday needs the date and the payoff in the first line, not the third paragraph. A waitlist page has almost no proof section to write, since the product does not fully exist yet, so the whole page has to work through the hero and a "what happens after you join" section instead.
Here is the same nine-section skeleton, mapped to the actual friction point on eight common page types:
| Page type | What the reader is really deciding | Section carrying the most risk |
|---|---|---|
| SaaS free trial | Will this cost me money I didn't agree to | Objections + CTA microcopy |
| Lead magnet / opt-in | Is my email worth this PDF | Value-exchange line + objection |
| Webinar registration | Can I justify blocking this exact hour | Hero (date, payoff) |
| Waitlist / early access | Why wait, with no date and no guarantee | "What happens next" section |
| Ecommerce product | Will this specific item do the specific job | Proof + returns objection |
| Local service | Can I trust a stranger with my home or health | Proof (credentials, area) |
| Online course | Will I actually finish this one | Curriculum mechanism + objection |
| Consultation booking | Is this a sales call wearing a different shirt | "What happens on the call" |
The prompts below are grouped by page type for that reason. Most give you three or four sections rather than all nine, because those are the sections where a generic prompt produces a page that is simply wrong for the reader, not just slightly bland.
What AI prompts write copy for a SaaS free trial landing page?
A trial page sells an action, not a purchase, and the reader already knows the real question is what happens after the trial ends. Skip that question and the page reads like every other SaaS hero: a broad promise, a feature grid, and a "Start Free Trial" button that says nothing about the card sitting behind it. Unlike almost every other page type below, a trial page also has to survive a second reading, on the day the trial actually ends, so the copy you write today is answering a question the reader will ask again in two weeks.
1. Hero and subhead for a trial page
Product: [name, one sentence on what it does].
ICP: [role, company size].
Trial length: [X days]. Card required: [yes / no].
Write 8 hero headlines, 10 words or fewer, that promise the action of
trying it, not the state of having transformed. Do not write "start
your free trial today" as one of them; every reader has read that
sentence already.
For the top 3, add a subhead (18 words max) stating what the reader can
do in the first session, not what the product generally does.
If a card is required, at least one headline-and-subhead pair must
acknowledge that directly rather than leaving it for the button.
2. What happens when the trial ends
Trial length: [X days]. What happens at day [X+1]: [auto-charges the
card / downgrades to a free plan / requires a manual upgrade].
Write a 60-90 word section titled "What happens on day [X+1]."
State the mechanism plainly: does the card get charged automatically,
does access simply stop, or does the account downgrade to a free tier.
Do not write "no strings attached" unless a card is genuinely not
required. End with one sentence on how to cancel, if cancellation is
relevant.
3. Objection: the billing fear
Card required: [yes / no]. Cancellation method: [in-app / email
support / self-serve].
Write a 45-60 word answer to: "Will I be charged without warning?"
Sentence one restates the fear precisely. Then state the actual policy:
when the card is charged, how much notice is given, and how to cancel.
If the honest answer includes real friction, for example cancellation
requires emailing support, say so rather than implying it is one click.
4. CTA and button microcopy
Trial length: [X days]. Card required: [yes / no]. Onboarding time:
[roughly X minutes].
Write 6 button labels, 4 words or fewer, for the trial CTA.
Under each, one line of microcopy (10 words max) answering whichever of
these the reader is most likely wondering: card required, setup time,
or what happens after the trial.
Include "Start Free Trial" once as a baseline, then 5 more specific
alternatives.
If you are the founder writing this page yourself, between everything else you run in a week, the founder AI workflow covers reusing prompts like these across the other documents a solo founder is also writing that same week.
What AI prompts write copy for a lead magnet or opt-in page?
A lead magnet page has the cheapest offer on this list and the highest suspicion attached to it. The reader is not deciding whether to buy, they are deciding whether the free thing behind the form is worth what arrives after they hand over an email address. Because the price of admission is an inbox rather than a card, the copy has to do more reassurance work per word than any page type with an actual dollar figure on it.
5. Hero for a lead magnet page
Lead magnet: [name, format: checklist / template / PDF guide].
Outcome after using it: [specific result, not "learn about X"].
ICP: [describe].
Write 8 hero headlines naming the outcome of using the magnet, not the
format of the magnet. "Checklist" and "template" belong in the subhead
or the visual, not the headline.
For the top 3, add a subhead (15 words max) naming who this is for.
6. The value-exchange line
What we send after signup: [the magnet only / the magnet plus a
nurture sequence, N emails over N days].
Unsubscribe policy: [one line].
Write one sentence, placed directly under the form, stating exactly
what arrives in the reader's inbox and how often. No euphemisms like
"occasional updates." If a nurture sequence follows the magnet, say how
many emails and over what period.
7. Objection: what's the catch
Magnet: [name]. Sign-up field: [email only / email + role].
Write a 40-60 word answer to: "What's the catch?"
State plainly: no card required if true, what data is collected and
why, field by field, and how to leave the list.
Do not write "we respect your privacy" without the next sentence
explaining what that means in practice.
8. CTA and form microcopy
Fields on the form: [list them, e.g. email only].
Write 5 button labels naming the outcome, not the action, "Send me the
checklist" over "Submit." Under each, one line of microcopy addressing
the thing a reader hesitates on when the ask is just an email: what's
the catch, and how often will you email me.
What AI prompts write copy for a webinar registration page?
A webinar page asks for the most expensive thing on this list: a fixed slot of someone's calendar, live, on a date they do not control. The hero has to earn that in one line, and the objections have to answer the reader who is already planning to just watch the replay. This is also the only page type here that needs copy for after the click, the confirmation and reminder messages, because the conversion you actually care about happens days later, not at the moment of registering.
9. Hero naming date, payoff, and stakes
Webinar topic: [one sentence]. Date and time: [exact, with timezone].
What attendees leave with: [specific: a template, an answer, a skill
demonstrated live].
Write 6 hero headlines that include the payoff and imply the live date
without necessarily stating it verbatim in every one.
For the top 3, add a subhead stating the date, time, and timezone in
full, plus one sentence on what makes attending live different from
watching a recording.
10. Why live matters (the replay objection)
What happens live that does not happen in the replay: [live Q&A / a
tool demoed in real time / an offer announced only during the session].
Write a 50-70 word section answering: "Can I just watch the replay
later?"
Give the honest answer. If a replay will genuinely be sent to everyone
who registers, say so; do not manufacture urgency that isn't real.
State what is specifically different about attending live.
11. Confirmation and reminder microcopy
Event: [name]. Time until event: [days].
Write 3 short blocks: an on-page confirmation message shown immediately
after registering, a reminder email subject line for 24 hours before,
and one for 1 hour before.
Each includes the exact date, time, and timezone, plus one line on what
to have ready, nothing, or a specific tool or account.
12. Registration CTA
Cost: [free / paid, price]. Replay included: [yes / no].
Write 5 button labels, 4 words or fewer, for the registration CTA.
Under each, microcopy addressing cost, if not obviously free, and
replay availability, whichever removes more friction for this specific
webinar.
What AI prompts write copy for a waitlist or early-access page?
A waitlist page has almost nothing to prove, because the thing being sold does not fully exist yet. The whole page has to work through what joining actually gets someone and what happens next, since there is no product screenshot or review to lean on. That absence of proof is also why this page type attracts the most fabricated numbers of any on this list, and why the prompt below spends a paragraph on that specifically.
13. Hero for a waitlist page
Product: [one sentence on what it will do]. Current status: [in
private beta / building / X people testing].
Write 8 hero headlines. Name what joining gets the reader, early
pricing, first access, input into what gets built, rather than a vague
"coming soon."
Do not state a number of people already on the list unless you can
supply the real, current figure. Leave [ACTUAL COUNT] as a placeholder
rather than inventing one.
14. What happens after you join
What joining actually gets someone: [early access by a date / priority
in launch order / a discount locked in / a say in what gets built].
Timeline, if known: [specific date, or "no fixed date, updates every X
weeks"].
Write a 60-90 word section titled "What happens after you join."
State the mechanism: what email arrives immediately, what arrives at
launch, and whether position on the list matters.
If there is genuinely no fixed timeline, say that directly rather than
implying one exists.
15. Join CTA and reassurance
Data collected: [email only / email + use-case question].
Write 5 button labels for joining a waitlist, avoid "Sign Up" alone.
Under each, one line addressing what happens to this email if the
reader never hears back, and whether they can leave the list.
What AI prompts write copy for an ecommerce product page?
A product page is the only page type here selling something the reader can return, which changes what the proof section has to do. It also works at the item level, not the category level, so the hero cannot promise a transformation, it has to promise what this specific thing does. Reviews and specs also make ecommerce the page type most tempting to pad with invented numbers, a rating that sounds plausible, a "trusted by thousands" line nobody can check, so the prompts below constrain the model to only the reviews and specs you actually supply.
16. Product hero at the item level
Product: [specific name, not category]. Core use case: [one concrete
scenario, e.g. "for standing 8-hour warehouse shifts," not "for
comfort"].
Write 8 hero headlines naming the specific scenario the product solves,
not a generic category benefit. Ban "premium," "quality," and "comfort"
unless followed immediately by what that means physically.
17. Spec-to-benefit table
Specs: [list 4-6 raw specs, e.g. material, weight, dimensions,
certification].
For each spec, write the one-line consequence for the buyer, in plain
language a non-expert would recognize. Format as a two-column table:
Spec | What it means for you.
Do not add a consequence for a spec that has no real one. Write
"informational only" instead of inventing a benefit.
18. Shipping and returns objection
Shipping time: [X days, region]. Return window: [X days]. Return cost:
[free / buyer pays].
Write a 50-70 word section covering shipping and returns as one block,
using the real numbers only.
State the return cost plainly, even if the buyer pays it. A vague
return policy costs more trust at checkout than an honest, unflattering
one.
19. Review-based proof section
Reviews available: [paste 3-5 real reviews verbatim, with star ratings
if shown].
Using only the pasted reviews, select and lightly trim 3 for the page.
Each: the specific detail the reviewer mentioned, trimmed to 40-60
words, with star rating if available.
Do not write a new review, combine two reviews into one, or add a
detail the reviewer did not mention.
What AI prompts write copy for a local service business page?
A plumber's landing page and a dentist's landing page sell trust before they sell anything else, because the reader is about to let a stranger into their home or their mouth. The hero has to be hyperlocal, and the proof section does work no other page type on this list asks of it. Most local service pages fail on genericness rather than dishonesty: a template that never names the neighborhood or the license reads like it was copied from a franchise playbook, which is close to what actually happened.
20. Hyperlocal hero
Service: [specific service, e.g. "emergency drain unblocking," not
"plumbing services"]. Service area: [specific towns or neighborhoods,
not just a city name]. Response time, if relevant: [e.g. "same day,"
"within 2 hours"].
Write 8 hero headlines naming the specific service and the area
together. If response time is a genuine differentiator, include it in
at least 3.
21. Credentials and trust section
Real credentials: [license number/type, insurance status, years
serving this area, professional body membership, only what is true and
checkable].
Write a 50-70 word trust section using only the credentials supplied.
Do not add "fully licensed and insured" unless a license type or number
is given. Do not invent a number of years served or jobs completed.
22. Pricing transparency objection
Pricing model: [flat rate / hourly plus callout fee / free quote before
work starts].
Write a 45-60 word answer to: "Will I get a surprise bill?"
State the actual pricing model plainly, including the callout fee if
one exists. If the real answer is "it depends on what we find," say
that, and state how the reader learns the price before work starts.
23. Call-first CTA
Phone number: [number]. Booking option: [phone only / phone + online
form].
Write 4 CTA blocks recognizing this audience often prefers calling: a
primary "Call now" button with the number visible, and, if online
booking exists, a secondary option with one line on what happens after
the form is submitted.
What AI prompts write copy for an online course or cohort page?
A course page competes with every course the reader already paid for and never finished, so the objection almost writes itself, and the curriculum section needs to read like a schedule, not a list of topics. Feature-style bullets are the fastest way to lose this reader, since a list of module names looks identical to the eleven other courses they abandoned, and only a concrete schedule signals that finishing is actually plausible this time.
24. Hero with a realistic timeframe
Course topic: [one sentence]. Format: [self-paced / cohort with a
start date]. Time commitment: [hours per week, weeks total].
Write 8 hero headlines naming the specific transformation and the real
time commitment together. Do not hide the time commitment for a
punchier headline.
25. Curriculum as a schedule, not a feature list
Modules: [list module names and, for each, the one thing a student can
do after it that they couldn't before].
Write the curriculum section as a numbered, week-by-week schedule, not
bullet features. For each week: what happens, and the one new
capability gained.
Do not describe a module as "an overview of X." State what the student
produces or can now do.
26. The "I never finish courses" objection
Completion structure: [deadlines / accountability check-ins / cohort
peer pressure / none, fully self-paced].
Write a 50-70 word answer to: "I've bought courses before and never
finished them."
Concede the pattern is real before answering it. State the specific
structural thing, not motivation, that makes this different, if one
exists. If the course is genuinely self-paced with no structure, say
that plainly rather than promising something you don't have.
27. Enrollment CTA with guarantee and payment terms
Price: [amount]. Payment plan: [yes / no, terms]. Guarantee: [refund
window, or "none"].
Write 5 button labels for enrollment. Under each, one line stating
price, payment plan if one exists, and the guarantee terms exactly. No
"risk-free" language unless a specific refund window is named.
What AI prompts write copy for a consultation or discovery call page?
This is the highest-friction ask on the list: a live conversation with a person who might try to sell them something. The page has one job before any other, answer whether this is a sales call in disguise, honestly, before the reader books. Where a product page or a course page can let proof do the reassuring, a booking page has no artifact to point at yet, so the reassurance has to live in a plain description of the 30 minutes itself.
28. Hero and subhead for a booking page
Who this is for: [describe]. What they get from the call regardless of
whether they buy: [a specific deliverable, an audit, a plan, an answer
to one question].
Write 8 hero headlines naming what the reader walks away with from the
call itself, not what they get if they become a client.
For the top 3, add a subhead (18 words max) stating call length and
format.
29. What happens on the call
Call length: [X minutes]. Structure: [e.g. "10 min on your current
setup, 15 min on options, 5 min on next steps if it's a fit"].
Is there a pitch: [yes, at the end / no, separate call if interested].
Write a 60-90 word section titled "What happens on this call," laying
out the actual structure minute by minute.
State plainly whether there is a sales pitch and when, rather than
letting the reader assume either way.
30. Booking CTA and logistics
Duration: [X minutes]. Time zones supported: [describe]. What to
bring: [nothing / one specific thing].
Write 4 button labels for booking a call. Under each, one line covering
duration and what, if anything, to prepare, so the reader is not
surprised by either.
How do you keep 30 prompts consistent across 8 page types?
Look back across the 30 prompts above and the repeats are obvious: ICP, voice, and the real top objection show up in nearly every one, while only the page-specific fields, trial length, webinar date, return window, actually change from page to page. Retyping the stable half for every new page type is the same problem reusable prompt variables for dev teams describes for engineering teams, solved the same way: keep what doesn't change per page type in a saved context, and keep only the page-specific fields in the prompt itself.
Once a prompt above gives you a winning headline or button label, test it against whatever is live today rather than trusting it on the strength of reading well. A/B test your prompts covers the method for keeping variants straight once you have a dozen headlines competing for one slot.
Prompt Architects is the tool we build, so treat this next paragraph as a disclosure rather than a pitch. Global Variables hold your ICP, voice, and top objection once so they resolve into whichever of the 30 prompts above you run next. The Prompt Library keeps all 30 saved and versioned in one place. Team Sharing means a founder writing the trial page and a contractor writing the local-service page are pulling from the same ICP line instead of two separate guesses at it. There is a free plan, and paid plans start at $4.99 per month at the time of writing (current pricing).
What we don't do is generate or host the page itself. If you need software that builds and publishes it, that's a page builder or a dedicated copywriting tool, and this post isn't a comparison of those. We handle the layer underneath: the 30 prompts above, saved somewhere they survive past this browser tab.
Stop rewriting prompts. Start shipping.
Works with ChatGPT, Claude, Gemini, Grok, Midjourney, Ideogram, Veo3 & Kling. 5.0★ on the Chrome Web Store.
Create An Account