seo-plan
Build SEO strategy and roadmap. Use when: planning site architecture, content strategy, or phased implementation.
What this skill does
# /digital-marketing-pro:seo-plan
## Purpose
Generate a comprehensive SEO strategy with industry-specific templates, competitive analysis, content roadmap, and phased implementation plan. Covers both traditional SEO and AI search readiness.
## Dispatcher mode (Confirm-Then-Dispatch)
When invoked on a brand that already has recent specialist outputs in `${CLAUDE_PLUGIN_DATA}/{brand}/seo/`, this skill operates as an **orchestrator** — it reads those outputs as inputs, scores the brand across four pillars, and uses the **weakest pillar to drive the lead theme** of the plan.
### Step D0 — detect fresh outputs (≤ 30 days)
Look under `${CLAUDE_PLUGIN_DATA}/{brand}/seo/` for the latest dated subfolder of each:
| Specialist skill | Output folder |
|---|---|
| `/digital-marketing-pro:tech-seo-audit` | `seo/tech-seo-audit/{YYYY-MM-DD}/PLAN.md` |
| `/digital-marketing-pro:content-decay-scan` | `seo/content-decay-scan/{YYYY-MM-DD}/PLAN.md` |
| `/digital-marketing-pro:aeo-audit` | `seo/aeo-audit/{YYYY-MM-DD}/PLAN.md` |
| `/digital-marketing-pro:backlink-gap` | `seo/backlink-gap/{YYYY-MM-DD}/PLAN.md` |
| `/digital-marketing-pro:gsc-ai-performance` | `seo/gsc-ai-performance/{YYYY-MM-DD}/PLAN.md` |
| `/digital-marketing-pro:keyword-cluster` | `seo/keyword-cluster/{YYYY-MM-DD}/PLAN.md` |
| `/digital-marketing-pro:seo-drift` | `seo/seo-drift/{YYYY-MM-DD}/PLAN.md` |
Any folder dated within the last **30 days** counts as fresh — its `PLAN.md` becomes a primary input.
### Step D1 — confirm before dispatching missing specialists
If some specialists have no fresh output, **do not silently re-run them.** Print exactly:
```
The following specialist outputs are missing or stale (>30 days old):
- tech-seo-audit (last: 2026-05-12 — 23 days old)
- backlink-gap (no run found)
- gsc-ai-performance (no run found)
Running these now will use approximately N MCP credits / API calls.
Run them now in this session? (y / N — default N)
```
- **If `y`** — dispatch in this order:
- **Parallel batch 1**: `tech-seo-audit`, `backlink-gap`, `aeo-audit`, `gsc-ai-performance` (independent)
- **Sequential after**: `content-decay-scan` (depends on `tech-seo-audit`'s URL inventory), `keyword-cluster` (depends on `aeo-audit` query set)
- Each specialist runs its own budget guard; surface aborts back to the user
- **If `N` or default** — fall through; treat missing pieces as Phase 0 ("Discovery") work in the final plan
### Step D2 — pillar scoring (the heart of the dispatcher)
Score each of four pillars 1–10 based on the available specialist outputs:
| Pillar | Sources | What 10 looks like |
|---|---|---|
| **Technical** | tech-seo-audit / gsc-ai-performance / Core Web Vitals data | Clean crawlability, all CWV pass, schema validates, sitemap accurate |
| **Content** | content-decay-scan / seo-audit / content-engine outputs | Topic coverage matches search demand, no cannibalisation, freshness ≥ 80% |
| **Topical** | keyword-cluster / aeo-geo / entity-audit | Clear pillar+spokes structure, entity consistency across Knowledge Graph |
| **AI Search** | aeo-audit / gsc-ai-performance / aeo-geo | Cited in AI Mode + AI Overviews + ChatGPT + Perplexity for target queries |
**The lowest-scoring pillar becomes the LEAD THEME** of the next quarter's plan. Everything else is supporting work. This forces focus.
### Step D3 — dispatcher output
Produce `${CLAUDE_PLUGIN_DATA}/{brand}/seo/seo-plan/{YYYY-MM-DD}/00-pillar-scorecard.md`:
```
Pillar scorecard for {brand} ({date})
=====================================
Technical : 8 / 10 ✓ healthy
Content : 6 / 10 ⚠ moderate gaps
Topical : 4 / 10 ⚠ LEAD THEME — weakest pillar
AI Search : 7 / 10 ✓ trending up
Lead theme this quarter: Topical authority build-out
(keyword cluster expansion + entity consistency + Knowledge Graph optimisation)
```
The rest of the plan (sections 1-6 below) is then **framed around the lead theme** — supporting work for the other 3 pillars stays in the plan but doesn't drive timeline / budget.
## Numbered output convention
The full dispatcher run produces, under `${CLAUDE_PLUGIN_DATA}/{brand}/seo/seo-plan/{YYYY-MM-DD}/`:
```
00-pillar-scorecard.md (from Step D2)
01-discovery.md (business type, audience, competitors — from §1 below)
02-competitive-analysis.md (competitors + gap synthesis — from §2 + backlink-gap if fresh)
03-architecture.md (URL hierarchy, internal-link strategy — from §3 + keyword-cluster if fresh)
04-content-strategy.md (content gaps, calendar, E-E-A-T — from §4 + content-decay-scan if fresh)
05-technical-foundation.md (hosting, schema, CWV — from §5 + tech-seo-audit if fresh)
06-roadmap.md (phased 12-month — from §6, framed around lead theme)
07-industry-template.md (which template applied — from §Industry Templates)
08-kpi-dashboard.md (metrics + cadence — what gets re-measured next drift)
PLAN.md (the deliverable)
```
## Input Required
- **Business type**: SaaS, ecommerce, local service, publisher/media, agency, or general
- **Website URL**: Existing site (if any) to assess
- **Target audience and markets**: Geographic, demographic, and intent profiles
- **Competitors**: 3-5 competitor URLs for gap analysis
- **Budget and timeline**: Resource constraints
- **KPIs**: What success looks like (traffic, rankings, conversions, AI visibility)
## Process
### 1. Discovery
- Business type, target audience, competitors, goals
- Current site assessment (if exists) — crawl health, content inventory, authority signals
- Budget and timeline constraints
- Key performance indicators (KPIs) aligned to business objectives
### 2. Competitive Analysis
- Identify top 5 competitors
- Analyze their content strategy, schema usage, technical setup
- Identify keyword gaps and content opportunities
- Assess their E-E-A-T signals
- Estimate domain authority and link profiles
- AI visibility comparison — which competitors appear in AI overviews
### 3. Architecture Design
- Design URL hierarchy and content pillars based on business model
- Plan internal linking strategy (hub/spoke, topic clusters)
- Sitemap structure with quality gates applied
- Information architecture for user journeys
- Navigation and breadcrumb planning
### 4. Content Strategy
- Content gaps vs competitors
- Page types and estimated counts
- Blog/resource topics and publishing cadence
- E-E-A-T building plan (author bios, credentials, experience signals)
- Content calendar with priorities
- AI-optimized content structure (entity consistency, citation-worthy formatting)
### 5. Technical Foundation
- Hosting and performance requirements
- Schema markup plan per page type
- Core Web Vitals baseline targets (LCP <2.5s, INP <200ms, CLS <0.1)
- AI search readiness requirements
- Mobile-first considerations
- International SEO setup (if applicable)
### 6. Implementation Roadmap (4 phases)
**Phase 1: Foundation (weeks 1-4)**
- Technical setup and infrastructure
- Core pages (home, about, contact, main services/products)
- Essential schema implementation (Organization, LocalBusiness, BreadcrumbList)
- Analytics and tracking setup (GA4, GSC, rank tracking)
**Phase 2: Expansion (weeks 5-12)**
- Content creation for primary pages
- Blog launch with initial posts
- Internal linking structure buildout
- Local SEO setup (if applicable)
- First E-E-A-T improvements (author pages, credentials)
**Phase 3: Scale (weeks 13-24)**
- Advanced content development (pillar pages, topic clusters)
- Link building and digital PR outreach
- GEO/AEO optimization for AI search visibility
- Performance optimization (CWV, page speed)
- Schema expansion (FAQ, Product, VideoObject as applicable)
**Phase 4: Authority (months 7-12)**
- Thought leadership content
- PR and media mentions
- Advanced schema implementation
- Continuous optimization based on data
- Competitive gap monitoring
## Industry Templates
### SaaS
- Primary pages: features, pricing, integrations, usRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".