Prompt recipes for SEO blog posts

Why prompt recipes beat one-size-fits-all prompts

Generic prompts create generic drafts. For SEO, you need structure that matches intent, language that reads clean, and sections that win quick answers. Prompt recipes give the model a clear job, clear constraints, and a repeatable format. The result is a draft that needs light editing instead of a full rewrite.

How these recipes are built

• Inputs first: You supply the topic, audience, and 3–5 sources or notes.
• Structure locked: Each recipe fixes the page pattern: guide, list, FAQ, or comparison.
• AEO ready: Every draft starts with a short answer block and uses clean subheads.
• Edit checklist: Each recipe ends with a short checklist so you can polish fast.

Rules that keep drafts safe and useful

• Use only the provided sources or notes. Do not invent facts.
• Keep sentences short and direct. Avoid filler and buzzwords.
• Add a two-to-three sentence answer under the first H2.
• Use plain HTML-friendly headings and lists.
• Leave placeholders where a screenshot or table will go.

Recipe 1: The Step-by-Step Guide

This is your go-to for “how to” intent. It wins when readers want a clear sequence, and it aligns with quick-answer boxes when the answer block is tight.

Prompt

Goal: Draft an SEO-friendly "how to" guide.Topic: [insert topic]Audience: [role or industry]Outcome: [what the reader gets done]Sources to use (paraphrase or quote): - [URL or notes 1]- [URL or notes 2]- [URL or notes 3]Constraints:- No invented facts- Clear, simple language- Short paragraphs (2–4 lines)- Use H2s and H3s; start with a two-sentence answer blockStructure:H2: What this guide covers (with the two-sentence answer block)H2: StepsH3: Step 1 — [verb + result] [2–4 lines. Include quick checks or tools.]H3: Step 2 — [verb + result]H3: Step 3 — [verb + result]H2: Example (brief worked example or template)H2: Common mistakes (bullet list with fixes)H2: FAQ (3–5 short Q&As using real phrasing)H2: Next step (one link or CTA)

Editing checklist

• Is the answer block present and accurate?
• Do steps begin with verbs and lead to an outcome?
• Does the example make the steps concrete?
• Are FAQs phrased as real questions from search?

Recipe 2: The List Post that Earns Saves

Use this for “ideas,” “tips,” “tools,” and “ways to” queries. It works when readers want quick scanning and a compact payoff per item.

Prompt

Goal: Draft an SEO-friendly list post that people will save.Topic: [insert topic]Audience: [role or industry]Number of items: [e.g., 10]Sources to use (evidence and examples): - [URL or notes 1]- [URL or notes 2]Constraints:- No invented facts- Short, skimmable items- Each item explains: what it is, how to use it, quick result- Start with a two-sentence answer block under the first H2Structure:H2: What this list will help you do (with two-sentence answer block)H2: [Number] ways to [result] without [pain]H3: [Item 1]: what, how, quick resultH3: [Item 2]: what, how, quick result...H2: How to pick your top three (short decision tips)H2: FAQ (3–5 Q&As)

Editing checklist

• Does each item have a mini “what/how/result” flow?
• Are examples concrete and sourced where needed?
• Is the title aligned with the count and outcome?

Recipe 3: The FAQ Page that Wins People Also Ask

Use this when the topic spawns many related questions. Phrasing must match how people actually ask. Keep answers tight so they can be pulled into rich results.

Prompt

Goal: Draft an SEO-friendly FAQ page.Topic: [insert topic]Audience: [role or industry]Questions to cover (exact phrasing): - [Q1]- [Q2]- [Q3]- [Q4]- [Q5]Sources to use:- [URL or notes 1]- [URL or notes 2]Constraints:- Two-to-four line answers- Plain language- No invented factsStructure:H2: Quick answers to [topic][Two-sentence answer block that defines or frames the topic]H2: QuestionsH3: [Q1][2–4 line answer]H3: [Q2][2–4 line answer]H3: [Q3][2–4 line answer]H2: Related resources (link to 2–3 deeper pages)

Editing checklist

• Do questions match real phrasing from search?
• Are answers short enough to be excerpted?
• Are resource links relevant to next steps?

Recipe 4: The Comparison that Reduces Bounce

Great for “A vs B” searches. The trick is to state criteria first, then give a clear pick for common cases. Help the reader decide and you will win clicks from the result page.

Prompt

Goal: Draft an SEO-friendly comparison article.Topic: [A] vs [B]Audience: [role or industry]Decision criteria (ranked): - [Criterion 1]- [Criterion 2]- [Criterion 3]Sources to use: - [URL or notes 1]- [URL or notes 2]Constraints:- No invented facts- Balanced, then clear picks for scenarios- Start with a two-sentence answer blockStructure:H2: Quick answer (two-sentence answer block with the quick pick)H2: CriteriaH3: [Criterion 1] — what it means and why it mattersH3: [Criterion 2]H2: A vs BH3: A: strengths, limits, best forH3: B: strengths, limits, best forH2: ScenariosH3: If [case], pick [A]H3: If [case], pick [B]H2: FAQ (3–5 Q&As)

Editing checklist

• Does the quick answer name a pick and a reason?
• Do scenarios map to common real-world cases?
• Is the comparison neutral in tone but decisive in guidance?

Recipe 5: The Problem–Solution Case Mini

Short case posts give you proof and internal link targets. Use this pattern to show the path from issue to outcome in a compact read.

Prompt

Goal: Draft a short problem–solution case.Client type: [e.g., local restaurant]Problem: [plain-language statement]Solution: [what we did]Outcome: [specific metric with timeframe]Sources: internal notes and approved data onlyConstraints:- 400–700 words- One chart placeholder- Two-sentence answer block under first H2Structure:H2: The quick result (two-sentence answer block with metric and timeframe)H2: The problem[3–5 lines]H2: The approach[steps in bullets]H2: The outcome[metric, timeframe, and what it means]H2: What to try next[one or two actions]

Editing checklist

• Are numbers precise and time-bound?
• Is the problem stated in the client’s words?
• Does the approach map to steps you actually used?

Setting up your inputs fast

The fastest way to keep quality high is to prep a small input block you paste into every prompt. It keeps facts straight and tone steady.

Topic: [insert]Audience: [insert]Angle: [one-line promise]Brand voice: clear, direct, proof-firstDo:- Short sentences- Concrete examples- Answer first, then stepsDon't:- Hype, fluff, or vague claims- Invented factsSources (quote or paraphrase only):- [URL or notes 1]- [URL or notes 2]- [URL or notes 3]

How to edit AI drafts in minutes

Use a simple pass that cuts mistakes and sharpens the message without taking an hour.

1. Answer block: Is it present, correct, and tight?
2. Headings: Do H2s and H3s map to search intent?
3. Facts: Check names, dates, and numbers against sources.
4. Flow: Remove duplicated ideas and trim long sentences.
5. Links: Add one internal link to a hub and one to a next-step page.

Where these recipes shine

• Scaling content while keeping tone and structure consistent
• Training new writers and keeping edits predictable
• Launching new clusters where speed matters

Common pitfalls when prompting

• Prompts that ask for “long, comprehensive posts” without structure
• Letting the model pick sources and invent findings
• Skipping the answer block and burying the point
• Writing to please the model instead of the reader

A final template you can paste anywhere

Goal: Draft an SEO-ready article in the [pattern: guide | list | FAQ | comparison] format.Topic: [insert]Audience: [insert]Angle: [one-line promise]Use only these sources:- [links or notes]Constraints:- No invented facts- Two-sentence answer block under the first H2- Clear H2/H3 structure- Short paragraphs and lists- Plain HTML-friendly output

Final note

Prompt recipes give you speed with control. They keep structure locked, facts verified, and tone on brand. Use them to turn topics into drafts you can trust, then ship on a steady cadence. Over time that steady output builds clusters that rank and pages that drive real results.