SkillAgentSearch skills...

seo-plan

Build a 12-month SEO strategy and phased roadmap with industry templates (SaaS, ecommerce, local, publisher, agency). With fresh specialist outputs it runs as a dispatcher: scores four pillars — technical, content, topical, AI search — and makes the weakest pillar the plan's lead theme; missing spec…

Install / Use

npx skills add indranilbanerjee/digital-marketing-pro --skill seo-plan

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

91/100

Supported Platforms

Universal

Our assessment of seo-plan

seo-plan scores 91/100 on our quality scale, 22nd of 90 Product Management skills we index (top 25%).

Its SKILL.md is 15 KB long, well organised into 30 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.

It has 832 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 26 days ago, so seo-plan is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

seo-plan compared with similar skills

All 4 of these similar skills score higher than seo-plan; compare them before choosing.

SkillScoreStarsUpdatedFormat
seo-plan (this skill)by indranilbanerjee9183226d agoSKILL.md
Agent-Reachby Panniantong10090.1k18d agoCLAUDE.md
algorithmic-artby anthropics100177.9k11d agoSKILL.md
pptxby anthropics100177.9k11d agoSKILL.md
designby nextlevelbuilder100130.2k12d agoSKILL.md

Frequently asked questions

How do I install seo-plan?
Run npx skills add indranilbanerjee/digital-marketing-pro --skill seo-plan. The install tabs above show the steps for each supported agent.
Which AI agents does seo-plan work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is seo-plan safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is seo-plan still maintained?
The repository was last updated 26 days ago, so seo-plan is actively maintained.

name: seo-plan description: "Build a 12-month SEO strategy and phased roadmap with industry templates (SaaS, ecommerce, local, publisher, agency). With fresh specialist outputs it runs as a dispatcher: scores four pillars — technical, content, topical, AI search — and makes the weakest pillar the plan's lead theme; missing specialists re-run only after explicit confirmation. Plans and prioritises only — makes no live changes. Triggers on "/digital-marketing-pro:seo-plan", "build an SEO strategy", "what should our SEO roadmap be", "plan SEO for a new site", "which SEO pillar is weakest". Reads specialist PLAN.md outputs (tech-seo-audit, content-decay-scan, aeo-audit, backlink-gap, keyword-cluster, seo-drift); feeds /digital-marketing-pro:content-engine and /digital-marketing-pro:campaign-plan." argument-hint: "[business-type]" user-invocable: true

/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, use cases, solutions by role
  • Content pillars: product education, industry trends, comparison content, technical guides
  • Schema focus: SoftwareApplication, Product, FAQPage (if eligible), HowTo (deprecated — use article format instead)
  • Link strategy: integration partner pages, guest posts on tech blogs, product directories

Local Service

  • Primary pages: services, service areas, about, contact, testimonials
  • Content pillars: service guides, local area content, FAQ content, case studies
  • Schema focus: LocalBusiness, Service, Review, BreadcrumbList, GeoCircle
  • Link strategy: local directories, chamber of commerce, local press, community involvement

eCommerce

  • Primary pages: categories, products, brands, collections, buying guides
  • Content pillars: product education, comparison content, buying guides, trend content
  • Schema focus: Product, ProductGroup, Offer, AggregateRating, BreadcrumbList, ItemList
  • Link strategy: product reviews, affiliate partnerships, manufacturer relationships

Publisher/Media

  • Primary pages: sections, topic pages, author pages, about, editorial standards
  • Content pillars: news coverage, analysis, opinion, investigative, data journalism
  • Schema focus: Article, NewsArticle, Person (authors), Organization, VideoObject
  • Link strategy: original research citations, expert sourcing, data exclusives

Agency

  • Primary pages: services, industries, case studies, team, methodology
  • Content pillars: industry expertise, methodology content, case studies, thought leadership
  • Schema focus: Organization, Service, Person (team), Article
  • Link strategy: case study features, speaking engagements, industry publications, client co-marketing

Output

Deliverables

  • SEO Strategy Document: Complete strategic plan with business context, competitive landscape, and strategic direction
  • Competitive Analysis: Keyword gaps, content gaps, authority comparison, AI visibility comparison
  • Content Calendar: 12-week content roadmap with topics, formats, keywords, and publishing schedule
  • Implementation Roadmap: Phased action plan with milestones, responsibilities, and measurement checkpoints
  • Site Architecture Plan: URL hierarchy, content pillar structure, internal linking strategy
  • Schema Markup Plan: Per-page-type schema recommendations with JSON-LD templates
  • KPI Dashboard Specification: Metrics to track, tools needed, reporting cadence

Agents Used

  • seo-specialist — Strategy, competitive analysis, technical planning
  • content-creator — Content strategy and calendar planning
  • competitive-intel — Competitor analysis and gap identification
  • marketing-strategist — Business alignment and KPI framework

Scripts Used

  • competitor-scraper.py — Competitor site analysis
  • tech-seo-auditor.py — Current site technical assessment
  • keyword_cluster.py — Keyword clustering with SERP-overlap + quality scorecard (use via /digital-marketing-pro:keyword-cluster)
  • content-scorer.py — Current content quality baseline

Quality scorecard

Every PLAN.md this skill produces must p

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars832
CategoryProduct
Updated26d ago
Forks136

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions