E2E SEO Assistant
irinabuht12-oss/marketing-skills
Full SEO workflow covering technical audits, content gaps, backlink opportunities, on-page fixes, and content briefs.
Subdomain ownership map for a domain. An agent skill from seranking/seo-skills.
Install SEO Subdomain
$ npx skills add seranking/seo-skills --skill seo-subdomain -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seranking/seo-skills seo-subdomain --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/seranking/seo-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-subdomain .claude/skills/seo-subdomain && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "seo-subdomain" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-subdomain into .claude/skills/seo-subdomain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-subdomain", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/seranking/seo-skills/tree/main/skills/seo-subdomainType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add seranking/seo-skills --skill seo-subdomain -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seranking/seo-skills seo-subdomain --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seranking/seo-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo-subdomain .agents/skills/seo-subdomain && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "seo-subdomain" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-subdomain into .agents/skills/seo-subdomain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-subdomain", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seranking/seo-skills --skill seo-subdomain -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seranking/seo-skills seo-subdomain --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seranking/seo-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo-subdomain .cursor/skills/seo-subdomain && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "seo-subdomain" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-subdomain into .cursor/skills/seo-subdomain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-subdomain", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/seranking/seo-skills.git --path skills/seo-subdomain--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add seranking/seo-skills --skill seo-subdomain -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seranking/seo-skills seo-subdomain --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seranking/seo-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo-subdomain .gemini/skills/seo-subdomain && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "seo-subdomain" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-subdomain into .gemini/skills/seo-subdomain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-subdomain", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install seranking/seo-skills seo-subdomainInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add seranking/seo-skills --skill seo-subdomain -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/seranking/seo-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo-subdomain .github/skills/seo-subdomain && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "seo-subdomain" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-subdomain into .github/skills/seo-subdomain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-subdomain", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seranking/seo-skills --skill seo-subdomain -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install seranking/seo-skills seo-subdomain --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seranking/seo-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo-subdomain .opencode/skills/seo-subdomain && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "seo-subdomain" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-subdomain into .opencode/skills/seo-subdomain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-subdomain", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
seo-subdomain- GitHub stars
- 160
- Token cost
- ~2.1k tokens
- SKILL.md length
- 648 words
- Files
- 1
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- MIT
At a glance
Subdomain ownership map for a domain. An agent skill from seranking/seo-skills.
- Works in 10 steps: Validate & preflight → Discover subdomains… → Per-subdomain overview… → …
- The user asks subdomain analysis
- SKILL.md covers Prerequisites, Process, Output format and Tips
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
SEO Subdomain is an agent skill from seranking/seo-skills. Subdomain ownership map for a domain. Lists subdomains, queries overview/keywords/competitors/backlinks per subdomain, surfaces which subdomains own which topic clusters, where there's fragmentation, and whether consolidation is warranted. Use when the user asks "subdomain analysis", "subdomain ownership", "subdomain SEO", "blog vs main domain", "support vs docs subdomain", or "should I consolidate subdomains".
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Link building and Content strategy. The repository describes itself as: Claude SEO Skills — production Claude Agent Skills for the SE Ranking MCP server. Content briefs, AI Search share of voice, audits, backlink gaps, keyword clusters, schema… The licence is MIT.
When your agent uses it
- The user asks subdomain analysis
- Subdomain ownership
- Blog vs main domain
- Support vs docs subdomain
Example prompts
- “subdomain analysis”
- “subdomain ownership”
- “subdomain SEO”
- “/seo-subdomain”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Validate & preflight
- Discover subdomains DATA_getDomainSubdomains
- Per-subdomain overview DATA_getDomainOverviewWorldwide
- Per-subdomain top keywords DATA_getDomainKeywords
- Per-subdomain competitors DATA_getDomainCompetitors
- Per-subdomain backlinks DATA_getBacklinksSummary and DATA_getBacklinksRefDomains (top 20)
- Authority distribution DATA_getDistributionOfDomainAuthority
- Detect fragmentation
- Make recommendations
- Synthesise SUBDOMAINS.md
What it can do on your machine
Read from SKILL.md and the folder at commit fd6d140. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
SEO Subdomain loads about 2.1k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 648 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from seranking/seo-skills at commit fd6d140, republished under its MIT licence (© seranking). 648 words, ~2,094 tokens.
Download SKILL.mdSave it as
.claude/skills/seo-subdomain/SKILL.md (or your agent's skills folder).- name
- seo-subdomain
- description
- Subdomain ownership map for a domain. Lists subdomains, queries overview/keywords/competitors/backlinks per subdomain, surfaces which subdomains own which topic clusters, where there's fragmentation, and whether consolidation is warranted. Use when the user asks "subdomain analysis", "subdomain ownership", "subdomain SEO", "blog vs main domain", "support vs docs subdomain", or "should I consolidate subdomains".
Example output: examples/seo-subdomain-notion-so-20260514/SUBDOMAINS.md
Subdomain Analysis
Map a domain's subdomain ecosystem. Which subdomains exist, what each ranks for, where they overlap, and whether the structure is healthy or fragmented. Output: an ownership map (which topic is owned by which subdomain), a fragmentation report, and recommendations for consolidate / split / leave alone.
Prerequisites
- SE Ranking MCP server connected.
- User provides: a target root domain (e.g.
example.com). The skill discovers subdomains automatically. - Optional:
--limit Nto cap the number of subdomains analysed (default: top 10 by ranked keyword count).
Process
Validate & preflight
- Normalise root domain (no protocol, no
www.). DATA_getCreditBalance— surface remaining credits. Subdomain analysis is N × ~5 calls; cost scales with subdomain count.
- Normalise root domain (no protocol, no
Discover subdomains
DATA_getDomainSubdomains- List all subdomains of the root domain.
- For each: keyword count, traffic estimate, backlinks count.
- Sort by ranked-keyword count descending.
- Apply
--limit(default top 10).
Per-subdomain overview
DATA_getDomainOverviewWorldwide- For each subdomain in scope: domain authority, traffic estimate, organic + paid keyword counts, top regions.
- This establishes a baseline for cross-subdomain comparison.
Per-subdomain top keywords
DATA_getDomainKeywords- For each subdomain: top 100 organic keywords with positions, intent, traffic.
- Cluster keywords by topic. This skill's grouping is a lightweight per-subdomain ownership map, not a content plan — token-grouping by head term + intent is sufficient here. (For full content-cluster planning use
seo-keyword-cluster, which now clusters by SERP overlap, not text similarity.) - Each subdomain gets a list of "owned topics" (clusters where it dominates) and "minor topics".
Per-subdomain competitors
DATA_getDomainCompetitors- For each subdomain: top organic competitors by
common_keywords. - Surface: do different subdomains have different competitor sets? (Sign of legitimately separate scopes.) Do they share competitors? (Sign of redundant scopes.)
- For each subdomain: top organic competitors by
Per-subdomain backlinks
DATA_getBacklinksSummaryandDATA_getBacklinksRefDomains(top 20)- Subdomains often have separate backlink profiles. Capture each.
- Surface: do subdomains have meaningfully different referring-domain populations?
Authority distribution
DATA_getDistributionOfDomainAuthority- For each subdomain, pull DA distribution of referring domains.
Detect fragmentation
- For each topic-cluster, identify all subdomains ranking for keywords in that cluster.
- Fragmentation signal: ≥ 2 subdomains rank in the top 50 for the same high-volume keyword (cannibalization).
- Healthy split: distinct topic clusters per subdomain, minimal overlap.
Make recommendations
- Consolidate: if
blog.example.comandexample.com/blog/both rank for the same topic cluster but neither dominates — pick one canonical home. - Split: if a subdomain is ranking for a topic completely off-mission for the root domain, that's a split worth keeping.
- Leave alone: if subdomains have distinct topic ownership and don't cannibalize, don't disturb.
- Investigate: ambiguous cases flagged for human review.
- Consolidate: if
Synthesise
SUBDOMAINS.md
Show full SKILL.md (237 more words)Show less
Output format
Create a folder seo-subdomain-{target-slug}-{YYYYMMDD}/ with:
seo-subdomain-{target-slug}-{YYYYMMDD}/
├── SUBDOMAINS.md (synthesised report + recommendations — primary deliverable)
├── 06-topic-ownership-map.md (cluster × subdomain matrix — load-bearing reference content teams brief from)
├── 07-fragmentation-flags.md (cannibalization detected — load-bearing reference for consolidation decisions)
└── evidence/
├── 01-subdomains-list.md (DATA_getDomainSubdomains — raw step output)
├── 02-overview-by-subdomain.md (per-subdomain overview rows)
├── 03-keywords-by-subdomain/
│ ├── blog-example-com.md
│ ├── docs-example-com.md
│ └── ... (one per subdomain)
├── 04-competitors-by-subdomain.md
└── 05-backlinks-by-subdomain.mdTop-level: SUBDOMAINS.md + 06-topic-ownership-map.md + 07-fragmentation-flags.md. Content teams brief from the ownership map; consolidation decisions cite the fragmentation flags directly. The 01–05 step files preserve raw API outputs in evidence/.
SUBDOMAINS.md follows this shape:
# Subdomain Analysis: {root domain}
> Snapshot dated {YYYY-MM-DD} · Subdomains analysed: {n} of {n discovered} (limit: top {limit} by keyword count)
## Subdomain inventory
| Subdomain | Keywords | Traffic est. | Backlinks | Domain authority | Top topics owned |
|---|---|---|---|---|---|
| {root} | {n} | {n}/mo | {n} | {DA} | {topics} |
| blog.{root} | {n} | {n}/mo | {n} | {DA} | {topics} |
| docs.{root} | {n} | {n}/mo | {n} | {DA} | {topics} |
| ... |
## Topic ownership map
| Topic cluster | Owned by | Also ranks (cannibalization?) |
|---|---|---|
| {topic 1} | blog.{root} (avg pos 3.2 across 47 keywords) | {root} (avg pos 12) — {⚠ cannibalization} |
| {topic 2} | docs.{root} | (none) |
| ... |
## Fragmentation flags
### {⚠ Cannibalization detected: topic = {topic X}}
- `blog.{root}` ranks {n} keywords for {topic X}, avg position {p}.
- `{root}` (root path) ranks {m} keywords for the same topic, avg position {p}.
- The two sets overlap on {k} exact keywords.
- **Recommendation:** consolidate to `blog.{root}` (the stronger ranker). 301 the root-path duplicates with intent preserved.
### ... (per fragmentation finding)
## Recommendations summary
- **Consolidate:** {n} subdomain pairs → see fragmentation flags above.
- **Split intentional and healthy:** {n} subdomains have distinct ownership; leave alone.
- **Investigate:** {n} edge cases flagged for human review.
## Risk notes
- Subdomain consolidation requires careful 301 redirect mapping; track via `seo-drift` after the migration.
- A subdomain with separate backlinks (per `evidence/05-backlinks-by-subdomain.md`) is harder to consolidate without losing link equity — plan accordingly.
## Raw data
- See per-subdomain files under `evidence/03-keywords-by-subdomain/`.
- Topic ownership matrix: `06-topic-ownership-map.md`.Tips
- Respect rate limit. The skill makes ~5 calls per subdomain. With
--limit 10, that's ~50 calls; pace sequentially. - Call
DATA_getCreditBalancebefore running. Cost scales with subdomain count: ~20–60 credits typical for--limit 10; up to 150+ for unlimited. --limitis your friend. Sites with hundreds of subdomains (large platforms) don't need every subdomain analysed — top 10 by keyword count covers >90% of organic value usually.- Don't conflate "subdomain has lower DA" with "subdomain is bad." Subdomains often have lower DA than the root because they accumulate links separately. The question is topic ownership and cannibalization, not DA per se.
- Consolidation is risky. A 301 from
blog.example.comtoexample.com/blog/retains most link equity but can lose 5–15% in transition. Track post-migration withseo-drift. - Don't recommend consolidation when one subdomain is on a different platform. If
blog.example.comis on a different CMS, the engineering cost of consolidation may exceed the SEO benefit. Surface this as a constraint, not a recommendation. - The topic-ownership matrix is the highest-leverage artifact. Use it to brief content teams on which subdomain should publish what.
- Pair with
seo-pageto deep-dive into specific URLs flagged in cannibalization. - Pair with
seo-driftto baseline subdomains before major restructures.
© seranking, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/seo-subdomain of seranking/seo-skills.
Open the folder on GitHubat commit fd6d140
Compare with similar skills
SEO Subdomain next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| SEO Subdomain this skillseranking/seo-skills | 160 | — | ~2.1k | Automated safety check: Pass | MIT | |
| E2E SEO Assistantirinabuht12-oss/marketing-skills | 4k | — | ~1.9k | Automated safety check: Pass | None | |
| SEO Competitorrampstackco/claude-skills | 941 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Competitor Researchkostja94/marketing-skills | 1k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Traction SEO Contenthashgraph-online/awesome-codex-plugins | 1.3k | — | ~587 | Automated safety check: Pass | MIT | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 19k | 2 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
SEO Competitor
rampstackco/claude-skills
Run a competitive SEO analysis comparing the user's site to chosen competitors across SERP overlap, content depth, backlink profiles, technical posture, and brand presence.
Competitor Research
kostja94/marketing-skills
When the user wants to analyze competitors for SEO, content, backlinks, or positioning.
Traction SEO Content
hashgraph-online/awesome-codex-plugins
Plan SEO and content marketing traction experiments from Traction.
SEO Keyword Clustering
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
SEO Content Brief Generator
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
More from seranking/seo-skills
All 32 skills in this repoSEO Google
seranking/seo-skills
Direct access to Google's own SEO data via Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, GA4 organic…
SEO API
seranking/seo-skills
SE Ranking API integration architect. An agent skill from seranking/seo-skills.
SEO Content Audit
seranking/seo-skills
E-E-A-T + CITE quality audit for an EXISTING piece of content.
SEO Content Brief
seranking/seo-skills
Generate a writer-ready SEO content brief from a target domain and topic.
SEO Drift
seranking/seo-skills
Capture an SEO baseline snapshot for a domain or URL, then on later runs compare the current state and surface regressions.
SEO Firecrawl
seranking/seo-skills
Ad-hoc web scraping, site mapping, and full-site crawling via Firecrawl MCP.
Related
Categories
Questions about SEO Subdomain
What does SEO Subdomain do?
Subdomain ownership map for a domain. An agent skill from seranking/seo-skills. SEO Subdomain is an agent skill from seranking/seo-skills. Subdomain ownership map for a domain.
When should I use SEO Subdomain?
SEO Subdomain fits situations like: the user asks subdomain analysis; subdomain ownership; blog vs main domain; support vs docs subdomain.
How do I install SEO Subdomain in Claude Code?
Run `npx skills add seranking/seo-skills --skill seo-subdomain -a claude-code`. Or copy the skill folder (skills/seo-subdomain in seranking/seo-skills) into .claude/skills/seo-subdomain in your project. Claude Code loads it when a task matches its description.
How do I install SEO Subdomain in Codex?
Run `npx skills add seranking/seo-skills --skill seo-subdomain -a codex`. Or copy the skill folder (skills/seo-subdomain in seranking/seo-skills) into .agents/skills/seo-subdomain in your project. Codex loads it when a task matches its description.
Can I use SEO Subdomain in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seranking/seo-skills --skill seo-subdomain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-subdomain, .gemini/skills/seo-subdomain, .github/skills/seo-subdomain and .opencode/skills/seo-subdomain in your project.
What does SEO Subdomain need to run?
SKILL.md names no scripts, command-line tools or credentials: SEO Subdomain is instructions for the agent only.
Does SEO Subdomain access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is SEO Subdomain safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does SEO Subdomain use?
SEO Subdomain is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does SEO Subdomain use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to SEO Subdomain?
Skills that share tags, products or a category with SEO Subdomain: E2E SEO Assistant (irinabuht12-oss/marketing-skills, 4k stars), SEO Competitor (rampstackco/claude-skills, 941 stars), Competitor Research (kostja94/marketing-skills, 1k stars) and Traction SEO Content (hashgraph-online/awesome-codex-plugins, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains SEO Subdomain?
seranking (a GitHub organization) maintains it in seranking/seo-skills, which has 160 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on June 25, 2026.
Source: seranking/seo-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.