Content Plan: From Topic List to Question-Led Editorial Roadmap

What it does

• Five-stage buyer question map. Defines the questions that actually exist at each stage, so the plan covers the journey instead of one slice of it.
• Question bank per stage. Gives each content piece a specific job — a question it exists to answer — instead of a vague topic assignment.
• AI answer audit. Shows how Claude, ChatGPT, and Perplexity answer each question today and whether you are cited — the visibility you actually compete for.
• Gap analysis. Finds questions with real demand where you are absent, which is where the highest-leverage content lives.
• Calendar with rationale per slot. Every piece ships with its reasoning attached, so the plan survives team changes and budget reviews.

When to use it

• Building a new editorial roadmap from scratch: Run this before spending a quarter writing content, so every piece has a question it answers.
• Refreshing a stale content plan: Run quarterly to re-audit AI answers and re-prioritize — visibility changes as fast as the models do.
• Deciding what to write next: When the calendar is full of ideas but the reasoning is thin, this forces each idea to justify itself.
• Preparing a content strategy deliverable for a client: The roadmap plus rationale per slot is a strategy document, not a content schedule.

The methodology

1. 1

   Map the five buyer stages and their questions

   List the stages your buyer moves through (awareness, research, comparison, decision, retention — adjust to your funnel). For each stage, write every question a real buyer would ask, in their language. Pull from support tickets, sales calls, forum threads, and review complaints — not from your own vocabulary. The questions are the raw material; the stage labels are just organization.

   2–3 hours for a new domain, 45 minutes when revisiting
2. 2

   Audit how AI answers each question today

   Run the top questions through Claude, ChatGPT, Perplexity, and Gemini. For each answer, record: which sources it cites (or if it answers without citing anyone), whether your site appears, and what angle wins. This is the AI visibility baseline — the exact list of answers you are currently absent from. Save the raw outputs; they become the evidence in the gap analysis.

   2–3 hours for 20–30 questionsClaudeChatGPTPerplexityGemini
3. 3

   Build the gap analysis

   For each question, mark: (a) demand — how often the question surfaces across sources, (b) your coverage — do you have a page that directly answers it, (c) AI visibility — are you cited. The questions with high demand, low coverage, and zero citations are your priority set. Questions where a competitor is consistently cited are your attack targets.

   1 hour
4. 4

   Score and prioritize

   Score each candidate question on demand, coverage gap, and citation gap. Weight them by business relevance — a question your buyer asks before a high-ticket decision outranks a higher-volume question from a low-value audience. Cut the list to what one team can actually produce well in a quarter.

   1 hour
5. 5

   Write the roadmap with rationale per slot

   Produce the calendar: each slot names the piece, the question it answers, the stage it serves, the evidence it will cite, and the metric that tells you it worked. If a slot cannot state its question and its evidence, it does not go on the calendar.

   1–2 hours

Common mistakes

• Planning from search volume alone — You write about what people type, not what they are trying to resolve — then wonder why high-volume topics convert nothing. Volume is a filter, not a strategy.
• Skipping the AI visibility audit — You produce pages the answer engines never cite, which is the audience that matters now. The audit is what turns a topic list into an entry ticket.
• Assigning topics instead of questions — A topic can be written fifty ways; a question has a correct answer. Without the question, every piece drifts toward generic coverage.
• No refresh cadence — AI answers change quarterly. A plan built once is stale by the second quarter — the roadmap needs a re-audit slot built in.

Output

An editorial roadmap: a calendar where every piece is tied to a specific buyer question, the AI answers that question currently gives, your gap, and the evidence the piece will use. Each slot carries its rationale, so the plan defends itself.

Next steps

Run seranking-dataforseo first if you need demand data to size the question set, or seo-technical-audit if the site itself is capping what the plan can achieve. Once the roadmap is live, answer-page-rebuilder restructures the priority pages into the question-answer format answer engines quote.

Time & resources

Low for the process itself; the judgment is in weighting demand against business relevance.

Take it with you