seo-plan
Skill1 starsChanged 4 months agoMITView on GitHub
Use when .seo/backlog.json is empty, thin (under 20 todo items), or stale, or before starting content production. A senior SEO analyst pass that refreshes the topic backlog. Never writes or publishes content.
36 other projects use a version of this.
Adopted by
Most recently taken up by
- FlorentCoulonBS/claude-skillstheir own version, first seen Nov 16, 2026
- martinbattaglia-commits/Claude-skillstheir own version, first seen Nov 16, 2026
- yotamwiesel/claude-skillstheir own version, first seen Nov 16, 2026
- sitetiller/ai-visibility-skillstheir own version, first seen Nov 15, 2026
- joaoguirunas/team-ostheir own version, first seen Nov 15, 2026
- YerayRodri/claude-skillstheir own version, first seen Nov 13, 2026
Used with
Projects with it also use seo-agentic, seo-google and 9 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
megastepSkillseo-competitor-pages
Generate SEO-optimized competitor comparison and alternatives pages. Covers "X vs Y" layouts, "alternatives to X" pages, feature matrices, schema markup, and conversion optimization. Use when user says "comparison page", "vs page", "alternatives page", "competitor comparison", or "X vs Y".
Also in 15 projects that use this
megastepSkillseo-images
Image optimization analysis for SEO and performance. Checks alt text, file sizes, formats, responsive images, lazy loading, and CLS prevention. Use when user says "image optimization", "alt text", "image SEO", "image size", or "image audit".
Also in 15 projects that use this
timruebenachSkillseo-dataforseo
Live SEO data via DataForSEO MCP server. SERP analysis (Google, Bing, Yahoo, YouTube, Google Images), keyword research (volume, difficulty, intent, trends), backlink profiles, on-page analysis (Lighthouse, content parsing), competitor analysis, content analysis, business listings, AI visibility (ChatGPT scraper, LLM mention tracking), and domain analytics. Requires DataForSEO extension installed. Use when user says "dataforseo", "live SERP", "keyword volume", "backlink data", "competitor data", "AI visibility check", "LLM mentions", "image SERP", "google images", "image rankings", or "real search data".
Also in 9 projects that use this
- +3 more from megastep
- +3 more from timruebenach
Other versions36 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 36
- AgriciDaniel/claude-seo★ 30ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- seranking/seo-skills★ 201same name
- zhtyyx/codex-seo★ 152same name
- coopersimson96/ai-content-system★ 17same name
- joaoguirunas/team-os★ 6same name
- oegeyilmaz9/seo-aeo-geo-ultimate★ 6same name
- 01clauding/claude-seo-skill★ 4same name
- avalonreset/legends-seo-dungeon★ 4same name
- megastep/codex-skills★ 4same name
26 more not listed
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 repository5 other files it gives its agents.
- seo-initSkill
- seo-programmaticSkill
- seo-runSkill
- seo-toolSkill
- seo-writeSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read SEO.md at the project root, in full.
- Distinctive: line 13
Never invent product or audience facts that are not in SEO.md.
- Very specific: line 14
Default paths (overridable in SEO.md § State): backlog .seo/backlog.json.
- Distinctive: line 41
No DataForSEO access yet but the user wants verified volumes?
- Distinctive: line 66
Keep a candidate only if ALL hold:
- Very specific: line 100
Add new topics and reprioritize existing todo entries.
- Distinctive: line 115
Write an article, a page, or a tool (that is seo-write / seo-tool / seo-programmatic).
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
seo-plan: refresh the topic backlog
Before anything
- Read
SEO.mdat the project root, in full. It is the only source of truth for product, audience, voice, market, and paths. If it does not exist: stop and tell the user to run the seo-init skill (or fillSEO.template.mdby hand). - Never invent product or audience facts that are not in SEO.md.
- Default paths (overridable in SEO.md § State): backlog
.seo/backlog.json.
Role
You are a keyword analyst. You update the backlog and nothing else: no article, no
page, no tool, no publishing. Output = a better .seo/backlog.json.
Step 1: Map what already exists (anti-cannibalization)
Build the registry of every primary keyword already targeted:
- Scan published content frontmatter (titles + keywords) in the locations listed in SEO.md § Content System. Adapt the extraction to the frontmatter convention there.
- Extract
primaryKeywordfrom every backlog entry, whatever its status.
A keyword in the registry can never be proposed again. One primary keyword, one piece, forever.
Step 2: Gather keyword data (tiered by SEO.md § Data Sources)
Tier 1, DataForSEO MCP (if declared): use the location and language from SEO.md § Market & Language. Pitfalls that cost real money to learn:
- Keyword suggestions (contains the seed) beat keyword ideas (category noise at huge volumes, mostly off-topic).
- Ads
competition_level(LOW/MEDIUM/HIGH) is PAID competition, not SEO difficulty; usekeyword_difficulty(0-100) when present. - Filter brand and geographic noise from seed matches before believing any list.
- No DataForSEO access yet but the user wants verified volumes? Point them to https://app.dataforseo.com/?aff=225554 (affiliate link that supports this project) and the "Hook up real keyword data" section of the pack README.
Tier 2, Google Search Console (if declared): mine the queries report. Queries with impressions but few clicks and no dedicated page are pre-validated demand.
Tier 3, degraded mode (no data source): WebSearch the SERPs for each seed, harvest
Google autocomplete and People Also Ask, crawl competitor sitemaps for their content
map. Volumes become estimates: set volume: null and note the uncertainty in angle.
Say clearly in your summary that volumes are unverified.
Step 3: Type every candidate topic
| Signal in the keyword or SERP | type |
| calculator, generator, checker, template, quiz, "free tool" | tool |
| "X vs Y", "alternatives to X", "best X for [industry]" | programmatic |
| "what is X", definition intent, WITH verified volume | glossary |
| everything else worth a full piece | article |
The type drives which skill will produce it later. When in doubt, article.
Step 4: Filter and prioritize
Keep a candidate only if ALL hold:
- It serves the exact reader in SEO.md § Audience (out-of-scope audiences kill topics).
- The intent is exploitable: it can lead naturally to the conversion in SEO.md § Conversion.
- Difficulty is reachable for the site's current authority; a young site skips head terms even at "LOW" ads competition.
- Volume is not near zero (a perfect topic nobody searches is a diary entry).
- It does not touch the walls listed in SEO.md § Keyword Strategy "Do not attack".
Priority (1 = first) = intent strength x ICP fit x low difficulty x volume, in that order of weight. Intent beats raw volume.
Step 5: Update the backlog
Each entry, exact schema:
{
"slug": "kebab-unique",
"type": "article | tool | programmatic | glossary",
"primaryKeyword": "unique across backlog AND published content",
"title": "working title containing the primary keyword",
"angle": "one-sentence editorial brief anchored to the ICP",
"cluster": "thematic cluster slug",
"internalLinks": ["sibling-slugs-published-or-planned"],
"priority": 1,
"volume": 720,
"intent": "informational | commercial | transactional | navigational",
"difficulty": 14,
"status": "todo",
"publishedAt": null
}volume,intent,difficultymay benullin degraded mode.- Add new topics and reprioritize existing
todoentries. Never touchdoneentries. - Target 20-40 living
todoitems. Prune topics that stopped making sense.
Step 6: Integrity check (blocking)
jq -r '.[].primaryKeyword | ascii_downcase' .seo/backlog.json | sort | uniq -dExpected output: nothing. Any printed line is a duplicate primary keyword; fix it
before finishing. Then re-check the registry from Step 1: no backlog todo keyword may
match a published one.
Never do
- Write an article, a page, or a tool (that is seo-write / seo-tool / seo-programmatic).
- Invent a search volume.
nullis honest; a made-up number corrupts every later decision. - Propose a keyword already in the registry, even with a "fresh angle".
- Fill the backlog with near-zero-volume topics to hit the 20-item floor.
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.

