seo-plan
Skill0 starsChanged 3 days agoMITView on GitHub
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".
36 other projects use a version of this, 20 of them edited.
Adopted by
Most recently taken up by
- FlorentCoulonBS/claude-skillsedited, first seen Nov 16, 2026
- martinbattaglia-commits/Claude-skillsedited, first seen Nov 16, 2026
- yotamwiesel/claude-skillsword for word, first seen Nov 16, 2026
- sitetiller/ai-visibility-skillstheir own version, first seen Nov 15, 2026
- joaoguirunas/team-osedited, first seen Nov 15, 2026
- seranking/seo-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use seo-agentic, seo-google and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AgriciDanielSkillseo-agentic
Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).
Also in 4 projects that use this
timruebenachSkillseo-google
Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "google api setup", "real CWV data", "impressions", "clicks", "CTR", "position data", "LCP", "INP", "CLS", "FCP", "TTFB", or "Lighthouse scores".
Also in 10 projects that use this
timruebenachSkillseo-flow
FLOW framework integration — evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.
Also in 8 projects that use this
- +3 more from timruebenach
Other versions36 projects use a version of this.
Word for word · 7
- coopersimson96/ai-content-system★ 17100% same
- 01clauding/claude-seo-skill★ 4100% same
- megastep/codex-skills★ 4100% same
- realwigu/claude-skills★ 4100% same
- get-proofpilot/claude-skills-catalog★ 1100% same
- royaluniondesign-sys/claude-os★ 1100% same
- yotamwiesel/claude-skills★ 0100% same
Edited · 20
- AgriciDaniel/claude-seo★ 30k61% same
- zhtyyx/codex-seo★ 15262% same
- joaoguirunas/team-os★ 662% same
- avalonreset/legends-seo-dungeon★ 472% same
- alpit-patel/seo-aeo-geo-kit★ 259% same
- agrivisionai/claude-skills★ 168% same
- hungphamwp/claude-skills★ 186% same
- mahiunfiltered/claude-code-skills★ 168% same
- unknownking07/claude-skills★ 170% same
- ahmedaminsa/aljazeera360-mcp-server★ 068% same
10 more not listed
Wrote their own version · 9
- indranilbanerjee/digital-marketing-pro★ 934same name
- seranking/seo-skills★ 201same name
- oegeyilmaz9/seo-aeo-geo-ultimate★ 6same name
- amirjahfar1/automate-seo-with-claude★ 2same name
- lsidore/seo-md★ 1same name
- david-corroy/skills-seo-geo★ 0same name
- Gallyan/trouvable★ 0same name
- sitetiller/ai-visibility-skills★ 0same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- auditoria-localSkill
- consent-mode-v2-gtmSkill
- diseno-webSkill
- mejora-sistemaSkill
- n8n-code-javascriptSkill
- n8n-code-pythonSkill
- n8n-expression-syntaxSkill
- n8n-mcp-tools-expertSkill
- n8n-node-configurationSkill
- n8n-validation-expertSkill
- n8n-workflow-patternsSkill
- reelSkill
- seo-auditSkill
- seo-competitor-pagesSkill
- seo-contentSkill
- seo-geoSkill
- seo-hreflangSkill
- seo-imagesSkill
- seo-pageSkill
- seo-programmaticSkill
- seo-schemaSkill
- seo-sitemapSkill
- seoSkill
- seo-technicalSkill
- shopify-audit-setupSkill
The file
Files
Strategic SEO Planning
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 companieslocal-service.md— Local service businessesecommerce.md— E-commerce storespublisher.md— Content publishers/mediaagency.md— Agencies and consultanciesgeneric.md— General business template
Output
Deliverables
SEO-STRATEGY.md— Complete strategic planCOMPETITOR-ANALYSIS.md— Competitive insightsCONTENT-CALENDAR.md— Content roadmapIMPLEMENTATION-ROADMAP.md— Phased action planSITE-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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

