From aaron-seo-geo
Tracks keyword rankings, SERP positions, and AI visibility over time. Compares snapshots, measures position deltas, and flags ranking drops for SEO monitoring.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aaron-seo-geo:rank-tracker <domain> [keyword list]When to use
Use when tracking keyword rankings, monitoring position changes, comparing ranking snapshots, or detecting ranking drops.
<domain> [keyword list]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Tracks keyword positions, SERP feature ownership, and AI visibility over time.
Tracks keyword positions, SERP feature ownership, and AI visibility over time.
Set up rank tracking for [domain] targeting these keywords: [keyword list]
Analyze ranking changes for [domain] over the past [time period]
Expected output: a ranking report or delta summary plus the standard handoff summary for memory/monitoring/.
memory/open-loops.md.Emit the standard shape from skill-contract.md §Handoff Summary Format.
All integrations optional (see 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.
Stop and ask the user when:
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):
When a user requests rank tracking or analysis:
Label every metric Measured (tool/export), User-provided, or Estimated (model inference); never present an estimate as measured; if a required metric is unavailable, mark it N/A — do not invent it.
Reference: See Ranking Analysis Templates for the complete output templates for all seven steps.
Sample outcome: average position improves from 15.3 to 12.8, top-10 keywords rise from 12 to 17, and the report highlights the biggest winners, biggest drops, and next actions.
Track consistently, segment by intent, watch competitors, and include SERP feature plus GEO signals.
| 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 for tracking setup, root-cause taxonomy, CTR benchmarks, SERP feature impact, and algorithm-update assessment.
Ask "Save these results?" If yes, write to memory/monitoring/ — see Skill Contract §Save Results Template.
Initial setup (no baseline) → alert-manager. Subsequent runs (baseline exists) → Terminal. Visited-set rule applies per skill-contract.md.
npx claudepluginhub aaron-he-zhu/seo-geo-claude-skills --plugin aaron-seo-geoTracks keyword rankings via Moz and Google Search Console, detects drops, and generates alerts. Use when monitoring organic search positions or setting up ranking baselines.
Sets up and runs rank tracking with Ahrefs MCP: picks keywords to track, segments them by purpose, sets baselines, defines alert thresholds, and establishes a reporting cadence.
Tracks keyword ranking positions for a domain over time using NodesHub SERPdata API. Saves daily snapshots and compares changes.