ChatGPT Prompts for Content Marketing

<context> Brand: [BRAND] Audience: [AUDIENCE] Business goal this quarter: [GOAL e.g. pipeline, signups, retention] Primary channels: [CHANNELS e.g. blog, LinkedIn, newsletter] Current content maturity: [none / sporadic / consistent] </context> <task> 1. Define one measurable content objective tied to [GOAL] with a target metric and timeframe. 2. Identify 3 audience segments inside [AUDIENCE] and the job-to-be-done each cares about. 3. Propose 4 content pillars that ladder up to the objective; justify each in one sentence. 4. Map each pillar to a primary channel and a funnel stage (TOFU/MOFU/BOFU). 5. Recommend a realistic weekly cadence given the maturity level. 6. List the 3 biggest risks to execution and a mitigation for each. Return as a structured brief with headers. </task>

<context> Brand: [BRAND] Audience: [AUDIENCE] Top 5 customer pain points: [LIST] Product categories: [CATEGORIES] </context> <task> 1. Cluster the pain points into 3-5 themes; name each theme as a content pillar. 2. For each pillar, write a one-line positioning statement connecting [BRAND] to the pain. 3. List 6 sub-topics per pillar suitable for long-form articles. 4. Flag which pillars are differentiated vs. table-stakes vs. me-too. 5. Recommend which single pillar to over-invest in this quarter and why. Return as a pillar table. </task>

<context> Brand: [BRAND] Audience: [AUDIENCE] Product: [PRODUCT] Sales cycle length: [DAYS/WEEKS] </context> <task> 1. Define the buyer journey stages for [AUDIENCE] (awareness, consideration, decision, retention). 2. For each stage, describe the dominant question the buyer is asking. 3. Recommend 2 content formats per stage that best answer that question. 4. Give one concrete title example per format. 5. Identify the single most underserved stage and explain the opportunity. Return as a journey map table. </task>

<context> Brand: [BRAND] Main competitors: [COMPETITOR 1, COMPETITOR 2, COMPETITOR 3] Topic area: [TOPIC] Audience: [AUDIENCE] </context> <task> 1. List the content angles competitors most likely own around [TOPIC]. 2. Identify 5 angles they are probably under-serving for [AUDIENCE]. 3. For each gap, rate difficulty to win (low/med/high) and expected payoff. 4. Recommend 3 gaps [BRAND] should attack first. 5. Suggest a distinctive point of view that would make [BRAND]'s take hard to copy. Return as a gap table plus a 2-sentence POV recommendation. </task>

<context> Brand: [BRAND] Content objective: [OBJECTIVE] Channels: [CHANNELS] Current baselines (if any): [METRICS] </context> <task> 1. Recommend one north-star content metric tied to [OBJECTIVE]. 2. List 3 leading indicators that predict the north-star metric. 3. List 3 lagging/business indicators that prove impact. 4. Propose realistic 90-day targets given the baselines (or industry benchmarks if none). 5. Define a simple weekly reporting format covering all metrics. Return as a KPI tree with targets. </task>

<context> Brand: [BRAND] Content pillar: [PILLAR] Audience: [AUDIENCE] Funnel stage focus: [TOFU/MOFU/BOFU] </context> <task> 1. Generate 30 specific article titles under [PILLAR] for [AUDIENCE]. 2. Vary the formats: how-to, listicle, opinion, case study, comparison, framework, mistake. 3. Tag each idea with its likely funnel stage and search intent. 4. Flag the 5 with the strongest organic upside and the 5 best for social. 5. Avoid generic titles; each must imply a specific takeaway. Return as a numbered table with format and intent columns. </task>

<context> Brand: [BRAND] Audience: [AUDIENCE] Raw customer quotes / reviews / support tickets: [PASTE TEXT] </context> <task> 1. Extract the recurring phrases and exact wording customers use about [TOPIC]. 2. Group them into desires, objections, and points of confusion. 3. Turn each group into 3 content angles written in the customer's own language. 4. Flag any phrases worth using verbatim as headlines. 5. Note which angles reveal an underserved need. Return as a voice-of-customer table. </task>

<context> Topic: [TOPIC] Audience: [AUDIENCE] Depth required: [beginner / intermediate / expert] Word-count target: [WORDS] </context> <task> 1. Summarize what [AUDIENCE] already knows vs. needs to learn about [TOPIC]. 2. List the 6-9 sub-questions a complete article must answer. 3. Order them into a logical H2/H3 outline. 4. For each section, note the key point and one supporting data point or example to find. 5. Flag any claim that needs a cited source before publishing. Return as a structured outline with research to-dos. </task>

<context> Brand: [BRAND] Topic area: [TOPIC] Audience: [AUDIENCE] </context> <task> 1. Propose 8 evergreen angles that stay relevant for 12+ months. 2. Propose 6 timely angles tied to current shifts in [TOPIC]. 3. For each timely angle, note the window of relevance. 4. Recommend a 70/30 split plan across evergreen and timely. 5. Flag any angle at risk of going stale fast. Return as two labeled lists plus a split recommendation. </task>

<context> Brand: [BRAND] Approved ideas: [PASTE LIST] Cadence: [POSTS PER WEEK] Channels: [CHANNELS] Key dates / launches: [DATES] </context> <task> 1. Sequence the approved ideas across a 6-week calendar at the given cadence. 2. Balance funnel stages and formats across each week. 3. Anchor relevant pieces to the key dates and launches. 4. Assign a primary channel and a repurposing channel to each piece. 5. Flag any week that is thin or overloaded and rebalance. Return as a week-by-week calendar table. </task>

<context> Title: [TITLE] Target keyword: [KEYWORD] Audience: [AUDIENCE] Brand voice: [VOICE e.g. direct, expert, friendly] Word count: [WORDS] Outline (if any): [PASTE OUTLINE] </context> <task> 1. Write the full article in [BRAND]'s voice for [AUDIENCE]. 2. Open with a hook that states the reader's problem in the first two sentences. 3. Use the keyword naturally in the intro, one H2, and the conclusion — never forced. 4. Include concrete examples, a short actionable list, and one mini-framework. 5. Close with a single clear next step. 6. Keep paragraphs to 2-3 sentences for scannability. Return the finished draft with H2/H3 headers. </task>

<context> Topic: [TOPIC] Audience: [AUDIENCE] The one promise of the piece: [PROMISE] Tone: [TONE] </context> <task> 1. Write 5 distinct opening hooks: a bold claim, a surprising stat, a question, a story, and a contrarian take. 2. Each hook must lead naturally into [PROMISE]. 3. Keep each under 60 words. 4. Note which hook fits which channel best. 5. Recommend your top pick and explain why in one line. Return as 5 labeled options plus a recommendation. </task>

<context> Audience: [AUDIENCE] Goal of the piece: [GOAL] My raw notes / transcript: [PASTE MESSY TEXT] </context> <task> 1. Identify the single core argument buried in the notes. 2. Reorganize the ideas into a logical structure with headers. 3. Cut repetition and tangents; keep every original insight. 4. Smooth the prose for [AUDIENCE] without inventing new claims. 5. Flag any gap where a missing point would strengthen the piece. Return the cleaned draft plus a short list of gaps. </task>

<context> Article topic: [TOPIC] Target keyword: [KEYWORD] Audience: [AUDIENCE] Primary benefit: [BENEFIT] </context> <task> 1. Write 10 headline options using varied formulas (number, how-to, question, promise, curiosity). 2. Keep each headline under 60 characters where possible and include or imply [KEYWORD]. 3. Write 3 meta descriptions of 150-160 characters, each with a benefit and soft CTA. 4. Rate each headline on clarity and click appeal (1-5). 5. Recommend the strongest headline and meta pairing. Return as labeled lists with ratings. </task>

<context> Draft section: [PASTE SECTION] Audience: [AUDIENCE] Level of expertise: [LEVEL] </context> <task> 1. Identify 3 abstract claims in the section that need grounding. 2. For each, suggest a concrete example relevant to [AUDIENCE]. 3. Propose one analogy that makes the hardest concept intuitive. 4. Suggest 2 data points worth sourcing (mark as "verify before publishing"). 5. Rewrite one weak paragraph applying the additions. Return the suggestions plus the rewritten paragraph. </task>