seo-drift

Captures SEO baselines and detects on-page regressions through rule-based comparison.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/coseto6125/claude-setup --skill seo-drift-coseto6125
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seo-drift
Source: https://github.com/coseto6125/claude-setup/tree/main/skills/seo-drift
Command: npx skills add https://github.com/coseto6125/claude-setup --skill seo-drift-coseto6125

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? SEO elements like title tags, canonicals, schema markup, and Core Web Vitals can silently change after deployments or content edits, causing traffic loss that goes unnoticed for weeks. This Skill snapshots a page's SEO-critical elements and diffs future states against that baseline so regressions are caught immediately. ## Core Features & Use Cases - Baseline Capture: Records title, meta description, canonical, robots directives, headings, JSON-LD schema, Open Graph tags, Core Web Vitals, status code, and content hashes into a local SQLite database. - Rule-Based Comparison: Runs 17 comparison rules across CRITICAL, WARNING, and INFO severity levels to classify every detected change with recommended actions. - Change History: Stores all baselines and comparisons per URL so you can review when a change happened and trace regressions over time. - Use Case: Before a deployment, run a baseline on your key landing page; after the deploy, run a comparison to instantly see whether the canonical was dropped, noindex was added, or the title changed. ## Quick Start Ask the assistant to capture an SEO baseline for https://example.com and then compare it after your next deployment to detect any SEO regressions.

Frequently Asked Questions about seo-drift

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

FAQPage Schema
How do I monitor SEO changes on a web page over time?▼

Capture a baseline snapshot of the page's SEO-critical elements, then run comparisons after deployments or content edits. The comparison applies 17 rules across three severity levels and stores results in SQLite so you can review the full change history per URL.

What SEO elements does a baseline snapshot capture?▼

Each baseline records the title tag, meta description, canonical URL, robots directives, H1-H3 headings, JSON-LD schema, Open Graph tags, Core Web Vitals, HTTP status code, and SHA-256 hashes of the HTML body and schema content.

Which SEO changes are treated as critical regressions?▼

Critical findings include schema removal, canonical changed or removed, noindex added, H1 removed or drastically changed, title removed, and status code shifting from 2xx to 4xx or 5xx. These typically cause measurable traffic loss within days and require immediate action.

Can I compare a page without Core Web Vitals data?▼

Yes, pass the skip-CWV option when capturing a baseline or running a comparison. CWV fields are stored as null and the CWV-related rules are skipped, while all other comparison rules still run normally.

What happens if no baseline exists when I run a comparison?▼

The comparison reports that no baseline exists for the URL and suggests capturing one first. You can also target a specific earlier snapshot by passing a baseline ID instead of using the most recent one.