COMMUNITY OBSERVEDMetric claims: AUTHOR REPORTEDSOURCE AUDITED📈 Jev for SEO

Borja Fatjo Jev for SEO Workflow

An internal-link analysis test: the author says 586 pages took 45.1 seconds and produced 584 link suggestions, and compares Claude's results and cost.

From the original post

Jev is WILD for SEO audit 🤯

in 45.1 seconds it read all 586 pages on my site and rebuilt the internal link map. 584 links placed, 139 pages it refused to link because nothing honestly fit. total cost $0.21.

Claude Opus 5, same 586 pages, same clock, got through 21 of them and spent $1.43.

per page that is ~190x cheaper. the full Opus pass would have run $43.

internal linking is the perfect Jev job. it is not writing, it is 8,790 yes/no calls: does this page have a real reason to link to that one, and is there anchor text already sitting in the copy. that is a classification problem, and we have been paying frontier prices to do it one page at a time.

what you are watching: left column is Jev, right is Opus, same queue, same rubric. the run stops the moment Jev finishes so Opus stops burning tokens.

coming soon to @distribb_io + connector + gpt plugin

— borja

How Jev fits in the loop

  1. Agent collects runtime context or input state from external sources.
  2. Bounded decision options are formatted into Jev System One questions.
  3. Jev scores each candidate option and returns a probability for it.
  4. Deterministic code executes the selected action or routes to specialized models.

How to reproduce

  1. Read the author's original post on X at https://x.com/borjafat/status/2101018783976722479.
  2. Inspect the described workflow architecture and bounded decision points.
  3. Test Jev System One decision queries against the provided task context.

Why this build matters

Demonstrates real-world Jev for SEO experimentation by @borjafat with verified community reach of 822.2k views.

Limitations

  • Implementation details are based on the author's public post on X.
  • Performance figures and benchmarks are author-reported community claims.
  • Production deployments may require custom calibration and policy thresholds.

Patterns