seo-drift
Skill873 starsChanged 9 months agoMITView on GitHub
Compare two SEO snapshots by script: gainers, losers, drift classes. \"what moved after the core update\"
We split this skill into the rules it gives an agent
9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json
- Very specific: line 34
If no brand exists: ask "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults
- Very specific: line 51
All outputs go to ${CLAUDE_PLUGIN_DATA}/{brand}/seo/seo-drift/{YYYY-MM-DD}/.
- Very specific: line 74
If >40% in decline: likely Core Update or competitor catch-up.
- Very specific: line 75
If >20% reshuffle: likely intent shift (AI Mode reweighting).
- Very specific: line 76
If >30% growth: find amplification opportunities.
- Distinctive: line 77
If >15% new: new SERP coverage — track and validate intent fit.
- Distinctive: line 135
Don't run during a Core Update rollout: Wait until Google announces "rollout complete" + 7–14 days of settling.
- Distinctive: line 137
GSC's data lag is ~3 days: When pulling "current month" data, use the date range ending 3 days ago, not yesterday.
“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/digital-marketing-pro:seo-drift
Script location. If your host does not set
${CLAUDE_PLUGIN_ROOT}, the scripts are in this plugin'sscripts/folder, next toskills/. Run them with Python 3.10 or newer:python, orpython3wherepythonis not found (macOS, many Linux systems).
Purpose
Take two snapshots of SEO performance data — separated by weeks, a Core Update, a content refresh, or an algorithm change — and produce a structured drift report: top gainers, top losers, classifications (growth / decline / reshuffle / stable / new / lost), and diagnostic patterns. Works with classic GSC, the new GSC AI Performance Report, rank-tracker exports, and aeo-audit probe results.
Context efficiency
Heavy skill. Grep before Read any referenced file, then Read only matched ranges with offset + limit. List ${CLAUDE_PLUGIN_DATA}/<brand>/ before opening files. On re-invocation mid-session, skip files already in context.
When to Use
- Monthly performance review — last month vs the month before
- Core Update triage — pre-update vs post-update + settling window (use 14+ days after rollout-complete)
- AI Mode citation tracking — quarter-over-quarter
aeo-auditoutputs to see which queries gained / lost AI Mode citations (Google AI Mode citation diff is a leading indicator for organic decline) - Content refresh attribution — before vs after a planned content update to attribute lift to the refresh vs other factors
- GSC AI Performance Report — month-over-month deltas on the new (3 Jun 2026) combined AI Overviews + AI Mode report
- Site migration audit — pre-migration baseline vs post-migration settling
Don't use for single-point-in-time analysis (use the source skill — seo-audit, aeo-audit, gsc-ai-performance).
Brand context (auto-applied)
- Read
~/.claude-marketing/brands/_active-brand.jsonfor the active slug, then load~/.claude-marketing/brands/{slug}/profile.json - If no brand exists: ask "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults
- Apply
skills/context-engine/industry-profiles.mdfor industry-specific noise thresholds (YMYL industries should use higher--noiseto filter out routine Quality Rater Guidelines volatility)
Inputs
| Input | Source | Required? |
| Baseline CSV | Older snapshot | yes |
| Current CSV | Newer snapshot | yes |
| Join keys | Auto-detected (query, keyword, page, url) or --join-on flag | optional |
| Noise threshold | --noise (default 5%) — % below which a metric is "stable"; YMYL industries should use 10% to filter out Quality Rater Guidelines volatility | optional |
| Top-N | --top (default 20) — gainers/losers per metric | optional |
Both snapshots must come from the same source. Mixing a GSC export with an Ahrefs export will produce nonsense — different sources count different things.
Process (10 steps, numbered-file output)
All outputs go to ${CLAUDE_PLUGIN_DATA}/{brand}/seo/seo-drift/{YYYY-MM-DD}/.
00-input.md— capture baseline date range, current date range, source (GSC / GSC AI / rank-tracker / aeo-audit), brand context01-baseline.csv— copy baseline export here (so the drift run is reproducible months later)02-current.csv— copy current export here03-drift-run.json— run the script:python "${CLAUDE_PLUGIN_ROOT}/scripts/seo_drift.py" \ --baseline "${CLAUDE_PLUGIN_DATA}/{brand}/seo/seo-drift/{date}/01-baseline.csv" \ --current "${CLAUDE_PLUGIN_DATA}/{brand}/seo/seo-drift/{date}/02-current.csv" \ --top 30 --noise 5 \ --out "${CLAUDE_PLUGIN_DATA}/{brand}/seo/seo-drift/{date}/03-drift-run.json"04-quality-scorecard.md— readquality_scorecardfrom03-drift-run.json. Ifstatus: needs_review, diagnose:date_range_distinct: warn→ script couldn't auto-validate. Manually confirm in00-input.mdthat baseline and current cover non-overlapping windows.sample_size: fail→ either input has < 50 rows. Re-export without row limits.metric_compatibility: fail→ no numeric metrics in BOTH inputs. Column-name mismatch — re-export from the same source.no_lookup_collisions: fail→ duplicate keys in one input (e.g., same query × page row twice). Re-export with deduplication or use--join-onto add a distinguishing column.
05-biggest-gainers.md— narrative on the top 10 gainers across impressions / clicks / position. For each: hypothesis on cause (new content? backlinks gained? Core Update favoured E-E-A-T? Featured Snippet rotation?). Hand off candidates to/digital-marketing-pro:content-enginefor amplification.05-biggest-losers.md— narrative on the top 10 losers. For each: triage matrix —is_yMYL × had_recent_change × Core_Update_window→ action (refresh content / restore reverted change / wait for next algo cycle / accept and reallocate).06-ai-mode-shift.md(only if input source is GSC AI Performance Report) — queries that LOST AI Mode impressions are a leading indicator. Cross-reference with/digital-marketing-pro:aeo-auditto verify citation loss in synthetic probes.07-classification-distribution.md— counts table:- growth / decline / reshuffle / stable / new / lost
- If >40% in decline: likely Core Update or competitor catch-up. Run
/digital-marketing-pro:seo-auditfor diagnosis. - If >20% reshuffle: likely intent shift (AI Mode reweighting). Run
/digital-marketing-pro:aeo-geoto align with new intent patterns. - If >30% growth: find amplification opportunities. Run
/digital-marketing-pro:content-engineto brief follow-ups. - If >15% new: new SERP coverage — track and validate intent fit.
PLAN.md— single-page summary: stats + scorecard + top 5 actions ranked by impact × effort, with owner suggestions (SEO lead / content lead / dev team).
Output format
${CLAUDE_PLUGIN_DATA}/{brand}/seo/seo-drift/2026-06-04/
├── 00-input.md
├── 01-baseline.csv
├── 02-current.csv
├── 03-drift-run.json
├── 04-quality-scorecard.md
├── 05-biggest-gainers.md
├── 05-biggest-losers.md
├── 06-ai-mode-shift.md (only when input is GSC AI Performance Report)
├── 07-classification-distribution.md
└── PLAN.mdQuality scorecard (the four gates)
| Gate | What it checks | Why it matters |
| date_range_distinct | Baseline and current cover non-overlapping windows | Overlapping windows produce false-positive deltas — same data on both sides |
| sample_size | Each input has ≥ 50 rows | Below this, drift is noise |
| metric_compatibility | ≥ 1 numeric metric exists in both inputs | If columns differ (e.g., Ahrefs vs GSC), there's nothing to compare |
| no_lookup_collisions | No duplicate keys within an input | Duplicates make the delta math ambiguous |
status: ready requires sample, metric compatibility, and no-collision gates pass (date-range-distinct is warn not fail — the script can't always autodetect dates).
Classification rules
Each row in the report falls into one bucket:
| Classification | Trigger | Interpretation |
| growth | ≥ 2 metrics moved up > noise%, no metric down > 10% | Clear win — investigate for amplification |
| decline | ≥ 2 metrics moved down > noise%, no metric up > 10% | Clear loss — triage by YMYL × Core-Update-window |
| reshuffle | Significant moves in opposite directions (e.g., impressions up, position down) | AI Mode signature — content is being shown more broadly but for slightly different intents |
| stable | No metric moved more than noise% | No action |
| new | Absent in baseline, present in current | New content or new SERP coverage — track |
| lost | Present in baseline, absent in current | Content removed, deindexed, or fell out of tracking window |
Position is special: for position, lower numbers are better. The script automatically inverts position-delta direction for gain/loss ranking — you'll see -85.9% under position as a top gainer (page moved from position 12 to position 2).
Chain handoffs
This skill is typically a consumer + diagnostician:
/digital-marketing-pro:gsc-ai-performanceorseo-auditoraeo-audit— generates the snapshots/digital-marketing-pro:seo-drift— this skill- Branch by finding:
- High decline →
/digital-marketing-pro:seo-auditfor technical-side check +/digital-marketing-pro:content-decay-scanfor content-side - High reshuffle →
/digital-marketing-pro:aeo-geofor intent realignment - High growth →
/digital-marketing-pro:content-enginefor amplification briefs
- High decline →
Tips & caveats
- Don't run during a Core Update rollout. Wait until Google announces "rollout complete" + 7–14 days of settling. Mid-rollout deltas are unreliable.
- Position deltas are noisier than impression/click deltas — pages bouncing between positions 8 and 12 produce ±30% position deltas that mean nothing. Trust impression/click moves more for diagnosis.
- GSC's data lag is ~3 days. When pulling "current month" data, use the date range ending 3 days ago, not yesterday.
- The GSC AI Performance Report (3 Jun 2026) has NO click data. drift on AI report = impressions-only drift. Don't try to compute CTR drift from it.
- For Core Update triage, run drift twice: pre-update vs day-after-rollout-complete (the "blast"), and pre-update vs 14-days-after (the "settled state"). The two often disagree, and the 14-day view is the one that matters.
- Reshuffle classification is a leading indicator — when reshuffle counts spike, intent reweighting is happening. The next quarter's drift will usually show clearer growth/decline. Don't react too fast.
Agents used
analytics-analyst(primary) — interpretation + cause hypothesesseo-specialist— for technical-cause hypotheses on loserscompetitive-intel— when decline correlates with a competitor's winmarket-intelligence— for algo-update context (was there a Core Update in the window?)
See also
/digital-marketing-pro:gsc-ai-performance— pull the GSC AI Performance Report (input source)/digital-marketing-pro:seo-audit— diagnose decline causes/digital-marketing-pro:aeo-audit— diagnose AI Mode citation loss/digital-marketing-pro:content-decay-scan— for content-side decline triage/digital-marketing-pro:content-engine— for amplifying gainersscripts/seo_drift.py— the underlying drift engine
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 1
Wrote their own version · 22
- AgriciDaniel/claude-seo★ 20ksame name
- nowork-studio/notfair-plugin★ 4.1ksame name
- nowork-studio/toprank★ 4ksame name
- AgriciDaniel/codex-seo★ 795same name
- zhtyyx/codex-seo★ 108same name
- dancolta/seo-drift-monitor★ 19same name
- ZachArticulateV/designer-pro-and-seo★ 9same name
- joaoguirunas/team-os★ 4same name
- amirjahfar1/automate-seo-with-claude★ 2same name
- avalonreset/legends-seo-dungeon★ 2same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use seo-sxo, seo-maps and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
webdevarifSkillseo-sxo
Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".
Also in 18 projects that use this
webdevarifSkillseo-maps
Maps intelligence for local SEO: geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification, competitor radius mapping, and LocalBusiness schema generation. Three tiers: free (Overpass + Geoapify), DataForSEO, and DataForSEO + Google. Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", or "SoLV".
Also in 16 projects that use this
megastepSkillseo-page
Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says "analyze this page", "check page SEO", or provides a single URL for review.
Also in 20 projects that use this
megastepSkillseo-sitemap
Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".
Also in 18 projects that use this
mangollcSkillseo-backlinks
Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.
Also in 14 projects that use this
- +6 more from webdevarif
- +1 more from megastep
In this repository164 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ab-test-planSkill
- ad-creativeSkill
- add-integrationSkill
- aeo-auditSkill
- aeo-geoSkill
- agency-dashboardSkill
- agent-readiness-auditSkill
- analytics-insightsSkill
- anomaly-scanSkill
- attribution-modelSkill
- attribution-reportSkill
- audience-intelligenceSkill
- audience-profileSkill
- autopilot-statusSkill
- backlink-gapSkill
- brand-setupSkill
- budget-optimizerSkill
- budget-trackerSkill
- c2pa-metadataSkill
- campaign-auditSkill
- campaign-orchestratorSkill
- campaign-planSkill
- campaign-statusSkill
- case-study-planSkill
- checkSkill
- churn-riskSkill
- client-onboardingSkill
- client-proposalSkill
- client-reportSkill
- client-validation-documentSkill
- cohort-analysisSkill
- competitor-alertsSkill
- competitor-analysisSkill
- competitor-monitorSkill
- competitor-pagesSkill
- connectSkill
- content-briefSkill
- content-calendarSkill
- content-decay-scanSkill
- content-engineSkill
- content-repurposeSkill
- context-engineSkill
- continuous-improvement-loopSkill
- counter-narrativeSkill
- cowork-setupSkill
- creative-healthSkill
- creative-testing-frameworkSkill
- credential-switchSkill
- crisis-responseSkill
- crm-syncSkill
- croSkill
- dark-funnelSkill
- data-exportSkill
- data-importSkill
- digital-prSkill
- email-sequenceSkill
- emerging-channelsSkill
- engagement-workflowSkill
- entity-auditSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

