Jev MotherF*Cker Rank Me

The rule everything is built on

Code finds, Jev judges, the dashboard shows the probabilities.

Jev never writes prose. It answers narrow typed questions over crawled text and returns choice, score or noul answers with probabilities attached, which the code turns into ranked findings only where the answer is decisive. An LLM-authored finding is the defining failure mode of this category, so it is designed out rather than warned about.

Run it

The whole install is one command. It prints a URL and serves the dashboard and the API on the same port.

1Installed

npx jevseo
The package is scoped; the command is not. npm i -g jevseo puts a plain jev-seo on your PATH.

2Lifecycle

start --detach · status · stop · doctor
stop kills by PID from a pid file, never by process name.

3From a checkout

npm install · npm run dev
Dev is two ports with HMR: Vite 5173 + API 8787. Production is one.

4Optional only

opencode for deep research · uv/Python for the MCP · a GCP service account for Search Console. Without that key the agent is never granted the gsc tool, so it cannot source real traffic or keyword data — the audit still runs, on on-page mining alone.

How an audit runs

Eight stages. The model is never asked anything code can count for itself.

CrawlBreadth-first, bounded by page count, depth and a wall-clock budget. Reads and honours robots.txt, seeds from sitemap.xml. Refuses private, loopback and link-local addresses so a pasted URL cannot reach an internal service.
ExtractTitle, description, H1, headings, opening text, body text, word count, canonical, language, image alt coverage, link counts, noindex, structured data, viewport.
Deterministic checks15 rule checks code can count for itself.
Page judgementsOne request per page carrying every question for that page, fired concurrently behind a bounded pool. One item per request, because packing items has been shown to cost accuracy.
Keyword passCode mines bigram and trigram candidates from titles, headings and body. Jev judges each: is it a real query, is a buyer typing it, what intent, which cluster, and does a page already serve it.
Competitor passEach rival is crawled and judged on the same rubric, so the scorecards are comparable, plus a “worth copying” judgement and the single change that would most improve its AI citability.
ThresholdsThree bands. Decisive answers become findings; the grey zone goes to a “needs a human” pile and is deliberately not acted on.
StreamNewline-delimited JSON, so counters, the wall and the teardown tick as judgements land rather than after the report.

Three primitives, three bands

Both live in one reviewable file rather than being generated per call, because question design and threshold tuning move accuracy more than the choice of model does.

Primitives

choicescorenoul

choice picks one of up to 255 options and returns the full distribution · score is an ordered 2–10 rubric returning the probability-weighted mean · noul returns P(yes) for one proposition, used as a gate.

noul is a real primitive name, not a typo. Renaming it breaks the schema.

Bands

actreviewescalate

Decisive answers become findings. The grey zone is published, not hidden — and widening act to raise apparent coverage is the easiest way to make this product wrong.

What it will not tell you

The limits are part of the product, so they are stated rather than discovered.

No search volume, honestly

Jev carries no index, no volume data and no backlink graph, so there is no way to produce a monthly search count from this state — not approximately, not as an estimate. Keyword opportunity is computed in code from what is actually observable: on-page frequency, whether the term appears in headings, and how many pages carry it.

google-trends was removed rather than registered, because it has no official API and its “relative interest” index is exactly the pseudo-volume this product refuses to put in front of a paying customer.

Variable	Meaning
`JEV_DATA_DIR`	state directory, default `~/.jev-seo`
`PORT`	port, default 8787 (`--port` beats it)
`JEV_ENV_FILE`	explicit `.env` path
`JEV_WEB_DIST`	explicit built-UI path
`JEV_MODEL`	judge model, default `jev-1.13-free`
`ZEN_API_KEY`	only for the rate-limited `jev-1.13`

All mutable state goes in ~/.jev-seo. The install directory is never written to — under npx it is a cache npm garbage-collects.

The four layers