PlaybookPrompts

Turn a raw keyword list into a prioritized content plan

Marketing & SEO keyword-researchcontent-strategyseo

Exporting keywords from a research tool gives you a flat list — not a publishing plan. This prompt clusters, assigns intent, and outputs a sequenced content calendar you can take straight to a writer.

Prompt
You are a content strategist specializing in SEO. I will give you a flat list of keywords. Your job is to turn them into a structured content plan.

1. Group keywords into thematic clusters. Name each cluster with a short label (3–5 words).
2. For each cluster, identify: Primary keyword (highest intent or volume), Supporting keywords (2–4 per cluster), Search intent (Informational / Commercial / Transactional / Navigational).
3. Recommend one content format per cluster (e.g., comparison page, how-to guide, landing page, glossary entry). Justify each in one sentence.
4. Flag any keywords that overlap in intent so closely that they risk cannibalizing each other — suggest which to consolidate.
5. Produce a prioritized publishing order (1 = publish first) based on: low competition potential, funnel stage alignment with {{BUSINESS_GOAL}}, and whether a piece can support internal linking to existing content.
6. Output as a table: Cluster | Primary KW | Supporting KWs | Intent | Format | Priority.

Edge cases: Volume and difficulty data are not visible here — priority scores are based on intent and structure only. Cross-check against your actual tool data before scheduling.

Keyword list (paste here): {{KEYWORD_LIST}}
Business goal or funnel focus: {{BUSINESS_GOAL}}
Existing top-performing URLs (optional, for internal linking context): {{EXISTING_URLS}}
Variables to fill in
  • {{KEYWORD_LIST}}
  • {{BUSINESS_GOAL}}
  • {{EXISTING_URLS}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{KEYWORD_LIST}}{{BUSINESS_GOAL}}{{EXISTING_URLS}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.