kai-seo-auditlisted

# /kai-seo-audit — Prioritized Technical Fix List > **Kai root note:** `knowledge/`, `harness/`, and `scripts/` paths in this skill live in the Kai install, not the user's project. Resolve them against the first ancestor directory of this SKILL.md that contains a `knowledge/` folder (the Kai plugin root, `~/.claude/kai`, or the kai-cmo-harness repo). `MARKETING.md`, `memory/`, and any output files live in the current project. If a referenced `scripts/` command is not available in this install, say so, skip it, and continue with the file-based guidance — never fabricate its output. ## Objective A client-facing audit of one site in which every finding is traceable to a retrieved artifact, ordered so the reader knows what to fix first and what it costs. The deliverable states its audit mode, carries a health score computed only from observed checks, lists P0 through P3 fixes with pages affected, and names the access or exports that would remove the remaining uncertainty. An audit whose numbers cannot be traced back to a collector run is worse than no audit — it moves budget on invented evidence. ## Done when Work type `audit-report` — floor **E3/C4/O1** (`harness/eco-floors.yaml`). - **E3** — a named human approved the exact delivered file, hash-pinned, and every quantitative claim in it resolves to a collector source in `workspace/seo-audit/`. - **C4** — the Kai Data Provenance Rule is satisfied: collector run before writing, mode declared, a collector source cited for e