GEO technical readinessCLI + agent skill

Find the issue.Trace it to source.Prove the fix.

geopilot audits any website for the technical conditions crawlers and AI search systems document — robots, sitemaps, indexability, canonicals, metadata, structured data — shows the evidence, maps it to the line that caused it, and verifies the change it proposes.

npx geopilot scan https://your.site
No accounts · no telemetry · no model callsnpm 0.0.2GitHubApache-2.0

Honest by contract. Technical readiness only. GEO does not measure or predict citations, rankings, traffic or inclusion in any AI or search product.

The loop

Observable finding to verified fix, with nothing assumed in between.

URL scans and a 0–100 score are commodity. The difference is the chain: evidence, a source mapping you can check, the smallest safe patch, and verification that never overstates what it proved.

01

Observe

Fetch the site the way a crawler does: robots.txt first, sitemaps, server HTML, bounded and SSRF-guarded.

02

Evidence

Every finding carries the URL, header, selector or line that shows it, capped and redacted.

03

Trace

On Next.js App Router and static HTML, map the value to the literal that produced it — or say why not.

04

Patch

Propose the smallest closed-list change. Safe fixes apply with --apply; guarded ones need their id.

05

Prove

Re-check the rule condition, not the fingerprint. V4 counts only on a server GEO started after the write.

Four outputs, never blended

A score that refuses to guess.

A repository-only scan of a Next.js app finds and traces problems but reports insufficient evidence rather than a readiness number: its HTTP sub-checks cannot run, and a rule never passes on part of its own checks.

Readiness

Weighted prevalence of failures in direct evidence. Inferred and agent observations never enter it.

Coverage

How much of what applies was assessed directly. Below 50%, no readiness number is shown.

Confidence

The direct share of what was evaluated. Repo-only inferences lower it, visibly.

Scope

Exactly which rule and subject pairs were checked. Change it, and numeric deltas are suppressed.

Every number in the docs is recomputed from executable fixtures. See the worked examples →

Broad reach, graduated trust

Every stack gets a URL audit. Source claims are earned.

A framework is not “supported” because it can be scanned by URL or read by an agent. Each output names the tier that actually applied.

TierCapabilityAvailable onWhat it may claim
T0Universal URLAny web stackObserved URL findings. No source claims.
T1Generic repositoryAny readable repoHints and candidate files only. No automatic patch.
T2Verified source mappingNext.js App Router, static HTMLFile and line, when the evidence meets the bar.
T3Deterministic remediationNext.js App Router, static HTMLFive closed-list fixes, approvals, snapshots, rollback.
AgentContextual investigationAny repository your coding agent can readRecommendations and hypotheses, labelled agent-suggested. Never engine provenance.
Two independent experiences

Useful without AI. Better with your agent.

New to GEO? Install the plugin and run a scan. Your agent checks your code against every rule, shows you what to fix first, and fixes it with your approval. The CLI measures your running site when you want proof.

  • Claude Code/plugin install geopilot --marketplace moelzanaty3/geopilotSupported
  • GitHub Copilot CLIcopilot plugin marketplace add moelzanaty3/geopilotSupported
  • OpenCodenpx geopilot agent install --host opencodeSupported
  • OpenAI Codexcodex plugin marketplace add moelzanaty3/geopilotSupported

Read the plugin guide →

In our published benchmark on sample projects, geopilot and a plain prompt found the same planted bugs. On the projects kept back during tuning, geopilot raised no false alarms against 1.56 per report, and far fewer wrong ideas. A plain prompt raised slightly more useful ideas, and cost about half as much.

The CLI, no model involved

Crawl any site, run deterministic rules, explain them, trace source on supported frameworks, apply approved fixes, verify outcomes, cache runs. It never calls an LLM, ships no provider SDK and needs no API key.

The agent plugins, your model

Your agent reads your code on any framework with no install, gives you a code score and the fixes to do first, explains them in plain words, and applies what you approve.

One command to the first result.

Point it at a URL, a repository, or both. Nothing is written outside .geo/ until you approve it.

npx geopilot scan . --url http://127.0.0.1:3000