---
name: blog-post-anatomy
description: Draft or check a blog post that answers one buyer question, built so a person can skim it and an AI tool can quote it. Use when the user is writing, editing or reviewing a blog post or article for their company website.
---

# Blog post anatomy

A good post answers one question for one buyer. You build it so a person can skim it and an AI tool can quote it.

## Read these first

- `context/buyer.md`
- `context/voice.md`
- `context/proof.md`

## Before you write

Ask for the one question the post answers, and the turning point it belongs to. If the user gives you two questions, that's two posts. Say so.

## The parts, from the top down

1. **The title.** The buyer's question, in the buyer's words.
2. **The answer.** The first 40 to 90 words answer the question. If a reader stops here, they still leave with something.
3. **The name and the date.** Who wrote it, and when it was last updated. Both show on the page.
4. **The method.** Your way of doing this, with a name a reader can repeat.
5. **The proof.** A customer story, or numbers that say where they came from.
6. **The subheadings.** Each one is a question or a plain statement. A reader should be able to follow the post from the subheadings alone.
7. **The buyer's questions.** Three to five questions a buyer would type, each with an answer that makes sense on its own.
8. **The line.** One sentence near the end that says who does this work and who it's for.
9. **The next step.** One, and only one.
10. **The links.** One up to the service or guide the post supports. One or two across to related posts.

## Behind the page

| Part | What to do |
|---|---|
| Title for search results | Match it to the search you want. Count the characters, and count anything your site adds to the title on its own. |
| Description | 150 to 160 characters that say what the post answers. No two pages share one. |
| Web address | A few plain words that describe the page. |
| Pictures | Photos of real work, placed near the words they support. Give each one a short description for readers who can't see it. |
| Code | Any code that tells machines what the page says has to match the words on the page, word for word. Treat it as housekeeping. |

## Before it's published

Run this check and show the result.

- The post answers one question for one buyer.
- Every number says where it came from.
- Every client fact is approved.
- The post links up to a main page, and at least one related page is ready to link to it.
- You've read it out loud once.

## Rules

- Make the post long enough to answer the question in full, and no longer. Google says there's no ideal word count.
- Use only proof from the proof file. Don't invent a name, a number, a quote or a result.
- Any code that tells machines what the page says has to match the words on the page, word for word.
- One post a week, never a batch. Keeping the slot matters more than polishing the post.

---

From The search playbook by Wit & Craft. witandcraft.com
