Write an original, genuinely useful article for people searching [TARGET KEYWORD]. The article must satisfy the search intent without padding, invented research, or claims that cannot be supported. Target keyword and likely intent: [TARGET KEYWORD] Reader, publication, and goal: [AUDIENCE AND GOAL] Facts, sources, and product context I can support: [SOURCE NOTES] Required angle, examples, or points to cover: [CONTENT REQUIREMENTS] Length, voice, and publishing constraints: [EDITORIAL REQUIREMENTS] First infer the primary reader question and any secondary questions this article should answer. Then produce: 1. A one-sentence search-intent statement and a proposed H1. 2. A skimmable outline with H2s and only useful H3s. Put the direct answer or definition near the beginning. Order sections by the reader’s decision or workflow, not by keyword variants. 3. The finished article in [EDITORIAL REQUIREMENTS], with a 40–60 word introduction, clear transitions, concrete examples where supported, and a conclusion that tells the reader what to do next. Use the target keyword naturally in the title, introduction, and one relevant subheading; do not force repetitions. 4. A short source and claim note listing every factual claim that needs citation, plus suggested source types if [SOURCE NOTES] does not support it. Do not manufacture statistics, quotes, case studies, expert opinions, product capabilities, or search results. Do not use vague filler such as “it is important to note.” Before answering, check that each section advances the reader’s intent and that all factual claims are supported by [SOURCE NOTES] or clearly marked for verification. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TARGET KEYWORD] | Enter the main search phrase and its likely informational, commercial, or transactional intent. | how to create an employee onboarding checklist — informational intent |
| [AUDIENCE AND GOAL] | Describe the reader, publication, desired outcome, and what they need to decide or accomplish. | HR managers at companies with 50–500 employees who need a repeatable first-30-days process. |
| [SOURCE NOTES] | Paste approved facts, links, research notes, subject-matter input, and product details you can verify. | Our HR lead recommends preboarding, first-day access, role expectations, 30-day goals, and manager check-ins. We can cite the company handbook but have no survey data. |
| [CONTENT REQUIREMENTS] | List required points, examples, internal links, competing angles to avoid, and any claims that need careful treatment. | Include a downloadable-checklist mention, distinguish HR tasks from manager tasks, and avoid legal advice about employment classification. |
| [EDITORIAL REQUIREMENTS] | State target word count, voice, formatting rules, reading level, and citation or style requirements. | 1,300–1,600 words, practical and calm, short paragraphs, US English, no unsupported statistics. |
How to use
- Paste source notes that can actually support the article’s facts, especially product claims and examples.
- Check the intent statement and outline before accepting the draft; the opening should answer the searcher’s first question quickly.
- Review the claim note and add citations or remove claims before publication.
- Follow up with: “Rewrite the outline for a reader who already knows the basics and needs a comparison framework before choosing an approach.”
Variations
Article outline only
Use this when you need to approve information architecture before drafting.
Create an article outline for [KEYWORD] for [AUDIENCE]. The article’s job is to help readers [READER TASK]. Use only these verified notes: [SOURCES]. Provide an intent statement, H1, 6–9 H2s, useful H3s, and the question each section answers. Include a suggested internal-link placement. Do not draft prose or invent supporting claims. Check that the structure follows the reader’s workflow rather than repeating keyword variations.
Expert interview article
Use this when the article will be built from an interview or transcript.
Turn this interview material, [TRANSCRIPT], into a [LENGTH] article about [TOPIC] for [AUDIENCE]. Build the article around the interviewee’s supported insights, not a transcript recap. Create an H1, an opening that names the reader problem, 4–6 themed sections, and a conclusion. Attribute direct quotes accurately and use short excerpts only. Flag assertions that need external verification or a follow-up question; do not fabricate quotes.
Content refresh brief
Use this when an existing article needs a substantive update.
Assess and refresh this existing article: [CURRENT ARTICLE]. Its target query is [KEYWORD], and these are new verified facts or requirements: [UPDATED NOTES]. Produce a refresh brief with sections to keep, remove, combine, rewrite, or add; then draft only the changed sections. Identify claims that have become unsupported or dated. Preserve useful original material where accurate. Check that the revision better answers the current reader intent without adding unsupported data.
Tips
- Start with the reader’s immediate task, not a broad history of the topic; searchers usually need a definition, decision, or process first.
- Use source notes to constrain examples and claims, because plausible-sounding invented statistics are harder to catch after copyediting.
- Make each H2 answer a distinct question; two headings that lead to the same advice should usually be combined.
- Treat the keyword as a routing signal, not an instruction to repeat an exact phrase throughout the body.
FAQ
Will an AI-written article rank in search?
Ranking depends on usefulness, accuracy, topical fit, technical SEO, and competition. A draft needs editorial judgment and source verification before it is published.
How many times should I use the target keyword?
There is no reliable fixed number. Use it where it naturally identifies the topic, then use precise related language that helps readers understand the subject.
Can AI provide sources for an article?
It can suggest research directions, but verify each source and claim yourself. Do not cite a source solely because an AI says it exists or supports a statement.