Agent skill · Content & Marketing

seo-drift

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO — baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".

Infrasity-Labsgithub.com/Infrasity-LabsGitHub ↗
claude-codeMIT
Install
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill seo-drift --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Path: .claude/skills/seo-drift/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 97
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# SEO Drift Monitor (April 2026) Git for your SEO. Capture baselines, detect regressions, track changes over time. --- ## Commands | Command | Purpose | |---------|---------| | `/seo drift baseline <url>` | Capture current SEO state as a "known good" snapshot | | `/seo drift compare <url>` | Compare current page state to stored baseline | | `/seo drift history <url>` | Show change history and past comparisons | --- ## What It Captures Every baseline records these SEO-critical elements: | Element | Field | Source | |---------|-------|--------| | Title tag | `title` | `parse_html.py` | | Meta description | `meta_description` | `parse_html.py` | | Canonical URL | `canonical` | `parse_html.py` | | Robots directives | `meta_robots` | `parse_html.py` | | H1 headings | `h1` (array) | `parse_html.py` | | H2 headings | `h2` (array) | `parse_html.py` | | H3 headings | `h3` (array) | `parse_html.py` | | JSON-LD schema | `schema` (array) | `parse_html.py` | | Open Graph tags | `open_graph` (dict) | `parse_html.py` | | Core Web Vitals | `cwv` (dict) | `pagespeed_check.py` | | HTTP status code | `status_code` | `fetch_page.py` | | HTML content hash | `html_hash` (SHA-256) | Computed | | Schema c

What's inside
Steps it walks through
  1. Commands
  2. What It Captures
  3. How Comparison Works
  4. Severity Levels
  5. Storage
  6. Tables
  7. Command: baseline
  8. Command: compare
  9. Command: history
  10. Cross-Skill Integration
  11. Error Handling
  12. Security
  13. Typical Workflows
  14. Pre/Post Deployment Check
Ships with 1 file
  • references/comparison-rules.md
Commands it runs
python scripts/drift_baseline.py <url>
python scripts/drift_baseline.py <url> --skip-cwv
python scripts/drift_compare.py <url>
python scripts/drift_compare.py <url> --baseline-id 5
python scripts/drift_compare.py <url> --skip-cwv
python scripts/drift_report.py <comparison_json_file> --output drift-report.html
python scripts/drift_history.py <url>
python scripts/drift_history.py <url> --limit 10
More from dev-gtm-claude-skills
All skills →
About this skill
What does the seo-drift skill do?

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO — baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".

How do I install it?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill seo-drift --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going