SkillAgentSearch skills...

seo-drift

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO: baseline, diff, and track changes to your on-page SEO

Install / Use

npx skills add AgriciDaniel/claude-seo --skill seo-drift

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

98/100

Category

Operations

Supported Platforms

Universal

Our assessment of seo-drift

seo-drift scores 98/100 on our quality scale, 13th of 745 Operations skills we index (top 2%).

Its SKILL.md is 7.2 KB long, well organised into 19 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.

With 29,294 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
19/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 2 days ago, so seo-drift is actively maintained.
  • Our last check on 2026-11-14 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

seo-drift compared with similar skills

All 4 of these similar skills score higher than seo-drift; compare them before choosing.

SkillScoreStarsUpdatedFormat
seo-drift (this skill)by AgriciDaniel9829.3k2d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install seo-drift?
Run npx skills add AgriciDaniel/claude-seo --skill seo-drift. The install tabs above show the steps for each supported agent.
Which AI agents does seo-drift work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is seo-drift safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is seo-drift still maintained?
The repository was last updated 2 days ago, so seo-drift is actively maintained.

name: seo-drift description: > SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO: baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check". user-invocable: true argument-hint: "baseline|compare|history <url>" license: MIT metadata: author: AgriciDaniel original_author: "Dan Colta (Pro Hub Challenge)" version: "2.4.0" category: seo

SEO Drift Monitor (April 2026)

Git for your SEO. Capture baselines, detect regressions, track changes over time.


Commands

| Command | Purpose | |---------|---------| | /seo drift baseline <url> | Capture current SEO state as a "known good" snapshot | | /seo drift compare <url> | Compare current page state to stored baseline | | /seo drift history <url> | Show change history and past comparisons |


What It Captures

Every baseline records these SEO-critical elements:

| Element | Field | Source | |---------|-------|--------| | Title tag | title | parse_html.py | | Meta description | meta_description | parse_html.py | | Canonical URL | canonical | parse_html.py | | Robots directives | meta_robots | parse_html.py | | H1 headings | h1 (array) | parse_html.py | | H2 headings | h2 (array) | parse_html.py | | H3 headings | h3 (array) | parse_html.py | | JSON-LD schema | schema (array) | parse_html.py | | Open Graph tags | open_graph (dict) | parse_html.py | | Core Web Vitals | cwv (dict) | pagespeed_check.py | | HTTP status code | status_code | fetch_page.py | | HTML content hash | html_hash (SHA-256) | Computed | | Schema content hash | schema_hash (SHA-256) | Computed |


How Comparison Works

The comparison engine applies 17 rules across 3 severity levels. Load references/comparison-rules.md for the full rule set with thresholds, recommended actions, and cross-skill references.

Severity Levels

| Level | Meaning | Response Time | |-------|---------|---------------| | CRITICAL | SEO-breaking change, likely traffic loss | Immediate | | WARNING | Potential impact, needs investigation | Within 1 week | | INFO | Awareness only, may be intentional | Review at convenience |


Storage

All data is stored locally in SQLite:

~/.cache/claude-seo/drift/baselines.db

Tables

  • baselines: Captured snapshots with all SEO elements
  • comparisons: Diff results with triggered rules and severities

URL normalization ensures consistent matching: lowercase scheme/host, strip default ports (80/443), sort query parameters, remove UTM parameters, strip trailing slashes.


Command: baseline

Captures the current state of a page and stores it.

Steps:

  1. Validate URL (SSRF protection via google_auth.validate_url())
  2. Fetch page via "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run fetch_page.py <URL>
  3. Parse HTML via "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run parse_html.py <URL>
  4. Optionally fetch CWV via "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run pagespeed_check.py <URL> (use --skip-cwv to skip)
  5. Hash HTML body and schema content (SHA-256)
  6. Store snapshot in SQLite

Execution:

"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_baseline.py <url>
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_baseline.py <url> --skip-cwv

Output: JSON with baseline ID, timestamp, URL, and summary of captured elements.


Command: compare

Fetches the current page state and diffs it against the most recent baseline.

Steps:

  1. Validate URL
  2. Load most recent baseline from SQLite (or specific --baseline-id)
  3. Fetch and parse current page state
  4. Run all 17 comparison rules
  5. Classify findings by severity
  6. Store comparison result
  7. Output JSON diff report

Execution:

"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_compare.py <url>
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_compare.py <url> --baseline-id 5
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_compare.py <url> --skip-cwv

Output: JSON with all triggered rules, old/new values, severity, and actions.

After comparison, offer to generate an HTML report:

"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_report.py <comparison_json_file> --output drift-report.html

Command: history

Shows all baselines and comparisons for a URL.

Execution:

"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_history.py <url>
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run drift_history.py <url> --limit 10

Output: JSON array of baselines (newest first) with timestamps and comparison summaries.


Cross-Skill Integration

When drift is detected, recommend the appropriate specialized skill:

| Finding | Recommendation | |---------|----------------| | Schema removed or modified | Run /seo schema <url> for full validation | | CWV regression | Run /seo technical <url> for performance audit | | Title or meta description changed | Run /seo page <url> for content analysis | | Canonical changed or removed | Run /seo technical <url> for indexability check | | Noindex added | Run /seo technical <url> for crawlability audit | | H1/heading structure changed | Run /seo content <url> for E-E-A-T review | | OG tags removed | Run /seo page <url> for social sharing analysis | | Status code changed to error | Run /seo technical <url> for full diagnostics |


Error Handling

| Scenario | Action | |----------|--------| | URL unreachable | Report error from fetch_page.py. Do not guess state. Suggest user verify URL. | | No baseline exists for URL | Inform user and suggest running baseline first. | | SSRF blocked (private IP) | Report validate_url() rejection. Never bypass. | | SQLite database missing | Auto-create on first use. No error. | | CWV fetch fails (no API key) | Store null for CWV fields. Skip CWV rules during comparison. | | Page returns 4xx/5xx | Still capture as baseline (status code IS a tracked field). | | Multiple baselines exist | Use most recent unless --baseline-id specified. |


Security

  • All URL fetching goes through "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run fetch_page.py, which enforces SSRF protection (blocks private IPs, loopback, reserved ranges, GCP metadata endpoints)
  • No curl, no subprocess HTTP calls -- only the project's validated fetch pipeline
  • All SQLite queries use parameterized placeholders (?), never string interpolation
  • TLS always verified -- no verify=False anywhere in the pipeline

Typical Workflows

Pre/Post Deployment Check

/seo drift baseline https://example.com     # Before deploy
# ... deploy happens ...
/seo drift compare https://example.com      # After deploy

Ongoing Monitoring

/seo drift baseline https://example.com     # Initial capture
# ... weeks later ...
/seo drift compare https://example.com      # Check for drift
/seo drift history https://example.com      # Review all changes

Investigating a Traffic Drop

/seo drift compare https://example.com      # What changed?
/seo drift history https://example.com      # When did it change?

Related Skills

View on GitHub
GitHub Stars29.3k
CategoryOperations
Updated2d ago
Forks3.7k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions