agentleFS
serankingseranking/seo-skills/skills/seo-competitor-gap-analysis/SKILL.md

seo-competitor-gap-analysis

Skill201 starsChanged 5 months agoMITView on GitHub

Compare a target domain to its top organic competitors and surface keywords the competitors rank for that the target does not, filtered by intent, volume, and difficulty. Use when the user asks for a competitor gap analysis, keyword gap, organic content gap, missing keyword opportunities, or wants to see what their competitors are ranking for that they are not.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user did not provide competitors, pull the top 5 organic competitors for the target in the target market.

    line 19
  2. Distinctive:

    Use the comparison endpoint as a cross-check.

    line 33
  3. Very specific:

    Create a folder seo-competitor-gap-analysis-{target-slug}-{YYYYMMDD}/ with:

    line 50
  4. Very specific:

    Call DATA_getCreditBalance before running.

    line 117
  5. Distinctive:

    Do not recommend capturing branded competitor keywords unless the user explicitly asks.

    line 119
  6. Distinctive:

    When many gap keywords cluster around a theme, recommend a hub page plus cluster rather than 50 individual articles.

    line 120

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Example output: examples/seo-competitor-gap-analysis-wix-com-20260514/REPORT.md

Competitor Gap Analysis

Identify the specific keywords your competitors rank for in the top 20 that your domain does not, ranked by commercial value and realistic capture difficulty.

Prerequisites

  • SE Ranking MCP server connected.
  • User provides: (a) target domain, (b) 3 to 5 competitor domains (or ask the skill to auto-discover them), (c) market country (default: us), and optionally filters (min volume, max KD, intent).

Process

  1. Validate or discover competitors DATA_getDomainCompetitors
    • If the user did not provide competitors, pull the top 5 organic competitors for the target in the target market.
    • Surface the list to the user and ask them to confirm or override before proceeding.
    • Note: the upstream API does not support limit/offset, so this call returns the full set (~60KB for popular domains) and the MCP harness writes it to a file. Read that file path, parse the {data: [...]} JSON, sort by common_keywords desc, and take the top 5.
  2. Pull competitor keyword sets DATA_getDomainKeywords
    • For each competitor, pull keywords where they rank in the top 20 of the target country.
    • Save per-competitor lists.
  3. Pull target keyword set DATA_getDomainKeywords
    • For the target domain, pull all ranking keywords in the target country (any position).
    • This is the exclusion set.
  4. Compute the gap DATA_getDomainKeywordsComparison (cross-check)
    • Keywords ranked by at least one competitor in the top 20 but not ranked by the target domain at all.
    • Use the comparison endpoint as a cross-check.
  5. Filter and segment
    • Apply user-specified filters on volume, KD, and intent.
    • Segment by intent: informational, commercial, transactional, navigational.
    • Segment by competition: how many of the N competitors rank for each gap keyword.
  6. Score and prioritise
    • Score each gap keyword: traffic potential (volume × CTR model) + intent weighting + inverse KD.
    • Surface the top 50 opportunities with reasoning per keyword.
  7. Map to content actions
    • For each top opportunity, recommend: new article, expand existing page, refresh existing page, programmatic template.
    • Flag quick wins: competitors rank with thin content (detected by URL pattern and content-length heuristics).

Output format

Create a folder seo-competitor-gap-analysis-{target-slug}-{YYYYMMDD}/ with:

seo-competitor-gap-analysis-{target-slug}-{YYYYMMDD}/
├── REPORT.md                                (synthesised report — primary deliverable)
├── gaps.csv                                 (full gap list — load-bearing CSV the writers/planners paste into briefs)
└── evidence/
    ├── 01-competitors.md                    (competitor list / discovery — raw step output)
    ├── 02-competitor-keywords-{domain}.md   (one per competitor — raw step output)
    ├── 03-target-keywords.md                (target's existing ranking set — raw step output)
    └── 04-gap-raw.md                        (human-readable full gap list before filtering — raw step output)

Top-level: REPORT.md + gaps.csv. The numbered step files preserve the raw API outputs in evidence/ for reproducibility.

REPORT.md follows this shape:

# Competitor Gap: {target}
Market: {country}
Competitors analysed: {list}

## Summary
- Competitor keywords in top 20: {n}
- Target keywords overall: {n}
- Gap keywords (opportunities): {n}
- Gap traffic potential: ~{n}/mo

## Top 50 opportunities

### Informational intent
| # | Keyword | Volume | KD | Competitors ranking | Action | Score |
|---|---|---|---|---|---|---|
| 1 | {kw} | {n} | {n} | {3 of 5} | New article | {score} |
| 2 | ... | ... | ... | ... | ... | ... |

### Commercial intent
| # | Keyword | Volume | KD | Competitors ranking | Action | Score |
|---|---|---|---|---|---|---|
...

### Transactional intent
...

## Quick wins (top 10)
Keywords where competitors rank in positions 5 to 20 with thin content, low DT, or old dates.

| # | Keyword | Weakest competitor position | Suggested angle |
|---|---|---|---|
| 1 | {kw} | example.com at #14 (2022 article, 800 words) | Fresh, comprehensive guide |

## Recommended next steps
1. Run `content-brief` on the top 3 opportunities to generate writer-ready briefs.
2. Run `keyword-cluster-planner` on the full gap list to build a sequencing plan.
3. Add the gap keywords to an SE Ranking project for rank tracking once content ships.

## Files
- gaps.csv: full gap list for spreadsheet analysis
- evidence/04-gap-raw.md: human-readable full gap list before filtering

gaps.csv columns: keyword,volume,kd,cpc,intent,competitors_ranking,top_competitor_position,target_position,action,score

Tips

  • Data API rate limit: 10 requests per second. For large sites, DATA_getDomainKeywords may paginate heavily; set a ceiling (e.g., top 1,000 keywords per domain) unless the user explicitly asks for the full set.
  • Call DATA_getCreditBalance before running. A full pass on 10 seeds typically consumes 30–80 credits; 20 seeds can exceed 150.
  • The competitors_ranking count is the best signal of realism. Keywords ranked by 4 of 5 competitors are validated opportunities; keywords ranked by only 1 may be noise.
  • Do not recommend capturing branded competitor keywords unless the user explicitly asks. Pivoting to compete on "competitor brand review" is a viable strategy but only if the user opts in.
  • When many gap keywords cluster around a theme, recommend a hub page plus cluster rather than 50 individual articles.
  • Chain this skill with content-brief and keyword-cluster-planner naturally. Mention them in the Recommended next steps section of the output.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.