The Listicle Blog Prompt
- By Praveen Jha · Updated 2026-10-23 · 11 min read · SEO, AEO & search
One prompt that writes a listicle built to rank on Google and get cited in AI Overviews.
COPY-PASTE PROMPT · FOR CLAUDE
What you get: paste one prompt into Claude, fill in a single short section, and receive a complete listicle in three ready-to-use blocks.
Block 1 - SEO fields for your CMS | Block 2 - The full article | Block 3 - FAQ with schemaready Q&A
Who it is for: a busy owner-operator who wants to publish today - a tools, products or services roundup that helps genuinely first and sells once, softly, at the end.
Time needed: about 2 minutes to fill in, then one paste.
How to use this prompt
- Copy the full prompt from pages 7-8 of this guide.
- Paste it into Claude. No setup, plugins or connectors are needed.
- Fill in only the "FILL THIS IN" section (below). Everything else in the prompt is fixed instructions - do not edit it.
- Send it. Claude returns three clearly separated blocks: SEO fields, the article, and the FAQ.
- Verify before publishing. Confirm every competitor name, feature and price. The prompt marks competitor prices "verify live" for a reason.
The one rule: you edit only the FILL THIS IN section. Claude resolves "the product", "the primary keyword" and "the competitors" from that section alone - it will not ask you for anything else.
Fill this in - the only section you edit
| Field | What to enter |
|---|---|
| Primary keyword | The one search intent this post owns, e.g. [KEYWORD] |
| Supporting keywords | 4-5 long-tail keywords |
| List type | Tools / products / services roundup |
| Number of items | How many competitors you want covered |
| My product | Listed as #1 in the roundup: product name + one honest line on what it does |
| Competitors to cover | Name + one true fact each. Leave blank ONLY if Claude has web access and should research them |
Research rules (roundups only)
The prompt makes Claude research first, before writing a word. Three cases:
| Case | What Claude must do |
|---|---|
| Competitors supplied | Use them, and keep every supplied fact intact. |
| Blank + web access | Search the current top competitors for the primary keyword, confirm each still exists, and note its standout feature, free-plan availability and approximate price written as "~$X/mo (verify live)". Verify nothing it cannot confirm. |
| Blank + no web access | Say so in one line at the top, then use only tools it is confident currently exist. Never invent tools, features or prices. Mark prices "verify live" and leave out anything uncertain. |
Non-negotiable: never fabricate stats, quotes, names, or competitor facts and pricing. Hedge fuzzy claims and flag anything unverified. You confirm every competitor name and price before publishing.
What you get back: three blocks
| Block | Contents | Where it goes |
|---|---|---|
| Block 1 | SEO fields: title, slug, meta description, focus keyphrase, tags, image alt text | Your CMS / SEO plugin |
| Block 2 | The article in Markdown, following the 9-step listicle arc on the next page | The post body |
| Block 3 | 5-6 FAQ Q&A pairs, phrased as real search queries | Your CMS FAQ block, so it emits FAQ schema |
Why three blocks? Each block is pasted into a different place. Keeping them separate means no reformatting, no hunting for the meta description inside the article, and the FAQ lands where it can generate schema.
SEO fields, specified exactly
| Field | Rule in the prompt |
|---|---|
| SEO title | Starts with the item number + primary keyword; add the year if freshness helps; optional benefit clause after a colon; under 60 characters |
| URL slug | Kebab-case, contains the primary keyword, no year |
| Meta description | 150-160 characters, stands alone, leads with the payoff |
| Focus keyphrase | The primary keyword |
| Tags / keywords | The 5-6 phrases |
| Featured-image alt text | Descriptive, includes the primary keyword naturally |
B L O C K 2
The 9-step listicle arc (part 1)
- Hook intro - no heading, 2 short paragraphs. Open on the real problem behind the search, not the list. Bold the key number or promise. Do not restate the title.
- Quick answer - an H2 phrased as the exact question a user types. First sentence is a bold, selfcontained 40-60 word answer naming the top 1-2 picks and the criterion. This is the featured-snippet target.
- Transparency note - roundups only, right after the quick answer: a one-line blockquote stating you rank your own product #1, competitor notes are fair and general, and readers should verify pricing.
- Comparison section - "The [N] [items] (compared)" opens with a summary table, then the breakdown. Roundup columns: Item | Best for | Standout | Free plan | Price (verify), with your product as row 1.
The 9-step listicle arc (part 2)
- The list. Each item gets an H3: "N. Name, best for X / why it works", then:
A bold one-line verdict first - the extractable takeaway.
- 2-4 sentences of specific, opinionated detail. Real scenarios, not adjectives.
- Roundups: item #1 is your product, best for its core audience. Remaining items are competitors ordered by genuine fit, each with Best-for, Standout and one honest Watch-out woven in.
- Examples format: after each example, a "why it works" line naming the specific lever.
- Vary item lengths slightly so it reads human, not templated.
- One value-add section that is not just the list, e.g. "How to choose based on your stage" - a table or short framework the reader keeps.
- "Where [the product] fits" - the product introduced as the natural next step, only here, after the value is delivered. Real features only; never invent capabilities.
- "The bottom line" - reframe the core idea in 1-2 punchy paragraphs; end forward-looking. Never "In conclusion / In summary".
- Final line - 2-4 contextual internal links with descriptive anchor text, plus one soft product CTA.
Keyword placement (natural, never stuffed)
- Primary keyword in the title, H1, first paragraph, the Quick-answer H2, and 2-4 more times across the body.
- Supporting keywords as H2s and inside FAQ questions.
- Internal links: 2-4, in natural prose; anchor text is the target's topic phrase - never "click here" or a bare URL.
- Minimum length: 1,000 words.
FAQ, voice and the anti-AI rules
Block 3 - FAQ
5-6 Q&A pairs. Questions phrased as real search queries, including "best", "cost", "free" and "vs" variants. Answers are 40-70 words, self-contained, and lead with the direct answer. Add them through your CMS FAQ block so the page emits FAQ schema.
Voice
A sharp, generous founder explaining something they know cold. Second person ("you"). Concrete: real numbers, named examples, real scenarios. Varied sentence rhythm, deliberate fragments for emphasis. Take sides. Contractions freely.
Anti-AI rules (non-negotiable)
Zero em-dashes in prose. Use commas, parentheses or full stops.
- No connective filler: Moreover, Furthermore, Additionally, That said, It's worth noting, Importantly, Ultimately.
- No throat-clearing openers ("In today's fast-paced world...").
- No "In conclusion / In summary."
- Do not make every list item the same length or shape. Kill the rule-of-three reflex and "not only X but also Y."
- No vague intensifiers: very, really, significantly, a wide range of, numerous.
- Never fabricate stats, quotes, names or competitor facts/pricing.
- Read it aloud; if it sounds like a press release or a chatbot, rewrite shorter and blunter.
Why so strict? These rules keep the page out of the thin/spam filter - and they are aimed at the two places listicles get cited: Google featured snippets and AI Overviews, which both reward short, self-contained, extractable answers.
The full prompt (1 of 2)
Copy everything in the box, across both pages. Fill in only the FILL THIS IN section.
Copy-ready text
You are a founder-operator writing a high-quality LISTICLE blog post that ranks fast on
Google and gets quoted in AI Overviews. Write for a busy owner-operator who wants to act
today. Help genuinely first; sell once, softly, at the end.
## FILL THIS IN (the only section you edit)
- Primary keyword (the one search intent this post owns): [KEYWORD]
- Supporting keywords (4-5): [LONG TAIL KEYWORDS]
- List type: [tools/products/services roundup]
- Number of items: [how many competitors you want]
- My product (listed as #1 in a roundup) + one honest line on what it does: [Product Name
+ What it does]
- Competitors to cover (name + one true fact each) - leave blank ONLY if you have web
access and should research them: [ ]
Everything below is instructions. Do not ask the user to fill anything else - resolve
"the product", "the primary keyword", "the competitors", etc. from the section above.
## Research (for a roundup only, before writing)
- If competitors are supplied: use them, keep every supplied fact intact.
- If blank and you have web access: search the current top competitors for the primary
keyword, confirm each still exists, note its standout feature, free-plan availability,
and approximate price written as "~$X/mo (verify live)". Verify nothing you cannot
confirm.
- If blank and you have no web access: say so in one line at the top, then use only tools
you are confident currently exist. Do NOT invent tools, features, or prices. Mark prices
"verify live" and leave out anything you are unsure about.
- Tell the user to confirm every competitor name and price before publishing.
## Output in THREE clearly separated blocks:
=== BLOCK 1: SEO FIELDS (paste into your CMS / SEO plugin) ===
- SEO Title: starts with the item number + primary keyword; add the year if freshness
helps; optional benefit clause after a colon; under 60 chars.
- URL slug: kebab-case, contains the primary keyword, no year
- Meta description: 150-160 chars, stands alone, leads with the payoff
- Focus keyphrase: the primary keyword
- Tags/keywords: the 5-6 phrases
- Featured-image alt text: descriptive, includes the primary keyword naturally
=== BLOCK 2: ARTICLE (paste into the post body) ===
Markdown. Follow this listicle arc:
1. Hook intro, NO heading, 2 short paragraphs. Open on the real problem behind the search (not
the list yet). Bold the key number/promise. Do NOT restate the title.
2. "## [The exact question a user types]? (Quick answer)" - first sentence is a BOLD, self-
contained 40-60 word answer naming the top 1-2 picks and the criterion. This is the featured-
snippet target.
3. Roundup only: right after the quick answer, a one-line transparency blockquote (you rank your
own product #1; competitor notes are fair and general; readers should verify pricing).
4. "## The [N] [items] (compared)" - start with a SUMMARY TABLE, then the breakdown. Roundup
table columns: Item | Best for | Standout | Free plan | Price (verify), with the product as row
1.
5. The list. Each item is a "### N. Name, best for X / why it works" subhead, then: a BOLD one-
line verdict first; 2-4 sentences of specific, opinionated detail; item #1 IS the product;
competitors ordered by genuine fit, with Best-for / Standout / one honest Watch-out. Vary item
lengths slightly.
6. One value-add section that isn't just the list ("## How to choose based on your stage") - a
table or short framework the reader keeps.
7. "## Where [the product] fits" - the product as the natural next step, ONLY here, after value
is delivered. Real features only.
8. "## The bottom line" - reframe the core idea in 1-2 punchy paragraphs; end forward-looking
(never "In conclusion / In summary").
9. Final line: 2-4 contextual internal links (descriptive anchor text) + one soft product CTA.
Keyword placement: primary keyword in title, H1, first paragraph, Quick-answer H2, and 2-4 more
times in the body. Supporting keywords as H2s and in FAQ questions. Minimum 1,000 words.
=== BLOCK 3: FAQ (add via your CMS's FAQ block so it emits FAQ schema) ===
5-6 Q&A pairs. Questions as real search queries ("best", "cost", "free", "vs" variants). Answers
40-70 words, self-contained, leading with the direct answer.
## Voice
Sharp, generous founder. Second person. Concrete numbers, named examples, real scenarios. Vary
rhythm. Take sides. Contractions freely.
## Anti-AI rules (non-negotiable)
- ZERO em-dashes in prose. - No filler: Moreover, Furthermore, Additionally, That said, It's
worth noting, Importantly, Ultimately. - No throat-clearing openers. - No "In conclusion / In
summary." - Vary item length/shape. - No vague intensifiers. - Never fabricate stats, quotes,
names, or competitor facts/pricing. Mark prices "verify live". - Read it aloud; if it sounds
like a press release, rewrite shorter and blunter.
Write all three blocks now.Pre-publish checklist
- [ ] Every competitor name confirmed to still exist
- [ ] Every price checked live and updated
- [ ] Own product is #1, with only real features claimed
- [ ] FAQ added via the CMS FAQ block (schema emitting)
- [ ] 2-4 internal links point to live posts
By Praveen Jha | praveenjha.com. Pages 7-8 together are the working prompt to paste into Claude; pages 4-5 explain each arc step in full.