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.
适合你，如果定期检查网站SEO健康度，担心改版或迁移破坏排名
npx oh-my-skill add nowork-studio/notfair/seo-driftcurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- nowork-studio/notfair/seo-driftnpx oh-my-skill verify nowork-studio/notfair/seo-drift怎么用
商店整理自技能原文 · 版本 82a79b7 · 表述以原文为准安装后，Claude 会抓取你网站的 SEO 状态（排名、索引页数、标题、元描述、规范标签、结构化数据等）作为基线，后续运行时对比基线，报告哪些 SEO 指标发生了变化，比如排名下降、页面掉出索引、标题被意外覆盖等。
当你要求监控 SEO 随时间的变化、在网站改版或迁移后检查 SEO 是否回退、或者问“我的网站 SEO 有什么变化”时触发。
技能原文 SKILL.md
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;
noindexnewly 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.