Categories

One-shot conversion landing page prompt

Generate a full, SEO-aware 5-section landing page from a single research input — ready for human refinement or direct deployment.

What You'll Get

• Production-ready 5-section landing page (hero, benefits/features, social proof, pricing/offer, final CTA)

• Headline stacks with six variations per section and CTA microcopy

• SEO meta, FAQ-ready content, and on-page heading suggestions

• Three prioritized A/B tests with hypotheses and test guidance

• Form microcopy, recommended UX fields, and example outputs

How to Use

• 1Provide product summary, ICP, primary keyword, search intent, assets, top objections, brand tone, and constraints as inputs to the prompt.

• 2Run the one-shot prompt in ChatGPT and request optional outputs (ad-angle matrix, email sequences, example outputs) as needed.

• 3Replace placeholders ([MISSING_ASSET]) and mark any performance metrics with [VERIFY] before publishing; hand-off copy to designers/developers for implementation.

Test outcome-focused CTAs

Run an A/B test between outcome-focused CTAs (e.g., 'Generate prompt') and generic CTAs (e.g., 'Download template') to see which drives higher CTR and lead quality. Monitor downstream lead quality, not just clicks.

Works Best With

Works best when you provide:

• Primary keyword and observed search intent (informational/commercial/transactional).

• Clear audience/ICP and region/language for tone and localization.

• Concise product summary: core promise, features, top objections, CTAs, pricing model.

• Proof assets: logos, testimonials, case-study metrics, security/compliance badges.

• Brand voice guidance and any UX constraints (button limits, hero image availability).

Prompt Template

## Goal
- Create a single, production-ready one-shot prompt that, when run, produces an organic-search-focused, conversion-optimized 5-section landing page (hero, benefits/features, social proof, pricing/offer, CTA) which ranks for the target keyword, satisfies the specified search intent, and converts visitors via clear CTAs and evidence-based proof placement.

## Inputs
- Provide these inputs inside the prompt block below as full sentences or short paragraphs:
  - Primary keyword: {{primary_keyword}}
  - Search intent (informational / commercial / transactional / navigational): {{search_intent}}
  - Target audience / ICP: {{audience}}
  - Region and language: {{region_language}}
  - Content type (landing page / sales page / product page): {{content_type}}
  - Product summary, core promise, top objections, proof assets, brand tone, CTAs, pricing model: {{product_summary}}
- If keyword data or intent signals are missing, infer the most likely intent and propose up to two alternative keywords with rationale.

## Prompt
You are a senior conversion copywriter and SEO strategist for a B2C/B2B product. Using the inputs below, produce a concise brief/spec first, then generate the full deliverables described. Work in {{region_language}} and match the specified voice and content type.

Inputs:
Primary keyword: {{primary_keyword}}
Search intent: {{search_intent}}
Audience / ICP: {{audience}}
Region & language: {{region_language}}
Content type: {{content_type}}
Product summary and assets (core promise, objections, proof, tone, CTAs, pricing): {{product_summary}}

Task requirements — deliver everything in a single JSON object with the exact keys and order below. Keep responses factual; clearly label assumptions. Use plain, production-ready copy and short copy snippets optimized for conversion and SEO. Prioritize readability and scannability; use active voice and present tense.

Required JSON output keys and content (order matters):
1) spec — one-paragraph content brief (purpose, primary keyword, search intent, two target user scenarios, primary CTA, top 3 SEO on-page goals)
2) content_outline — full H1/H2/H3 map and structure for the landing page; include estimated word count per section and recommended micro-UX elements (form fields, trust badges, hero image alt text)
3) landing_page — a section-by-section production-ready copy for 5 sections: hero, benefits/features, social proof, pricing/offer, final CTA. For each section include:
   - main headline (H1 or H2 as appropriate)
   - subheadline
   - 3-6 body bullets or paragraphs (scannable)
   - exact placement suggestion for proof assets (testimonials, logos, stats)
4) headline_variations — provide 6 headline variations for each of the 5 sections (label by section)
5) cta_variations — provide 5 CTA alternatives (short action verbs + 1-2-line supporting microcopy for each) and recommend which to A/B against first
6) microcopy — form labels, button text, inline help, privacy note, and error message examples (keep buttons ≤ 4 words; privacy note ≤ 14 words)
7) seo_meta — short meta title (≤ 60 chars) and meta description (≤ 160 chars) optimized for the primary keyword and intent; suggest canonical URL slug
8) internal_links — 3 prioritized internal link targets with anchor text and rationale (use existing site pages if known; otherwise suggest generic pages)
9) faqs — 6 SEO-focused FAQ Q&A pairs (Q as user-intent queries; answers 20-45 words). Flag any answer that is an assumption.
10) schema_suggestions — list recommended schema types (FAQPage, Product, Review, WebPage) and provide one minimal example JSON-LD snippet for the FAQPage based on the provided faqs
11) proof_placement — exact guidance: which proof asset to use where (hero social proof, mid-page testimonials, pricing trust badges), plus 3 micro-test ideas for proof placement
12) ab_tests — three prioritized A/B test variants (hypothesis, variant copy/element, expected metric uplift, test duration & sample size guidance)
13) notes_and_assumptions — list any assumptions made, sources cited, and “do not claim” guardrails (e.g., no invented stats, no medical/legal promises)

Formatting and content rules:
- Produce the JSON object only. All string values should be plain text or nested JSON structures (no HTML). Fields that map to content blocks should preserve line breaks for human readability.
- For each copy block include a short on-page SEO note: target keyword density goal (percentage range), suggested H-tag, and 1-2 internal link anchor suggestions.
- Keep meta title ≤ 60 chars and meta description ≤ 160 chars. Recommend slug with hyphens and the primary keyword.
- For A/B tests include measurable KPI (CTR, CR, or avg order value).
- Call out any claim that requires verification with [VERIFY] tag.
- Do not invent customer names, statistics, or certifications. If a proof asset is missing, mark the proof slot as [MISSING_ASSET] and suggest acceptable replacements (case study type, metric, or testimonial format).
- If the primary keyword or intent conflicts with the content type, state the conflict in spec and propose a prioritized fix (keyword change or content re-targeting).

Tone and UX constraints:
- Use the brand tone in {{product_summary}}. If tone missing, default to: clear, confident, helpful.
- Keep hero headline ≤ 12 words; section headlines ≤ 10 words where possible.
- Buttons ≤ 4 words; microcopy concise.
- Language, spelling, and units must match {{region_language}}.

Produce the final JSON only. End.

## Output Format
- Required top-level JSON keys (in the exact order listed in the Prompt): spec, content_outline, landing_page, headline_variations, cta_variations, microcopy, seo_meta, internal_links, faqs, schema_suggestions, proof_placement, ab_tests, notes_and_assumptions.
- Each landing_page section must include H-tag suggestion, headline, subheadline, body (array of bullets/paragraphs), proof_placement note, and recommended word count.
- Provide an H1/H2/H3 map inside content_outline as an ordered list.
- Make the JSON scannable: nested objects and arrays; avoid long unbroken strings where possible.

## Guardrails
- Do not invent data or statistics. Mark unverifiable items with [VERIFY] or [MISSING_ASSET].
- Distinguish facts vs. assumptions in notes_and_assumptions.
- Apply E‑E‑A‑T: include explicit expertise signal phrasing (e.g., “used by X years of experience” only if provided).
- Avoid medical, legal, or financial advice language unless vetted; add caution language if content touches those domains.
- Do not deviate from the requested JSON keys or their order.
- Ensure all copy matches declared search intent and audience; if a conflict exists, call it out in spec.
- SEO guardrails: canonicalize keyword in title, H1, and slug; keep title/description length limits; include 3-5 internal links; add FAQ schema when FAQs provided.
- Accessibility: include hero image alt text and CTA focus order suggestion.

## Examples
Keyword → 3-bullet content brief excerpt
- Keyword: landing page copy prompt
- Brief excerpt:
  - Purpose: Rank for “landing page copy prompt” and convert visitors seeking templates to write high-converting pages.
  - Primary CTA: Download template (lead magnet) — short conversion path < 2 fields.
  - SEO goals: H1 contains keyword, meta title optimized ≤ 60 chars, FAQ addresses long-tail variants.

Variables

Usage Notes

Not for

• • Pages requiring verified regulatory, medical, legal, or financial claims without documented evidence

• • Final front-end code or full accessibility implementation (this is copy-first output)

Do not include

• • Unverified performance metrics without marking [VERIFY] and attaching a source

• • Personal or sensitive data in prompt inputs

• • Concrete guarantees or endorsements unless documented and permissioned

One-shot conversion landing page prompt

Generate a conversion-optimized, SEO-aware 5-section landing page (hero, benefits, social proof, pricing, CTA) from one prompt input.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

• Auto-fill & personalize from your inputs

• AI-assisted edits: tone, structure, constraints

• Attach context so outputs stay consistent

• Iterate and save versions

What you'll get

Output format

Markdown

Best used when

• When working on conversion landing page prompt or landing page template.

Avoid when

• Pages requiring verified regulatory, medical, legal, or financial claims without documented evidence

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Primary Keyword

Provide the key details needed for this variable.

Search Intent

Provide the key details needed for this variable.

Audience

Provide the key details needed for this variable.

Region Language

Provide the key details needed for this variable.

Content Type

Provide the key details needed for this variable.

Product Summary

Provide the key details needed for this variable.

Rules

• Provide product summary, ICP, primary keyword, search intent, assets, top objections, brand tone, and constraints as inputs to the prompt.

• Run the one-shot prompt in ChatGPT and request optional outputs (ad-angle matrix, email sequences, example outputs) as needed.

• Replace placeholders ([MISSING_ASSET]) and mark any performance metrics with [VERIFY] before publishing; hand-off copy to designers/developers for implementation.

Canonical Examples

Input: B2B SaaS: 'CartBoost' checkout conversion optimizer. Primary keyword: "checkout optimization software." Search intent: commercial. Audience: ecommerce growth managers and performance agencies in US/UK. Content type: landing page. Product: SaaS that reduces checkout friction via A/B tests, prebuilt UX templates, and one-click payment integrations. Top objections: implementation time, data security, integration complexity. Proof: 2 customer logos, 1 short case-study metric missing. Tone: clear, confident, helpful. CTA: 'Start free trial'. Pricing: monthly SaaS tiers.

Loading result...

Failed to load output.

Spec paragraph + H1/H2 map + 5-section landing copy (hero, benefits, social proof, pricing, CTA) + SEO/meta/FAQ/schema + AB tests and proof placement.

Why it works: This example demonstrates a conversion- and SEO-focused one-shot that returns a production-ready landing-page JSON spec tailored to a B2B SaaS buyer intent. It includes brief, H-tag map, ready copy, SEO meta, FAQ schema, proof-placement rules, microcopy, and prioritized A/B tests — all aligned to growth-focused stakeholders.

Input: DTC hardware: 'QuietBuds' wireless noise-cancelling earbuds. Primary keyword: "wireless noise cancelling earbuds." Search intent: transactional. Audience: US/EU consumers 25-45 looking for premium ANC earbuds. Content type: product landing page. Product summary: premium sound, 30hr battery with charging case, multipoint Bluetooth, IPX4, 2-year warranty. Objections: price, fit/comfort, battery life in real-world. Proof assets: product images available; no customer reviews provided. Tone: friendly, premium, confident. CTA: 'Buy now'. Pricing: $199 one-time purchase.

Loading result...

Failed to load output.

Product landing JSON with hero, features, social proof placeholder, pricing, CTA, meta, FAQ schema, proof placement, and AB tests.

Why it works: Shows a consumer-focused example where the single prompt assembles SEO-led product page copy, PDP optimizations, ad-angle hooks, meta content, FAQ schema, and CRO tests while flagging missing reviews and recommending concrete proof placements.

Works Best With

Works best when you provide:

• Primary keyword and observed search intent (informational/commercial/transactional).

• Clear audience/ICP and region/language for tone and localization.

• Concise product summary: core promise, features, top objections, CTAs, pricing model.

• Proof assets: logos, testimonials, case-study metrics, security/compliance badges.

• Brand voice guidance and any UX constraints (button limits, hero image availability).