How do I install the SEO Drift skill?

Run npx skillmds add majiayu000/seo-drift in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is SEO Drift safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with SEO Drift?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is SEO Drift free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published SEO Drift?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

SEO Drift by majiayu000 — Agent Skill

Name: SEO Drift
Rating: 4.2 (5 reviews)
Author: majiayu000

SEO Drift

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.

majiayu000 ca19a22 2 files · 5.7 KB Updated Sep 9, 2026 567 repo stars

File contents

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.

---name: seo-driftdescription: 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.--- # 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.

Frequently asked questions