30x seo plan
SEO strategy planning: competitor analysis, keyword strategy, content calendar, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content calendar", or "SEO roadmap".From its SKILL.md
npx -y skills add norahe0304-art/30x-seo --skill 30x-seo-planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
4.1 KB, 924 tokens by cl100k_base, as published. Nobody here has run it
SEO Strategy Planning
What This Skill Does
Create SEO strategy: analyze competitors, plan keywords, create content calendar, output implementation roadmap.
Does NOT do:
- Website architecture design → use
site-architecture - Technical SEO checks → use
seo-technical - Content generation → use
seo-content-writer
Optional Input
| Input | Source | Description |
|---|---|---|
| seo-keywords output | /seo keywords | If keyword research exists, read as strategy input |
Not a hard dependency. You can plan first then research, or research first then plan.
Process
Step 1: Discovery
Ask user:
- Business type (SaaS / E-commerce / Local service / Media / Other)
- Target audience (Who are your customers?)
- Main competitors (3-5)
- Goals (Traffic? Conversions? Brand?)
- Existing website? (Yes → analyze current state; No → new site planning)
Step 2: Competitor Analysis
For each competitor, analyze:
| Dimension | Check Points |
|---|---|
| Content | What pages? Blog frequency? Content depth? |
| Keywords | What keywords rank? Content topics? |
| E-E-A-T | Author info? Expert endorsements? Trust signals? |
| Structure | URL hierarchy? Navigation design? |
Tools: WebFetch + Perplexity
Output: COMPETITOR-ANALYSIS.md
Step 3: Keyword Strategy
If seo-keywords output exists → read and integrate If not → infer from competitor analysis + user input
Determine:
- Core keywords (3-5)
- Long-tail keywords (10-20)
- Topic clusters
Output: Integrate into SEO-STRATEGY.md
Step 4: Content Planning
Based on keyword strategy, plan:
| Content Type | Example |
|---|---|
| Pillar pages | Authoritative long-form on core topics |
| Cluster pages | Detailed articles around pillars |
| Blog posts | Regular update content |
Output: CONTENT-CALENDAR.md
# Content Calendar
## Month 1
| Week | Topic | Target Keyword | Type | Priority |
|------|-------|----------------|------|----------|
| 1 | ... | ... | Pillar | High |
| 2 | ... | ... | Cluster | Medium |
Step 5: Implementation Roadmap
Simplified roadmap:
| Phase | Timeline | Focus |
|---|---|---|
| Launch | Week 1-2 | Technical foundation (→ seo-technical), core pages |
| Content | Week 3-8 | Publish per calendar (→ seo-content-writer) |
| Optimize | Week 9-12 | Monitor rankings, adjust strategy |
Output: IMPLEMENTATION-ROADMAP.md
Output Files
| File | Content |
|---|---|
SEO-STRATEGY.md | Complete strategy: goals, keywords, topic clusters |
COMPETITOR-ANALYSIS.md | Competitor analysis report |
CONTENT-CALENDAR.md | Content calendar (for seo-content-writer) |
IMPLEMENTATION-ROADMAP.md | Implementation roadmap |
Integration
seo-keywords ──(optional)──> seo-plan
│
├──> seo-content-writer (content generation)
├──> site-architecture (architecture design)
└──> seo-technical (technical checks)
| Skill | When to Use |
|---|---|
seo-keywords | Do keyword research before planning |
site-architecture | When detailed architecture design needed |
seo-content-writer | Generate content per calendar |
seo-technical | Check technical foundation |
Example
User: /seo plan
Claude: Please tell me:
1. Business type?
2. Target audience?
3. Main competitors?
4. SEO goals?
User: SaaS project management tool, targeting SMBs, competitors are Asana, Monday, Notion
Claude: [Executing competitor analysis...]
[Creating keyword strategy...]
[Planning content calendar...]
[Outputting 4 files]
[PROTOCOL]: Update this header on changes, then check CLAUDE.md
What ships with it: 6 files
27.4 KB alongside SKILL.md
assets/
- agency.md4.4 KB
- ecommerce.md4.8 KB
- generic.md4.1 KB
- local-service.md5.3 KB
- publisher.md4.5 KB
- saas.md4.4 KB
Gives 0 of the 12 instructions most marketing audience skills give in 924 tokens
Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07
- Apply Poppins font to headingsin 41 of 690, across 6 files
- Apply Lora font to body textin 41 of 690, across 6 files
- Use Arial fallback for headingsin 39 of 690, across 4 files
- Use Georgia fallback for body textin 39 of 690, across 4 files
- Maintain text hierarchy and formattingin 39 of 690, across 4 files
- Use accent colors for non-text shapesin 38 of 690, across 3 files
- Use RGB values for precise color matchingin 38 of 690, across 3 files
- Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
- Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
- Use active voice instead of passive voicein 26 of 690, across 10 files
- Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
- Prioritize clarity over clevernessin 22 of 690, across 8 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.