Claude AI Prompts for Blog Writing
If you’ve typed “write a blog post about [your topic]” into Claude and gotten back something flat, generic, and kind of… corporate-sounding, I want to stop you right there. That’s not a Claude problem. That’s a prompt problem.
I’ve been using Claude as my primary writing partner for this entire blog, and the difference between the posts I get now and the posts I got when I first started is entirely down to how I write my Claude AI prompts for blog writing. Not the tool. The instructions I give it.
This post is going to show you exactly what changed, the specific pieces a good blog-writing prompt needs, why vague requests can’t produce anything but generic output, and a real prompt structure (a simplified version of the one I actually use) that you can copy and adapt today.
No fluff. Let’s get into it.
Why Vague Prompts Produce Generic Content
Here’s the thing people miss: Claude isn’t guessing what you want. It works with exactly what you give it. If you type “write a blog post about how to start a blog,” you’ve given it a topic and nothing else. No audience. No voice. No structure. No angle.
So it does the only reasonable thing it can do: it writes the average version of that post. The version that could have been written by anyone, for anyone, based on the most common patterns of “how to start a blog” content that exists. That’s not Claude failing you. That’s Claude accurately reflecting how little direction it was given.
Think of it this way: if you hired a freelance writer and said “write me something about blogging,” you’d get back something generic too. Writers need a brief. Claude needs one even more, because it has zero context about your brand unless you hand it to it in the prompt itself.
The good news is that once you understand this, fixing it isn’t complicated. You just need to know what to actually include.
The Elements a Good Blog-Writing Prompt Needs
A prompt that produces content that sounds like you, not like generic AI filler, needs to cover six things. Miss any of these, and you’ll feel the gap in the output.
1. Audience
Who is this post actually for? “Beginners” isn’t specific enough on its own. Are they beginners who’ve never touched WordPress, or beginners who have a blog but no traffic? Tell Claude exactly who’s reading, including what they already know and what’s still confusing them. This shapes vocabulary, pacing, and what needs explaining versus what can be assumed.
2. Your Angle or Real Experience
This is the single biggest lever for making content sound human. Generic AI writing has no lived experience behind it; it’s synthesizing patterns, not recalling what actually happened. When you feed Claude your real experience (a mistake you made, a specific result you got, or an opinion you formed after doing the thing), it has actual material to work with instead of defaulting to generic advice.
I cover this in more depth in How I Use AI to Write Blog Posts Faster Without Sounding Robotic. The short version is that AI can’t invent your personal experience, so if you don’t give it to Claude, it won’t show up in the post.
3. What NOT to Do
This one gets skipped constantly, and it’s one of the most useful parts of a prompt. Tell Claude explicitly what to avoid: no hype words, no “in today’s fast-paced digital world” openers, no fake enthusiasm, no generic listicle filler, and no claiming things you haven’t tested. Negative instructions narrow the output as much as positive ones do.
4. Structural Requirements
Don’t leave structure to chance. Specify your headings, whether you want a FAQ section, how long the intro and conclusion should be, and whether you want numbered steps, subheadings, or a specific flow. If your blog has a format readers expect, spell it out.
5. SEO Requirements
If ranking matters to you (and it should), give Claude the focus keyword, where it needs to appear (first 100 words, meta description, naturally through the body), your URL slug preference, and your tags. Also tell it which of your existing posts to link to, by actual name, not “insert relevant internal link here.” Claude can’t guess your own back catalog; you have to supply it.
6. Output Format
Tell Claude exactly how you want the final piece delivered: Markdown, a specific word count range, SEO metadata up top, whatever matches your workflow. This saves you from reformatting everything by hand afterward.
Once a prompt has all six of these, Claude isn’t writing “a blog post about blogging” anymore; it’s writing your post, for your reader, in your voice.
Why Specificity Is What Makes It Sound Like You
I want to push on this point because it’s the part people underestimate. A lot of bloggers think “sounding like AI” is a tone problem, like there’s a setting somewhere that makes writing sound robotic, and if you could just find the right words, it’d disappear.
It’s not a tone problem. It’s an information problem.
Generic AI writing sounds generic because it’s built from generic input. When I write a prompt for The Income Plug, I don’t just say, “Write in a confident, no-hype voice.” I tell Claude to use “I” instead of “we,” because this is a personal brand, not a company. I tell it not to write like someone who just discovered the topic; I’ve been doing this, and the post needs to read that way. I give it the actual mistake I made or the actual result I got, so there’s something real to anchor the post to instead of generic advice.
That specificity is what separates a post that sounds like a template from a post that sounds like a person. Claude will use whatever voice guidance and real detail you give it; the quality ceiling is set by what you put into the prompt, not by some hidden limitation in the model.
If you’re still deciding whether Claude is even the right tool for this compared to other options, I broke that down in Best AI Writing Tools for Beginner Bloggers.
A Real Prompt Structure You Can Copy and Adapt
Here’s a simplified version of the structure I actually use, genericized so you can adapt it to your own blog and voice. Copy this, fill in your own details in the brackets, and adjust.
Write a blog post titled "[YOUR TITLE]" for [YOUR BLOG NAME].
AUDIENCE: [Who exactly is reading this — their experience
level, what they already know, what they’re confused about]
MY REAL EXPERIENCE TO INCLUDE: [A specific thing that
happened to you related to this topic — a mistake, a result,
a number, an opinion you formed from doing it]
BRAND VOICE (NON-NEGOTIABLE):
– [e.g., Honest and practical, no hype]
– [e.g., Confident, not a beginner discovering things]
– [e.g., “I” not “we” — this is a personal brand]
– [e.g., Plain English, explain any jargon]
WHAT NOT TO DO:
– No generic AI-sounding openers
– No overused phrases like “in today’s digital world”
– No claims I haven’t actually tested
– No fake urgency or hype language
STRUCTURE:
– [Your heading requirements]
– FAQ section with at least [X] questions before the conclusion
– Conclusion of at least [X] words summarizing the post
SEO REQUIREMENTS:
– Focus keyword: “[your keyword]”
– Keyword in first 100 words and in the meta description
– Keyword used naturally throughout, not stuffed
– Suggested URL slug
– Suggested meta description
– Suggested tags
– Link naturally to these existing posts of mine where
relevant: “[Post Title 1]”, “[Post Title 2]”
OUTPUT FORMAT:
– Full post in Markdown
– [Your target word count]
– SEO title, meta description, keyword, slug, and tags at
the top
That’s it. It looks like a lot the first time you write it out, but once you have a template like this saved, you’re just swapping in the topic, the real experience, and the specific posts to link to each time. The brand voice and structural rules stay the same across every post.
If you want to see how this looks when it’s filled in and applied to an entire content workflow, I go through that in Claude for Blogging.
For the official reference on how Claude handles instructions like this, Anthropic’s own prompt engineering documentation is worth a look; you can find it in Anthropic’s prompt engineering guide.
Does This Guarantee the Post Will Rank?
Not on its own, and I want to be upfront about that before we get to the FAQ. A well-structured prompt gets you a well-structured, on-topic, keyword-optimized draft. Whether it actually ranks depends on other factors too: competition for that keyword, your site’s existing authority, backlinks, and how well the post answers what people are actually searching for. I go into that distinction in more detail in Can AI Write Blog Posts That Actually Rank on Google? Worth reading if ranking is your main goal here, not just producing content faster.
FAQ
Do I need to write a prompt this detailed every single time? Not from scratch. Once you’ve built your core template, your brand voice rules, your SEO requirements, and your structural preferences, you save it and just swap in the topic, your real experience for that post, and which existing posts to link to. The bulk of the work is a one-time setup.
What if I don’t have “real experience” to add for every topic? You almost always have more than you think. It doesn’t have to be a dramatic story; it can be a specific number (how long something took you), an opinion you formed, a mistake you noticed other people making, or a detail about how you personally do the thing. Even a small specific detail beats no detail at all.
Will Claude actually follow all these instructions, or does it ignore some of them? In my experience, the more specific and structured the prompt, the more consistently Claude follows it. Vague instructions get vague adherence. If something isn’t showing up in the output, say, the FAQ section or a specific word count, it usually means that requirement needs to be stated more clearly, not buried in a paragraph of other instructions.
Can I use this same prompt structure for other AI writing tools, not just Claude? The underlying principles — audience, real experience, what not to do, structure, SEO requirements, output format, and applying to any AI writing tool. The specific wording and how well it’s followed will vary by tool, but the framework itself isn’t Claude-specific.
How long should my blog-writing prompt actually be? Long enough to cover all six elements, short enough that you’re not repeating yourself. Mine typically run several paragraphs to a full page, depending on the post. Don’t worry about hitting a target length; worry about whether you’ve actually included audience, voice rules, real experience, what to avoid, structure, and SEO requirements. If those are covered, the prompt is doing its job.
Do I need to give Claude my entire back catalog of posts every time I want internal links? No, just the two to four posts that are genuinely relevant to the topic at hand. Naming them specifically (not “link to a relevant post”) is what matters. Claude can’t guess your own site’s content or guess at URLs it hasn’t been given, so you have to supply the actual titles yourself.
Conclusion
The gap between generic AI content and content that sounds like an actual person isn’t about which AI tool you use; it’s about what you put into the prompt. Claude AI prompts for blog writing that actually work give it something to work with: a specific audience, your real experience, clear rules about what to avoid, a defined structure, your SEO requirements, and the exact output format you need. Skip any of these, and you’re left with the same flat, average-sounding output that gave AI writing its bad reputation in the first place.
The template in this post is a starting point, not a rulebook. Adapt the brand voice section to match how you actually talk. Swap in your own posts for the internal links. Add or remove structural requirements based on what your blog needs. The goal isn’t to follow this exactly;; it’s to understand why each piece matters so you can build a prompt structure that consistently produces content sounding like you, post after post.
Once you’ve got a template that works, the actual writing part gets a lot faster and a lot less frustrating.
