jev-seo
Free Rust CLI SEO/GEO auditor, no subscription needed
125 followers
Free Rust CLI SEO/GEO auditor, no subscription needed
125 followers
Semrush and Ahrefs cost $130+/month for work that's mostly deterministic: crawling a site, checking meta tags, validating schema, checking what AI crawlers can see. jev-seo does that in a free Rust CLI. No subscription, no paid API keys needed for the core checks (crawl, audit, schema, robots, sitemap). Optional Jev-powered semantic scoring (intent classification, GEO/AI-citation scoring) needs a free API key. Also ships as an MCP server for coding agents. cargo install jev-seo
Update: v0.1.2 is out. Three fixes in this release came directly from comments on this thread, basic auth support, a hreflang cluster check, and soft-404 detection tuned against a real production pattern someone described. Also added real AI-citation tracking, asks a model your buyer query and tells you who it names, using the connected agent's own model by default so it stays free.
Appreciate everyone who actually dug into the code instead of just upvoting. This is a better tool because of it.
@priyankamandal thanx
the "no subscription for the deterministic checks" framing is honest and rare - most tools in this space bundle the boring crawl/schema/robots stuff with the paid layer just because they can. one thing I didn't see addressed: does it handle sites that are behind basic auth or still on a staging subdomain? that's usually exactly when a team wants an SEO/AI-crawler audit, before the site is public, and most hosted auditors can't touch it since they need a public URL to craw
@galdayan good catch, staging alone works fine, it's basic auth that's missing rn. no --user/--pass flag yet to get past it. you're right that's exactly when teams want this, before the site's public. adding it, not on the roadmap doc yet but going in
@akashpriyadarshii appreciate the fast turnaround, most maintainers would've just filed that away. saw the thread with Anton below too, the raw-html-only crawl point is a real gap for anyone doing client-rendered pages, good that it's an honest "same blind spot" answer instead of overselling it
appreciate that. --user/--pass landed for the basic auth gap, that one's actually done now.
the raw-vs-rendered diff anton asked for is still open, added a paid firecrawl fetch-mode swap since then but that's not the same thing, still raw html by default, no diff between the two. fixing that properly next weekend, not before