citabilitylisted

# GEO citability Score one page for citability: whether an AI engine can lift a passage from it and use that passage as an answer without rewriting the surrounding context. You do not compute the score. `geo score` does. Your job is to run it, read the envelope, and turn seven numbers into the two or three changes worth making this week. ## Preflight Run this first, once per session: ```bash geo --version ``` Expected: `seomator-geo-audit 1.2.x` or newer. - **Command not found** -> stop and say: "The geo CLI is not installed. Install it with `uv tool install seomator-geo-audit` (or `pipx install seomator-geo-audit`), then run this again." - **Older than 1.2.0** → stop and say: "This skill needs seomator-geo-audit 1.2.0 or newer. Upgrade with `uv tool upgrade seomator-geo-audit`." - **Two `geo` binaries or anything else odd** → run `geo doctor` and relay what it reports. ## Run ```bash geo score <url> --json ``` Add `--allow-private` only when the user is auditing `localhost`, a private IP or a staging host. Add `--no-render` if they want the fast path and do not care about the JavaScript-gap signal. Output is JSON whenever stdout is not a terminal, so `--json` is belt-and-braces rather than required. ## Read the envelope | Field | What it tells you | |---|---| | `ok` | Whether the command produced a valid result. It is **not** a verdict on the site. | | `scores.composite` / `scores.tier` | The number and its label. Always report both. | | `completeness` | How man