Track keyword rankings over time with trend analysis, movement detection, and competitive benchmarking.
Works with
Records and monitors keyword positions across traditional SERPs and AI-generated responses, with historical trend analysis and significant movement alerts
Tracks SERP features (featured snippets, PAA, image/video packs) and AI Overview citation rates for comprehensive search visibility
Compares rankings against competitors with share-of-voice metrics and head-to-head keyword analys
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrank-trackerExecute the skills CLI command in your project's root directory to begin installation:
Fetches rank-tracker from aaron-he-zhu/seo-geo-claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate rank-tracker. Access via /rank-tracker in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
873
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
873
stars
SEO & GEO Skills Library · 20 skills for SEO + GEO · ClawHub · skills.sh System Mode: This monitoring skill follows the shared Skill Contract and State Model.
Tracks, analyzes, and reports on keyword ranking positions over time. Monitors both traditional SERP rankings and AI/GEO visibility to provide comprehensive search performance insights.
System role: Monitoring layer skill. It turns performance changes into deltas, alerts, and next actions.
Use this when the conversation involves any of these situations — even if the user does not use SEO terminology:
Use this whenever the task needs time-aware change detection, escalation, or stakeholder-ready visibility.
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Set up rank tracking for [domain] targeting these keywords: [keyword list]
Analyze ranking changes for [domain] over the past [time period]
Compare my rankings to [competitor] for [keywords]
Create a ranking report for [domain/campaign]
Expected output: a delta summary, alert/report output, and a short handoff summary ready for memory/monitoring/.
memory/monitoring/.memory/open-loops.md and memory/decisions.md.Next Best Skill below when a change needs action.Note: All integrations are optional. This skill works without any API keys — users provide data manually when no tools are connected.
See CONNECTORS.md for tool category placeholders.
With ~~SEO tool + ~~search console + ~~analytics + ~~AI monitor connected: Automatically pull ranking positions from ~~SEO tool, search impressions/clicks from ~~search console, traffic data from ~~analytics, and AI Overview citation tracking from ~~AI monitor. Daily automated rank checks with historical trend data.
With manual data only: Ask the user to provide:
Proceed with the full analysis using provided data. Note in the output which metrics are from automated collection vs. user-provided data.
When a user requests rank tracking or analysis:
Set Up Keyword Tracking -- Configure domain, location, device, language, update frequency. Add keywords with volume, current rank, type, and priority. Set up competitor tracking and keyword categories (brand/product/informational/commercial).
Record Current Rankings -- Ranking overview by position range (#1, #2-3, #4-10, #11-20, etc.), position distribution visualization, detailed rankings with URL, SERP features, and change.
Analyze Ranking Changes -- Overall movement metrics, biggest improvements and declines with hypothesized causes, recommended recovery actions, stable keywords, new rankings, lost rankings.
Track SERP Features -- Feature ownership comparison vs competitors (snippets, PAA, image/video pack, local pack), featured snippet status, PAA appearances.
Track GEO/AI Visibility -- AI Overview presence per keyword, citation rate and position, GEO performance trend over time, improvement opportunities.
Compare Against Competitors -- Share of voice table, head-to-head comparison per keyword, competitor movement alerts with threat level.
Generate Ranking Report -- Executive summary with overall trend, position distribution, key highlights (wins/concerns/opportunities), detailed analysis, SERP feature report, GEO visibility, competitive position, recommendations.
Reference: See references/ranking-analysis-templates.md for complete output templates for all 7 steps.
User: "Analyze my ranking changes for the past month"
Output:
# Ranking Analysis: [current month, year]
## Summary
Your average position improved from 15.3 to 12.8 (-2.5 positions = better)
Keywords in top 10 increased from 12 to 17 (+5)
## Biggest Wins
| Keyword | Old | New | Change | Possible Cause |
|---------|-----|-----|--------|----------------|
| email marketing tips | 18 | 5 | +13 | Likely driven by content refresh |
| best crm software | 24 | 11 | +13 | Correlates with new backlinks acquired |
| sales automation | 15 | 7 | +8 | Correlates with schema markup addition |
## Needs Attention
| Keyword | Old | New | Change | Action |
|---------|-----|-----|--------|--------|
| marketing automation | 4 | 12 | -8 | Likely displaced by new HubSpot guide |
**Recommended**: Update your marketing automation guide with [current year] statistics and examples.
| 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 for technical issues, competitor changes |
| Drop 5-10 positions | Investigate immediately | Full diagnostic: technical, content, links |
| Drop off page 1 | Emergency response | Comprehensive audit + recovery plan |
| Position gained | Document and learn | What worked? Can you replicate? |
Reference: See references/tracking-setup-guide.md for root cause taxonomy, CTR benchmarks by position, SERP feature CTR impact, algorithm update assessment, tracking configuration best practices, keyword selection and grouping strategies, and data interpretation guidelines.
After delivering monitoring data or reports to the user, ask:
"Save these results for future sessions?"
If yes, write a dated summary to memory/monitoring/YYYY-MM-DD-<topic>.md containing:
If any findings should influence ongoing strategy, recommend promoting key conclusions to memory/hot-cache.md.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added rank-tracker from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in rank-tracker — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
rank-tracker fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added rank-tracker from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
rank-tracker fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
rank-tracker is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
rank-tracker reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: rank-tracker is the kind of skill you can hand to a new teammate without a long onboarding doc.
rank-tracker has been reliable in day-to-day use. Documentation quality is above average for community skills.
rank-tracker is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 39