Write a blog post for [TARGET AUDIENCE] targeting the primary keyword [TARGET KEYWORD]. The reader is trying to solve this problem: [READER PROBLEM]. Use these source notes, product facts, examples, or links as the only factual basis: [SOURCE MATERIAL]. The desired action after reading is [READER NEXT STEP]. First, infer the likely search intent from the keyword and state it in one sentence. Then write the article. Requirements: 1. Create a specific title that includes the primary keyword naturally. Write a 120-155 character meta description and a short introduction that identifies the reader's problem and previews the practical answer. 2. Use an H2-led outline that answers the main question early, then explains the decision criteria, process, examples, exceptions, and next steps in the order a reader needs them. Do not force exact-match keywords into every heading. 3. Include one practical checklist, table, or numbered process where it helps the reader act. Use concrete examples drawn only from the source material; label a hypothetical example as hypothetical. 4. Address at least two common mistakes, tradeoffs, or edge cases relevant to this topic. Avoid unsupported statistics, claims of guaranteed results, filler introductions, and generic advice such as "optimize your strategy." 5. End with a concise conclusion and a relevant next step, not a repetitive summary. Output: title, meta description, suggested URL slug, article outline, then a 1,000-1,400 word draft in Markdown. Before finalizing, check that every material claim is supported by the source material or clearly framed as general guidance. Also check that each section helps answer the reader's stated problem; cut sections that only repeat the keyword. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TARGET AUDIENCE] | Describe the people the post is for and their relevant level of experience. | First-time managers at US software companies |
| [TARGET KEYWORD] | Enter the main Google search phrase the article should target. | how to run a one-on-one meeting |
| [READER PROBLEM] | State the practical question or problem the searcher needs solved. | They need a repeatable meeting format that surfaces blockers without turning into a status update. |
| [SOURCE MATERIAL] | Paste verified notes, links, product details, examples, or research the article may use. | Our managers use a 30-minute weekly format: employee agenda first, priorities, obstacles, feedback, and documented follow-ups. Managers should not use it for performance ratings. |
| [READER NEXT STEP] | Describe the sensible action you want readers to take after the article. | Download the meeting agenda template or adapt the structure for their next one-on-one. |
How to use
- Paste the target keyword, reader problem, and only source material you can stand behind.
- Keep the inferred intent if it matches the searcher; correct it before asking for a draft if it does not.
- Check the opening and every H2 against the reader problem, then remove sections that add no decision or action.
- Follow up with: "Rewrite the examples for [AUDIENCE] and keep every claim limited to my source material."
Variations
Product comparison
Use this when readers are choosing between options.
Write a comparison post targeting [COMPARISON KEYWORD] for [AUDIENCE]. Compare [OPTION A] and [OPTION B] using only [VERIFIED FACTS]. Start with who each option suits, then use a criteria table covering [DECISION CRITERIA], limitations, and switching costs. Include a recommendation by use case, not one universal winner. Produce a title, meta description, outline, and 900-1,200 word draft. Flag any comparison point unsupported by my facts. Ask up to 3 questions only if required inputs are missing.
Expert interview
Use this when your article is based on a recorded interview.
Turn this interview material, [INTERVIEW NOTES], into a 900-word article for [AUDIENCE] targeting [KEYWORD]. Preserve the speaker's meaning and mark direct quotations only where exact wording is supplied. Organize it around [CENTRAL QUESTION], with an opening insight, three themed sections, practical takeaways, and a conclusion. Do not invent quotes, credentials, or examples. Output a title, meta description, outline, and draft. Check that every attributed statement appears in the notes. Ask up to 3 questions only if a needed input is absent.
Content refresh
Use this when an existing post needs a more useful update.
Audit and rewrite this existing article: [CURRENT DRAFT]. It targets [KEYWORD] for [AUDIENCE], and these are the verified updates to include: [NEW FACTS]. Keep accurate material that still serves the reader, remove stale or repetitive sections, and add missing decision criteria or steps. Output a brief change log followed by a 1,000-1,300 word replacement draft with title and meta description. Flag claims that need a source rather than repairing them with invented facts. Ask up to 3 questions only if required inputs are missing.
Tips
- Choose one primary keyword with a clear reader task; an article cannot satisfy informational research and a purchase-ready comparison equally well.
- Give the model source notes before asking for examples, especially for pricing, product capabilities, legal claims, and statistics.
- A useful heading changes what the reader understands or does; replace headings that merely restate the keyword.
- Treat the first draft's fact flags as an editorial to-do list, not permission to publish unsupported claims.
FAQ
How long should an AI-written blog post be?
Match length to the question, not a fixed SEO target. A simple process may need 800 words, while a comparison with real criteria may need more.
Can AI add statistics to my post?
Only if you provide reliable sources or independently verify them. This prompt tells the model to flag unsupported claims instead of inventing proof.
Should I use the target keyword in every heading?
No. Use it naturally in the title, opening, and relevant headings; reader-oriented subtopics usually create a better article structure.