Understand Search. Fix What Matters.

Open-source SEO and AI-search auditor for websites and code repositories.
Finds what is wrong, groups it by root cause and fixes the safe parts in your code — with rollback.

Searvex report overview: health score, issue groups, what was not covered, and the three issues to fix first
_{Unedited capture of a real report (ovokodo.com, 52 pages). English / Türkçe · light / dark / system.}

Quick start

npm install -g searvex-seo

searvex audit https://example.com --open

Or as a Claude Code plugin, no npm install needed:

/plugin marketplace add cihantopac/searvex
/plugin install searvex@searvex

Then run /searvex <url> [path]. Requires Node.js ≥ 20.10. Full reference: docs/cli.md.

How it works

Workflow: Audit, Understand, Prioritize, Fix, Verify, Monitor


Audit	A live site (robots.txt-compliant crawl) or a repository: Next.js, Astro, Nuxt, Laravel, WordPress, static HTML.
Understand	Every finding comes with evidence, an official source and the date that source was checked.
Prioritize	One broken layout on 50 pages is one task, not 50.
Fix	Approve a diff for safe fixes, or hand the rest to your coding agent with a ready-made repair prompt.
Verify & monitor	Re-audit after a change; failed verification rolls back. Regressions show up in the next run and in CI.

From findings to fixes

Issues grouped by root cause, with selection checkboxes

Select what to fix. Issues are grouped by root cause and labelled automatic, agent-assisted or manual.

Editable repair prompt with copy and Markdown download

Generate a repair prompt for Claude Code, Codex or any agent: exact URLs or file:line, evidence, fix and verification. Secrets redacted.

What it checks

Technical SEO — crawlability, indexability, canonicals, redirects, hreflang, metadata, structured data, links, performance and security signals.
Local and staging builds — audit a build as its public site (--site-url) with a pre-launch profile (--pre-launch): test-server findings and deliberate pre-launch states go to a launch checklist instead of the score.
GEO / AI search — AI crawler access by purpose, snippet controls, entity consistency, content clarity.
Repositories — findings with file:line in framework source, plus 12 rule types fixed automatically (dry run → approval → apply → verify → rollback).
Search data, optional and read-only — Search Console (API or CSV export) and Chrome UX Report. Without them, clicks and Core Web Vitals are shown as not measured, never estimated.
Competitors — topic and page-type coverage gaps, labelled as hypotheses.
For pipelines and agents — a versioned report.json with a published JSON Schema (searvex schema), every affected URL per finding, distinct exit codes (unreachable or robots-blocked 4, interrupted 5), --progress ndjson, --max-duration, host and port limits, and searvex prompt for repair prompts outside the browser.

Evidence, not claims

Status: v1.3.0 (release notes, changelog).

91 rules, each tied to an official source: 72 verified, 17 heuristic, 2 reported as unmeasurable. searvex rules show <id>
Tested with unit, integration, browser and end-to-end runs; CI on Linux, macOS and Windows with Node 20, 22 and 24 (quality report).
Validated on 13 public sites and 9 repositories; live Search Console and CrUX values matched the official exports.
Safe by default — read-only, SSRF protection, robots.txt honoured, secret files never read, every change journaled with byte-for-byte rollback.

Searvex never promises rankings, traffic or AI citations. The health score is Searvex's own summary, not a search-engine metric. See limitations.

Documentation

CLI reference · Architecture · Knowledge base · Security · Privacy

Related tools

Independent open-source tools by the same author:

Relivaro — software reliability, security and release readiness.
Jourilo — UX and conversion engineering in real browser journeys.
Markilo — brand identity and vector design for Claude Code (made the Searvex identity).

Contributing & license

Rules, framework adapters and fixtures are the most valuable contributions; every rule needs an official source and a test fixture (CONTRIBUTING.md). Report vulnerabilities via SECURITY.md.

Apache-2.0