coffeegrind123

SEO Manager — AI skill for Claude Code

AI community

Claude Code skill: a complete SEO program from the terminal — research, build, and measure.

How to install SEO Manager

This entry records only its repository, not the path inside it, so there is no exact command to give. Open coffeegrind123/seo-manager and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What SEO Manager does

Claude Code skill: a complete SEO program from the terminal — research, build, and measure. Real crawl budget from your own access logs, AI-crawler ingestion, content decay, SERP drift, index-bloat scoring. No backend, no database, stdlib Python only.

Alternatives in AI

Manifest — Real-time cost observability for OpenClaw agents — track tokens, costs, messages, and model usage 4.1k ★
Geo SEO Claude — GEO-first SEO skill for Claude Code 3.6k ★
VibeMeter — A project to measure costs for Cursor and other AI provider 379 ★

README

seo-manager

A [Claude Code](https://claude.com/claude-code) skill that runs a complete SEO program for a git-based website from the terminal — research, build, measure — with every gate written down and every data source measured rather than assumed.

**No backend, no database, no MCP server.** State is a committed `.seo/` directory. Scripts are stdlib Python 3 with no installs.

What it does

**Propose and build**

Workflow	Job
`setup`	write `.seo/conventions.md` — the site facts every other workflow adapts from
`research`	keyword research that starts from what the product IS, gated by a page-1 authority count
`build-guide`	ship a guide as a PR, through a corpus sameness gate
`build-tool`	ship a free interactive tool as a PR
`trend-scan`	what is moving in the niche
`geo-scan`	whether AI assistants cite the site
`backlinks`	prospecting, with an explicit do-not-buy list

**Measure what already exists**

Workflow	Job
`crawl-log`	real crawl budget from your own access log: budget by silo, statuses served to bots, AI-crawler ingestion, verified-vs-spoofed Googlebot
`decay`	pages that lost rank, separated from pages whose demand fell
`drift`	whole-page-1 diffs: new entrants, AI-Overview changes, volatility, algorithm-update correlation
`programmatic`	index-bloat scoring across generated silos, decided on index evidence
`health`	technical audits triaged into queue items

Design rules it holds itself to

Never fabricate data. A failed call is reported, never papered over.
A negative result is only as good as its control. Every probe that can report "absent" runs a control that must come back "present" first — because a broken instrument and a real finding look identical. Both of the tools that needed this caught a false conclusion during development.
A refused SERP read is a failed read, never an empty page 1. The relevance guard re