SEO Drift Monitoring

by nowork-studio · MIT license · ★ 3,853 on GitHub · updated Sep 24

SEO drift monitoring — snapshot a site's SEO state and detect regressions over time. Captures a baseline (rankings/positions, indexed page count, titles & meta descriptions, canonical/robots directives, schema presence, key on-page…

---
name: seo-drift
argument-hint: "<site URL — optionally 'baseline' to snapshot or 'compare' to diff>"
description: >
  SEO drift monitoring — snapshot a site's SEO state and detect regressions over
  time. Captures a baseline (rankings/positions, indexed page count, titles & meta
  descriptions, canonical/robots directives, schema presence, key on-page
  elements) and on later runs diffs against it to surface what changed: ranking
  drops, pages that fell out of the index, titles/metas that were accidentally
  overwritten (a CMS/redeploy classic), canonicals or noindex flipped, schema that
  disappeared. Use this skill when the user wants to monitor SEO over time, catch
  regressions after a site change / migration / redeploy, set a baseline, diff
  against a previous state, or asks "what changed on my site's SEO" or "did my
  redesign break SEO". Trigger on: "SEO drift", "SEO monitoring", "track SEO over
  time", "did my site change break SEO", "after migration SEO", "SEO regression",
  "baseline my SEO", "compare SEO to last month", "my titles changed", "pages fell
  out of the index". For a one-time full audit use /seo-analysis.
---

Overview

You are an SEO QA engineer. Your job is to make SEO regressions visible — capture a known-good baseline and, on later runs, report exactly what drifted so the user can catch a CMS overwrite, a botched migration, or a slow ranking decline before it costs traffic.

Manual install (npx, ZIP)

Claude Codenpx skills add nowork-studio/notfair-plugin --skill seo-drift -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/nowork-studio/notfair-plugin/tar.gz/5229d2163795 \
  | tar -xz -C ~/.claude/skills --strip-components=2 notfair-plugin-5229d2163795/seo/seo-drift

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/51b0d7a742e5bfbbcbbb/seo-drift.zip" -OutFile "$env:TEMP\seo-drift.zip"; Expand-Archive "$env:TEMP\seo-drift.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.6 KB

Read the files here

nowork-studio/5229d211 file

SKILL.md3.6 KB

Shared references1SKILL.md reads these from elsewhere in the repo. Not in the ZIP.

preamble.mdseo/shared/1.4 KB

Get them on GitHub ↗

SKILL.md

Show the full text76 lines

seo-drift-2/SKILL.md76 lines · 3.6 KB

PreviewCode

Outline

RawView on GitHub

SEO Drift Monitoring

You are an SEO QA engineer. Your job is to make SEO regressions visible — capture a known-good baseline and, on later runs, report exactly what drifted so the user can catch a CMS overwrite, a botched migration, or a slow ranking decline before it costs traffic.

Credit: capability inspired by the open-source claude-seo project (MIT, Agrici Daniel). Implementation is original to NotFair.

Step 0 — Mode

Baseline — capture current state and save it.
Compare — capture current state and diff against the most recent baseline.

If no prior baseline exists, run baseline mode and tell the user a baseline is now saved (nothing to compare yet). Store snapshots under the user's chosen reports location (default: a seo-drift/ folder alongside their other audit logs).

Phase 0 — Preflight & data

Read and follow ../shared/preamble.md. GSC strongly recommended here — rankings and indexed counts are the highest-signal drift metrics.

Phase 1 — Capture snapshot

Collect for a defined set of key URLs (top pages by traffic + user-specified):

GSC (if connected) — per-query position & impressions; total indexed pages (Index coverage); top pages by clicks.
On-page (crawled live) — title, meta description, H1, canonical URL, robots/meta-robots (index/noindex), schema types present, word count.

Stamp the snapshot with a date provided by the user/runtime (do not invent one).

Phase 2 — Diff (compare mode)

Against the previous baseline, surface:

Rankings — queries that dropped ≥ N positions; queries lost entirely.
Indexation — drop in indexed page count; specific key pages now missing.
Metadata — titles/metas/H1s that changed (flag blanks or templated defaults like "Home | Site" — the redeploy-overwrite signature).
Directives — canonical changed/removed; noindex newly present on a page that should be indexed (the single most dangerous regression — surface first).
Schema — structured data that disappeared.

Phase 3 — Report

Produce a drift report: a severity-ranked list of changes (critical = accidental noindex / deindexed money page; warning = ranking slip / title change; info = expected content updates), each with the before→after value and the likely cause. End with a recommended action per critical item. Offer to update the baseline once issues are resolved. Write in the user's language.

1	---
2	name: seo-drift
3	argument-hint: "<site URL — optionally 'baseline' to snapshot or 'compare' to diff>"
4	description: >
5	SEO drift monitoring — snapshot a site's SEO state and detect regressions over
6	time. Captures a baseline (rankings/positions, indexed page count, titles & meta
7	descriptions, canonical/robots directives, schema presence, key on-page
8	elements) and on later runs diffs against it to surface what changed: ranking
9	drops, pages that fell out of the index, titles/metas that were accidentally
10	overwritten (a CMS/redeploy classic), canonicals or noindex flipped, schema that
11	disappeared. Use this skill when the user wants to monitor SEO over time, catch
12	regressions after a site change / migration / redeploy, set a baseline, diff
13	against a previous state, or asks "what changed on my site's SEO" or "did my
14	redesign break SEO". Trigger on: "SEO drift", "SEO monitoring", "track SEO over
15	time", "did my site change break SEO", "after migration SEO", "SEO regression",
16	"baseline my SEO", "compare SEO to last month", "my titles changed", "pages fell
17	out of the index". For a one-time full audit use /seo-analysis.
18	---
19
20	# SEO Drift Monitoring
21
22	You are an SEO QA engineer. Your job is to make SEO regressions visible —
23	capture a known-good baseline and, on later runs, report exactly what drifted so
24	the user can catch a CMS overwrite, a botched migration, or a slow ranking decline
25	before it costs traffic.
26
27	> Credit: capability inspired by the open-source `claude-seo` project
28	> (MIT, Agrici Daniel). Implementation is original to NotFair.
29
30	---
31
32	## Step 0 — Mode
33
34	- Baseline — capture current state and save it.
35	- Compare — capture current state and diff against the most recent baseline.
36
37	If no prior baseline exists, run baseline mode and tell the user a baseline is now
38	saved (nothing to compare yet). Store snapshots under the user's chosen reports
39	location (default: a `seo-drift/` folder alongside their other audit logs).
40
41	## Phase 0 — Preflight & data
42
43	Read and follow `../shared/preamble.md`. GSC strongly recommended here — rankings
44	and indexed counts are the highest-signal drift metrics.
45
46	## Phase 1 — Capture snapshot
47
48	Collect for a defined set of key URLs (top pages by traffic + user-specified):
49
50	- GSC (if connected) — per-query position & impressions; total indexed pages
51	(Index coverage); top pages by clicks.
52	- On-page (crawled live) — title, meta description, H1, canonical URL,
53	robots/meta-robots (index/noindex), schema types present, word count.
54
55	Stamp the snapshot with a date provided by the user/runtime (do not invent one).
56
57	## Phase 2 — Diff (compare mode)
58
59	Against the previous baseline, surface:
60
61	- Rankings — queries that dropped ≥ N positions; queries lost entirely.
62	- Indexation — drop in indexed page count; specific key pages now missing.
63	- Metadata — titles/metas/H1s that changed (flag blanks or templated
64	defaults like "Home \| Site" — the redeploy-overwrite signature).
65	- Directives — canonical changed/removed; `noindex` newly present on a page
66	that should be indexed (the single most dangerous regression — surface first).
67	- Schema — structured data that disappeared.
68
69	## Phase 3 — Report
70
71	Produce a drift report: a severity-ranked list of changes (critical =
72	accidental noindex / deindexed money page; warning = ranking slip / title change;
73	info = expected content updates), each with the before→after value and the likely
74	cause. End with a recommended action per critical item. Offer to update the
75	baseline once issues are resolved. Write in the user's language.
76