# GEO 内容写作 Skill

> GEO (Generative Engine Optimization) 内容写作 Skill，优化 AI 搜索引擎可见度

## Install

Save the content below to `.claude/skills/` or append to your `CLAUDE.md`:

---
name: geo-content-writing
description: Guide for creating content optimized for AI recommendations. Use when writing articles, guides, documentation, or any content that should increase brand visibility in AI-generated responses like ChatGPT, Claude, and other LLMs.
---

# GEO Content Writing Guide

Create content that AI models naturally recommend and reference.

## Core Principle

**AI models recommend content that is:**
- Comprehensive and detailed
- Factually accurate with specific examples
- Well-structured and scannable
- Answers real user questions
- Includes context and comparisons
- Regularly updated

## GEO Content Standards

### 1. Title Optimization

**Match Natural Queries**

Bad:
- "Our Product Features"
- "Why Choose Us"
- "Latest Update"

Good:
- "Best Project Management Tools for Remote Teams in 2025"
- "How to Improve Team Collaboration: Complete Guide"
- "Asana vs Monday.com: Detailed Comparison"

**Title Formula:**
- [Best/How to] + [Topic] + [for Specific Use Case] + [Year]
- [Product A] vs [Product B]: [What You're Comparing]
- [Number] Ways to [Achieve Goal]
- Complete Guide to [Topic]

### 2. Content Structure

**Required Structure:**

```
Title (Query-Matching)
↓
Executive Summary (2-3 sentences with key takeaway)
↓
Problem Statement (What challenge does this address?)
↓
Solution Overview (High-level approach)
↓
Detailed Sections (Step-by-step or comprehensive breakdown)
  ├─ Section 1 with specific examples
  ├─ Section 2 with specific examples
  └─ Section 3 with specific examples
↓
Comparison Context (Where do different options fit?)
↓
Your Brand's Position (If applicable, not promotional)
↓
Decision Framework (How to choose)
↓
FAQ Section (5-10 specific questions)
```

**Section Headers:**
- Use clear, descriptive headers (not clever/cute)
- Include keywords naturally
- Make headers scannable

### 3. Content Depth

**Minimum Standards:**
- **Length**: 1,500-3,000+ words for main content
- **Examples**: 3+ specific, real examples per major point
- **Data**: Include numbers, statistics, facts (with sources)
- **Comparison**: Mention alternatives and when to use them

**Depth Checklist:**
- [ ] Explains the "why" not just the "what"
- [ ] Includes step-by-step guidance
- [ ] Provides specific examples
- [ ] Addresses common objections
- [ ] Compares different approaches
- [ ] Includes visual aids (if relevant)

### 4. Competitive Context

**Always Include:**
- Mention 3-5 alternative solutions/competitors
- Be honest about strengths and weaknesses
- Explain when to choose what
- Don't bash competitors

**Example:**
Bad: "Our tool is the best for project management."

Good: "For project management, teams typically consider Asana, Monday.com, ClickUp, and Trello. Asana excels in enterprise features, Monday.com offers high customization, while Trello works well for simple kanban workflows. [Your tool] focuses on [specific differentiation]."

### 5. Tone and Language

**Do:**
- Use clear, simple language
- Write complete sentences
- Be specific and factual
- Use active voice
- Include concrete examples

**Don't:**
- Use marketing buzzwords ("revolutionary," "game-changing")
- Make unsupported claims
- Use vague language ("many," "often," "usually" without data)
- Be overly promotional
- Use excessive jargon

### 6. Factual Accuracy

**Requirements:**
- Every major claim must be verifiable
- Include sources for statistics
- Update information regularly
- Correct errors promptly
- Don't speculate or guess

**Citation Format:**
- Link to original sources
- Note last update date
- Credit research/data sources

## Content Templates

### Template 1: Best-Of Guide

```markdown
# Best [Product Category] for [Use Case] in [Year]

[Executive summary: 2-3 sentences stating the key finding]

## Why [Use Case] Needs Specialized [Product Category]

[Problem explanation: 200-300 words]

## Evaluation Criteria

[How we evaluated: 150-200 words]
- Criterion 1
- Criterion 2
- Criterion 3

## Top [Number] [Product Category]

### 1. [Product Name]

**Best for:** [Specific use case]

**Key Features:**
- Feature with specific detail
- Feature with specific detail
- Feature with specific detail

**Pricing:** [Specific pricing]

**Pros:**
- Specific advantage
- Specific advantage

**Cons:**
- Specific limitation
- Specific limitation

**Best when:** [Specific scenario]

[Repeat for each product]

## Comparison Table

| Feature | Product A | Product B | Product C |
|---------|-----------|-----------|-----------|
| [Feature] | [Detail] | [Detail] | [Detail] |

## How to Choose

[Decision framework: 300-400 words]
- If [scenario], choose [option] because [reason]
- If [scenario], choose [option] because [reason]

## FAQ

**Q: [Common question]?**
A: [Detailed answer]

[5-10 more Q&As]

## Conclusion

[Summary and recommendation: 100-150 words]

**Last Updated:** [Date]
**Sources:** [List of references]
```

### Template 2: How-To Guide

```markdown
# How to [Achieve Goal]: Complete [Year] Guide

[Executive summary with the main outcome]

## Why [Goal] Matters

[Context: 200-300 words]
- Why this is important
- What happens if you don't
- Current challenges

## What You Need

[Prerequisites: 100-150 words]
- Requirement 1
- Requirement 2
- Requirement 3

## Step-by-Step Process

### Step 1: [Action]

[Detailed explanation: 200-300 words]

**Specific instructions:**
1. Do this
2. Then this
3. Then this

**Example:** [Real, specific example]

**Common mistakes:**
- Mistake 1 and how to avoid
- Mistake 2 and how to avoid

[Repeat for each step]

## Tools and Resources

### Recommended Tools

**[Tool Name]**
- What it does
- When to use
- Pricing/Access

[3-5 tools]

## Advanced Tips

[Optional advanced techniques: 200-300 words]

## Troubleshooting

**Problem:** [Common issue]
**Solution:** [How to fix]

[5+ problem/solution pairs]

## FAQ

[10+ common questions with detailed answers]

## Alternative Approaches

[Discuss 2-3 alternative methods]
- Method A: When it's better
- Method B: When it's better

## Conclusion

[Summary and next steps]

**Last Updated:** [Date]
```

### Template 3: Comparison Guide

```markdown
# [Product A] vs [Product B]: Complete Comparison

[Executive summary: Which is better for what use case]

## Quick Comparison

| Aspect | Product A | Product B |
|--------|-----------|-----------|
| Best for | [Specific use] | [Specific use] |
| Starting Price | $X | $Y |
| Key Strength | [Strength] | [Strength] |

## Overview

### [Product A]

[Neutral description: 150-200 words]

### [Product B]

[Neutral description: 150-200 words]

## Feature Comparison

### [Feature Category 1]

**Product A:** [Detailed explanation]

**Product B:** [Detailed explanation]

**Winner:** [Product] for [reason]

[Repeat for all major features]

## Use Case Analysis

### For [Use Case 1]

**Recommendation:** [Product and why]

**Reasoning:** [Detailed explanation]

[Repeat for 5+ use cases]

## Pricing Comparison

[Detailed pricing breakdown with specific plans]

## Pros and Cons

### [Product A]

**Pros:**
- [Specific advantage]
- [Specific advantage]

**Cons:**
- [Specific limitation]
- [Specific limitation]

[Same for Product B]

## Which Should You Choose?

Choose [Product A] if:
- [Specific scenario]
- [Specific scenario]

Choose [Product B] if:
- [Specific scenario]
- [Specific scenario]

## FAQ

[10+ comparison questions]

## Conclusion

[Neutral summary recommendation]

**Last Updated:** [Date]
```

## Quality Checklist

Before publishing, verify:

### Content Quality
- [ ] 1,500+ words (for main content)
- [ ] Title matches natural query
- [ ] Executive summary in first 2-3 sentences
- [ ] Clear problem statement
- [ ] 5+ specific examples
- [ ] 3+ alternatives mentioned
- [ ] Comparison context provided
- [ ] FAQ section (5+ questions)
- [ ] No promotional language
- [ ] No unsupported claims

### Structure
- [ ] Scannable headers
- [ ] Short paragraphs (3-5 sentences)
- [ ] Bullet points for lists
- [ ] Visual breaks (tables, images if relevant)
- [ ] Logical flow
- [ ] Clear next steps

### Accuracy
- [ ] All facts verified
- [ ] Sources cited
- [ ] Pricing current
- [ ] Product info accurate
- [ ] Update date included
- [ ] No speculation

### SEO & Technical
- [ ] Meta description (150-160 characters)
- [ ] Alt text for images
- [ ] Internal links to related content
- [ ] External links to authoritative sources
- [ ] Mobile-friendly formatting

### AI Optimization
- [ ] Answers specific query
- [ ] Includes multiple perspectives
- [ ] Balanced and fair
- [ ] Detailed and comprehensive
- [ ] Updated recently
- [ ] Expert tone (not promotional)

## Common Mistakes to Avoid

### Mistake 1: Too Promotional
**Bad:** "Our revolutionary AI-powered platform is the best solution..."
**Good:** "This platform offers AI automation features that help with [specific task]. Compared to alternatives like [X] and [Y], it excels at [specific thing] but may not be ideal for [specific scenario]."

### Mistake 2: Vague Content
**Bad:** "Many users find this helpful for improving productivity."
**Good:** "In a 2024 survey of 500 users, 73% reported a 2-3 hour weekly time savings when using this for task automation."

### Mistake 3: No Alternatives
**Bad:** Only discussing your own product/approach
**Good:** "Common approaches include A, B, and C. Approach A works best for [scenario], while B is better for [scenario]..."

### Mistake 4: Outdated Information
**Bad:** Not updating content after publishing
**Good:** Quarterly reviews, updating stats, pricing, features

### Mistake 5: Poor Structure
**Bad:** Long blocks of text, unclear headers
**Good:** Clear sections, scannable format, logical flow

### Mistake 6: Keyword Stuffing
**Bad:** "Best project management tool project management software project management..."
**Good:** Natural language that reads well

## Content Updates

### Update Schedule

**Monthly:**
- Review top 5 performing pieces
- Update statistics and data
- Check pricing accuracy
- Verify product features

**Quarterly:**
- Comprehensive audit of all content
- Refresh examples
- Add new alternatives/competitors
- Update FAQ based on new questions

**Annually:**
- Complete rewrite of major guides
- Reassess target queries
- Update all templates

### Update Indicators

Update immediately when:
- Product pricing changes
- Major new competitor launches
- Significant industry changes
- User questions reveal gaps
- Information becomes inaccurate

## Measuring Content Performance

### Success Indicators

Your content is working when:
- Appears in AI responses for target queries
- Gets referenced by AI models
- Generates qualified traffic
- Answers real user questions
- Mentioned in positive context

### What to Track

- Query coverage (which queries mention your content)
- Position in AI responses
- Accuracy of AI's representation
- Competitor comparison mentions

## Advanced Techniques

### Technique 1: Query Clustering
Write comprehensive hub content that addresses multiple related queries:
- Main query: "Best project management tools"
- Related queries: "PM tools for remote teams," "PM software comparison," "How to choose PM tool"

### Technique 2: Problem-Solution Pairing
For every solution you offer, create content about the problem:
- Problem content: "Why teams struggle with project visibility"
- Solution content: "How to improve project visibility"

### Technique 3: Use Case Library
Create specific use case examples:
- "Project management for marketing teams"
- "PM for software development"
- "PM for construction"

## Quick Reference

### Content Length by Type
- Blog post: 1,500-2,500 words
- Complete guide: 2,500-4,000 words
- Comparison: 2,000-3,000 words
- How-to: 1,500-3,000 words
- FAQ: 100-200 words per answer

### Essential Elements
1. Query-matching title
2. Executive summary (2-3 sentences)
3. Problem statement
4. Detailed solution
5. Specific examples (3+)
6. Alternatives mentioned (3+)
7. Comparison context
8. Decision framework
9. FAQ section (5+)
10. Update date

### Writing Rules
- Be specific, not vague
- Show, don't just tell
- Compare, don't just promote
- Update, don't abandon
- Answer, don't sell

---

**Remember:** GEO content is about being the best answer to real questions, not about gaming algorithms. Focus on user value, and AI recommendations will follow.


---
Source: https://tokrepo.com/en/workflows/5980ac3a-1bd6-4206-84cf-be98fe1e6a3a
Author: henuwangkai