GEO Scan — Content Readiness Audit
Run geoptimize against a URL or build directory. The deterministic report is suitable for regression checks; optional Gemini, Copilot, or Claude reviews are experimental and do not predict ranking, indexing, rich results, visibility, or citation.
Workflow
-
Identify the URL, file, or build directory.
-
Run the deterministic scan with machine-readable output:
npx geoptimize scan <target> --json npx geoptimize scan <directory> --dir --json -
Report the deterministic score, methodology version, critical findings, and heuristic limitations.
-
Use
--multi-aionly when the user explicitly asks for a subjective review. Label the result an experimental blend and keep the deterministic score separate. -
Prioritize sourced quantitative claims, unintentional
noindex, malformed or misleading structured data, and reproducible content regressions. -
Suggest
/geo-generateonly for an optional artifact preview. State thatllms.txtis an unscored proposal.
Boundaries
- FAQ content and
llms.txthave no score impact. - A score increase is not evidence of a ranking or citation increase.
- Generated schema must match visible content and current feature documentation.
- If a URL scan fails, use an authorized local build instead of bypassing access controls.
- Always use
--jsonwhen another tool will consume the result.