Agent skill

SEO Keyword Niche

by seranking in seranking/seo-skills

Mine longtail keywords + question keywords for a topic at scale to surface niche content opportunities.

MITAuto-check passedMarketing & SEO

Install SEO Keyword Niche

skills CLI
$ npx skills add seranking/seo-skills --skill seo-keyword-niche -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install seranking/seo-skills seo-keyword-niche --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
seo-keyword-niche
GitHub stars
161
Token cost
~3.1k tokens
SKILL.md length
986 words
Files
1
Skills in repo
32
Repo updated
First seen
Licence
MIT

At a glance

Mine longtail keywords + question keywords for a topic at scale to surface niche content opportunities.

  • Works in 9 steps: Validate & preflight → Longtail expansion… → Question expansion… → …
  • The user asks longtail keywords
  • 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 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.

When your agent uses it

  • The user asks longtail keywords
  • Question keywords
  • Content opportunities at scale
  • Programmatic SEO

Example prompts

  • “longtail keywords”
  • “question keywords”
  • “niche content”
  • “/seo-keyword-niche”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Validate & preflight
  2. Longtail expansion DATA_getLongTailKeywords
  3. Question expansion DATA_getKeywordQuestions
  4. Related expansion DATA_getRelatedKeywords and DATA_getSimilarKeywords
  5. Filter and clean
  6. SERP sample for representative keywords DATA_getSerpResults
  7. Cluster by intent + theme
  8. Propose a content tier
  9. Quality gates (anti-thin-content guardrails)

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 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.

Always · name and description, kept in context so the agent knows when to use it
~152
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k

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). 986 words, ~3,079 tokens.

Download SKILL.mdSave it as .claude/skills/seo-keyword-niche/SKILL.md (or your agent's skills folder).
name
seo-keyword-niche
description
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 SEO", "content mining", or "what should I write about for {topic}".

Example output: examples/seo-keyword-niche-espresso-machine-reviews-20260514/KEYWORD-NICHE-PLAN.md

Keyword Niche

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.

Prerequisites

  • SE Ranking MCP server connected.
  • User provides: a seed topic (e.g. "running shoes", "tax preparation"), or 2–5 seed keywords. Target country (default us). Optional: minimum volume threshold (default: 50/mo for niche skill — lower than seo-keyword-cluster's 100), maximum KD (default: 40 for accessibility).

Process

  1. Validate & preflight

    • Confirm seeds make sense (not too broad, not branded, not single-letter).
    • DATA_getCreditBalance — surface remaining credits. This skill is heavier than most: pulling longtail at depth costs more than pulling head terms.
  2. Longtail expansion DATA_getLongTailKeywords

    • For each seed: pull longtail variants (typically 3+ words, lower individual volume, lower KD).
    • Target: 200–500 longtail candidates per seed.
  3. Question expansion DATA_getKeywordQuestions

    • For each seed: pull question-phrased keywords.
    • These are gold for content mining — explicit user intent in the keyword.
  4. Related expansion DATA_getRelatedKeywords and DATA_getSimilarKeywords

    • For each seed: pull related + similar keywords.
    • Catches semantic neighbours that longtail expansion missed.
  5. Filter and clean

    • Remove keywords below min_volume and above max_kd.
    • Strip branded keywords the seed-domain doesn't own (unless the user supplied a branded seed).
    • Tag each keyword with detected intent: informational, commercial, transactional, navigational.
    • De-duplicate across seeds.
  6. SERP sample for representative keywords DATA_getSerpResults

    • For 5–10 representative keywords (one per emerging cluster), pull top 10.
    • Identify the dominant page type for each cluster (informs the template proposal in step 8).
  7. Cluster by intent + theme

    • Group keywords by semantic similarity + intent.
    • Each cluster: name, primary keyword, supporting keywords, total volume, weighted KD, dominant page type.
    • Target 8–20 clusters (more granular than seo-keyword-cluster's 5–12 — this skill is for niche tiers).
  8. Propose a content tier

    • Template structure: which fields make each page unique. For {city} apartment rentals, the template fields are {city}, {neighborhood}, {price_range}, {property_count}. For {tool} alternatives it's {tool}, {competitor_count}, {primary_use_case}.
    • URL pattern: /{category}/{slug}/ or /{topic}/{tool}-alternatives/ etc.
    • Sample pages: 3 fully-spec'd page wireframes for representative cluster keywords.
    • Internal-linking automation: how to link pages within the tier (hub-spoke from a category page, or peer-to-peer for genuinely flat structures).
  9. Quality gates (anti-thin-content guardrails)

    • Minimum unique data per page: template fields must produce ≥ 5 unique attributes (counts, prices, names, dates, etc.). Pages without 5+ unique attributes are duplicates in disguise — skip those keyword variants.
    • Minimum word count: 600 words effective content (excludes navigation, footer, boilerplate).
    • Schema requirement: every templated page gets Article (or relevant type) + BreadcrumbList.
    • Index/noindex split: if the variant doesn't pass the unique-data threshold, generate the page but noindex it.
Show full SKILL.md (537 more words)Show less
9a. Programmatic publishing — extra gates

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.

  • Per-row uniqueness threshold (≥ 30% varying fields). Of the template's content-producing fields (excluding nav/footer boilerplate), at least 30% must hold values that differ from the median sibling page. A 12-field template where 9 fields are identical across pages is templated mush — Google's spam systems are well-tuned for this since the 2024 core update. Compute: varying_fields / content_fields ≥ 0.30 per row vs the cluster median.
  • Min unique-fact count vs parent + sibling (≥ 5 facts). Each row carries at least 5 facts that do not appear on the parent hub page or any sibling page in the same cluster. Facts = numbers, dates, named entities, original quotes, photos. Synonym shuffles don't count. Sample 10 rows manually before greenlighting the tier.
  • Data-source independence. Don't auto-publish from a single source (one CSV, one API, one scrape). If the page's only differentiator is a row from cities.csv, the page is a CSV row dressed as content — likely thin. Combine ≥ 2 independent data sources per page.
  • Index-bloat circuit-breaker. After the first 50 pages ship, monitor GSC. If the index-coverage rate drops below 60% (Google indexed <60% of submitted), pause the tier and re-audit. Continuing past this signal compounds bloat across the rest of the tier.
  • Crawl-budget honesty. Sites under 50k pages can usually crawl whatever you ship. Sites >50k must factor in crawl-budget cost: every thin programmatic page steals attention from the cornerstone content. If the site is in this band and the unique-fact count is borderline, default to noindex.

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.

  1. Synthesise KEYWORD-NICHE-PLAN.md

Output format

Create 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:

markdown
# 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

Tips

  • Respect rate limit: 10 req/sec. Steps 2–4 fan out across all seeds; pace sequentially.
  • Cost: ~30–80 credits for 5 seeds, ~150+ for 10–20 seeds. Call DATA_getCreditBalance before running and surface the estimate.
  • Programmatic SEO is risky. Pages that don't pass the unique-data threshold are dead weight at best, penalty bait at worst. The quality gates in step 9 are not optional.
  • The pilot recommendation is critical. 10 pages with thoughtful templates outperform 1000 pages of templated mush.
  • For e-commerce / inventory-driven content (city pages, product variations), the unique-data threshold is usually easy to hit.
  • For "best X for Y" content (where Y has many variants), pick variants that have genuinely distinct content — don't templatise across near-synonyms.
  • Pair with seo-keyword-cluster for the broader pillar+spoke architecture (this skill complements, not replaces).
  • Pair with seo-content-brief to expand individual pillar topics into full editor briefs.
  • Pair with seo-technical-audit after first 100 pages ship to catch any thin-content / canonicalization issues.
  • Don't auto-publish. The template, URL pattern, and quality gates ship from this skill; the content authoring + review remains a human responsibility.

© 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-keyword-niche of seranking/seo-skills.

Open the folder on GitHubat commit fd6d140

Compare with similar skills

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.

SEO Keyword Niche compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
SEO Keyword Niche this skillseranking/seo-skills161—~3.1kAutomated safety check: PassMIT
SEO Programmaticsickn33/agentic-awesome-skills47k2 repos~2.4kAutomated safety check: NotesMIT
Page Play Builderaaron-he-zhu/aaron-marketing-skills2.9k—~3.6kAutomated safety check: PassApache-2.0
SEONexus-JPF/note-companion870—~2.2kAutomated safety check: PassMIT
Prd V09 Alternatives Pagesmattgierhart/PRD-driven-context-engineering180—~2.4kAutomated safety check: PassMIT
Suede CompetitorsJasonColapietro/suede-creator-skills127—~2.7kAutomated safety check: PassMIT

Similar skills

  • SEO Programmatic

    sickn33/agentic-awesome-skills

    Plan and audit programmatic SEO pages generated at scale from structured data.

    47k GitHub starsUsed in 2 repos~2.4k tokens
    Marketing & SEOAuto-check: notes
  • Page Play Builder

    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 /…

    2.9k GitHub stars~3.6k tokensUpdated today
    Marketing & SEOAuto-check passed
  • SEO

    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.

    870 GitHub stars~2.2k tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed
  • Prd V09 Alternatives Pages

    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.

    180 GitHub stars~2.4k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Suede Competitors

    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.

    127 GitHub stars~2.7k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Paw Mkt SEO

    pawbytes/skill-suites

    SEO specialist for technical audits, keyword strategy, and GEO.

    113 GitHub stars~1.8k tokensUpdated 8 days ago
    Marketing & SEOAuto-check passed

More from seranking/seo-skills

All 32 skills in this repo
  • SEO 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…

    161 GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check passed
  • SEO API

    seranking/seo-skills

    SE Ranking API integration architect. An agent skill from seranking/seo-skills.

    161 GitHub stars~4.1k tokensUpdated 3 mo ago
    Auto-check passed
  • SEO Content Audit

    seranking/seo-skills

    E-E-A-T + CITE quality audit for an EXISTING piece of content.

    161 GitHub stars~3k tokensUpdated 3 mo ago
    Auto-check passed
  • SEO Content Brief

    seranking/seo-skills

    Generate a writer-ready SEO content brief from a target domain and topic.

    161 GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • 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.

    161 GitHub stars~3.4k tokensUpdated 3 mo ago
    Auto-check passed
  • SEO Firecrawl

    seranking/seo-skills

    Ad-hoc web scraping, site mapping, and full-site crawling via Firecrawl MCP.

    161 GitHub stars~2.3k tokensUpdated 3 mo ago
    Auto-check passed

Categories

Questions about SEO Keyword Niche

What does SEO Keyword Niche do?

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.

When should I use SEO Keyword Niche?

SEO Keyword Niche fits situations like: the user asks longtail keywords; question keywords; content opportunities at scale; programmatic SEO.

How do I install SEO Keyword Niche in Claude Code?

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.

How do I install SEO Keyword Niche in Codex?

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.

Can I use SEO Keyword Niche 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-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.

What does SEO Keyword Niche need to run?

SKILL.md names no scripts, command-line tools or credentials: SEO Keyword Niche is instructions for the agent only.

Does SEO Keyword Niche 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 Keyword Niche 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 Keyword Niche use?

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.

How many tokens does SEO Keyword Niche use?

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.

What are the alternatives to SEO Keyword Niche?

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.

Who maintains SEO Keyword Niche?

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.