SERP-informed outline generation with H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, FAQ question planning, and internal linking zones. Lighter than a full content brief — generates article skeleton and structure only, ready for $blog write to consume. Use when user says "outline", "blog outline", "content outline", "structure blog", "plan sections", "article skeleton", "heading structure", "SERP analysis", "competitive outline", "plan article".
Generates skeletal blog post outlines informed by SERP analysis. A lighter alternative to a full content brief — produces heading hierarchy, section targets, and content gap notes without deep statistics research or full competitive analysis.
Gather from the user:
If only a topic is given, infer the keyword and intent from context.
Use WebSearch to analyze the top 5 results for the target keyword:
Search for the target keyword
For each of the top 5 results, note:
Use WebFetch on the top 2-3 results to extract detailed heading structures if the search snippets are insufficient.
Compile a summary of common patterns and missed opportunities.
Create a structured outline with the following format:
# Outline: [Topic]
## Title Suggestions
1. [Primary title — 40-60 chars, front-loaded keyword, power word]
2. [Alternative title — different angle]
3. [Alternative title — question format]
## Target Parameters
- **Primary keyword**: [keyword]
- **Search intent**: [Informational/Commercial/Transactional]
- **Target word count**: [X,XXX] words
- **H2 sections**: [6-8]
- **Target reading level**: Flesch 60-70
---
## Outline
### H2: [Section Title — Question Format] (~300-400 words)
- **Answer-first opener**: [What stat or fact should open this section?]
- **Key points to cover**:
- [Point 1]
- [Point 2]
- [Point 3]
- **H3: [Subsection]** (if appropriate)
- [What this subsection covers]
- **Key statistic to find**: [What data point would strengthen this section?]
- **Chart suggestion**: [Bar/Line/Donut/None] — [What data to visualize]
- **Image placement**: [Yes/No] — [Description of recommended image]
### H2: [Section Title] (~300-400 words)
[... repeat for 6-8 sections ...]
### FAQ Section (3-5 items)
1. [Question from People Also Ask] — [Brief answer direction]
2. [Question from People Also Ask] — [Brief answer direction]
3. [Question from People Also Ask] — [Brief answer direction]
4. [Question from SERP analysis] — [Brief answer direction]
### Conclusion (~100-150 words)
- Key takeaways to summarize
- Call to action direction
---
## Internal Linking Zones
- **Link TO from this post**: [Existing content that should be referenced]
- **Link FROM to this post**: [Existing content that should link here]
## Content Gaps to Exploit
1. [What competitors miss that this post should cover]
2. [Unique angle or original perspective to include]
3. [Format advantage — visuals, depth, or structure competitors lack]
Guidelines for heading generation:
After generating the outline, add a dedicated content gaps analysis:
Save the outline to outlines/[slug]-outline.md or to a user-specified path.
Confirm the outline is ready for $blog write to consume.
If the outlines/ directory does not exist, create it.
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
Manage Trello boards, lists, and cards via the Trello REST API.
Category:productivity