SERP Rank Tracking
Rank tracking

Rank tracking without a tracker subscription — position movers between any two periods from real Search Console data. Use when asked "how are my rankings", "what moved this week/month", "track my keywords", or "did the update hit me".
---
name: rank-tracking
description: Rank tracking without a tracker subscription — position movers between any two periods from real Search Console data. Use when asked "how are my rankings", "what moved this week/month", "track my keywords", or "did the update hit me".
---
# Rank Tracking
## Requires
The free Ryze MCP connector (`https://connector.get-ryze.ai/mcp`). Claude Code: `claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp`. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp
Rank trackers estimate your position by scraping SERPs daily. Search Console records the position Google actually served you at. Use the real number.
## Workflow
1. **Property.** `google_search_console__listSites` → pick the user's domain.
2. **Two windows.** Default: last 28 days vs previous 28. If the user names an event ("since the March update"), split around that date. GSC data lags ~2 days — never include today.
3. **Pull both periods.** `google_search_console__runRawSearchAnalytics`, dimensions `["query"]`, rowLimit high enough to cover the site (start 5000). Repeat with `["page"]` for page-level movement.Overview
The free Ryze MCP connector (https://connector.get-ryze.ai/mcp). Claude Code: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp
Manual install (npx, ZIP)
npx skills add Ryze-AI-Adgent/open-seo-mcp-skills --skill rank-tracking -g -a claude-codenpx degit Ryze-AI-Adgent/open-seo-mcp-skills/skills/rank-tracking#main ~/.claude/skills/rank-trackingConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md2.3 KB
Read SKILL.md here
Show the full text34 lines
Rank Tracking
Requires
The free Ryze MCP connector (https://connector.get-ryze.ai/mcp). Claude Code: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp
Rank trackers estimate your position by scraping SERPs daily. Search Console records the position Google actually served you at. Use the real number.
Workflow
- Property.
google_search_console__listSites→ pick the user's domain. - Two windows. Default: last 28 days vs previous 28. If the user names an event ("since the March update"), split around that date. GSC data lags ~2 days — never include today.
- Pull both periods.
google_search_console__runRawSearchAnalytics, dimensions["query"], rowLimit high enough to cover the site (start 5000). Repeat with["page"]for page-level movement. - Join and diff. Match queries across periods, compute position delta, clicks delta, impressions delta.
- Classify:
- Winners — position improved ≥ 2 spots on queries with real impressions
- Losers — dropped ≥ 2 spots (sort by clicks lost, not by delta — a 4→7 drop on a money query beats a 40→80 crash on a nothing query)
- New — queries appearing only in the recent period
- Lost — queries that vanished
- Spot-verify (optional). For the 3–5 most important losers, if DataForSEO SERP tools are exposed in the workspace, pull the live SERP to see who took the spot. Skip if unavailable.
Output
Verdict first (net up/down and the single biggest move), then four tables: Winners, Losers, New, Lost — query, positions before→after, clicks delta. If the user asked about a specific algorithm update, answer that question explicitly with the before/after evidence.
Recurring
If the user wants this weekly, suggest scheduling it (Claude Code scheduled tasks / a routine) rather than re-running by hand.
| 1 | |
| 2 | name rank-tracking |
| 3 | description Rank tracking without a tracker subscription — position movers between any two periods from real Search Console data. Use when asked "how are my rankings", "what moved this week/month", "track my keywords", or "did the update hit me". |
| 4 | |
| 5 | |
| 6 | # Rank Tracking |
| 7 | |
| 8 | ## Requires |
| 9 | |
| 10 | The free Ryze MCP connector (`https://connector.get-ryze.ai/mcp`). Claude Code: `claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp`. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp |
| 11 | |
| 12 | Rank trackers estimate your position by scraping SERPs daily. Search Console records the position Google actually served you at. Use the real number. |
| 13 | |
| 14 | ## Workflow |
| 15 | |
| 16 | **Property.** `google_search_console__listSites` → pick the user's domain. |
| 17 | **Two windows.** Default: last 28 days vs previous 28. If the user names an event ("since the March update"), split around that date. GSC data lags ~2 days — never include today. |
| 18 | **Pull both periods.** `google_search_console__runRawSearchAnalytics`, dimensions `["query"]`, rowLimit high enough to cover the site (start 5000). Repeat with `["page"]` for page-level movement. |
| 19 | **Join and diff.** Match queries across periods, compute position delta, clicks delta, impressions delta. |
| 20 | **Classify:** |
| 21 | **Winners** — position improved ≥ 2 spots on queries with real impressions |
| 22 | **Losers** — dropped ≥ 2 spots (sort by clicks lost, not by delta — a 4→7 drop on a money query beats a 40→80 crash on a nothing query) |
| 23 | **New** — queries appearing only in the recent period |
| 24 | **Lost** — queries that vanished |
| 25 | **Spot-verify (optional).** For the 3–5 most important losers, if DataForSEO SERP tools are exposed in the workspace, pull the live SERP to see who took the spot. Skip if unavailable. |
| 26 | |
| 27 | ## Output |
| 28 | |
| 29 | Verdict first (net up/down and the single biggest move), then four tables: Winners, Losers, New, Lost — query, positions before→after, clicks delta. If the user asked about a specific algorithm update, answer that question explicitly with the before/after evidence. |
| 30 | |
| 31 | ## Recurring |
| 32 | |
| 33 | If the user wants this weekly, suggest scheduling it (Claude Code scheduled tasks / a routine) rather than re-running by hand. |
| 34 |
Details
- License
- MIT
- Stars on the repo
- ★ 3,135
- Checked
- Source
- Ryze-AI-Adgent/open-seo-mcp-skills ↗
- Creator
- Ryze-AI-Adgent · 8 listings
Similar skills
See all →
SkillCross-Platform Reverse Engineer
SkillBrainstorm Ideas
SkillCode Review Feedback Analyzer
SkillBug Diagnosis Framework
SkillImplement Spec
SkillPR Description WriterMore from Ryze-AI-Adgent
SkillAI Engine Visibility Tracker
SkillBacklink Comparison Tool
SkillKeyword Gap Analyzer
SkillSEO Content Brief
SkillKeyword Research & Metrics
SkillAnalytics-Based SEO Audit