AI builders are brilliant at layout and terrible at words you'd actually publish. The hero says "Innovative solutions for modern businesses," the feature page describes mechanics, and pricing is a grid of "Basic / Pro / Enterprise" with no reason to pick one. Visitors bounce not because the design is bad but because the words are interchangeable with any competitor.
These 25 prompts fix that — one section at a time, each forcing specificity. Use them after you generate the site (any of our build-* prompts) to replace plausible copy with words that earn the next click. All work in ChatGPT, Claude, Gemini, or inside v0/Bolt/Lovable's chat.
Hero and positioning: say what you do in one breath
1. The hero rewrite. Our Homepage Hero Section prompt condenses your whole value into headline + subhead + CTA:
Write a homepage hero for [product] for [audience] where the primary benefit is [benefit]. Need headline (≤8 words), subhead (≤18 words), and CTA button text.
The word limits are the feature. Without them the model writes a paragraph. With them it has to choose — and choosing is where positioning lives.
2. The 3-second test.
Here is my current hero: [hero]. Would a stranger who lands here for 3 seconds know what I do, who it's for, and what to do next? Score 1–10 on each, then rewrite the lowest-scoring line.
Score before rewrite prevents the common trap of polishing words that were solving the wrong job.
3. Comparison page that doesn't trash the competitor. Use Vs. Competitor Comparison Page when you need to win on truth:
Write a fair comparison page for [product] vs [competitors] for [audience]. Win on truth — specific where you're better, honest where you're not.
The honest concession is what earns trust — without it the page reads as marketing, not evaluation.
4. Trust & social proof — evidence, not decoration. Our Trust & Social Proof Section turns scattered quotes and numbers into a real trust block:
Turn these into a trust section for [product] for [audience]: [testimonials, logos, numbers]. Present as evidence, not decoration — numbers with context.
"Trusted by 1,000 users" is decoration. "1,000 teams migrated from [competitor] last quarter, avg setup 8 minutes" is evidence.
Features: outcomes over mechanics
5. Feature page — the outcome constraint. Feature Page Copy forces outcome framing:
Explain [feature] for [product] in terms of the outcome it produces for [audience], not how it works. One headline + 2-sentence paragraph.
Run it per feature. The aggregate reads as a list of results, not a tech spec.
6. The "so what" drill.
Here's my feature description: [text]. For each sentence, ask "so what?" and rewrite the sentence to answer it from the visitor's perspective. Remove any sentence where the answer is "it's technically impressive."
Engineers love mechanics. Buyers love "so I can..."
7. Information architecture check first. Before you write any section copy, run Website Information Architecture Planner:
Plan the IA for [product] for [audience] with goal [goal]. Output page list, nav order, and what each page must prove.
Writing copy for pages that shouldn't exist is wasted work. This prompt tells you which sections deserve copy at all.
8. Empty-state copy that nudges. Use Empty State Copy for the blank screen after signup:
Write empty-state copy for [product] where the user's task is [task]. Turn the blank screen into a nudge with one clear action.
"The blank canvas" is where activation dies. One good nudge there is worth more than another landing page variant.
Pricing and decisions: make comparison easy
9. Pricing page that scans. Pricing Page Copy makes tiers comparable:
Write pricing tiers for [product] for [audience] with offer [offer]. Make the recommended plan obvious and every tier comparable on the same axes.
"Same axes" is the anti-confusion constraint — most pricing pages fail because each tier lists different features.
10. FAQ that removes doubt. Website FAQ Section is input-driven — feed it real objections:
Turn these real objections for [product] from [audience] into an FAQ: [objections]. Remove doubt, don't restate features.
Don't invent "What is X?" FAQs. Use the last 5 support tickets.
11. Comparison as decision tool.
Here is my draft comparison: [page]. A visitor is choosing between us and [competitor] on [criteria]. Where does this page make the decision harder? Rewrite that part to make the tradeoff explicit.
The page's job isn't to say you're better — it's to make the decision easy. Even if the easy decision is "not you" for the wrong audience, that's a qualified lead saved.
12. The price-anchoring pass.
Rewrite this pricing copy to anchor the value before the number: [copy]. Show the cost of not choosing, then the price, then what the price includes in outcome language.
Order matters. Value → price → scope is more persuasive than price → justification.
Capture and keep: CTAs, popups, and follow-up
13. Blog CTA that matches the article. Use Blog Post CTA Optimizer after you publish any content site:
Rewrite this end-of-post CTA for [product] with goal [goal] so it matches what the reader just learned in [content]: [content]. The CTA is [current CTA].
Generic "Subscribe to our newsletter" after a blog about pricing pages is ignored. "Get the pricing page teardown checklist" after that same article is clicked.
14. Exit-intent without desperation. Exit-Intent Popup Offer:
Write an exit-intent popup for [product] offering [offer] to [audience]. No desperate discount language — earn the email with relevance.
The prompt's ban on desperation is why it works. "Wait! 10% off!" trains visitors to bounce to trigger discounts. Relevance trains them to stay.
15. Newsletter incentive that earns the email. Newsletter Signup Incentive:
Write a newsletter signup block for [audience] on [topic] that earns the email — name the specific thing they get and how often.
"Join our newsletter" is a request. "Get one teardown of a high-converting page every Tuesday, 3 minutes to read" is a promise.
16. Onboarding email that gets to first value. Use Post-Signup Onboarding Email:
Write the first email a new signup for [product] gets, built to get them to [goal] — not to sell them again.
Selling to someone who just signed up is the fastest way to lose them. Activation — one small win — is the real onboarding metric.
17. Testimonial request that gets specifics. Testimonial Request Email:
Ask a happy customer for a testimonial for [product] in a way that gets a specific, usable quote about [task], not "great service!"
Specific prompt → specific testimonial → specific trust section. The chain starts here.
Fix the dead ends and metadata
18. 404 that keeps people. 404 Page Copy:
Write 404 copy for [product] in tone [tone] that keeps the visitor on site — acknowledge the dead end, give 2 useful links, one action.
A 404 that says "Page not found" is a goodbye. One that says "That page moved — here's where pricing and docs now live" is a recovery.
19. Changelog users actually read. Changelog / Release Notes:
Turn these shipped changes into release notes users skim: [content].
The test is skim-ability — the prompt forces outcome bullets ("You can now...") over commit messages ("Fixed bug in...").
20. Plain-English policy summary. Plain-English Policy Summary:
Add a plain-English summary above this policy so people understand what they agreed to: [content].
Legal text that hides the meaning destroys trust. A summary that says "We store your email to send you what you asked for, nothing else" builds it.
21. SEO meta batch that gets clicks. Use SEO Meta Description Batch once the IA pages exist:
Write meta descriptions for these pages that get clicked, not just summarized: [content] with keywords [keyword].
The prompt's distinction matters: accurate summaries lose to clickable ones on the SERP. Clicks are the meta description's only job.
Revision shortcuts: tighten without regenerating
22. The headline tightening pass.
Here are my section headlines: [headlines]. Cut each to ≤6 words that make a claim (not a topic). Flag any headline a competitor could also claim — rewrite that one to be specific.
"Features" is a topic. "Ship pricing in 2 minutes" is a claim. Claims convert.
23. The jargon strip.
Find jargon in [copy] — "innovative," "cutting-edge," "leverage," "unlock" — and replace each with the concrete thing it hides. If a sentence is still true with jargon removed, the jargon was hiding nothing — cut the sentence.
24. Voice consistency check.
Here are 3 sections of my site: [sections]. Do they sound like one product or three vendors? Flag vocabulary or tone shifts and suggest the single voice word to rule each section (e.g., "direct," "warm," "technical").
Builders shift voice between sections because each generation is independent. This pass reunifies it.
25. The pre-launch bounce audit.
As a skeptic visiting [site description], where would you bounce and what question caused it? List the top 3 bounce points and the one sentence that would keep you on each.
Fix those three sentences before you ship. That audit is worth more than another template swap.
Use order
Don't run all 25. Start with the page that earns or loses most: hero → pricing → feature → FAQ → proof. Then capture → dead ends → SEO. The pattern is build with build-* → polish with website-* — one generation, many targeted rewrites.
Start with Homepage Hero Section, Pricing Page Copy, and SEO Meta Description Batch in the Promptigo library — every website prompt is free to copy with variables you can fill in. Then browse the full AI website builder collection for the build-* starter that matches your site type.