What does this skill do, and when should you use it?
seo-plan is a strategic planning skill for new and existing websites. It organizes discovery around business type, audience, competitors, goals, constraints, and KPIs, then turns that input into architecture, content, technical, and implementation decisions. The roadmap is divided into four phases covering foundation, expansion, scale, and authority. Its documented deliverables include strategy, competitor analysis, content calendar, implementation roadmap, and site structure files.
Collects business type, target audience, competitors, goals, current-site context, budget, timeline, and KPIs; analyzes up to five competitors for content strategy, schema usage, technical setup, keyword gaps, content opportunities, E-E-A-T signals, and estimated domain authority; loads an industry template from assets/ and designs URL hierarchy, content pillars, internal linking, sitemap structure, and user-journey information architecture; plans page types, estimated page counts, publishing cadence, E-E-A-T signals, schema, Core Web Vitals targets, AI-search readiness, and mobile-first considerations; produces SEO-STRATEGY.md, COMPETITOR-ANALYSIS.md, CONTENT-CALENDAR.md, IMPLEMENTATION-ROADMAP.md, and SITE-STRUCTURE.md. Optional DataForSEO tools can provide competitive intelligence, traffic estimates, keyword research, and local business data.
- An SEO consultant plans a new SaaS website from technical foundation through a 12-month authority roadmap.
- A marketing team maps competitor gaps, content priorities, internal linking, and local SEO work for an existing service business.
- An e-commerce team designs URL hierarchy, content pillars, schema planning, and phased KPIs before launch.
- An in-house SEO lead needs to turn content, technical work, dependencies, and resources into an executable plan.
How do you install this skill?
- Competitor analysis, domain-authority assessment, and traffic or keyword estimates may require external services; obtain explicit consent and disclose data handling before using DataForSEO or fetching websites.
- Fixed word counts, timelines, KPIs, and SEO thresholds are not guarantees and should be recalibrated to the industry, region, budget, and baseline.
- The document does not specify Chinese-language strategy or mainland-China service reachability; confirm data-source and API availability first.
- Several 2025–2026 search and platform claims in the templates lack citations within this skill and should be verified individually before use.
- Local filesystem
This skill is part of the AgriciDaniel/claude-seo repository and is located at skills/seo-plan/SKILL.md. The README documents collection installation on Unix/macOS/Linux with: git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git; bash claude-seo/install.sh. No standalone installation command for only seo-plan is documented.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/seo-plan" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
In Claude Code, make a request containing “SEO plan,” “SEO strategy,” “SEO planning,” “content strategy,” “keyword strategy,” “content calendar,” “site architecture,” or “SEO roadmap,” optionally supplying a business type, such as: /seo plan saas. Without a website URL, it uses new-site planning mode. For an unrecognized business type or missing industry template, it falls back to generic.md.
What are this skill's strengths and limitations?
- Covers discovery, competitive analysis, architecture, content, technical foundations, and implementation planning in one workflow.
- Includes SaaS, local-service, e-commerce, publisher, agency, and generic business templates.
- Defines concrete document deliverables, phased work, KPI targets, resource requirements, dependencies, and risk mitigation.
- Can be used without DataForSEO; external data enrichment is explicitly optional.
- The skill’s SKILL.md does not document a live crawler or an implementation for independently validating competitor data.
- Domain-authority, traffic, and keyword details depend on optional DataForSEO tools.
- The README documents installation for the full 33-skill repository, not a standalone seo-plan install.
- Competitive analysis assumes identified top competitors; without a URL, current-site assessment and URL-dependent gap analysis are skipped.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Strategic SEO Planner this page | 47 · Use with care | ★ 19k | 23d ago | MIT |
| Blog Brief Planner | 44 · Not recommended | ★ 2.4k | 13d ago | MIT |
| Blog Strategy Architect | 49 · Use with care | ★ 2.4k | 13d ago | MIT |
| Competitive Intelligence Analysis | 41 · Not recommended | ★ 2.8k | 8mo ago | MIT |
| Content Gap Analysis | 52 · Use with care | ★ 3k | 13d ago | Apache-2.0 |
The repository README compares the broader Claude SEO collection with manual audits, agency engagements, and commercial SEO audit tools; those comparisons are not specific to seo-plan. seo-plan is best suited to structured strategy documents and phased roadmaps, rather than serving as a standalone replacement for a deep crawler or proprietary backlink database.
How did FollowSkills review this skill?
The skill is limited to SEO planning and shows no malware, credential theft, or destructive defaults; however, competitor analysis, external URL access, and optional DataForSEO integration do not disclose permission scope, data flows, user confirmation, sensitive-data handling, or rollback, so 12 points are deducted.
The process, template fallback, and no-URL handling are reasonably specified, and the referenced industry templates are present; however, template loading, artifact generation, and API-failure behavior are unspecified, with no path-specific test evidence, so the static score is 8.
Trigger phrases, the business-type argument, and six templates define a basic use case; however, non-fit boundaries, input/output constraints, Chinese support, mainland-China reachability, and the limits of competitor analysis or domain-authority estimates are unclear, so 7 points are deducted.
The document is readable and layered, with process, templates, deliverables, KPIs, and error handling; MIT licensing, author, and version are available from metadata and repository context, but the skill lacks a changelog, explicit maintenance owner and update path, installation/dependency notes, examples, and FAQs, so 7 points are deducted.
It covers the core planning task with strategy, competitor analysis, content calendar, implementation roadmap, and site structure deliverables; however, fixed word counts, timelines, KPIs, and domain-authority estimates lack calibration evidence, and outputs still require human validation and revision, so the static score is 6.
The skill provides no per-claim sources for SEO judgments, KPI targets, schema advice, or industry conclusions; repository CI and tests are generic and do not demonstrate coverage of the seo-plan key path, so verifiability is limited to 4.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →