seo-content
Skill1 starsChanged 30 days agoMITView on GitHub
Plans and audits search content: keyword research, intent and page type, topic clusters, briefs, programmatic pages without doorway risk, comparison pages with EU legal gates, local SEO, GSC page-2 audits and pre-publish gates. Use for "keyword research", "content gaps vs competitors", "content brief", "programmatic SEO", "comparison page", "page 2 queries", "cannibalisation". Not for links (seo-authority) or AI citations (seo-ai-search).
39 other projects use a version of this.
Adopted by
Most recently taken up by
- alpit-patel/seo-aeo-geo-kittheir own version, first seen Nov 8, 2026
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
- zhtyyx/codex-seotheir own version, first seen Nov 1, 2026
- genspark-ai/genofficetheir own version, first seen Oct 25, 2026
- joaoguirunas/team-ostheir own version, first seen Oct 21, 2026
- susantedit/claude-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use seo-agentic, seo-image-gen 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 5 projects that use this
timruebenachSkillseo-image-gen
AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says \"generate image\", \"OG image\", \"social preview\", \"hero image\", \"blog image\", \"product photo\", \"infographic\", \"seo image\", \"create visual\", \"image-gen\", \"favicon\", \"schema image\", \"pinterest pin\", \"generate visual\", \"banner\", or \"thumbnail\".
Also in 16 projects that use this
- timruebenachSkill
seo-cluster
SERP-based semantic topic clustering for content architecture planning. Groups keywords by actual Google SERP overlap (not text similarity), designs hub-and-spoke content clusters with internal link matrices, and generates interactive visualizations. Optionally executes content creation if claude-blog is installed. Use when user says "topic cluster", "content cluster", "semantic clustering", "pillar page", "hub and spoke", "content architecture", "keyword grouping", or "cluster plan".
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 23 projects that use this
- megastepSkill
seo-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 23 projects that use this
mangollcSkillseo-backlinks
Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.
Also in 17 projects that use this
- +3 more from timruebenach
- +2 more from megastep
Other versions39 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 39
- AgriciDaniel/claude-seo★ 20ksame name
- genspark-ai/genoffice★ 12ksame name
- zhtyyx/codex-seo★ 152same name
- mangollc/claude-seo-skill★ 39same name
- MoizIbnYousaf/marketing-cli★ 33same name
- sanky369/vibe-building-skills★ 30same name
- coopersimson96/ai-content-system★ 17same name
- ZachArticulateV/designer-pro-and-seo★ 10same name
- bestdeejay-design/agent-skills★ 6same name
- joaoguirunas/team-os★ 6same name
29 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 repository7 other files it gives its agents.
- seo-ai-searchSkill
- seo-authoritySkill
- seo-engine-policiesSkill
- seo-evidenceSkill
- seo-optimizerSkill
- seo-strategySkill
- seo-technicalSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Never forecast a published number onto a client site.
- Very specific: line 15
No rollout without a pre-declared revert rule (applicability, holdout, what stays fixed, metric + window, trigger).
- Distinctive: line 52
If the intent cannot be named, the page is not ready to build.
“Common” is measured: kept by at least 6 in 10 of the 36 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-content
Which queries are worth winning, which page owns each, and what that page must contain before it ships.
<!-- grammar-excerpt -->Label every tactic with one of the 9 marks: [documented: <URL>, <date>] · [documented-secondary: …] · [unverified: …] · [measured: MARK, n=S, c=C] · [practitioner: anonymised sources · …] · [hypothesis] · [vendor] · [memory] · [unvalidated house heuristic].
Numbers keep their denominator; marks are counts, not verdicts; bundles support direction, not size.
Never forecast a published number onto a client site; only the client's own GSC demand and funnel forecast.
No rollout without a pre-declared revert rule (applicability, holdout, what stays fixed, metric + window, trigger).
Repetition never proves; full grammar: skill seo-optimizer § Evidence marks.
<!-- /grammar-excerpt -->Load rule
Open one reference per load-when row the question touches (a "by H2" row: only the part holding that H2); never a file "to be thorough". A pointer into another seo- skill's file is a citation: quote it, or first load that skill's SKILL.md and open the file through its own load-when row. Engine pages, ledger and practitioner parts and the crawler registry are lookup-only.
Load when
| ID | Question shape | Open |
| CO1 | keyword research | the part holding the step: part 1 (order, GSC, Bing, free sources) or part 2 (categorise, validate, prioritise, map) |
| CO2 | intent, page type, refresh, decay | by H2: part 1 (intent, clusters, briefs, titles, scoring) or part 2 (refresh and decay triage, cannibalisation) |
| CO3 | programmatic pages, section risk | by H2: part 1 (distinction, checklist, data tiers, patterns, playbooks) or part 2 (implementation, section-level risk check, when not to) |
| CO4 | comparison pages, EU legal gates | by H2: part 1 (subtypes, schema, fairness, claim audit, EU legal gates) or part 2 (rollout gates, comparison-site practice) |
| CO5 | GSC page 2, striking distance | by H2: part 1 (access, MCP guards, anonymisation, bands, segments) or part 2 (page audit, the three above you, output contract) |
| CO6 | briefs, personas, research before the brief | by H2: part 1 (modes, rules, information gain, research, variants) or part 2 (competitor filter, output shape, personas, wireframes) |
| CO7 | pre-publish and pipeline gates | publishing-gates.md |
| CO8 | local and Maps | local-and-maps-seo.md |
| CO9 | SERP clustering, page types | page-types-and-serp-clustering.md |
| CO10 | prompts for flow wins | flow-win-prompts.md |
Scripts (run, not loaded): scripts/gsc_bigquery.sql (GSC bulk export: low CTR, page 2, cannibalisation), scripts/autocomplete_expand.py (set both --hl and --gl).
Not mine
| Question | Skill |
| will an engine penalise this template | seo-engine-policies |
| does a content tactic work | seo-evidence |
| links, PR, E-E-A-T | seo-authority |
| getting cited by AI answer engines | seo-ai-search |
| "can we say this" (claims) | your claims review |
Rules
- If the intent cannot be named, the page is not ready to build.
- One stable URL per distinct intent; identical bodies with changed titles or slugs are a doorway warning sign; check function (funnels to one page = doorway).
- Value per URL decides programmatic scale, not the production method.
- Comparison and credit/insurance pages pass the EU legal gates before a precise number ships.
- GSC first: own impressions beat any keyword-tool estimate.
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.