30 Claude Prompts That Write Full Blog Posts

You are a comparison-content writer who helps readers decide between two options fairly. <context> I need a head-to-head comparison blog post written as one self-contained Markdown artifact, complete and ready to publish, that compares two options and gives a clear verdict. </context> <inputs> - The two options: [OPTION A] vs [OPTION B] - What they're used for: [USE CASE] - Comparison criteria that matter: [PRICE, FEATURES, EASE, SUPPORT, ETC] - Target reader and their priorities: [AUDIENCE] - Primary keyword: [E.G. "A VS B"] - CTA or affiliate model: [NEXT STEP] </inputs> <task> Write the full comparison: three title options, a meta description, a quick-verdict box up top for skimmers, an intro framing who each option suits, a side-by-side comparison table on the key criteria, an H2 deep-dive per criterion weighing both, a "best for" breakdown by use case, an honest "the catch" for each, an FAQ, and a closing CTA. Stay balanced and recommend based on reader type, not blanket winner. </task> <constraints> - One Markdown file; give a clear verdict but justify it by use case, not bias. - Render the comparison as a Markdown table; cover the criteria I listed. - Keyword in title and intro; scannable; quick verdict above the fold. </constraints> <format> Return the complete comparison as a Markdown artifact, then note which option you recommended for each reader segment and why. </format>

You are a content writer who writes "best alternatives to X" posts that capture switcher intent. <context> I need an alternatives blog post written as one self-contained Markdown artifact, complete and ready to publish, that presents strong alternatives to a popular tool or product. </context> <inputs> - The product people are leaving: [X] - Why they look for alternatives: [PAIN POINTS WITH X] - The alternatives to feature: [LIST WITH A NOTE EACH] - Target reader: [AUDIENCE] - Primary keyword: [E.G. "X ALTERNATIVES"] - CTA or affiliate model: [NEXT STEP] </inputs> <task> Write the full post: three title options, a meta description, an intro acknowledging why people seek alternatives to X, a quick "who X is and isn't right for" frame, each alternative as an H2 with a best-for label, how it compares to X, key strengths, drawbacks, and pricing, a comparison table, a "how to choose" guide, an FAQ, and a closing CTA. Be specific about which alternative wins for which need. </task> <constraints> - One Markdown file; each alternative has a distinct angle versus X, no generic praise. - Acknowledge what X does well so the post reads credible, not like a hit piece. - Keyword in title and intro; render the table in Markdown; scannable. </constraints> <format> Return the complete post as a Markdown artifact, then note which alternative you'd position as the top pick and the migration angle to emphasize. </format>

You are an honest reviewer who writes in-depth product or service review posts. <context> I need a review blog post written as one self-contained Markdown artifact, complete and ready to publish, that gives a balanced verdict on one product or service. </context> <inputs> - The product or service: [WHAT YOU'RE REVIEWING] - Who it's for: [TARGET USER] - Your hands-on experience or angle: [WHAT YOU KNOW] - The pros and cons: [STRENGTHS AND WEAKNESSES] - Pricing and key features: [DETAILS] - Primary keyword and CTA: [E.G. "X REVIEW", NEXT STEP] </inputs> <task> Write the full review: three title options, a meta description, a verdict-and-rating box up top, an intro on what it is and who it's for, H2 sections on features, ease of use, pricing value, and support, a clear pros and cons list, a "who should and shouldn't buy it" breakdown, alternatives mention, an FAQ, and a closing CTA. Be specific and honest, citing concrete details. </task> <constraints> - One Markdown file; balanced verdict with real cons, not a sales page in disguise. - Use concrete examples and specifics; include the rating and verdict above the fold. - Keyword in title and intro; scannable structure; pros/cons as clean lists. </constraints> <format> Return the complete review as a Markdown artifact, then note the rating you assigned and the single biggest factor behind it. </format>

You are a content writer who writes buyer's-guide posts that help readers make a confident purchase. <context> I need a buyer's-guide blog post written as one self-contained Markdown artifact, complete and ready to publish, that teaches readers how to choose within a product category. </context> <inputs> - The category: [E.G. STANDING DESKS, CRM SOFTWARE] - Who's buying and their context: [AUDIENCE] - The factors that matter when choosing: [CRITERIA] - Price ranges or tiers: [BUDGET BANDS] - A few options to mention: [PRODUCTS, OPTIONAL] - Primary keyword and CTA: [KEYWORD, NEXT STEP] </inputs> <task> Write the full guide: three title options, a meta description, an intro on what readers will be able to decide after reading, a "key factors to consider" section with an H2 per factor and what to look for, a budget-tier breakdown of what you get at each price, a "questions to ask before buying" checklist, a quick top-pick mention if products are provided, an FAQ, and a closing CTA. Make it advice-first, not just a product pitch. </task> <constraints> - One Markdown file; teach the decision framework so the post helps even without buying your product. - Concrete guidance per factor; budget tiers with what each unlocks. - Keyword in title and intro; scannable; checklist in Markdown list format. </constraints> <format> Return the complete buyer's guide as a Markdown artifact, then note which decision factor most readers overlook and how you surfaced it. </format>

You are a content writer who writes targeted "best X for Y" posts that match a solution to a specific audience. <context> I need a use-case blog post written as one self-contained Markdown artifact, complete and ready to publish, that recommends the best options for one specific audience or scenario. </context> <inputs> - The format: [E.G. "BEST LAPTOPS FOR STUDENTS", "BEST CRMS FOR REALTORS"] - The specific audience and their constraints: [WHO AND WHY THEY'RE DIFFERENT] - The options to feature: [LIST WITH NOTES] - What "best" means for this group: [PRIORITIES] - Primary keyword and CTA: [KEYWORD, NEXT STEP] - The year: [2026] </inputs> <task> Write the full post: three title options, a meta description, an intro on why this audience's needs differ from the general case, a "what matters for this group" criteria box, each option as an H2 with a best-for-this-audience verdict, the audience-specific strengths and trade-offs, and pricing, a comparison table, a "our pick for [audience]" callout, an FAQ, and a closing CTA. Tailor every recommendation to the named audience. </task> <constraints> - One Markdown file; every pick is justified against this audience's specific needs, not generic quality. - Render the table in Markdown; name the audience throughout for relevance. - Keyword and year in title; scannable structure. </constraints> <format> Return the complete post as a Markdown artifact, then note the audience-specific angle that differentiates this from a generic roundup. </format>

You are a ghostwriter who turns a founder's or expert's point of view into a sharp thought-leadership post. <context> I need a thought-leadership blog post written as one self-contained Markdown artifact, complete and ready to publish, that stakes out a clear opinion and backs it up. </context> <inputs> - The core argument or hot take: [YOUR POSITION] - Why you believe it: [REASONING, EXPERIENCE] - The common view you're pushing against: [THE STATUS QUO] - Who needs to hear it: [AUDIENCE] - Your voice and credibility: [WHO YOU ARE] - CTA: [NEXT STEP] </inputs> <task> Write the full post: three title options (one provocative), a meta description, a hook opening that states the contrarian position, an H2 framing the conventional wisdom and why it falls short, the argument built across H2 sections each with reasoning and a real example or anecdote, a fair acknowledgment of the counterargument and your rebuttal, a "what this means for you" application, and a closing CTA. Write in a confident first-person voice. </task> <constraints> - One Markdown file; take a real stance, no fence-sitting or both-sides mush. - Support claims with reasoning and examples, not just assertion; address the obvious objection. - First-person voice; scannable; keyword woven in if provided. </constraints> <format> Return the complete post as a Markdown artifact, then note the strongest counterargument and whether you rebutted or conceded it. </format>

You are a narrative ghostwriter who turns real experiences into resonant lessons-learned posts. <context> I need a personal-story blog post written as one self-contained Markdown artifact, complete and ready to publish, that tells a true story and extracts useful lessons. </context> <inputs> - The experience: [WHAT HAPPENED] - The struggle or turning point: [THE TENSION] - The lessons you took away: [KEY LESSONS] - Who can learn from it: [AUDIENCE] - Your voice: [DESCRIBE] - CTA: [NEXT STEP] </inputs> <task> Write the full post: three title options, a meta description, an opening scene that drops the reader into the moment, the story told in narrative arc (setup, struggle, turning point, outcome), each major lesson surfaced in its own H2 with the takeaway generalized for the reader, a "what I'd tell my past self" reflection, and a closing CTA. Keep the story honest and specific; the lessons earn their place from the narrative. </task> <constraints> - One Markdown file; vivid, specific storytelling, not vague platitudes. - Lessons must flow from the story, never feel bolted on; first-person voice. - Scannable with a clear arc; keyword used naturally if provided. </constraints> <format> Return the complete post as a Markdown artifact, then note the emotional beat the story turns on and the lesson readers will remember most. </format>

You are a strategist who writes forward-looking predictions posts that position the author as an expert. <context> I need a predictions blog post written as one self-contained Markdown artifact, complete and ready to publish, that forecasts where an industry is heading and what to do about it. </context> <inputs> - The industry or topic: [DOMAIN] - The timeframe: [E.G. 2026, NEXT 3 YEARS] - Your predictions: [THE FORECASTS] - The signals behind them: [WHY YOU BELIEVE EACH] - Target reader: [AUDIENCE] - CTA: [NEXT STEP] </inputs> <task> Write the full post: three title options, a meta description, an intro on why now is the moment to look ahead, each prediction as an H2 with the forecast, the signals and evidence supporting it, a confidence read, and a "what to do about it" action, a "what won't change" grounding section, a summary of the boldest call, and a closing CTA. Make predictions specific enough to be falsifiable, not safe and vague. </task> <constraints> - One Markdown file; concrete, falsifiable predictions tied to real signals, not hype. - Pair every forecast with an action the reader can take now. - Timeframe in title; scannable; keyword used naturally if provided. </constraints> <format> Return the complete post as a Markdown artifact, then note the boldest prediction and how you'd defend it if challenged. </format>

You are a commentator who writes timely reaction posts that add a fresh angle to breaking news. <context> I need a news-commentary blog post written as one self-contained Markdown artifact, complete and ready to publish, that reacts to a recent development with a clear point of view. </context> <inputs> - The news or development: [WHAT HAPPENED] - The known facts: [WHAT'S CONFIRMED, AND SOURCES] - Your angle or take: [YOUR INTERPRETATION] - Why your audience should care: [RELEVANCE] - Target reader: [AUDIENCE] - CTA: [NEXT STEP] </inputs> <task> Write the full post: three title options, a meta description, a lead that summarizes what happened in two or three sentences with the source, an H2 on why it matters to the reader, your analysis and angle across H2 sections, a "what most people are missing" insight, a "what to watch next" forward look, and a closing CTA. Separate confirmed facts from your opinion clearly. </task> <constraints> - One Markdown file; only state facts I provide with their sources, label opinion as opinion. - Add a genuine fresh angle, not a rehash of the headline; timely and concise. - Keyword used naturally; scannable; lead with the news. </constraints> <format> Return the complete post as a Markdown artifact, then note the unique angle you took and one fact worth double-checking before publishing. </format>

You are a content writer who writes myth-busting posts that correct misconceptions with evidence. <context> I need a myth-busting blog post written as one self-contained Markdown artifact, complete and ready to publish, that debunks common misconceptions about a topic. </context> <inputs> - The topic: [SUBJECT] - The myths to bust: [LIST OF MISCONCEPTIONS] - The truth and evidence for each: [REALITY AND SUPPORT] - Why the myths persist: [ORIGIN] - Target reader: [AUDIENCE] - Primary keyword and CTA: [KEYWORD, NEXT STEP] </inputs> <task> Write the full post: three title options, a meta description, an intro on why these myths cause real harm, each myth as an H2 stating the misconception, why people believe it, the reality with evidence, and what to do instead, a "the truth in one line" recap per myth, a summary, and a closing CTA. Correct firmly but without condescension toward people who believed the myth. </task> <constraints> - One Markdown file; back every correction with reasoning or evidence I provide, no bare assertions. - Respectful tone; explain why the myth was believable before debunking it. - Keyword in title and intro; scannable; clear myth/reality contrast. </constraints> <format> Return the complete post as a Markdown artifact, then note the most stubborn myth and the single strongest piece of evidence against it. </format>

You are a content marketer who writes results-driven case-study posts that double as social proof. <context> I need a case-study blog post written as one self-contained Markdown artifact, complete and ready to publish, that tells a customer-success story with concrete results. </context> <inputs> - The customer or subject: [WHO] - Their challenge before: [THE PROBLEM] - What they did or used: [THE SOLUTION] - The measurable results: [METRICS, BEFORE AND AFTER] - A quote if available: [TESTIMONIAL] - Target reader and CTA: [AUDIENCE, NEXT STEP] </inputs> <task> Write the full case study: three title options (one with a result number), a meta description, a results-summary box up top (key metrics at a glance), an intro on the subject and stakes, a "the challenge" section, a "the approach" section detailing what was done, a "the results" section with specific numbers, a pull-quote, a "how to replicate this" takeaways section, and a closing CTA. Use the metrics I provide; lead with the outcome. </task> <constraints> - One Markdown file; only use the metrics and quotes I provide, never invent results. - Lead with the outcome; make the takeaways transferable to the reader's situation. - Result number in the title; scannable; quote formatted as a blockquote. </constraints> <format> Return the complete case study as a Markdown artifact, then note the single most compelling stat and where you placed it for maximum impact. </format>

You are a content marketer who writes blog posts that educate and convert toward a product. <context> I need a conversion-focused blog post written as one self-contained Markdown artifact, complete and ready to publish, that teaches genuinely useful information while naturally leading to my product. </context> <inputs> - The reader's problem: [PAIN POINT] - My product and how it helps: [PRODUCT AND BENEFIT] - The useful teaching the post delivers: [VALUE-FIRST CONTENT] - Target reader: [AUDIENCE] - Primary keyword: [KEYWORD] - The conversion goal: [TRIAL / DEMO / SIGNUP] </inputs> <task> Write the full post: three title options, a meta description, an intro on the problem and the promise, value-first H2 sections that solve the problem manually first (earning trust), a section where the product is introduced as the faster way (not a hard sell), a soft proof or example, a comparison of doing it manually versus with the product, an FAQ, and a closing CTA toward the conversion goal. Deliver real value before any pitch. </task> <constraints> - One Markdown file; the post is useful even for a reader who never buys; product mention is earned, not forced. - Educate first, pitch second; keep the CTA clear but not pushy. - Keyword in title and intro; scannable structure. </constraints> <format> Return the complete post as a Markdown artifact, then note where you placed the product mention and why that point earns the pitch. </format>

You are a brand storyteller who writes narrative customer-success stories that feel human, not corporate. <context> I need a customer-success-story blog post written as one self-contained Markdown artifact, complete and ready to publish, that reads like a profile rather than a sterile case study. </context> <inputs> - The customer and what they do: [WHO THEY ARE] - Their situation and frustration before: [THE STARTING POINT] - Their journey to a solution: [WHAT CHANGED] - The outcome and any numbers: [RESULTS] - A quote or two: [THEIR WORDS] - Target reader and CTA: [AUDIENCE, NEXT STEP] </inputs> <task> Write the full story: three title options, a meta description, an opening that introduces the customer as a person with a relatable goal, the narrative of their frustration and search for a fix, the turning point and what they did, the payoff with concrete outcomes, woven-in quotes in their voice, a "what readers in the same spot can learn" takeaway, and a closing CTA. Keep it warm and human while staying truthful to the facts I provide. </task> <constraints> - One Markdown file; profile-style narrative, not a bullet-point case study; only use facts and quotes I provide. - Center the customer, not the product; let the product appear as part of their story. - Scannable with a clear arc; quotes as blockquotes; keyword used naturally if provided. </constraints> <format> Return the complete story as a Markdown artifact, then note the human detail you led with and why it makes the story relatable. </format>

You are a competitive-content writer who writes honest us-versus-competitor posts that win switchers without trashing rivals. <context> I need an us-versus-competitor blog post written as one self-contained Markdown artifact, complete and ready to publish, that compares my product to a competitor and makes a fair case. </context> <inputs> - My product: [NAME AND POSITIONING] - The competitor: [NAME] - Where we genuinely win: [OUR STRENGTHS] - Where they're strong or better suited: [HONEST CONCESSIONS] - The criteria buyers care about: [CRITERIA] - Primary keyword and CTA: [E.G. "US VS THEM", NEXT STEP] </inputs> <task> Write the full comparison: three title options, a meta description, a fair-verdict box, an intro framing the choice honestly, a side-by-side comparison table, an H2 per criterion weighing both products, a candid "when [competitor] is the better choice" section to build trust, a "who we're built for" section, an FAQ addressing switching, and a closing CTA. Win on fit and honesty, never by misrepresenting the competitor. </task> <constraints> - One Markdown file; concede where the competitor is genuinely better to earn credibility. - Accurate claims only; render the comparison as a Markdown table; no straw-manning. - Keyword in title and intro; scannable; verdict box above the fold. </constraints> <format> Return the complete comparison as a Markdown artifact, then note the concession you made to the competitor and why it strengthens the post. </format>

You are an SEO writer who builds FAQ-style posts that capture People-Also-Ask and voice-search traffic. <context> I need an FAQ-style blog post written as one self-contained Markdown artifact, complete and ready to publish, that answers a cluster of related questions on one topic. </context> <inputs> - The topic: [SUBJECT] - The questions to answer: [LIST OF QUESTIONS, IDEALLY FROM PAA] - Target reader: [AUDIENCE] - Primary keyword: [KEYWORD] - Brand voice: [DESCRIBE] - CTA: [NEXT STEP] </inputs> <task> Write the full post: three title options, a meta description, a short intro framing the topic, each question as an H2 phrased exactly as people search it, with a concise direct answer in the first one to two sentences followed by a fuller explanation, a "related questions" mini-list, a key-takeaways box, and a closing CTA. Front-load each answer so it's snippet- and voice-search-friendly. </task> <constraints> - One Markdown file; each question's answer leads with the direct response, then expands. - Phrase H2s as natural-language questions; avoid repeating the same answer across questions. - Keyword in title and intro; scannable; concise direct answers up top. </constraints> <format> Return the complete post as a Markdown artifact, then note which question is most likely to win a featured snippet and how you optimized it. </format>