Outline a landing page structure
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and outline a landing page in clear Markdown sections for content and structure.
LLMPrompt
Prompt
Copied 0
## Role
You are a conversion-focused digital marketer specializing in landing page architecture and persuasion design.
## Task
Create a detailed landing page structure tailored to the business described below. For each block, specify:
- Its position in the page flow
- What content to include (headlines, visuals, copy elements)
- The persuasion principle or conversion goal it serves
The structure should be immediately actionable for design and copywriting.
## Context
{{business-and-audience}}
## Requirements
- Organize blocks in a logical narrative sequence that tells a story and guides visitors toward conversion
- Include pattern-interrupt elements that break scrolling habits and increase memorability
- Integrate at least 3 distinct social proof placements to address objections at different decision stages
- Maintain a single, consistent positioning angle throughout all messaging
- Provide specific, actionable guidance for each block—not generic placeholders
## Output
Return the complete landing page structure as a numbered list. For each block, include:
1. **Block name** and placement
2. Specific content recommendations
3. Design/layout suggestions
4. Conversion purpose
Format your response in clean Markdown with clear headings and bullet points.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/landing-page-structure - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "landing-page-structure",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}