seo-drift

Capture SEO baselines, detect on-page changes, and track regressions over time.

19.4k|2.8k|Updated Feb 7, 2026

Search Tags:#sqlite #baseline #regression detection #on-page seo #schema monitoring #deployment check #seo drift

Ready to run

npx skills add https://github.com/AgriciDaniel/claude-seo --skill seo-drift-agricidaniel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: seo-drift
Source: https://github.com/AgriciDaniel/claude-seo/tree/main/skills/seo-drift
Command: npx skills add https://github.com/AgriciDaniel/claude-seo --skill seo-drift-agricidaniel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Silent SEO regressions caused by deployments, content updates, or third-party scripts often go unnoticed until traffic drops. This Skill provides a version-control system for on-page SEO elements, capturing known-good baselines and detecting exactly what changed and when. ## Core Features & Use Cases - Baseline Capture: Records title tags, meta descriptions, canonicals, robots directives, headings, JSON-LD schema, Open Graph tags, Core Web Vitals, HTTP status codes, and content hashes into a local SQLite database. - Rule-Based Comparison: Applies 17 comparison rules across CRITICAL, WARNING, and INFO severity levels to classify SEO drift and recommend specialized follow-up audits. - Change History: Tracks all baselines and comparisons per URL to pinpoint when regressions occurred. - Use Case: Before deploying a site update, capture a baseline; after deployment, run a comparison to immediately detect removed schema, changed canonicals, added noindex tags, or performance regressions. ## Quick Start Use the seo-drift skill to capture a baseline of https://example.com and then compare it after deployment to detect regressions.

Frequently Asked Questions about seo-drift

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect SEO regressions after a website deployment?▼

Capture a baseline of the page before deployment using the baseline command, then run the compare command after deployment. The comparison engine applies 17 rules across CRITICAL, WARNING, and INFO severity levels to identify removed schema, changed canonicals, added noindex directives, and performance regressions.

How to compare on-page SEO changes before and after a site update?▼

Use the baseline command to store the current SEO state as a known-good snapshot, then use the compare command to diff the current page against that baseline. The system tracks title tags, meta descriptions, canonicals, headings, JSON-LD schema, Open Graph tags, and Core Web Vitals.

Does SEO drift monitoring support Core Web Vitals and schema tracking?▼

Yes, the baseline captures Core Web Vitals metrics via PageSpeed checks and records JSON-LD schema arrays. Comparison rules detect CWV regressions greater than 20 percent, Lighthouse performance score drops of 10 or more points, and schema removal or modification.

Why does SEO comparison fail when no baseline exists for a URL?▼

The comparison command requires an existing baseline to diff against. If none exists for the normalized URL, the system informs the user and suggests running the baseline command first to capture the current page state.

What are the limitations of automated SEO drift detection?▼

Automated detection relies on deterministic rule thresholds and may flag intentional changes as warnings. It does not replace full technical audits, so cross-skill integration recommends specialized validation for schema, performance, content, and indexability findings.