jev-seo / site
llms.txt100 starsChanged 9 days agoMITView on GitHub
FOSS zero-cost SEO & GEO search radar for developers and AI agents. Rust CLI + MCP. No subscriptions, no credit card. Reach for jev-seo when you need to: Do not use jev-seo for paid keyword data or backlink graphs. It scrapes free endpoints, audits local files, and crawls live sites with robots honored. CLI: cargo install jev-seo, then jev-seo --help. MCP: run jev-seo mcp (or npx -y @akashpriyadarshii/jev-seo) for a stdio JSON-RPC 2.0 server with 15 tools (seo_cite_check, seo_gap, seo_audit,…
- Installs packages
The file
We split this llms.txt into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Check robots.txt for AI crawler permissions (GPTBot, ClaudeBot, PerplexityBot, Google-Extended): jev-seo robots example.com
- Very specific: line 23
Do not use jev-seo for paid keyword data or backlink graphs.
≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
# jev-seo > FOSS zero-cost SEO & GEO search radar for developers and AI agents. Rust CLI + MCP. No subscriptions, no credit card. - Homepage: https://jevseo.vercel.app/ - Real audit field report: https://jevseo.vercel.app/real-audit.html - Repo: https://github.com/AkashPriyadarshii/jev-seo - Sitemap: https://jevseo.vercel.app/sitemap.xml ## When to use this Reach for jev-seo when you need to: - Audit markdown or HTML files for on-page SEO issues, thin pages, title collisions, orphan pages, or AI slop: `jev-seo audit docs/` - Validate Schema.org JSON-LD markup: `jev-seo schema index.html` - Check robots.txt for AI crawler permissions (GPTBot, ClaudeBot, PerplexityBot, Google-Extended): `jev-seo robots example.com` - Score content for AI citation likelihood (GEO 1-10): `jev-seo geo page.md --query "your topic"` - Inspect live SERP competitors and rerank by relevance: `jev-seo query "your keyword"` - Generate a content brief from live competitors: `jev-seo brief "your topic"` - Track domain rank over time: `jev-seo rank --domain example.com --query "your keyword"` - Inspect XML sitemaps: `jev-seo sitemap https://example.com/sitemap.xml` Do not use jev-seo for paid keyword data or backlink graphs. It scrapes free endpoints, audits local files, and crawls live sites with robots honored. ## Call it CLI: `cargo install jev-seo`, then `jev-seo --help`. MCP: run `jev-seo mcp` (or `npx -y @akashpriyadarshii/jev-seo`) for a stdio JSON-RPC 2.0 server with 15 tools (seo_cite_check, seo_gap, seo_audit, seo_geo, seo_crawl, seo_llms, seo_brief, seo_extract, seo_explain, seo_report, seo_schema, seo_robots, seo_sitemap, seo_keywords, seo_serp_inspect).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.