Skip to content

Seo Drift Monitor

Detects when a deploy silently ships a noindex, drops a schema block, or rewrites your canonical. Baselines a page's SEO contract, diffs every change with Critical/Warning/Info…

Install

$git clone https://github.com/dancolta/seo-drift-monitor

Install command taken from the project's README or registry entry. Always review code before running it.

SEO Drift Monitor

Git for SEO. Baseline your page, catch the silent regressions your deploys ship.

Not a crawler. Not a rank tracker. Not a Lighthouse wrapper. This catches the moment a deploy silently flipped your canonical, dropped a JSON-LD block, or shipped noindex to prod — before Google notices.

Extension for the claude-seo skill ecosystem for Claude Code.

git clone https://github.com/dancolta/seo-drift-monitor.git ~/.claude/skills/seo-drift

How it compares

SEO Drift Monitor ContentKing Screaming Frog Manual (curl + eyeball)
Explicit baseline you commit to git ✓ ✗ ✗ partial
Catches accidental noindex at deploy time ✓ partial ✗ partial
Severity-classified diffs (Critical/Warning/Info) ✓ partial ✗ ✗
Fix recommendations wired to claude-seo sub-skills ✓ ✗ ✗ ✗
Runs in CI / pre-merge / agent loop ✓ ✗ partial partial
Zero monthly cost ✓ ✗ ($200+/mo) ✗ (license) ✓
Full-site crawl ✗ (by design) ✓ ✓ ✗
Keyword/ranking tracking ✗ (by design) ✓ ✗ ✗
Owned by developer, not marketing ✓ ✗ partial ✓

How It Works

Think of it like git for SEO. You baseline a page when it's in a good state, then check it later to see what broke.

1. Optimize a page with claude-seo
2. /seo-drift baseline <url>       -- save the "known good" state
3. Developer pushes changes...
4. /seo-drift check <url>          -- compare against the baseline
5. Fix issues using recommended claude-seo skills
6. /seo-drift baseline <url>       -- save the new "known good"
7. Repeat after every deploy

The baseline is explicit. You choose when to save it. Each check compares against the most recent baseline for that URL. You can create multiple baselines over time -- the check always uses the latest one.


Commands

Command What it does
/seo-drift baseline <url> Snapshot all SEO-critical elements as "known good"
/seo-drift check <url> Compare current state against the latest baseline
/seo-drift history <url> Show all baselines and checks for a URL

What Gets Checked

Intentionally focused on the elements most commonly broken by deploys, CMS updates, and content edits. No full crawl, no content quality analysis, no image audits -- just the things that silently tank rankings when someone changes them without checking.

Elements Captured in Every Baseline

Similar plugs

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…

Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.

Explore related