Resource
API Request Variable Builder
Turns a reusable API request prompt into a clean variable set covering endpoint, method, auth, payload, response format, and error handling.
Landing Page Variable Builder
Cleans up variables in landing page prompt templates — headline, audience, pain point, offer, social proof, CTA, and objections.
Overview
A landing page prompt can quickly collect overlapping placeholders. {{audience}} and {{targetAudience}}, {{cta}} and {{primaryCta}}, {{proof}} and {{socialProof}} — all pointing to the same value under different names added at different points in the template's life. This resource helps you turn those into one clean variable set before the prompt becomes too tangled to reuse across campaigns.
How to use this resource
-
Open in Prompt Variable Builder
Load this template. The tool detects all ten landing page variables.
-
Check for similar variable names
If your existing template has both {{audience}} and {{targetAudience}}, the tool will flag them. Use the rename field to consolidate to one name before sharing.
-
Set types and descriptions for tone and sections
Tone is text. Sections is best typed as list if you expect a comma-separated or bulleted list of section names.
-
Export for campaigns
Use the JSON schema in the campaign tool that substitutes values. Use Markdown as the copywriter reference.
Why This Works
- Landing page templates are among the most frequently forked prompt templates — each fork risks creating a new naming variant, and the similarity check surfaces those before they multiply
- Audience and CTA are the two variables most often duplicated across landing page template versions
- A documented objections variable prevents different team members from filling in different-format content for the same placeholder
Best for
- Landing page templates reused across multiple campaigns or audience segments
- Templates that grew incrementally and may have accumulated near-duplicate variable names
- Content teams sharing templates with external writers or agencies who need a clear variable reference
Not for
- One-page campaign sites built from scratch without a reusable template structure
- Landing pages where copy is written entirely by a human without AI assistance
Use cases
- Auditing a landing page template used across multiple campaigns for duplicate and similar variable names
- Standardising the variable names in a shared prompt library used by a content and performance marketing team
- Generating a JSON schema for a landing page prompt used in a headless CMS or campaign automation tool
- Documenting the variable set before handing a template to a freelance copywriter
FAQ
How do I collapse duplicate variable names like {{targetAudience}} and {{audience}} in a landing page prompt?
Paste the template into the Prompt Variable Builder and its similarity check flags near-identical names side by side, so a forked pair like {{targetAudience}}/{{audience}} or {{socialProof}}/{{proof}} shows up as a match. Rename each to one canonical name, then export the tidied set. It only detects and renames the placeholders — you fill and run the finished prompt in ChatGPT, Claude, or Gemini.
Which variables in this landing page template hold multi-line blocks versus a single line?
{{painPoint}}, {{offer}}, {{socialProof}}, and {{objections}} each sit on their own line under a label, so they're built to hold multi-line content, while {{headline}}, {{primaryCta}}, and {{tone}} are inline and expect a short single value. In the Prompt Variable Builder you can attach a description to each, so a teammate filling {{objections}} knows it takes several bulleted points rather than one sentence.
When should I export the JSON schema instead of the Markdown reference for this template?
Export the JSON schema when a campaign or substitution tool will inject values automatically, because it carries the type you set — so {{sections}} typed as a list arrives as an array, not one string — plus each variable's description. The Markdown export is the plain-language reference a copywriter reads. The Prompt Variable Builder produces both from the same template; you paste each into its destination.
More resources from Prompt Variable Builder
Resource
User Story Variable Builder
Documents and exports variables from user story and acceptance criteria prompt templates — persona, goal, outcome, constraints, and definition of done.
Resource
Candidate Evaluation Variable Builder
Documents variables in candidate evaluation prompt templates — candidate name, role, interview notes, strengths, concerns, and recommendation.
Resources that pair well
Resource
Agent Task Template
A reusable AI agent task template with variables for objective, context, available tools, constraints, success criteria, failure handling, and output format.
Resource
Agent Instruction Prompt Formatter
Formats fuzzy agent instructions into a structured prompt with objective, available tools, constraints, success criteria, and failure handling.
Related tools
Tool
Prompt Variable Builder
Turn any plain prompt into a reusable, variable-based template — auto-detect values and export.
Projects that use this resource
Project
Build a Programmatic SEO Site with AI
The full path to pages that rank at scale, not penalty bait — map the intents, build the data set, structure it, template the page, then QA before publishing hundreds.
Workflows that use this resource
Workflow
AI Programmatic SEO Workflow
Generate many intent-matched SEO pages from a template without the thin-content spam — map the search intents, define the page variables, build the template, and QA before publishing at scale.