seo-drift

Detects SEO regressions by diffing page snapshots against stored baselines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and 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 ranking and traffic losses that go unnoticed for weeks. This Skill captures baselines of SEO-critical page elements and diffs future states against them so regressions are caught immediately. ## Core Features & Use Cases - Baseline Capture: Snapshot 13 SEO-critical elements per URL (title, meta description, canonical, robots directives, headings, JSON-LD schema, Open Graph tags, Core Web Vitals, status code, content hashes) into a local SQLite database. - Rule-Based Comparison: Run 17 comparison rules across CRITICAL, WARNING, and INFO severity levels to classify every detected change with recommended actions. - Change History: Query the full history of baselines and comparisons per URL to pinpoint when a regression was introduced. - Use Case: Before a site deployment, run a baseline on key pages; after deployment, run compare to instantly see if a canonical was dropped, noindex was added, or schema was removed. ## Quick Start Ask the assistant to capture an SEO baseline for a URL, then later ask it to compare that URL against its baseline to see what changed.

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 elements, then run a comparison later to diff the current state against it. The comparison applies 17 rules that classify changes as CRITICAL, WARNING, or INFO with recommended actions.

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.

How do I check if a deployment broke my SEO?▼

Run a baseline on key URLs before deploying, then run a compare after deployment. Critical issues like removed canonicals, added noindex directives, or dropped schema are flagged immediately with cross-references to deeper audit commands.

Where is the SEO drift baseline data stored?▼

All baselines and comparison results are stored locally in a SQLite database at ~/.cache/claude-seo/drift/baselines.db. URLs are normalized before matching so equivalent URLs map to the same history.

What happens if Core Web Vitals data cannot be fetched?▼

If the PageSpeed fetch fails or no API key is available, CWV fields are stored as null and CWV-related comparison rules are skipped. The rest of the baseline and comparison pipeline continues normally.

Can I compare against an older baseline instead of the latest one?▼

Yes, the compare command accepts a --baseline-id option to diff against a specific historical snapshot. Without it, the most recent baseline for the normalized URL is used automatically.