web-seolisted
Install: claude install-skill yybd/app-factory
# web-seo — what a site is doing in search, and what to do about it
**Where the site is, and what it is made of**, comes from `.claude/seo-site.json` in
the site's own repo — hostnames, which directory serves which property, the publish
command, and the credentials for the live half. It is optional: without one, the repo
is the site. The shape is in [references/site-descriptor.md](references/site-descriptor.md).
**A baseline is worth more than any single reading.** Search numbers only mean
something against an earlier measurement of the same thing, so the first run of this
skill on a site is a baseline, and every later one is compared to it. Keep it where the
site keeps its own notes.
Work in two passes and in this order: **audit the pages** (`audit.py` — offline,
seconds, everything actionable now), then **read Google's response** — a snapshot
of Search Console and analytics. **No client for those APIs ships here**; GA4 is
read through Google's `analytics-mcp` server when the machine has it (§3), and the
rest of the snapshot is whatever export or dashboard the site already has. It can only
report what the pages already earned. Diagnosing from the response alone is how a markup problem gets
mistaken for a demand problem.
It does **not** set up measurement — that exists — and it does not write the
product's words: those come from `<slug>/profile.md` and are edited by
`copy-edit`. It decides *what* needs saying and where; that skill decides how it
reads.
This file is the m