seo-drift

Detect SEO regressions by diffing baseline page elements against later crawl results.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

SEO drift monitoring prevents unnoticed on-page changes from quietly degrading rankings by capturing a baseline and comparing later page states.

Core Features & Use Cases

  • Baseline capture: Snapshots track title tag, meta description, canonical, robots directives, heading structure, JSON-LD presence/content, Open Graph tags, Core Web Vitals, HTTP status code, and content/schema hashes.
  • Automated diff & severity: Compares current results against the most recent (or a chosen) baseline and classifies findings into CRITICAL, WARNING, and INFO with rule-based actions.
  • Deployment and regression workflows: Use it for pre/post checks around releases, investigations after traffic drops, and ongoing monitoring for high-risk pages.

Quick Start

Ask: /seo drift baseline https://example.com to capture a known-good snapshot, then later ask /seo drift compare https://example.com 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 before they impact rankings?▼

Detect SEO regressions by capturing a baseline snapshot of page-critical elements and diffing it against later crawl results to identify changes in title tags, canonicals, or JSON-LD before rankings drop.

What on-page elements should I monitor to prevent SEO drift?▼

Monitor title tags, meta descriptions, canonical URLs, robots directives, heading structure, JSON-LD schema, Open Graph tags, Core Web Vitals, and HTTP status codes to catch content regressions and prevent SEO drift.

How do I check for SEO regressions after a website deployment?▼

Check for post-deployment SEO regressions by capturing a pre-release baseline snapshot and running an automated diff comparison to classify changes into CRITICAL, WARNING, or INFO severity levels.

Can I use automated diffing to troubleshoot sudden traffic drops?▼

Yes, you can troubleshoot traffic or indexing issues by comparing the current crawl of a specific URL against a stored historical baseline to identify exactly which on-page elements changed.

Does this approach require external dependencies or specific storage?▼

This approach requires no external dependencies and uses SQLite-backed storage to retain baseline snapshots and historical diff data for ongoing monitoring and regression analysis.

What is the best way to track canonical changes and schema regressions?▼

Track canonical changes and schema regressions by capturing content and schema hashes in a baseline snapshot, then running rule-based comparisons against future crawls to flag any modifications.