Write conversion-focused website content for the page described below. Write for the reader’s job, problem, and decision stage, not for a generic audience. Do not invent testimonials, customer counts, results, integrations, certifications, guarantees, pricing, or claims that my source material does not support. Page type and URL goal: [PAGE TYPE] Target audience: [TARGET AUDIENCE] Offer and desired action: [OFFER AND CTA] Source material and proof: [SOURCE MATERIAL] Competitors or alternatives the reader considers: [ALTERNATIVES]
Voice and constraints: [VOICE AND CONSTRAINTS]
Produce copy in this order:
1. Three hero options, each with a headline of 6-12 words, a supporting paragraph of 25-40 words, and a CTA label.
2. One recommended page draft of 650-900 words using sections for problem or outcome, how it works, key benefits, proof, objections or FAQ, and final CTA. Match the page type; do not force every section if it would be inappropriate.
3. A message map showing the reader’s problem, desired outcome, mechanism, proof, objection, and CTA.
4. SEO title under 60 characters and meta description of 120-155 characters, both natural and non-repetitive.
Use concrete verbs and explain the mechanism behind every promised outcome. Keep the CTA specific to the next commitment, such as starting a trial, requesting a quote, or booking a call. Before answering, check that each factual claim is supported by the source material and that the first screen makes the audience, value, and action clear. Ask up to 3 clarifying questions only if a required input is missing.Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PAGE TYPE] | State the page type, page goal, and where it sits in the buyer journey. | B2B SaaS landing page for paid-search visitors evaluating a 14-day trial. |
| [TARGET AUDIENCE] | Describe the specific reader, their role, situation, and decision they need to make. | Operations managers at 50-300 person logistics companies who track exceptions in email and spreadsheets. |
| [OFFER AND CTA] | Describe what you sell, what is included, and the one action you want the reader to take. | Exception-tracking software with a 14-day trial; CTA: Start a trial. |
| [SOURCE MATERIAL] | Paste approved product facts, customer evidence, pricing details, and differentiators. | Imports shipment updates from CSV, assigns owners, and sends daily exception digests. Customer quote approved: “We cut our morning exception review from 90 minutes to 25.” |
| [ALTERNATIVES] | List the competitors, workarounds, or status quo the reader may compare against. | Spreadsheets, shared inboxes, and generic project-management tools. |
| [VOICE AND CONSTRAINTS] | State the desired voice plus legal, brand, length, or terminology restrictions. | Plain, practical, no unsupported ROI claims, no use of the word revolutionary. |
How to use
- Paste only approved product facts and label any evidence that cannot be published.
- Choose one hero option based on the visitor’s primary job, not the cleverest wording.
- Verify every proof point, price, integration, and promise with the responsible owner before publishing.
- Follow up with: “Rewrite the recommended draft for skeptical visitors who currently use [ALTERNATIVE], keeping all claims unchanged.”
Variations
Service page
Use this when selling a professional service rather than a product.
Write a service page for [SERVICE] aimed at [IDEAL CLIENT]. Use [APPROVED CREDENTIALS AND EVIDENCE], [ENGAGEMENT PROCESS], [PRICING OR SCOPE], and [CTA]. Produce a 700-900 word page with hero, who it is for, outcomes, process, deliverables, proof, qualification criteria, FAQ, and CTA. Explain what the client receives and what is excluded. Do not invent case-study results or credentials. Check that each outcome has a stated method or approved evidence. Ask up to 3 questions only if a required input is missing.
Product launch page
Use this when announcing a new feature or product.
Draft a launch page for [PRODUCT OR FEATURE] for [TARGET USER] using [APPROVED PRODUCT FACTS], [USER PROBLEM], [AVAILABILITY], and [CTA]. Produce a 500-750 word page with a clear before-and-after workflow, feature explanation, limitations, rollout details, FAQ, and CTA. Include three headline options. Do not imply general availability, performance gains, or integrations that are not confirmed. Check that the page distinguishes current capability from planned work. Ask up to 3 questions only if required information is missing.
About page
Use this when explaining a company’s purpose and credibility.
Write an About page for [COMPANY] using [ORIGIN STORY], [CUSTOMER], [TEAM FACTS], [OPERATING BELIEFS], and [CTA]. Produce 500-700 words with a concise company introduction, origin, the problem the company exists to solve, how it operates, proof, and next step. Avoid a chronological biography unless it helps the reader understand the mission. Do not invent founding details, team claims, or milestones. Check that every factual statement is supported by the inputs. Ask up to 3 questions only if required inputs are missing.
Tips
- Write the page around one primary reader and one primary action; competing CTAs usually belong on separate pages or later in the journey.
- Put proof near the claim it supports, such as a verified customer result beside the benefit rather than in a detached logo strip.
- Name the workflow or mechanism behind the offer, because vague outcome language makes legitimate claims sound interchangeable.
- Treat objections as buying questions: address implementation effort, fit, cost, risk, and alternatives with approved facts rather than defensive copy.
FAQ
Can I use AI website copy without editing it?
Use it as a structured draft, then verify every factual claim and tune the language to your product knowledge and brand.
How much source material does this need?
A clear audience, offer, CTA, and a short list of approved facts are enough for a first draft. More precise proof produces more credible copy.
Should a page target several customer types?
Only if they share the same problem, evaluation criteria, and next action. Otherwise make focused versions for each audience.