SEO Programmatic
sickn33/agentic-awesome-skills
Plan and audit programmatic SEO pages generated at scale from structured data.
Mine longtail keywords + question keywords for a topic at scale to surface niche content opportunities.
$ npx skills add seranking/seo-skills --skill seo-keyword-niche -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seranking/seo-skills seo-keyword-niche --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-keyword-niche .claude/skills/seo-keyword-niche && 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-keyword-niche" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-keyword-niche into .claude/skills/seo-keyword-niche/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword-niche", 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-keyword-nicheType 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-keyword-niche -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seranking/seo-skills seo-keyword-niche --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-keyword-niche .agents/skills/seo-keyword-niche && 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-keyword-niche" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-keyword-niche into .agents/skills/seo-keyword-niche/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword-niche", 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-keyword-niche -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seranking/seo-skills seo-keyword-niche --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-keyword-niche .cursor/skills/seo-keyword-niche && 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-keyword-niche" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-keyword-niche into .cursor/skills/seo-keyword-niche/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword-niche", 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-keyword-niche--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-keyword-niche -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seranking/seo-skills seo-keyword-niche --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-keyword-niche .gemini/skills/seo-keyword-niche && 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-keyword-niche" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-keyword-niche into .gemini/skills/seo-keyword-niche/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword-niche", 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-keyword-nicheInstalls 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-keyword-niche -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-keyword-niche .github/skills/seo-keyword-niche && 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-keyword-niche" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-keyword-niche into .github/skills/seo-keyword-niche/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword-niche", 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-keyword-niche -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-keyword-niche --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-keyword-niche .opencode/skills/seo-keyword-niche && 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-keyword-niche" agent skill from https://github.com/seranking/seo-skills/tree/main/skills/seo-keyword-niche into .opencode/skills/seo-keyword-niche/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword-niche", 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.
seo-keyword-nicheMine longtail keywords + question keywords for a topic at scale to surface niche content opportunities.
SEO Keyword Niche is an agent skill from seranking/seo-skills. Mine longtail keywords + question keywords for a topic at scale to surface niche content opportunities. Outputs a content tier plan (template + URL pattern + sample pages + quality gates) suitable for programmatic publishing or steady editorial output. Distinct from seo-keyword-cluster (which plans pillar+spoke architecture from broad seeds) — this skill goes deeper into the long tail. Use when the user asks "longtail keywords", "question keywords", "niche content", "content opportunities at scale", "programmatic…
Its SKILL.md is about 3.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 Keyword research, Quality gates and Programmatic SEO. 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.
9 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit fd6d140. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
SEO Keyword Niche loads about 3.1k tokens when it runs. Until then it costs about 152 tokens; SKILL.md has 986 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.
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.
The full file from seranking/seo-skills at commit fd6d140, republished under its MIT licence (© seranking). 986 words, ~3,079 tokens.
.claude/skills/seo-keyword-niche/SKILL.md (or your agent's skills folder).Example output: examples/seo-keyword-niche-espresso-machine-reviews-20260514/KEYWORD-NICHE-PLAN.md
Mine the long tail for content opportunities. Pulls longtail variants, question-intent keywords, related keywords, and SERP samples to find under-served niche keywords; clusters them by intent; proposes a content tier (template + URL pattern + sample pages + thin-content quality gates) that can be published programmatically or as a steady editorial cadence.
us). Optional: minimum volume threshold (default: 50/mo for niche skill — lower than seo-keyword-cluster's 100), maximum KD (default: 40 for accessibility).Validate & preflight
DATA_getCreditBalance — surface remaining credits. This skill is heavier than most: pulling longtail at depth costs more than pulling head terms.Longtail expansion DATA_getLongTailKeywords
Question expansion DATA_getKeywordQuestions
Related expansion DATA_getRelatedKeywords and DATA_getSimilarKeywords
Filter and clean
min_volume and above max_kd.SERP sample for representative keywords DATA_getSerpResults
Cluster by intent + theme
seo-keyword-cluster's 5–12 — this skill is for niche tiers).Propose a content tier
{city} apartment rentals, the template fields are {city}, {neighborhood}, {price_range}, {property_count}. For {tool} alternatives it's {tool}, {competitor_count}, {primary_use_case}./{category}/{slug}/ or /{topic}/{tool}-alternatives/ etc.Quality gates (anti-thin-content guardrails)
Article (or relevant type) + BreadcrumbList.noindex it.Most users discover this skill because they want to ship pages at scale (programmatic SEO, data-driven directories, location pages). Programmatic publishing is the highest-risk path for spam-classifier blowback. Apply these in addition to the gates above whenever the proposed tier expects to ship 50+ templated pages.
varying_fields / content_fields ≥ 0.30 per row vs the cluster median.cities.csv, the page is a CSV row dressed as content — likely thin. Combine ≥ 2 independent data sources per page.These gates are not negotiable for the programmatic path. If the proposed tier can't pass them, the right answer is fewer pages, not lower thresholds.
KEYWORD-NICHE-PLAN.mdCreate a folder seo-keyword-niche-{target-slug}-{YYYYMMDD}/ with:
seo-keyword-niche-{target-slug}-{YYYYMMDD}/
├── KEYWORD-NICHE-PLAN.md (synthesised plan — primary deliverable)
├── keywords.csv (all enriched keywords with cluster + intent — load-bearing CSV the publishing team paste into CMS/sheets)
├── 06-template-spec.md (fields, URL pattern, sample pages — load-bearing reference writers consult directly)
├── 07-quality-gates.md (thin-content guardrails — load-bearing reference release-gate readers consult directly)
└── evidence/
├── 01-seed-expansion.md (raw expansion per seed — raw step output)
├── 02-question-keywords.md (DATA_getKeywordQuestions)
├── 03-filtered-keywords.md (post min-vol / max-kd filter)
├── 04-cluster-assignment.md (every keyword and its cluster)
└── 05-serp-samples.md (top 10 for representative cluster keywords)Top-level: KEYWORD-NICHE-PLAN.md + keywords.csv + 06-template-spec.md + 07-quality-gates.md. Writers consult the template spec directly when authoring; release gates consult the quality gates directly. The 01–05 step files preserve raw API/clustering outputs in evidence/.
KEYWORD-NICHE-PLAN.md shape:
# Keyword Niche Plan: {topic}
> Generated {YYYY-MM-DD} · Country: {country} · Seeds: {list}
## Inventory
- Longtail keywords mined: {n}
- Question keywords: {n}
- After filter (min-vol {n}, max-kd {n}): {n}
- Clusters formed: {n}
- Estimated combined monthly volume: {n}
## Recommended content tier
### Template
**URL pattern:** `/{category}/{slug}/`
**Required fields per page:**
- `{slug}` — URL-friendly identifier
- `{H1}` — page primary heading
- `{TL;DR}` — first 200 words direct answer
- `{primary_keyword}` — target keyword
- `{related_keywords}` — secondary keywords from cluster
- `{unique_attributes}` — list of ≥ 5 differentiating attributes (numbers, names, dates)
- `{related_pages}` — internal-link list (3–5 sibling pages)
- `{schema_type}` — Article/Product/Other
- `{datestamp}` — last-updated date
**Sample pages:** see `06-template-spec.md` for 3 fully-spec'd wireframes.
## Cluster build order (top 10 by priority)
| Rank | Cluster | Volume (combined) | Weighted KD | Dominant page type | Pages to ship |
|---|---|---|---|---|---|
| 1 | {cluster name} | {n} | {kd} | {type} | {n} |
| ... |
## Quality gates (do not ship pages that fail)
1. **Unique-data threshold:** each page has ≥ 5 unique attributes vs sibling pages in the same cluster.
2. **Minimum word count:** 600 words effective content.
3. **Schema:** `Article` + `BreadcrumbList` (or relevant `@type` for the page).
4. **Internal links:** ≥ 3 outbound to siblings, ≥ 1 inbound from category hub.
5. **Index/noindex:** noindex pages that don't pass the unique-data threshold.
### Programmatic-only gates (apply when tier ships 50+ pages)
6. **Per-row uniqueness ≥ 30%:** at least 30% of content-producing fields hold values that differ from the cluster median.
7. **Min unique facts vs parent + sibling (≥ 5):** five facts per row that don't appear on the parent hub or any sibling.
8. **Data-source independence:** ≥ 2 independent data sources per page (no single-CSV pages).
9. **Index-bloat circuit-breaker:** pause tier if GSC index-coverage <60% after the first 50 pages.
## Scaling estimate
- Clusters: {n}
- Pages per cluster (median): {n}
- Total pages: {n}
- At {pages/week} cadence: {n weeks} to ship the tier.
- Crawl-budget impact (for sites > 10k pages): noindex strategy keeps thin variants out of the index.
## Risks / monitoring
- **Thin-content penalty:** the quality gates above are the guardrail. Audit at scale via `seo-technical-audit` after first 100 pages ship.
- **Index bloat:** monitor in GSC; if newly indexed pages don't accrue impressions in 60 days, candidate for noindex/consolidate.
- **Cannibalization:** monitor with `seo-subdomain` + `seo-page` after first 50 pages.
## Recommended next step
Build a small pilot — 10 pages from the top cluster — before committing to the full tier. Apply quality gates rigorously to the pilot. Re-audit after 60 days; iterate the template based on which pilot pages indexed and ranked.keywords.csv columns: keyword,volume,kd,cpc,intent,cluster,role_in_cluster,dominant_page_type,unique_attributes_estimate
DATA_getCreditBalance before running and surface the estimate.seo-keyword-cluster for the broader pillar+spoke architecture (this skill complements, not replaces).seo-content-brief to expand individual pillar topics into full editor briefs.seo-technical-audit after first 100 pages ship to catch any thin-content / canonicalization issues.© seranking, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/seo-keyword-niche of seranking/seo-skills.
Open the folder on GitHubat commit fd6d140
SEO Keyword Niche 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 Keyword Niche this skillseranking/seo-skills | 161 | — | ~3.1k | Automated safety check: Pass | MIT | |
| SEO Programmaticsickn33/agentic-awesome-skills | 47k | 2 repos | ~2.4k | Automated safety check: Notes | MIT | |
| Page Play Builderaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| SEONexus-JPF/note-companion | 870 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Prd V09 Alternatives Pagesmattgierhart/PRD-driven-context-engineering | 180 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Suede CompetitorsJasonColapietro/suede-creator-skills | 127 | — | ~2.7k | Automated safety check: Pass | MIT |
sickn33/agentic-awesome-skills
Plan and audit programmatic SEO pages generated at scale from structured data.
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "build programmatic SEO pages", "generate pages at scale", "rank on a high-authority third-party site", "borrow domain authority", "build a vs /…
Nexus-JPF/note-companion
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence.
mattgierhart/PRD-driven-context-engineering
Generate "X vs Y" and "Alternative to X" SEO/CRO pages targeting competitive search intent during PRD v0.9 Go-to-Market.
JasonColapietro/suede-creator-skills
Suede-owned comparison-page discipline for accurate, evidence-backed alternative, versus, and competitor-comparison content that wins evaluators and search intent.
pawbytes/skill-suites
SEO specialist for technical audits, keyword strategy, and GEO.
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…
seranking/seo-skills
SE Ranking API integration architect. An agent skill from seranking/seo-skills.
seranking/seo-skills
E-E-A-T + CITE quality audit for an EXISTING piece of content.
seranking/seo-skills
Generate a writer-ready SEO content brief from a target domain and topic.
seranking/seo-skills
Capture an SEO baseline snapshot for a domain or URL, then on later runs compare the current state and surface regressions.
seranking/seo-skills
Ad-hoc web scraping, site mapping, and full-site crawling via Firecrawl MCP.
Categories
Mine longtail keywords + question keywords for a topic at scale to surface niche content opportunities. SEO Keyword Niche is an agent skill from seranking/seo-skills. Mine longtail keywords + question keywords for a topic at scale to surface niche content opportunities.
SEO Keyword Niche fits situations like: the user asks longtail keywords; question keywords; content opportunities at scale; programmatic SEO.
Run `npx skills add seranking/seo-skills --skill seo-keyword-niche -a claude-code`. Or copy the skill folder (skills/seo-keyword-niche in seranking/seo-skills) into .claude/skills/seo-keyword-niche in your project. Claude Code loads it when a task matches its description.
Run `npx skills add seranking/seo-skills --skill seo-keyword-niche -a codex`. Or copy the skill folder (skills/seo-keyword-niche in seranking/seo-skills) into .agents/skills/seo-keyword-niche in your project. Codex loads it when a task matches its description.
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-keyword-niche -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-keyword-niche, .gemini/skills/seo-keyword-niche, .github/skills/seo-keyword-niche and .opencode/skills/seo-keyword-niche in your project.
SKILL.md names no scripts, command-line tools or credentials: SEO Keyword Niche is instructions for the agent only.
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.
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.
SEO Keyword Niche is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with SEO Keyword Niche: SEO Programmatic (sickn33/agentic-awesome-skills, 47k stars), Page Play Builder (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), SEO (Nexus-JPF/note-companion, 870 stars) and Prd V09 Alternatives Pages (mattgierhart/PRD-driven-context-engineering, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
seranking (a GitHub organization) maintains it in seranking/seo-skills, which has 161 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.