← Back to list
📣

rank-tracker Checked

Use when the user asks to "track rankings" or "查排名"; measures keyword and SERP-position deltas ov…
📣 Marketing skills By aaron-he-zhu Version v1.0.0 Added 2026-09-03 Updated 2026-09-03 Source ↗
8.4Overall rating
2Views
5Downloads
2.7kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "rank-tracker" skill by following the instructions at https://skill123.me/install/rank-tracker.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/rank-tracker.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 8 KB
📊 Static rating
8.4/10
Trigger
8.5
Structure
8.0
Workflow
8.4
Content
8.0
Engineering
6.0
Security
10.0

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

Use when the user asks to "track rankings" or "查排名"; measures keyword and SERP-position deltas over time from provided exports or connected tools, including AI-response checks. Not for multi-metric stakeholder reports or setting alerts — use performance-monitor (report or alert mode). 排名追踪/SERP监控

Rank Tracker

Tracks keyword positions, SERP feature ownership, and AI visibility over time.

Documentation

Use when the user asks to "track rankings" or "查排名"; measures keyword and SERP-position deltas over time from provided exports or connected tools, including AI-response checks. Not for multi-metric stakeholder reports or setting alerts — use performance-monitor (report or alert mode). 排名追踪/SERP监控

Rank Tracker

Tracks keyword positions, SERP feature ownership, and AI visibility over time.

Quick Start


Set up rank tracking for [domain] targeting these keywords: [keyword list]

Analyze ranking changes for [domain] over the past [time period]

Skill Contract

**Expected output**: a ranking report or delta summary plus the standard handoff summary for memory/monitoring/.

  • **Reads**: current rankings, prior baselines, target keyword list, locale/language/device/engine, snapshot/source refs, observation times/windows, stable page/content bindings, and any user-provided or tool metrics.
  • **Writes**: a user-facing monitoring deliverable and reusable summary.
  • **Promotes**: significant changes, confirmed anomalies, follow-up actions, and pending decisions to memory/open-loops.md.
  • **Done when**: every tracked keyword shows a current, context-matched position vs baseline with a labeled delta, or Unknown/NEEDS_REFRESH with its reason; each observation cites its source ref, observed time, window, locale/language/device/engine, evidence label, and ranking page ref; conflicts remain visible; and biggest movers and likely causes are named.
  • **Primary next skill**: performance-monitor (../performance-monitor/SKILL.md) when recurring monitoring should become automated.

### Handoff Summary

> Emit the standard shape from skill-contract.md §Handoff Summary Format (../../../references/skill-contract.md).

Data Sources

All integrations optional (see CONNECTORS.md (../../../CONNECTORS.md)). With tools, pull rankings from ~~SEO tool, impressions from ~~search console, traffic from ~~analytics, and AI citations from ~~AI monitor. Without tools, ask for positions, volumes, competitor data, and SERP feature status.

**Zero-dependency measurement loop** (no paid tool needed): never narrate a ranking movement you did not measure — record each check as a snapshot and let the ledger compute the delta. python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/ledger.py" record <domain> --source rank --data '{"<keyword>": <position>, ...}', then ledger.py diff <domain> --source rank for the change since the last check and ledger.py trend <domain> --source rank --field "<keyword>" for the series. Record real Search Console positions when connected, or the positions the user provides at Tier 1. A ranking delta is a **week-scale, confounded outcome** — attribute it against a control (a holdout keyword/competitor), not against zero; see references/measurement-protocol.md (../../../references/measurement-protocol.md). See scripts/connectors/README.md (../../../scripts/connectors/README.md).

Decision Gates

View full documentation

**Stop and ask the user when:**

  • No target keywords are provided and none can be inferred from CLAUDE.md or prior monitoring records — offer: (1) supply a keyword list, (2) track the domain's top known terms, (3) cancel.

**Continue silently (never stop for):**

  • No prior baseline exists — record the current run as the baseline, label all positions as the first snapshot, and proceed (do not invent a "previous" position).
  • Missing optional tool data (SERP features, AI citations) — mark N/A and proceed.

Instructions

When a user requests rank tracking or analysis:

1. **Set Up Keyword Tracking** — configure domain, market/locale, device, language, engine, update frequency, priorities, competitor watchlist, and stable page refs. Apply the SEO/GEO Evidence and Cycle Control Profile (../performance-monitor/references/evidence-and-cycle-control.md).

2. **Record Current Rankings** — output a position table where every row cites its source (tool export / user-provided / estimated), with position ranges, ranking URLs, feature ownership, and movement vs baseline.

3. **Analyze Ranking Changes** — highlight biggest wins, declines, stable terms, new rankings, lost rankings, likely causes, and recovery ideas; each delta labeled against its baseline.

4. **Track SERP Features** — compare ownership of snippets, PAA, image/video packs, local packs, and related feature shifts.

5. **Track GEO / AI Visibility** — monitor AI Overview presence, citation rate, citation position, and trend; mark each value Measured (from an ~~AI monitor) or N/A if unobserved.

6. **Compare Against Competitors** — report share of voice, head-to-head comparisons, and threat levels.

7. **Generate Ranking Report** — output overall trend, key wins, concerns, opportunities, SERP feature changes, GEO visibility, and recommendations, with each metric carrying its source tag.

Label every metric **Measured**, **User-provided**, **Calculated**, **Estimated**, **Proxy**, or **Unknown**; never present an estimate or proxy as measured. An applicable missing metric is Unknown with its reason. A stale or locale/language/device/engine-mismatched position is NEEDS_REFRESH, not a current ranking; N/A is only for a genuinely non-applicable field.

> **Reference**: See Ranking Analysis Templates (references/ranking-analysis-templates.md) for the complete output templates for all seven steps.

Example

A ranking report names the biggest winners, biggest drops, and next actions, with each position carrying its source tag and labeled delta against baseline.

Rank Change Quick Reference

### Response Protocol

| Change | Timeframe | Action |

|--------|-----------|--------|

| Drop 1-3 positions | Wait 1-2 weeks | Monitor — may be normal fluctuation |

| Drop 3-5 positions | Investigate within 1 week | Check technical issues and competitor changes |

| Drop 5-10 positions | Investigate immediately | Run a full diagnostic: technical, content, links |

| Drop off page 1 | Emergency response | Comprehensive audit + recovery plan |

| Position gained | Document and learn | Identify what worked and replicate |

> **Reference**: See Tracking Setup Guide (references/tracking-setup-guide.md) for tracking setup, root-cause taxonomy, CTR benchmarks, SERP feature impact, and algorithm-update assessment.

### Save Results

Ask "Save these results?" If yes, write to memory/monitoring/ — see Skill Contract (../../../references/skill-contract.md) §Save Results Template.

Reference Materials

  • SEO/GEO Evidence and Cycle Control Profile (../performance-monitor/references/evidence-and-cycle-control.md) — exact search observations, freshness, page bindings, and cycle rules
  • Tracking Setup Guide (references/tracking-setup-guide.md) — Setup rules, feature tracking, and interpretation guidance

Next Best Skill

Initial setup (no baseline) → performance-monitor (../performance-monitor/SKILL.md). Subsequent runs (baseline exists) → Terminal. Visited-set rule applies per skill-contract.md (../../../references/skill-contract.md).

Score breakdown

Trigger
8.5
What/When/When-Not present with Chinese trigger 查排名; when_to_use and keyword variety thinner than siblings.
Structure
8.0
105-line SKILL.md with two bundled references; depends on a reference inside the separate performance-monitor skill.
Workflow
8.4
Seven steps, stop/continue gates, strict evidence labels, NEEDS_REFRESH staleness rule and drop-response protocol.
Content
8.0
Concise imperative instructions with concrete ledger commands and threshold tables.
Engineering
6.0
Valid frontmatter; cross-skill reference and ledger.py connector missing from the standalone zip.
Security
10.0
No scripts or network calls bundled; WebFetch declared; no secrets or injection.
Clean focused rank-tracking skill with decision gates, evidence labeling and a drop-response protocol; thinner trigger coverage and cross-skill reference dependency.