seo-drift

Capture and compare SEO page states to identify drift and regressions.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/martingaam-hue/proavtive --skill seo-drift-martingaam-hue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seo-drift
Source: https://github.com/martingaam-hue/proavtive/tree/main/.claude/skills/seo-drift
Command: npx skills add https://github.com/martingaam-hue/proavtive --skill seo-drift-martingaam-hue

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Baseline, detect, and track SEO changes across pages to prevent traffic loss by highlighting regressions and unexpected shifts.

Core Features & Use Cases

  • Baseline capture for a URL to establish a known-good SEO state.
  • Compare current page state against the baseline to surface drift and rule-triggered issues.
  • History view to review past baselines and comparisons for audit and optimization.

Quick Start

Capture a baseline with /seo drift baseline <url>, then compare with /seo drift compare <url> to detect drift after changes.

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 drift on specific webpages over time?

Capture a baseline state for a URL, then compare future page states against it to detect SEO drift and regressions. This ongoing web monitoring uses rule-based comparison with severity levels to produce actionable diffs and prevent traffic loss.

How do I validate SEO regressions after a website deployment?

Validate SEO regressions after deployment by comparing the current page state against a previously captured baseline. This rule-based comparison applies severity levels to the diffs, highlighting unexpected shifts and deployment-triggered SEO issues for individual URLs.

Does this SEO drift monitoring require a database or external dependencies?

This SEO drift monitoring requires local SQLite storage to save baselines and comparison history, and has no external dependencies. URL normalization and rule-based comparisons run locally to track SEO issues for individual URLs without needing external services.

What is the best way to track historical SEO baselines and comparisons for auditing?

The best way to track historical SEO baselines and comparisons is using a local SQLite storage system that maintains a full history view. This allows you to review past baselines and rule-triggered diffs for audit and optimization purposes.

Can I troubleshoot SEO issues for individual URLs using rule-based comparison?

Yes, you can troubleshoot SEO issues for individual URLs by capturing a baseline state and running rule-based comparisons with severity levels. This produces actionable diffs that highlight specific SEO regressions and unexpected page state shifts.

What are the limitations of using local SQLite for web monitoring and SEO drift detection?

Using local SQLite for SEO drift detection limits monitoring to a single local environment rather than distributed or cloud-scale web monitoring. It requires manual URL normalization and rule-based comparison configuration for each individual URL tracked.