// how to
How to Write a Blog Post with Claude That's Worth Reading
Start with something only you know: a question customers ask, a mistake you’ve seen, a result you got. Let Claude interview you about it, turn your answers into an outline, then draft section by section. Edit for your voice and check every fact before publishing.
The short version
The internet doesn’t need another generic post; it needs your experience. Claude is a great interviewer and drafter, but the stories, examples and opinions have to come from you. That’s also what Google’s guidance rewards: helpful, people-first content.
Step by step
- Pick a real question a customer asked you, ideally more than once.
- Let Claude interview you about it (prompt below). Answer in your own words; rough is fine.
- Ask for an outline with a headline that answers the question.
- Draft one section at a time, so you can steer each part.
- Add your specifics: a real example, a number, a photo, a mistake you made.
- Edit and fact-check. Read it aloud; cut anything that sounds like everyone else.
Prompts to copy
The interview:
I want to write a blog post answering: "[customer question]". I'm a [your role] with [experience].
Interview me one question at a time to get the useful details only I would know:
examples, mistakes, numbers, opinions. Ask at least 6 questions.
The outline:
From my answers, make an outline. Headline: answers the question directly.
Intro: 2 sentences with the answer. Then 4-6 sections, each with the point it makes.
One section:
Draft section 2 in my voice, using only what I told you. About 200 words.
Write [EXAMPLE NEEDED] where a real example would help.
Example
A roofer’s post “How long does a roof replacement take?” becomes useful when it includes his real answer (“2-3 days for most homes here, but we’ve waited a week for the right shingles”) and what slows it down. No generic post has that.
Mistakes to avoid
- Starting with “write a blog post about X”. You’ll get the same post as everyone else.
- Invented statistics. Ask for [SOURCE NEEDED] markers and find real figures.
- Publishing 20 similar posts at once. Quality beats volume; Google’s spam policies target content made at scale mainly to rank.
When not to use it
When the post’s value is your personal opinion or story, write the draft yourself and use Claude only to edit. See edit your writing with Claude.
Frequently asked questions
Does Google penalize AI-written blog posts?
Google's guidance is about whether content is helpful, reliable and made for people, not about whether AI was used. Generic posts made mainly to rank don't do well; posts with real experience and useful detail can.
How long should a blog post be?
Long enough to fully answer the question, and no longer. Many good how-to posts are 600 to 1,500 words.
Free download
Get the AI Coding Starter Kit
A PDF you can use with any AI coding assistant: a project-rules template, 25 tested prompt patterns, a team adoption checklist and an assistant comparison sheet. The editable Markdown sources are included.
- Works with Copilot, Claude Code, Codex, Cursor and more
- Double opt-in, one-click unsubscribe
- No trackers, never shared