Landing Page Section Prompts for High-Converting Blocks

12 prompts that make every landing-page block earn its space — hero, social proof, problem-agitate, features, comparison, pricing, FAQ, risk-reversal, final CTA, and a section-order audit.

A landing page dies one block at a time: a hero that explains what the product is instead of what it does, a social-proof strip with no numbers and no names, a feature grid that reads like a competitor’s, and two CTAs at the bottom fighting each other. These 12 prompts force each block to earn its space — hero earns the scroll, social proof earns trust, problem-agitate earns four nods, features earn comprehension, and the final CTA earns the click. Pair with the CTA prompts to A/B the button copy itself.

Best for

  • Product launches
  • B2B landing pages
  • DTC product pages
  • Indie SaaS pricing pages
  • Newsletter / community landing pages

1. Hero section

Write the hero section for "{product}". Audience: {audience}. Output: H1 (≤8 words), sub-headline (≤20 words), 1-line clarifier on what it IS (1 noun), and CTA button copy + secondary CTA. Avoid jargon.

2. Social-proof section

Write the social-proof section. Available evidence: {logos, numbers, quotes}. Output: a headline ("Trusted by X who Y"), a quote with attribution, 1 quantified outcome, and a logo strip caption. Avoid "loved by everyone".

3. Problem-agitate section

Write the problem section. Audience's current pain: {paste}. Output: a 1-sentence headline that mirrors the pain, 3 specific pain bullets, 1 cost-of-inaction line. Should make the reader nod 4 times.

4. Solution-overview section

Write the "how it works" overview after problem. Output: 3 steps (verb + object), each 1 line, with the 1-line outcome under each step. Total ≤60 words. End with a transition to features.

5. Feature-block section (3 features)

For 3 features of {product}, write feature blocks. Each block: headline (≤6 words, value-led not feature-led), 1-sentence explanation, 1 supporting fact / metric, 1 visual placeholder description.

6. Use-case row (for multi-audience products)

{Product} serves {3 audiences}. Write a use-case row for each: audience name, their job, how {product} helps in 1 sentence, link text to detail page. Keep parallel structure.

7. Comparison-table section

Write a comparison-table section for {product} vs {top 2 competitors}. 5 rows of meaningful dimensions (not "advanced features ✓"). For each, the honest answer per column. End with a 1-line "pick us if you need X".

8. Pricing section

Write the pricing section for {N} tiers. For each: tier name, who it is for, 3 included items, 1 not-included item, CTA. End with a "questions about pricing?" link. No fake scarcity.

9. FAQ section

Write the FAQ section for {product}. Mine likely buyer hesitations: {paste}. Output 8 Q&A pairs, each answer ≤60 words. Include 1 question that handles the strongest objection.

10. Risk-reversal section

Write the risk-reversal section above the final CTA. Include: trial / guarantee terms, cancel policy, support response time, 1 specific reassurance. ≤70 words total.

11. Final-CTA section

Write the final CTA section. Output: a 1-sentence restatement of the value, 1 secondary trust signal, the button copy (different from hero), and 1 alternate path ("not ready? read the case study"). ≤50 words total.

12. Section-order audit

Below is my current landing page section order. Evaluate whether the order matches buyer-decision flow (awareness → consideration → commitment) for my audience: {audience}. Propose a new order with rationale.

{paste current sections}

Common mistakes

  • Hero that explains what the product IS instead of what it DOES for the reader
  • Generic feature blocks that read like a competitor’s marketing site
  • Social proof without a number, a name, or anything falsifiable
  • Pricing tiers without “who this is for” — buyers stall on the wrong tier
  • Two CTAs competing at the bottom, splitting attention and ad-attribution
  • FAQ that dodges the strongest objection instead of answering it directly
  • Section order that doesn’t follow buyer-decision flow (problem → proof → solution → ask)

Tags: #Prompt #E-commerce #E-commerce