← ClaudeAtlas

auditlisted

Run a technical SEO audit on a chosen managed site — verifies all 8 non-negotiables, runs Lighthouse mobile, checks Core Web Vitals from GSC field data, validates schema on representative pages, audits foundational infrastructure (GSC, GBP, GA4, GTM, BWT). Logs results to `sites/[name]/site-info.md` under "Technical SEO baseline." Use when the user types `/audit` or after any major site change.
mkreindel/seo-toolkit-template · ★ 0 · AI & Automation · score 68
Install: claude install-skill mkreindel/seo-toolkit-template
# `/audit` — Technical SEO auditor Walks a single site against the toolkit's technical SEO standards and writes the result. ## Inputs Required: - **Site** — must match a folder under `sites/[name]/`. Optional: - **Audit depth** — `quick` (8 non-negotiables only), `full` (default — non-negotiables + Lighthouse + schema + infrastructure + AI search visibility), `deep` (full + competitor comparison + backlink baseline + on-page audit of top 5 pages). ## Workflow ### Step 0 — Cron-mode detection (if invoked with `--cron`) If the invocation contains `--cron`, this skill runs in cron mode (no user available). Required behavior: 1. **Idempotency check:** see this skill's "Routine versioning + idempotency contract" section. If today's output already exists, exit cleanly with `exit: "idempotent-skip"`. Write one line to the audit log via `scripts/lib/audit-log.mjs` `appendRun({ exit: "idempotent-skip", ... })`. 2. **Escalation contract:** any decision that would normally prompt the user (missing required file, voice anti-AI failure, schema validation failure, keyword cannibalization, etc.) MUST be escalated by writing an item to `sites/{site}/_inbox/` via `scripts/lib/cron-mode.mjs` `writeInboxItem(...)`. After writing, exit cleanly with `exit: "escalated"`. Do NOT use `AskUserQuestion` in cron mode. 3. **Defaults:** when a choice would normally be asked, default to `site-info.md` / `goals.md` values. If both are silent on the required choice, escalate per (2). 4. **Audit l