Everything,
written down.
The full index of what Rank Sniper publishes about itself — the method, the scoring, the write contract and the record. If a claim is made anywhere on this site, the document behind it is on this page.
New here? Read the tutorial first — it is four steps and the first three need no install. Everything below is reference material you can come back to.
Rubric v1.0 · 11 scored criteria · pillar spec v1.0 · check registry v1.4-draft · pillar order SEO → AEO → GEO → AIO
Start here
| Document | What it answers |
|---|---|
| Tutorial | Four steps from an empty browser tab to your first scored report and first fix. |
| How it works | The daily loop — scan, score, fix, publish — and why it is a loop rather than an audit. |
| Free scan | What the no-install scan reads, what it returns, and what it never touches. |
| FAQ | The questions that come up most, each answered against a page that owns the detail. |
Method and scoring
| Document | What it answers |
|---|---|
| Scoring rubric | Every scored criterion, its weight, and the reasoning behind the weight. |
| Pillar specification | The four disciplines defined, with the boundary between them stated rather than implied. |
| SEO — classical search | Crawlability, indexation and the signals classical search engines still decide on. |
| AEO — answer engines | Answer content, llms.txt and what an engine needs in order to quote you correctly. |
| GEO — generative engines | Named-agent access and the 10 AI crawlers checked by name against robots.txt. |
| AIO — agent transactability | The structured facts an autonomous buyer needs before it can transact on your catalogue. |
| Crawler index | The AI crawlers we check for, who operates them, and what a block actually costs. |
| Our own crawler | The user-agent Rank Sniper identifies itself with, for anyone who meets it in a log. |
The product
| Document | What it answers |
|---|---|
| Write contract | The five moves, the three scopes, and how the non-destructive guarantee is enforced in code. |
| Command Center | The dashboard: composite score, pillar breakdown, coverage and the impact-ordered task list. |
| Attachments | Optional modules that sit beside the four pillars — none of them gate a pillar. |
| Shot reports | The before-and-after report format, and what is and is not proven in it today. |
| Pricing | How tiers are banded by catalogue size, and why never by discipline. |
| Projection | The modelling behind agent-traffic projections, with the assumptions written down. |
Record and legal
| Document | What it answers |
|---|---|
| Changelog | What shipped, what is being built, and what is deliberately not claimed yet. |
| Blog | Longer writing on answer-engine optimisation and what is changing in AI retrieval. |
| Privacy | What is collected today, what is stored, and what is still outstanding. |
| Terms | The terms as they stand, including the Founders Protocol signup terms. |
| Contact | Reach a human. Support, review questions and data requests all land here. |
How to read any of it
Two conventions run through all of these documents. The first is that a version is always stated: a rubric, a pillar specification and a check registry each carry a number, so a score can be traced to the rules that were in force when it was produced. The second is that unshipped work is labelled as unshipped, in the document itself, rather than described in a present tense it has not earned. Where you see a “planned” or “not claimed yet” marker, it is load-bearing.
If something on this site contradicts something else on it, that is a defect and we want it. Mail hello@ranksniperhq.com with the two URLs and we will reconcile them.
