Seo Drift logo

Seo Drift

OrganizationPopular
nowork-studio
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.

Overview

Publishernowork-studio
Repositorynotfair-plugin
Skill nameseo-drift
Stars
3.8K
Forks
488
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by nowork-studio on GitHub. Read the source before you install it.

Installation

Install the Seo Drift AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git /tmp/notfair-plugin
mkdir -p .claude/skills
cp -r /tmp/notfair-plugin/seo/seo-drift .claude/skills/seo-drift
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Seo Drift in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Seo Drift on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Seo Drift is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

What does the Seo Drift AI skill do?

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 / red...

Why use Seo Drift on TypingMind?

Because you install it once and use it with any model. Seo Drift is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Seo Drift in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nowork-studio/notfair-plugin/tree/main/seo/seo-drift. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Seo Drift?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Seo Drift?

As many as you like. As long as a model supports skills, you can use Seo Drift with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Seo Drift AI skill free?

Yes. It is published on GitHub by nowork-studio under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇