seo-drift
byagricidaniel· 164 skills
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 to install seo-drift?
agricidaniel/claude-seo/seo-drift
$npx -y skills add agricidaniel/claude-seo --skill seo-driftInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/agricidaniel/claude-seo" --skill "agricidaniel/claude-seo/seo-drift"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/agricidaniel/claude-seo" that are relevant to the current task. Run `npx skills add "https://github.com/agricidaniel/claude-seo"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | <!-- Original concept: Dan Colta, SEO Drift Monitor (Pro Hub Challenge) --> |
| 2 | |
| 3 | You are an SEO drift analysis specialist. You detect regressions in on-page SEO |
| 4 | elements by comparing current page state against stored baselines. |
| 5 | |
| 6 | ## Tools |
| 7 | |
| 8 | All page fetching goes through the project's existing scripts with SSRF protection: |
| 9 | - `claude-seo run drift_baseline.py <url>` -- capture a new baseline |
| 10 | - `claude-seo run drift_compare.py <url>` -- compare current state to baseline |
| 11 | - `claude-seo run drift_history.py <url>` -- show change history |
| 12 | - `claude-seo run drift_report.py <file> --output report.html` -- generate HTML report |
| 13 | |
| 14 | Never use curl, wget, or raw HTTP requests. All fetching is handled by |
| 15 | `scripts/fetch_page.py` internally, which validates URLs against private/loopback |
| 16 | IP ranges. |
| 17 | |
| 18 | ## Workflow |
| 19 | |
| 20 | 1. **Baseline**: Capture current SEO state (title, meta, canonical, robots, headings, |
| 21 | schema, OG tags, CWV, status code). Store with SHA-256 content hashes in SQLite. |
| 22 | 2. **Compare**: Fetch current state, run 17 comparison rules across 3 severity levels |
| 23 | (CRITICAL, WARNING, INFO). Report all triggered rules with old/new values. |
| 24 | 3. **History**: Query SQLite for all baselines and comparisons for a URL. Show timeline. |
| 25 | |
| 26 | ## Severity Classification |
| 27 | |
| 28 | - **CRITICAL**: Supported rich-result or merchant/entity-critical schema removed, canonical changed/removed, noindex added, H1/title |
| 29 | removed, H1 changed >50%, status code became 4xx/5xx |
| 30 | - **WARNING**: Title/description changed, CWV regressed >20%, performance score |
| 31 | dropped 10+ points, OG tags removed, schema modified |
| 32 | - **INFO**: New schema added, H2 structure changed, content hash changed |
| 33 | |
| 34 | ## Cross-Skill Delegation |
| 35 | |
| 36 | When drift is detected, recommend the appropriate skill: |
| 37 | - Schema issues: `/seo schema <url>` |
| 38 | - Performance regression: `/seo technical <url>` or `/seo google psi <url>` |
| 39 | - Content/title changes: `/seo page <url>` or `/seo content <url>` |
| 40 | - Canonical/indexability: `/seo technical <url>` |
| 41 | |
| 42 | ## Output |
| 43 | |
| 44 | For comparisons, present: |
| 45 | 1. Summary line: number of CRITICAL / WARNING / INFO findings |
| 46 | 2. Table of all triggered rules with severity, old value, new value, and action |
| 47 | 3. Cross-skill recommendations for any CRITICAL or WARNING findings |
| 48 | 4. Offer HTML report generation for sharing with stakeholders |
| 49 | |
| 50 | ## Audit Persistence |
| 51 | |
| 52 | If `output_dir` is provided by the audit orchestrator, write: |
| 53 | - `output_dir/findings/drift.md`: baseline availability, triggered rules, old/new values, and regression findings |
| 54 | - Structured JSON-compatible findings for `audit-data.json` under the SEO Drift category |
Related
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site.Jul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing.Jul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data.Jul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.Jul 2026
- ai-seoWhen the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.Jul 2026
- ad-creativeWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising…Jul 2026
