{}

Prompt Workbench

JSON Prompt Builder

Back to index

Guides

How to structure a JSON prompt for a landing page

A step-by-step guide to turning a rough landing page brief into a structured JSON prompt with offer, proof, objections, and CTA logic.

Published: April 2, 2026Updated: April 2, 2026Reading time: 5 minAuthor: Astraport Team

Landing prompts work best when they describe not just the product, but also the offer, awareness stage, proof stack, and CTA rhythm.

1. Define the offer first

Before writing sections, clarify what is being sold, who it is for, and why someone should care right now.

2. Break the page into persuasive blocks

  • Hero section
  • Offer explanation
  • Proof and trust
  • Objections
  • CTA placement

3. Tune CTA intensity

Use a softer CTA for expensive or complex offers. Use a stronger CTA when the ask is simple and low friction.

json
{
  "task": "Write a landing page for a CRM onboarding service",
  "target_audience": "Operations leads at small and mid-size companies",
  "language": "en",
  "output_format": "markdown",
  "offer_type": "service_offer",
  "awareness_stage": "problem_aware",
  "cta_intensity": "balanced",
  "trust_elements": ["case_studies", "client_logos"],
  "objection_handling": "implementation_time"
}
Open the Landing builder

FAQ

FAQ

What is the most common landing prompt mistake?

Teams often describe the product but forget the awareness stage and the proof blocks.

Should CTA intensity be high by default?

No. The right level depends on the audience, offer friction, and brand style.