seo-plan
Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", or "SEO roadmap".
Best use case
seo-plan is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", or "SEO roadmap".
Teams using seo-plan should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/seo-plan/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How seo-plan Compares
| Feature / Agent | seo-plan | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", or "SEO roadmap".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Strategic SEO Planning ## When to Use - Use when building an SEO strategy or roadmap for a new or existing site. - Use when planning content, architecture, and implementation phases together. - Use when the user asks for an SEO plan rather than a point-in-time audit. ## Process ### 1. Discovery - Business type, target audience, competitors, goals - Current site assessment (if exists) - Budget and timeline constraints - Key performance indicators (KPIs) ### 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 their domain authority ### 3. Architecture Design - Load industry template from `assets/` directory - Design URL hierarchy and content pillars - Plan internal linking strategy - Sitemap structure with quality gates applied - Information architecture for user journeys ### 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 ### 5. Technical Foundation - Hosting and performance requirements - Schema markup plan per page type - Core Web Vitals baseline targets - AI search readiness requirements - Mobile-first considerations ### 6. Implementation Roadmap (4 phases) #### Phase 1: Foundation (weeks 1-4) - Technical setup and infrastructure - Core pages (home, about, contact, main services) - Essential schema implementation - Analytics and tracking setup #### Phase 2: Expansion (weeks 5-12) - Content creation for primary pages - Blog launch with initial posts - Internal linking structure - Local SEO setup (if applicable) #### Phase 3: Scale (weeks 13-24) - Advanced content development - Link building and outreach - GEO optimization - Performance optimization #### Phase 4: Authority (months 7-12) - Thought leadership content - PR and media mentions - Advanced schema implementation - Continuous optimization ## Industry Templates Load from `assets/` directory: - `saas.md`: SaaS/software companies - `local-service.md`: Local service businesses - `ecommerce.md`: E-commerce stores - `publisher.md`: Content publishers/media - `agency.md`: Agencies and consultancies - `generic.md`: General business template ## Output ### Deliverables - `SEO-STRATEGY.md`: Complete strategic plan - `COMPETITOR-ANALYSIS.md`: Competitive insights - `CONTENT-CALENDAR.md`: Content roadmap - `IMPLEMENTATION-ROADMAP.md`: Phased action plan - `SITE-STRUCTURE.md`: URL hierarchy and architecture ### KPI Targets | Metric | Baseline | 3 Month | 6 Month | 12 Month | |--------|----------|---------|---------|----------| | Organic Traffic | ... | ... | ... | ... | | Keyword Rankings | ... | ... | ... | ... | | Domain Authority | ... | ... | ... | ... | | Indexed Pages | ... | ... | ... | ... | | Core Web Vitals | ... | ... | ... | ... | ### Success Criteria - Clear, measurable goals per phase - Resource requirements defined - Dependencies identified - Risk mitigation strategies ## DataForSEO Integration (Optional) If DataForSEO MCP tools are available, use `dataforseo_labs_google_competitors_domain` and `dataforseo_labs_google_domain_intersection` for real competitive intelligence, `dataforseo_labs_bulk_traffic_estimation` for traffic estimates, `kw_data_google_ads_search_volume` and `dataforseo_labs_bulk_keyword_difficulty` for keyword research, and `business_data_business_listings_search` for local business data. ## Error Handling | Scenario | Action | |----------|--------| | Unrecognized business type | Fall back to `generic.md` template. Inform user that no industry-specific template was found and proceed with the general business template. | | No website URL provided | Proceed with new-site planning mode. Skip current site assessment and competitive gap analysis that require a live URL. | | Industry template not found | Check `assets/` directory for available templates. If the requested template file is missing, use `generic.md` and note the missing template in output. | ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
seo-content-planner
Creates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.
puzzle-activity-planner
Plan puzzle-based activities for classrooms, parties, and events with pre-configured generator links
planning-with-files
Work like Manus: Use persistent markdown files as your "working memory on disk."
plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
inventory-demand-planning
Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers.
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
concise-planning
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.