seolisted

# SEO Content Audit ## Phase 0: Grounding Read `${CLAUDE_PLUGIN_ROOT}/references/grounding.md` and load any `_grounding/` folder it finds. Client documentation outranks every default in this skill, and any claim rules it contains bind the output. Name the loaded files at the top of what you produce. Grounding supplies target markets and languages, which decide whether hreflang and localized metadata are findings or non-issues. Also read `${CLAUDE_PLUGIN_ROOT}/references/output-location.md`. Normalize the target URL to its exact non-`www` domain and resolve today's output path now: ``` python "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_audit_output.py" --purpose SEO-AUDIT --scope <domain> --extension md ``` Use `python3` on macOS/Linux. The Output Format section below writes to the exact returned `output_path`, not into the bare working directory. Then resolve optional report metadata from the same working directory: ``` python "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_report_metadata.py" --toolkit "Market Context Kit" --host <exact active host> --provider <exact active LLM provider> --model <exact active model id> ``` Never guess a runtime value. Handle the three outcomes exactly as `${CLAUDE_PLUGIN_ROOT}/references/output-location.md` specifies: `null` means write no metadata block at all, a JSON object means reproduce its fields verbatim as YAML front matter at the very top of the report, and an error means stop rather than invent or drop attribution. Read `${CLAUDE_PLUGI