AI Prompts for Content Planning

Prompt Engineering for Content Marketing Planning

Artificial Intelligence Content Marketing SEO Article
20 mins

ø AI Prompts to for Content Marketing Planning

Step‑by‑step prompt frameworks for content marketing planning, including why it works, a ready‑to‑copy prompt, and what to measure next:

90‑Day Content Roadmap Architect

Topic Cluster and Authority Map Builder

Persona‑to‑Journey Message and Objection Matrix

Always‑on and Moment‑led Calendar Mixer

Content Operations Capacity and SLA Planner

This is the first in a series of posts detailing advanced prompt techniques for common digital marketing activities. You can simply cut and paste the prompts highlighted below and replace the text [in brackets like this] to give the prompt your context. However, if you want to get more from the prompts, check out the 'Why this works" bullets to try and understand the particular techniques at play, and how you might apply these to your future prompts. We've also provided the "What to measure" section so that you can measure the impact of prompts output, and see how it improve your existing content.

90‑Day Content Roadmap Architect

Description:
Turn business goals into a prioritised 90‑day plan with themes, formats, owners and a lightweight buy‑in pack for stakeholders.

Why this works:
It forces a diagnose‑then‑prioritise approach, couples strategy with measurement, and creates contrasted options you can compare before committing. The structure mirrors proven “audit then upgrade” workflows that bundle RICE (Reach, Impact, Confidence, and Effort) prioritisation and dual‑version outputs to speed decisions.

Copy‑and‑paste prompt:

Act as a senior content strategist. Build a 90‑day content roadmap that aligns to goals, audience needs and channel realities.

Inputs:
- Business goal + KPI: [e.g., increase qualified demo requests by 20%]
- Website address: [URL including https://]
- Ideal Customer Profiles (ICPs)/personas: [list; include market/region]
- Brand voice and tone: [e.g., practical, warm, expert; British English]
- Priority themes or products: [list]
- Channels in scope: [website, LinkedIn, email, short video, ads]
- Resources & constraints: [team roles, budget, compliance notes]
- Data sources you can use: [GA4, CRM, SEO tool, social analytics - reports will need to be uploaded with prompt]
- Seasonality/events to consider: [list]

Tasks:
1) Ask up to 5 clarification questions only if critical fields are blank or unclear. Otherwise proceed.
2) Current‑state snapshot: summarise content performance and obvious gaps by funnel stage.
3) Demand map: for each persona and stage, list problems, jobs‑to‑be‑done and proof required.
4) Idea bank: generate 25 ideas across formats. Tag each with funnel stage, pillar/cluster and proof assets needed.
5) Prioritise with RICE (Reach, Impact, Confidence, Effort). Show a ranked backlog with scores and one‑line rationale.
6) Produce two contrasted plans:
   - Plan A: Low‑risk, compounding evergreen cadence.
   - Plan B: Bold, POV‑led with 20% time for experiments.
   Explain trade‑offs and when to choose which.
7) Calendar: 12‑week schedule with owners, draft/publish dates, dependencies and “definition of done”.
8) Measurement plan: primary and secondary metrics per item, UTM conventions, review cadence, and stop criteria.
9) Stakeholder pack: 10‑slide outline to secure sign‑off.

Model guidance: use an advanced reasoning model for steps 2–7. Use a faster model to spin meta titles, social blurbs and UTMs after the plan is approved.
Output: Markdown tables. Keep British English. Do not reveal hidden chain‑of‑thought.

What to measure next:

  • Publication velocity (rate at which organistion creates and publishes content over a specific period)
  • % on‑time delivery
  • Assisted conversions per theme (use GA4 custom report or export GA4 data from Engagement reports and get AI to analyse)
  • Organic clicks to target pages
  • Calendar adherence

Topic Cluster and Authority Map Builder

Description:
Design pillars, clusters and an internal link plan that builds topical authority while serving real reader questions.

Why this works:
It compares search‑first and story‑first structures, maps entities and questions to ensure completeness, and outputs link architecture you can implement in one pass. This “state intent hypotheses then restructure” pattern is a reliable shortcut to gaining search authority.

Copy‑and‑paste prompt:

Act as an SEO content architect. Create a topic cluster plan and internal link map that balances search demand and brand narrative.

Inputs:
- Primary topic/pillar: [e.g., HR analytics software]
- Related entities and subtopics: [list]
- Geography: [e.g., UK and EU]
- Funnel emphasis: [awareness, consideration, decision]
- Brand voice: [e.g., authoritative, approachable; British English]
- Constraints: [claims to avoid, regulated terms]
- Competitive angles to counter: [list if known]

Tasks:
1) Intent hypotheses: outline dominant intents and confidence levels per subtopic.
2) Entity & question map: list expected sub‑questions and entities. Mark gaps as High/Med/Low priority and why.
3) Two contrasted outlines:
   - Outline A: Search‑first, optimised for coverage and snippets.
   - Outline B: Story‑first, optimised for narrative and differentiation.
   Recommend one based on goals.
4) Cluster plan: 1 pillar + 6–12 cluster pages with target word counts, content briefs, and required proof assets.
5) Internal link blueprint: parent‑child links, lateral “see also” links, and anchor suggestions.
6) Structured data: schema types to use and a generic JSON‑LD placeholder.
7) Editorial guardrails: tone, accessibility and inclusion notes.

Model guidance: use an advanced reasoning model for steps 1–5. Use a faster model for FAQs, metadata and anchor‑text variants.
Output: Markdown with tables. Keep British English.

What to measure next:

  • Primary keyword rank
  • Snippet ownership iin search rankings
  • Internal link CTR to pillar page
  • Growth in non‑brand organic clicks

Persona‑to‑Journey Message and Objection Matrix

Description:
Map messages, objections and proof to each stage of the journey and turn them into concrete content briefs.

Why this works:
Role play exposes what real buyers question, then the matrix converts that into prioritised briefs with testable hypotheses. Comparing two narrative styles makes the plan more resilient to stakeholder preferences.

Copy‑and‑paste prompt:

Act as a buyer enablement lead. Build a persona‑by‑journey content matrix that resolves objections and proves value.

Inputs:
- Personas: [e.g., HR Director, CFO, People Ops Manager]
- Desired action and KPI: [e.g., book a demo; demo-to-opportunity rate]
- Brand voice: [e.g., practical, empathetic; British English]
- Known objections: [price, integration, data privacy]
- Proof assets available: [case studies, benchmarks, certifications]
- Legal/compliance constraints: [list]

Tasks:
1) Role play interviews (condensed): for each persona and stage, list top questions, anxieties and decision criteria.
2) Message house: core promise, 3–5 supports, and proof per persona.
3) Content matrix: for each cell (persona × stage), propose 2 content ideas with format, desired belief shift, CTA and proof.
4) Two contrasted intros for one key piece:
   - Version A: high‑clarity, scannable.
   - Version B: narrative hook with authority signals.
5) Prioritise the top 10 pieces using RICE. Explain trade‑offs.
6) Brief templates: copy‑ready briefs for the top 5 items with key points, outline, and accessibility notes.

Model guidance: use an advanced reasoning model for role play, message house and RICE. Use a faster model to draft subject lines and CTA microcopy.
Output: Markdown tables and bullet points.

What to measure next:

  • Stage‑to‑stage progression rate (use CRM to track)
  • Content‑assisted pipeline
  • Reduction in sales‑raised objections over time

Always‑on and Moment‑led Calendar Mixer

Description:
Blend evergreen cadence with opportunistic, event‑driven content using a trigger library and a publish‑or‑pass decision tree.

Why this works:
You maintain compounding growth while still capturing spikes. The decision tree limits overwhelm by making teams compare “control vs opportunistic” impact before execution.

Copy‑and‑paste prompt:

Act as a newsroom‑style content editor. Create a calendar that mixes evergreen output with moment‑led opportunities.

Inputs:
- Evergreen themes: [list]
- Monitored triggers: [industry news, product updates, competitor moves, seasonal events]
- Channels: [website, LinkedIn, X, short video, email]
- Team capacity: [e.g., 6 posts/month + 2 reactive slots]
- Brand voice: [e.g., confident, helpful; British English]
- Risk tolerance: [low/medium/high]

Tasks:
1) Cadence plan: propose a sustainable evergreen rhythm by channel.
2) Trigger library: define what to watch and the RSS/alert sources to use.
3) Decision tree: publish‑or‑pass criteria within 30 minutes using Impact, Relevance, Originality, and Effort.
4) Playbooks: quick‑turn formats and templates for reactive posts.
5) Two contrasted treatments for one sample trigger:
   - Control: pragmatic explainer.
   - Challenger: bold POV take with a contrarian angle.
6) Weekly run‑sheet: who watches what, stand‑up questions, and SLA for sign‑off.

Model guidance: use an advanced reasoning model for steps 2–5. Use a faster model for headlines, snippets and image alt text.
Output: Markdown with checklists and tables.

What to measure next:

  • Time‑to‑publish for reactive items
  • Reach on moment posts
  • Uplift in followers
  • Organic brand mentions.

Content Operations Capacity and SLA Planner


Description:
Translate ambition into realistic throughput. Model capacity by role, set SLAs, and define a “definition of done” so planning sticks.

Why this works:
It replaces wishful calendars with evidence‑based throughput. By comparing an aggressive versus conservative plan, you secure buy‑in and protect quality. The governance layer mirrors effective refresh and operations patterns that bundle calendar, owners and QA in one pass.

Copy‑and‑paste prompt:

Act as a content operations lead. Build a capacity‑aware plan, SLAs and governance so the calendar is deliverable.

Inputs:
- Team roles and weekly hours available: [e.g. writer 1: 12h, editor: 6h]
- External partners/budget: [if any]
- Required outputs by channel: [e.g. 3 LinkedIn posts, website 1 longform]
- Review and compliance needs: [e.g. Financial Serviceds UK regulations, Head of department review]
- Definition of done constraints: [style, accessibility, inclusion, legal]
- Brand voice: [British English]
- Available historic data: [Previous content schedule with indication what was actually published if available, uploaded with prompt]

Tasks:
1) Throughput model: estimate realistic monthly output by format using historical velocity or sensible defaults.
2) SLA matrix: drafting, review, legal, design and publish times.
3) Risk register: list bottlenecks and mitigations.
4) Two contrasted capacity scenarios:
   - Scenario A: conservative, quality‑first.
   - Scenario B: aggressive, speed‑first.
   Provide trade‑offs and a recommended option.
5) Governance: RACI, definition of done checklist, and change‑control process.
6) 8‑week schedule with owners, buffers, and checkpoints.

Model guidance: use an advanced reasoning model for steps 1–5. Use a faster model to generate SOP checklists and notification templates.
Output: Markdown with tables and checklists.

What to measure next:

  • On‑time rate
  • Revision cycles per asset
  • Error rate at QA
  • Cycle time from brief to publish. 

 

 

Build a ü free personalised ¥ learning plan to see our course recommendations î for you

Free for 30 days

Build a å free personalised ¥ learning plan to see our course recommendations î for you

Free for 30 days