blog-strategy
Skill0 starsChanged 3 months agoMITView on GitHub
Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for GEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience. Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about", "blog topics", "content pillars", "blog ideation".
5 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- gaznilmuzammil12-prog/seo-skills-by-gaznilword for word, first seen Nov 16, 2026
- alpit-patel/seo-aeo-geo-kitedited, first seen Nov 8, 2026
- AgriciDaniel/claude-blogedited, first seen Oct 25, 2026
- coopersimson96/ai-content-systemedited, first seen Jun 25, 2026
- megastep/codex-skillsedited, first seen Feb 25, 2026
Other versions5 projects use a version of this.
Word for word · 1
- gaznilmuzammil12-prog/seo-skills-by-gaznil★ 0100% same
Edited · 4
- AgriciDaniel/claude-blog★ 2.7k48% same
- coopersimson96/ai-content-system★ 1799% same
- megastep/codex-skills★ 497% same
- alpit-patel/seo-aeo-geo-kit★ 261% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository85 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- llms-full.txtllms.txt
- llms.txtllms.txt
- ab-testingSkill
- accessibilitySkill
- ai-seoSkill
- analyticsSkill
- attributionSkill
- blog-analyzeSkill
- blog-audioSkill
- blog-auditSkill
- blog-brandSkill
- blog-briefSkill
- blog-calendarSkill
- blog-cannibalizationSkill
- blog-chartSkill
- blog-clusterSkill
- blog-discourseSkill
- blog-factcheckSkill
- blog-flowSkill
- blog-geoSkill
- blog-googleSkill
- blog-imageSkill
- blog-locale-auditSkill
- blog-localizeSkill
- blog-multilingualSkill
- blog-notebooklmSkill
- blog-outlineSkill
- blog-personaSkill
- blog-repurposeSkill
- blog-rewriteSkill
- blog-schemaSkill
- blog-seo-checkSkill
- blogSkill
- blog-taxonomySkill
- blog-translateSkill
- blog-writeSkill
- canonical-tagSkill
- competitorsSkill
- content-optimizationSkill
- content-strategySkill
- copywritingSkill
- core-web-vitalsSkill
- croSkill
- directory-submissionsSkill
- eeat-signalsSkill
- entity-seoSkill
- featured-snippetSkill
- google-search-consoleSkill
- heading-structureSkill
- indexingSkill
- indexnowSkill
- internal-linksSkill
- keyword-researchSkill
- local-seoSkill
- meta-descriptionSkill
- mobile-friendlySkill
- open-graphSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 2 are common, 3 are distinctive, and 1 is very specific to this project.
2
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Auto-loaded inputs (v1.8.0): when DISCOURSE.md exists at the project root (from /blog discourse), load it for cross-platform discourse …
- Common: line 80
None: No AI citation presence detected
- Distinctive: line 184
Every H2 opens with an answer-first paragraph (40-60 words with stat + source)
- Distinctive: line 204
Only 12% overlap between platforms.
- Common: line 227
Every post should be scored before publishing.
- Distinctive: line 241
ChatGPT: Ensure brand name appears consistently, maintain 30-day freshness, use conversational answer-first formatting
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Blog Strategy: Positioning & Content Architecture
Develops comprehensive blog strategies that build topical authority for Google rankings while establishing brand presence for AI citation platforms. Includes topic cluster architecture, AI citation surface strategy, content scoring targets, and GEO-specific optimization plans.
Research discipline references (v1.8.0):
skills/blog/references/research-quality.md- 5-dim rubric, pre-flight trap classes, cross-source clustering, freshness floorsskills/blog/references/synthesis-contract.md- 6 LAWs for synthesis output
Auto-loaded inputs (v1.8.0): when DISCOURSE.md exists at the project root (from /blog discourse), load it for cross-platform discourse signal alongside this skill's authority-source planning.
Cross-reference
Strategy planning should consider the FLOW 5-surface model (owned site, SERP plus AI Overviews, AI assistant citations, local pack, communities and video). Local-pack work is delegated to claude-seo; everything else lives inside claude-blog. Full mapping in skills/blog/references/flow-alignment.md.
For evidence-led audience-avatar, keyword-research, and content-prioritization prompts that feed strategic planning, see /blog flow find.
Workflow
Step 1: Discovery
Gather context through questions or project analysis:
- Business: What do you sell/do? Who are your customers?
- Blog goals: Traffic? Leads? Authority? AI citations?
- Current state: Existing blog content? (scan if project available)
- Competitors: Who are your 3-5 main competitors?
- Differentiator: What unique expertise or data do you have?
- Resources: Writing capacity (posts/week), budget for visuals?
Step 2: Competitive Landscape
Research competitors' blogs:
- WebSearch for competitor blog URLs
- For each competitor, assess:
- Publishing frequency
- Content types (guides, case studies, comparisons, news)
- Visual quality (images, charts, videos)
- Schema usage
- Social distribution (YouTube, Reddit, LinkedIn)
- AI citation presence (search ChatGPT/Perplexity for industry terms)
- Identify gaps no competitor covers well
Competitive AI Citation Analysis
Map competitor visibility across AI platforms. Use WebSearch to find how competitors appear in AI-generated responses for target keywords.
## Competitive AI Citation Map
| Query | ChatGPT Cites | Perplexity Cites | AI Overview Cites | Gap? |
|-------|--------------|-----------------|-------------------|------|
| [keyword] | [competitor/none] | [competitor/none] | [competitor/none] | [Yes/No] |
| [keyword] | [competitor/none] | [competitor/none] | [competitor/none] | [Yes/No] |
| [keyword] | [competitor/none] | [competitor/none] | [competitor/none] | [Yes/No] |Score each competitor's AI visibility:
- High: Cited in 3/3 platforms for multiple queries
- Medium: Cited in 1-2 platforms or for limited queries
- Low: Rarely cited, only in niche queries
- None: No AI citation presence detected
Identify AI citation gaps: queries where no competitor is cited. These represent the highest-opportunity targets for new content.
Note: only 12% overlap between platforms. A competitor strong on ChatGPT may be absent from Perplexity. Analyze each platform independently.
Step 3: Audience Mapping
Define 2-3 audience segments:
### Audience Segment: [Name]
- **Role**: [Job title / description]
- **Pain points**: [What problems do they have?]
- **Search behavior**: [What do they Google?]
- **AI behavior**: [What do they ask ChatGPT/Perplexity?]
- **Content preferences**: [Long guides? Quick answers? Video?]
- **Buying stage**: [Awareness / Consideration / Decision]Step 4: Content Pillar Design with Topic Cluster Architecture
Design 3-5 content pillars based on audience needs and competitive gaps. For each pillar, build the full hub-and-spoke cluster model.
### Pillar: [Topic Area]
- **Purpose**: Build authority in [topic]
- **Primary keywords**: [3-5 keywords]
- **Content types**: Pillar guide, supporting posts, comparisons, FAQ
- **Unique angle**: [What first-hand experience/data can you provide?]
- **Estimated posts**: [N] to achieve topic coverage
- **AI citation potential**: [High/Medium/Low] - [why]Cluster Architecture Design
For each pillar, design the complete hub-and-spoke structure:
### Cluster Architecture: [Pillar Topic]
┌──────────────────┐
│ Pillar Page │
│ 3,000-4,000w │
└────────┬─────────┘
│
┌─────────────────┼──────────────────┐
│ │ │
┌──────▼──────┐ ┌─────▼──────┐ ┌───────▼──────┐
│ Spoke #1 │ │ Spoke #2 │ │ Spoke #3 │
│ 1,500-2,500│ │ 1,500-2,500│ │ 1,500-2,500 │
└──────┬──────┘ └─────┬──────┘ └───────┬──────┘
│ │ │
└────────────────┼───────────────────┘
(cross-links between spokes)For each cluster, specify:
- 8-12 spoke topics per pillar, each targeting a specific long-tail keyword
- Internal linking plan between all cluster pages (every spoke links to pillar, pillar links to all spokes, spokes cross-link to related spokes)
- Content template assignment for each piece from the 12 available templates:
how-to-guide,listicle,case-study,comparison,pillar-page,product-review,thought-leadership,roundup,tutorial,news-analysis,data-research,faq-knowledge
### Cluster Build Plan: [Pillar Topic]
| # | Spoke Topic | Template | Target Keyword | Word Count | Internal Links |
|---|------------|----------|---------------|-----------|----------------|
| P | [Pillar title] | pillar-page | [keyword] | 3,000-4,000 | Links to all spokes |
| 1 | [Spoke title] | how-to-guide | [keyword] | 1,500-2,500 | Pillar + Spokes 2,3 |
| 2 | [Spoke title] | comparison | [keyword] | 1,500-2,500 | Pillar + Spokes 1,3 |
| 3 | [Spoke title] | listicle | [keyword] | 1,500-2,500 | Pillar + Spokes 1,2 |
| ... | ... | ... | ... | ... | ... |Reference: references/internal-linking.md for hub-and-spoke model and anchor text rules.
Step 5: Differentiation Strategy
The December 2025 Core Update rewards first-hand experience. Plan how to demonstrate genuine expertise:
| Signal Type | Implementation |
| Original data | Conduct surveys, analyze proprietary data, run experiments |
| Case studies | Document real client/project results with metrics |
| Build in public | Share process, learnings, and failures transparently |
| Expert interviews | Feature practitioners with first-hand knowledge |
| Tool reviews | Test products personally, share screenshots and results |
| Industry analysis | Provide unique perspective on public data |
Step 5.5: AI Citation Surface Strategy
Plan how to maximize AI citation across platforms. 80% of LLM citations come from outside the top 100 organic results. Traditional SEO alone is insufficient.
On-Site Optimization
Structure every piece of content for AI citability:
- Every H2 opens with an answer-first paragraph (40-60 words with stat + source)
- Citation capsules: 40-60 word self-contained passages per H2 section
- Q&A format: 60-70% of H2 headings phrased as questions
- FAQ sections with schema markup on every post
- Entity clarity: consistent terminology throughout (no synonym variation for key concepts)
- Structured data: JSON-LD for Article, FAQ, HowTo, and Review schemas
Off-Site Presence (Critical: 88-92% of AI citations from off-site)
| Channel | AI Citation Impact | Priority Action |
| YouTube | 0.737 correlation (strongest) | Companion videos for pillar posts |
| 450% citation surge | Authentic participation in 3-5 subreddits | |
| Review platforms | 2.6-3.5x multiplier | Maintain profiles on G2, Capterra (B2B) |
| Wikipedia/Wikidata | Credibility tiebreaker | Build notability, create Wikidata entry |
| Industry publications | Tier 2-3 citation source | Guest posts, expert commentary |
Cross-Platform Monitoring
- Track brand mentions in ChatGPT, Perplexity, Google AI Overviews
- Only 12% overlap between platforms; optimize for each separately
- 80% of LLM citations come from outside the top 100 organic results
- Monitor monthly: search 10-20 target queries on each platform, log citations
Reference: references/geo-optimization.md for detailed GEO tactics.
Step 5.6: Content Scoring Targets
Set quality standards that all blog content must meet:
### Content Quality Standards
| Metric | Target | Measured By |
|--------|--------|-------------|
| Blog quality score | 80+ | `/blog analyze` |
| E-E-A-T compliance | Named author + 8+ tier 1-3 sources | Manual review |
| AI citation readiness | Answer-first + FAQ + citation capsules | `/blog analyze` |
| Visual minimum | 2+ charts + 3+ images per post | Asset count |
| Internal links | 5+ per post (within cluster) | Link audit |
| Schema markup | Article + FAQ + relevant type | Structured data test |
| Word count | 1,500+ for spokes, 3,000+ for pillars | Word count tool |Every post should be scored before publishing. Posts below 80 quality score should be revised before going live.
Step 5.7: GEO-Specific Strategy
Plan passage-level citability across all content, tailored to each AI platform.
| AI Platform | Favors | Optimization Focus |
| ChatGPT | Recency, brand authority, conversational clarity | Update posts within 30 days, clear entity definitions |
| Perplexity | Citations, source diversity, structured answers | Tier 1-3 sources, numbered lists, data tables |
| Google AI Overviews | Structured data, schema, topical authority | FAQ schema, HowTo schema, complete topic clusters |
Strategy by platform:
- ChatGPT: Ensure brand name appears consistently, maintain 30-day freshness, use conversational answer-first formatting
- Perplexity: Maximize external citation count (8+ per post), use structured data tables, cite authoritative sources
- AI Overviews: Complete topic cluster coverage, implement all relevant schema types, achieve featured snippet format
Reference: references/geo-optimization.md for platform-specific optimization guides.
Step 6: Distribution Channel Strategy
AI visibility requires off-site presence (88-92% of AI citations come from off-site signals). Plan brand presence:
| Channel | AI Impact | Strategy |
| YouTube | 0.737 correlation (strongest) | Companion videos for pillar posts, how-tos, demos |
| 450% citation surge | Authentic participation in 3-5 subreddits, share insights not links | |
| Review platforms | 2.6-3.5x citation multiplier | Maintain profiles on G2, Capterra, TrustRadius (B2B) |
| Wikipedia/Wikidata | Credibility tiebreaker | Build notability through earned media, create Wikidata entry |
| Industry publications | Tier 2-3 citation source | Guest posts, expert commentary, study contributions |
| Social media | Brand mentions | LinkedIn thought leadership, Twitter/X insights |
Budget allocation recommendation: 40% owned content / 60% earned media and distribution.
Reference: references/distribution-playbook.md for detailed channel tactics and templates.
Step 7: Measurement Framework
### Metrics to Track
#### Traditional SEO
- Organic traffic (monthly)
- Keyword rankings (top 10, top 3)
- Domain authority / Domain Rating
- Internal link coverage
- Core Web Vitals
#### AI Citation Metrics (New)
- Share of Voice in ChatGPT responses (manual tracking)
- AI Overview citation rate (Google Search Console)
- Perplexity mentions (manual tracking)
- AI referral traffic (GA4: source contains chatgpt, perplexity, claude)
- Brand mention volume (branded search + web mentions)
#### Content Quality
- Blog quality score via `/blog analyze` (target: 80+)
- Content freshness (% of posts updated within 30 days)
- Visual element coverage (charts + images per post)
- Citation tier quality (% tier 1-3 sources)
#### Business Impact
- Blog-attributed leads/conversions
- Email subscribers from blog
- Content-assisted revenueStep 8: Generate Strategy Document
Output format:
# Blog Strategy: [Business Name]
## Executive Summary
[2-3 sentences on the strategic direction]
## Audience
[Segment summaries]
## Content Pillars & Cluster Architecture
[3-5 pillars with full hub-and-spoke cluster plans]
[Internal linking map for each cluster]
[Template assignments for each piece]
## Competitive Positioning
[How we differentiate - what unique value we bring]
[Competitive AI Citation Map showing gaps to exploit]
## AI Citation Surface Strategy
[On-site optimization checklist]
[Off-site presence plan with priority channels]
[Platform-specific GEO tactics]
## Content Quality Standards
[Scoring targets for all content]
[E-E-A-T compliance requirements]
## Distribution Channels
[Priority channels with specific tactics]
## Content Velocity
- New posts: [N]/week
- Freshness updates: [N]/month
- Visual elements: [N] charts + [N] images per post
## 90-Day Roadmap
### Month 1: Foundation
- [ ] Publish [Pillar 1] guide + [N] supporting spokes
- [ ] Set up YouTube channel / Reddit profiles
- [ ] Establish measurement dashboard
- [ ] Complete competitive AI citation audit
### Month 2: Expansion
- [ ] Publish [Pillar 2] guide + [N] supporting spokes
- [ ] First freshness update cycle
- [ ] Begin Reddit/YouTube distribution
- [ ] Launch off-site presence on review platforms
### Month 3: Optimization
- [ ] Audit all posts with `/blog analyze` (target: 80+ score)
- [ ] Optimize lowest-scoring posts
- [ ] Publish [Pillar 3] guide
- [ ] Review AI citation metrics across all platforms
- [ ] Adjust strategy based on data
## Measurement
[KPIs and tracking approach - traditional SEO + AI citation metrics]
## Reference Documents
- `references/internal-linking.md` - Hub-and-spoke model, anchor text rules
- `references/distribution-playbook.md` - Channel tactics and templates
- `references/geo-optimization.md` - GEO platform-specific optimization
- `references/content-templates.md` - 12 content templates with structures
## Next Steps
1. Run `/blog calendar` to create the first month's editorial calendar
2. Run `/blog brief` for the first pillar page
3. Run `/blog write` to generate the first article
4. Set up AI citation monitoring for target queriesDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

