geo-auditlisted

# geo-audit Audit a live website's readiness for AI search (GEO) and technical SEO using the `findable-audit` CLI (139 checks across 8 families), then turn the raw report into a prioritized, actionable fix plan. ## Step 1: Run the audit ```bash npx findable-audit <url> --json ``` - The URL scheme is optional; bare domains are assumed `https://`. - By default two report files are also written to the current directory (`<host>-<date>.md` and a self-contained printable `<host>-<date>.html`). Use `--no-report` to suppress them, or `--report <file>` (repeatable) to pick names and formats — extension decides: `.md`, `.html`, `.json`, `.sarif` (GitHub code scanning), `.xml` (JUnit, for GitLab CI / Jenkins), `.svg` (status badge for a README). Useful options: - `--max-pages <n>` (default `10`, `1` = homepage only): audits the homepage plus up to `n-1` same-origin pages discovered from the sitemap (falling back to homepage links); audited paths are listed in `sampledPages`. - `--min-score <n>` (default `60`): only affects the exit code, not the report. - `--cwv` (+ `--psi-key <key>`, `--psi-strategy <mobile|desktop>`): opts into Core Web Vitals via one PageSpeed Insights call (~15–30 s). Without it the `cwv-*` / `lab-*` checks report `skip`. The keyless endpoint is rate-limited, so pass a PSI key when the user has one. - `--indexnow-key <key>`: lets the IndexNow check verify the key file. - `--user-agent <ua>` (e.g. `"GPTBot/1.0"`): test UA-based blocking. -