git clone --depth 1 https://github.com/nowork-studio/notfair-plugin /tmp/seo-drift && cp -r /tmp/seo-drift/seo/seo-drift ~/.claude/skills/seo-driftSKILL.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; `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.
Analyze connected Google Analytics 4 traffic, acquisition, engagement, landing pages, ecommerce, events, and conversions, and safely manage supported GA4 key events or custom dimensions through NotFair MCP. Use for GA4, Google Analytics, traffic or conversion drops, channel attribution, realtime activity, report requests, measurement configuration, or Analytics MCP setup.
Query and operate connected Google Search Console properties through NotFair MCP. Use for live GSC query or page performance, clicks, impressions, CTR, position, traffic changes, indexing status, URL inspection, sitemap reads or approved sitemap submission/removal, and Search Console MCP setup. Route full-site SEO audits to seo-analysis.
>
Plan, validate, and safely publish Google Ads assets, including sitelinks, callouts, structured snippets, image assets, and Performance Max asset briefs. Use when asked for Google Ads assets, ad extensions, sitelinks, callouts, snippets, image assets, Performance Max assets, PMax creative, or an asset audit.
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run an audit before. Also trigger proactively when other ads skills detect that business-context.json is missing.
Generate and A/B test Google Ads copy. Use when asked to write ad copy, headlines, descriptions, create ad variants, test ad messaging, improve CTR, or generate RSA (Responsive Search Ad) components. Trigger on "ad copy", "write ads", "headlines", "descriptions", "RSA", "responsive search ad", "ad text", "ad creative", "improve CTR", "ad A/B test", "ad variants", "write me an ad", "ad variation experiment", or when the user wants to improve click-through rate on existing ads.
Score and diagnose Google Ads landing pages. Use when asked to audit a landing page, check landing page quality, diagnose high-CTR but low-conversion-rate ad groups, improve Quality Score's Landing Page Experience component, or compare an ad group's messaging against its landing page. Trigger on "landing page audit", "landing page score", "landing page quality", "why is my conversion rate low", "LPX", "landing page experience", "ad to page match", or when `/google-ads-audit` surfaces a high-CTR / low-CVR ad group.
Manage Google Ads — performance, keywords, bids, budgets, negatives, campaigns, ads, search terms, QS, location targeting, bulk operations, experiments, asset management, portfolio bidding, offline conversions. Use for any mention of Google Ads, CPA, ROAS, ad spend, or campaign settings.