gilde

← All craftbooks

SEO Blog Post

Content and writingevalv1.0.0released 2026-06-05workflow: build-loop

Write a complete, SEO-aware blog post that ranks and reads well: it locks the primary keyword, search intent, target reader, and a heading-by-heading outline FIRST, then drafts the full article in a single human voice with the keyword woven naturally into the title, intro, and H2s, and finally runs an editorial pass for clarity, flow, factual accuracy, and on-page SEO. Covers blog article, SEO content, how-to guide, listicle, thought-leadership post, content marketing, and organic-traffic writing. The scope-first ordering is the point: a small model that picks the keyword and outline before drafting avoids the classic failure of a rambling post that buries its topic and never satisfies the searcher's intent.

Steps

Entry step: keyword-scope. Each step names the specialist role it wants; the full working prompt is expandable.

  1. Keyword & outline scopeplannerentry

    lock the primary keyword, intent, reader, and H2 outline

    Show working prompt
    1) Identify the PRIMARY keyword/phrase the post targets and the matching search intent (informational, comparison, how-to, or commercial). 2) Define the target reader in one sentence (who they are, what they already know, what they want to leave with). 3) List 3-5 secondary keywords/related terms to weave in naturally. 4) Write the working title (must contain the primary keyword, ideally near the front) plus a 1-sentence meta description under 155 characters. 5) Produce a heading-by-heading outline: H1 (title), a hook intro, 4-7 H2 sections each with a one-line summary of what it covers, and a closing/CTA section. 6) Set the target word count (e.g. 1200-1600) and reading level. Write an acceptance-criteria checklist (e.g. 'primary keyword appears in title, first 100 words, and at least 2 H2s'; 'every outlined H2 is covered'; 'single consistent voice, no AI filler phrases like "in today's fast-paced world"'; 'ends with a clear CTA'; 'within target word count +/-15%'). Use write_task_note to record the keyword strategy, outline, and checklist, and write the same content to the produces path. No prose drafting yet.
  2. Draft the articlecopywriter

    write the full post to the locked outline and keyword plan

    Show working prompt
    Write the complete article to the locked outline. 1) Open with a hook intro (2-3 sentences) that names the reader's problem and previews the payoff; place the primary keyword in the first 100 words. 2) Write every outlined H2 section in full prose with concrete examples, short paragraphs (2-4 sentences), and lists where they aid scanning. 3) Weave secondary keywords in naturally — never keyword-stuff. 4) Use one consistent, specific voice; cut filler and hedging. 5) Close with the CTA section from the outline. 6) Output GitHub-flavored markdown with the H1 title at top, proper H2/H3 headers, and the meta description as an HTML comment or front-matter line at the top. Write the full post to the produces path and use write_task_note to record word count and which checklist items you believe pass.
  3. Editorial passreviewer

    tighten clarity, flow, accuracy, and on-page SEO

    Show working prompt
    Edit the draft in place against the checklist. 1) Read top to bottom for flow: does each section follow logically, are transitions smooth, is the voice consistent? 2) Cut every filler phrase, redundancy, and hedge; tighten long sentences. 3) Verify on-page SEO: primary keyword in title, first 100 words, and >=2 H2s; meta description present and under 155 chars; headings are descriptive. 4) Fact-check any concrete claim and flag/remove anything you cannot stand behind. 5) Confirm word count is within target and the CTA is clear. Rewrite weak passages directly rather than just commenting. Save the polished version back to the produces path and note any criteria still unmet.
  4. Evaluatereviewer

    Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.

    Show working prompt
    Read the final blog-post.md end to end and grade against the locked checklist. Check EACH criterion and write PASS/FAIL with a one-line reason: (a) primary keyword in title, first 100 words, and >=2 H2s; (b) every outlined H2 is present and substantive; (c) single consistent voice with no AI-filler phrases; (d) meta description present and under 155 characters; (e) clear CTA at the end; (f) word count within target +/-15%; (g) no unsupported factual claims. A post that is fluent but ignores the keyword plan or drops outlined sections FAILS.

Then route — this is the whole point of the loop:

- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`.
- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "draft" })` to loop back. The builder fixes exactly those gaps.

Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.
  5. Finishdeveloper

    All acceptance criteria met. Stamp a short summary and report DONE.

    Show working prompt
    Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.

Triggers

Phrases that suggest this craftbook to a crew.

Source

View this craftbook on GitHub · MIT license