// others monitor · we fix
MIT CLI for crawler access and extractability — not a citation tracker. 12 dimensions aeorank-cli@0.1.1 actually scores, then the 8 files it writes. Profound, Peec, Otterly, Scrunch, and Athena watch mentions. We fix upstream readability. The GitHub Action can fail the PR if GPTBot is blocked.
No account · copy the command above or see CLI docs · hosted app is experimental (dev)
// live scan
Same shape as an aeorank-cli@0.1.1 run — 12 dimensions, then the 8 files. Illustrative stream, not a live scan of your site. No LLM guesswork.
Every check is a pure function of HTML, headers, and files. Tools that prompt an LLM to evaluate your site give a different score every run. AEOrank gives the same score every run — exactly what you want in CI.
assert.equal(scan(A), scan(A)) No proprietary black-box score. Each of the 12 dimensions is a deterministic check you can read in the repo. No vendor can change your score by changing their model.
packages/core/src/checks/*.ts Other tools monitor — they tell you you're invisible and send a dashboard. AEOrank hands you the exact 8 files the CLI writes, ready to drop into your site root. One command, not a citation promise.
./dist/llms.txt · ./dist/schema.json · … // anatomy of a score
Your AEO score is a weighted sum of 12 dimensions aeorank-cli@0.1.1 scores (high / medium / low). Not a citation rank. The 36-row catalog in the repo is archived until a published CLI matches it.
llms.txt · schema.org markup · content structure
aeorank-cli@0.1.1 AI crawler access · answer-first · FAQ & speakable · E-E-A-T · meta descriptions · citation anchors
aeorank-cli@0.1.1 sitemap · HTTPS & redirects · page freshness
aeorank-cli@0.1.1 // 8 generated files
Every other AEO tool monitors — they hand you a dashboard and a todo list. AEOrank writes the eight files the published CLI generates (no ai.txt, answers.json, or report.html stubs). Click a file to read a sample.
Root-level policy + site map for LLMs. The emerging spec.
# Your Site > Agent-readable map of this site. Not a citation guarantee. ## Core pages - [Docs](/docs.md): developer reference - [Pricing](/pricing.md): plans and costs - [Blog](/blog.md): recent writing ## Optional - [llms-full.txt](/llms-full.txt): extended extract
JSON-LD structured data for every significant page.
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "Your Site",
"applicationCategory": "DeveloperApplication",
"operatingSystem": "Web",
"offers": { "@type": "Offer", "price": "0", "priceCurrency": "USD" },
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"reviewCount": "412"
}
} Full-context version with Q&A pairs and entity disambiguation.
# Your Site — full context > Extended extract for agents that want more than the llms.txt map. ## What is this product? This product scores AI visibility and writes the files crawlers read. ## How do I scan a site? npx aeorank-cli@0.1.1 scan https://your-site.com
Markdown context file for Claude and other coding agents.
# Your Site - Platform: detected from HTML (Webflow, Next.js, WordPress, …) - Purpose: agent-docs hygiene for coding assistants ## Commands - npx aeorank-cli@0.1.1 scan https://your-site.com
AI crawler rules to merge into robots.txt — GPTBot allowed.
# Append to robots.txt User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: /
FAQPage + speakable markup you can drop into a page.
<section> <h2>What does AEOrank generate?</h2> <p>Eight files: llms.txt, llms-full.txt, CLAUDE.md, schema.json, robots-patch.txt, faq-blocks.html, citation-anchors.html, sitemap-ai.xml.</p> </section>
H2/H3 markup with id attributes for deep links.
<h2 id="what-is-aeo">What is AEO?</h2> <p>AI Engine Optimization — structure a site so agents can extract answers.</p>
AI-oriented sitemap generated from the pages we scanned.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://your-site.com/</loc>
<lastmod>2026-09-03</lastmod>
</url>
</urlset> @aeorank/next, @aeorank/astro, @aeorank/nuxt, and 8 more. Drop one line of config and all 8 files are served at the correct route on build — no vendor dashboard to babysit.
Every file is generated locally. No upload, no telemetry, no required account, no API key. The entire toolchain is MIT and lives in your repo — if we vanished tomorrow, you'd still be fine.
Same HTML in → same files out. Tests pin output so a diff in your PR check means something actually changed — not just that an LLM was in a different mood.
// others monitor · we fix
They are closed monitoring SaaS. AEOrank is MIT, CLI/CI-first, and writes the 8 files aeorank-cli@0.1.1 actually generates after scoring 12 dimensions. We do not promise citations. The evidenced lever is crawler access plus extractability.
| AEOrank | Profound · Peec · Otterly · Scrunch · Athena | |
|---|---|---|
| What they sell | Score + generate the 8 fix files | Brand-mention / prompt dashboards |
| License | MIT · fork and self-host | Closed source |
| How you run it | CLI, GitHub Action, GitHub App (hosted app is experimental) | Vendor dashboard |
| Scoring | 12 dimensions (aeorank-cli@0.1.1) | LLM prompt tracking (varies by run) |
| CI | Action: fail the PR if GPTBot is blocked | None |
| Output | 8 files the published CLI writes | Mention reports — no fix files |
| Citation guarantee | None — crawler access + extractability | None — they monitor mentions after the fact |
| Price | CLI free · Pro $29/mo | Typically $89–$499/mo |
// open source by default
“Your AI visibility stack shouldn't live inside a vendor dashboard you can't read, can't fork, and can't afford."
Every AEO monitoring tool we looked at is closed-source SaaS — Profound, Peec, Otterly, Scrunch, Athena, typically $89–$499/mo. AEOrank is different on purpose. The core scanner, 11 framework plugins, the GitHub App, the GitHub Action, and every one of the 8 files we generate — all MIT licensed, all forkable, all self-hostable. You can stand the entire thing up inside your own infra in an afternoon.
The hosted app at app.aeorank.dev is experimental (Clerk Development) convenience — never because the tool needs it to work, and never the primary path to a score. If we vanished tomorrow, your CI would keep scoring, your files would keep regenerating, and your team would keep shipping. Try getting that commitment from a venture-backed dashboard.
MIT
TypeScript
no
zero
Early days. If you star it, you actually move the needle.
Loading contributors from github.com…
// three ways in
Same scorer under all three. Same 12 dimensions. Same 8 generated files. Pick the surface closest to where you already ship. The GitHub Action is the CI gate that can fail a PR if GPTBot is blocked.
Zero install. Zero account. Zero API key. 12 dimensions, then the 8 files aeorank-cli@0.1.1 writes. To fail a PR if GPTBot is blocked, use the GitHub Action — that flag is not on npm 0.1.1.
# one-off audit on any site $ npx aeorank-cli@0.1.1 scan https://your-site.com AEO Score: 31/100 (F) 12 dimensions · 8 generated files ✔ wrote aeorank-output/llms.txt ✔ wrote aeorank-output/schema.json ✔ wrote aeorank-output/robots-patch.txt ✔ wrote aeorank-output/CLAUDE.md … (+ 4 more)
One click. Zero YAML. Every pull request gets a Check Run that fails if GPTBot is blocked. Score thresholds (fail-below) are Action-only — the App does not support them yet.
# Flow
1. Install AEOrank on your repo
github.com/apps/aeorank
2. Open any PR
→ Check Run appears automatically
3. Check summary example:
━━━━━━━━━━━━━━━━━━━━━━━━
AEORANK · PR #419
━━━━━━━━━━━━━━━━━━━━━━━━
score 67 → 72 (+5) grade C → B
✔ llms.txt restored
✔ speakable markup added
✗ author.schema still missing Pin a version, set fail-on-crawler-block (fail the PR if GPTBot is blocked) and an optional fail-below score. AEO as code — the same way tests and coverage already work.
# .github/workflows/aeorank.yml
name: aeorank
on: [pull_request, push]
jobs:
score:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: vinpatel/aeorank-action@v1
with:
url: https://${{ github.event.pull_request.head.ref }}.preview.example.com
fail-below: 70
fail-on-crawler-block: true # what this adds to your repo + .github/workflows/aeorank.yml # CLI writes (when you generate files): + aeorank-output/llms.txt + aeorank-output/schema.json + aeorank-output/robots-patch.txt + aeorank-output/CLAUDE.md
// AI visibility scoreboard
Public snapshot from aeorank-cli — 12 dimensions you can run today. Below is the current top 10 from that board. No LLM evals, no inflated ranks, no citation claims.
| # | company | industry | score | grade | distribution |
|---|---|---|---|---|---|
| 01 | PlanetScale | devtools | 71 /100 | B | |
| 02 | Neon | devtools | 69 /100 | C | |
| 03 | Aiven | infra | 65 /100 | C | |
| 04 | Runway | ai / ml | 64 /100 | C | |
| 05 | Segment | martech | 64 /100 | C | |
| 06 | Amplitude | martech | 63 /100 | C | |
| 07 | ClickUp | saas | 60 /100 | C | |
| 08 | MongoDB | infra | 60 /100 | C | |
| 09 | Klaviyo | e-commerce | 59 /100 | C | |
| 10 | Braze | martech | 58 /100 | C |
// pricing
Same CLI on every plan. We don't gate the 12 dimensions, the 8 generated files, or local scans. You pay for more sites and hosted scans. Pro is $29; closed monitoring dashboards typically run $89–$499/mo. The working free path is npx aeorank-cli@0.1.1 scan <url> — hosted signup is experimental (dev) and not required.
starter plan
CLI is free. No credit card. No account.
most teams plan
More hosted scans. Same CLI. Same 8 fix files.
agency plan
50 client sites. Same 8 files.
$29/mo
score · generate · CI
closed
monitor · closed
closed
monitor · closed
closed
monitor · closed
closed
monitor · closed
closed
monitor · closed
// what an AI crawler sees vs. what you read
Left: the JSON-LD we emit on this page, verbatim — exactly what an AI crawler extracts. Right: the same answers for human eyes. We practice what we score.
Alone, no. AEOrank scores 12 dimensions on aeorank-cli@0.1.1 — llms.txt, schema, crawler access, structure, answer-first, FAQ/speakable, E-E-A-T, meta descriptions, citation anchors, sitemap, HTTPS, freshness. Then it writes 8 fix files. The GitHub Action can fail a PR if GPTBot is blocked; that flag is not on npm 0.1.1. llms.txt is agent-docs hygiene, not a citation guarantee. We do not promise to get you cited.
Every check is a pure function of HTML, headers, and file presence — no LLM calls, no randomness. Scan the same site twice, get the same score. That's how CI works. Tools that prompt GPT-4 to rate your site give you a different number on Tuesday than they did on Monday; you cannot fail a PR on that.
Yes, and this is unusual in the category. Profound, Scrunch, Otterly, Peec, and AthenaHQ are all closed-source SaaS — the scoring logic is a black box on someone else's server. AEOrank's scanner core, all 11 framework plugins, the GitHub App, the GitHub Action, and the file generators are under MIT. You can fork it, audit the checks, and self-host the entire stack.
Classical SEO tools check ranking signals for Google's blue-link results. AEOrank scores crawler access and extractability (12 dimensions on aeorank-cli@0.1.1) and writes the 8 files the CLI generates. Semrush's AI add-on and Ahrefs' Brand Radar report on visibility; neither writes those files.
They monitor: they run prompts through LLMs and tell you what AI said about your brand this week. AEOrank fixes upstream: 12 dimensions plus the 8 files aeorank-cli@0.1.1 writes. Typical monitoring plans run $89–$499/mo; AEOrank Pro is $29 and the CLI is free. Complements, not clones. Agency audits (including Mindtrades) still go crawler-gate first, then CLI, then human-reviewed fixes.
AEOrank is CLI/CI-first. The GitHub Action (vinpatel/aeorank-action) can fail the PR if GPTBot is blocked (fail-on-crawler-block). That flag is not on aeorank-cli@0.1.1. The GitHub App does not support fail-below yet (coming soon). Only claim merge-blocking for the gates that exist.
No. The scanner is deterministic and never calls an external model. The CLI runs fully locally. The hosted app (experimental / Clerk Development) fetches your public URL over HTTPS exactly like any other crawler — it is not required to get a score.
Crawler access is scored for GPTBot, ClaudeBot, PerplexityBot, and Google-Extended. That is technical readiness, not a citation tracker, and not a promise we add a new bot within a week.