Every public document.
One map.
What each Rank Sniper page answers, who it is for and what state it describes. Where a document covers something that has not shipped, its row says so.
- Documents indexed
- 34 public pages in 9 groups
- Composite rubric
- v1.0 · 11 scored registry checks
- Pillar layer
- v1.0 · 29 weighted checks
- Check registry
- v1.4-draft — a draft, not a stamped release
- Launch freeze
- Not stamped — pre-launch, so weights may still move, and every change is recorded
- Pillar order
- SEO → AEO → GEO → AIO
- Not published
- Internal rulings, audits and working documents. Every document below is a page on this site.
New to Rank Sniper?
Start with three.
From nothing to a scored report and a reading of it, with no install.
Start here
Read the tutorial first; the scan is its second step.
- TutorialLearning path
The learning path from first scan to monitoring, with what you can do at each step today.
For: Merchants What the no-install scan reads, what it returns, and what it never touches.
For: Merchants · agencies- FAQAnswers
The questions that come up most, each answered against the page that owns the detail.
For: Everyone
The framework,
the method, the terms.
What Rank Sniper measures, how every number is produced, and the vocabulary its reports use.
The four-pillar framework
AIO here means machine readability — whether the record parses and can be acted on. It is not the umbrella definition that treats AIO as all four disciplines at once, and it is not the off-site trust definition.
- The four pillarsFramework
The four disciplines defined, in fixed order, and how each is scored.
For: Merchants · developers Titles, meta descriptions, canonicals, H1s, alt text, sitemap.xml, URLs, product type, tags and Googlebot/Bingbot access.
For: Merchants · developersDescription depth, FAQ markup, list or unit markup in the description, answer-first openings and question-shaped headings.
For: Merchants · developersllms.txt, vendor attribution, quotable claims, freshness, named entities and the 10 AI crawlers checked by name.
For: Merchants · developers- AIO — AI optimisationPillar
Whether an agent can parse and act on the record: attributes, SKUs, offers, price and currency, availability, weight, imagery, schema conflicts.
For: Merchants · developers
Methodology and scoring
Rubric v1.0 for the composite, pillar layer v1.0 for the four pillar scores.
- Scoring rubricMethodology · preview
The composite formula, every weight the public scan uses, the pillar checks with their fix classes, and what is not measured yet.
For: Developers · agencies - How it worksWorkflow
Scan, detect, prioritise, optimise, verify, monitor — who acts at each move and what runs today.
For: Merchants - Crawler indexReference · sourced
Who reads a Shopify store and why, grouped by purpose, and which AI agents the scan checks by name.
For: Developers · merchants - RankSniperBotCrawler identity
Our own crawler: the exact user-agent, the complete list of what it fetches, and the two robots.txt lines that stop it.
For: Store owners · developers
Reference
Terms such as fix class or unscored check link straight to their lexicon entry from every page that uses them.
- LexiconGlossary
Search, structured-data, AI-crawler and Shopify terms defined, each marked as an industry term or a Rank Sniper product term.
For: Everyone - Field guidesGuides
The index of long-form Shopify guides.
For: Merchants · developers - Structured data for ShopifyField guide
Product JSON-LD on a Shopify theme: what is in the raw HTML, what a script adds later, and what the scan reads.
For: Merchants · developers - Shopify product data for AI agentsField guide
The product fields an agent reads — type, vendor, variants, SKUs, weights, options — and where each lives in Shopify.
For: Merchants · developers - Answer-engine readiness for ShopifyField guide
Descriptions, headings and markup an answer engine can quote rather than paraphrase.
For: Merchants · developers - llms.txt for ShopifyField guide
What the file is, why it is a proposal rather than a standard, and how the scan checks it.
For: Merchants · developers - Agentic commerce for ShopifyField guide
AI shopping and agent checkout as the vendors document them, and what a catalogue needs to be read at all.
For: Merchants · developers
Safe-write philosophy.
Shopify architecture.
How the Shopify app is designed to write — automatic, assisted, guided — and which parts of it exist. Nothing is written to any store today.
Architecture
Each row carries the state of the capability it describes.
The check registry, the two scoring layers, the Shopify integration and the designed safe-write contract.
For: Developers · agenciesHQ Merchant Command as designed, and which parts of it run on live store data today.
For: Merchants- AttachmentsAdd-ons · design
Optional modules designed to sit beside the four pillars. None has shipped, and none gates a pillar.
For: Merchants The before-and-after report format, and why none is published until a real store has been fixed and re-scanned.
For: Merchants · agencies
Programmes
Separate programmes with separate enrolments. Agency status creates no referral commission, and an affiliate gets no access to any merchant’s store.
Managing several client stores: what an agency account can see today and what is planned.
For: AgenciesReferring merchants: how affiliates are enrolled, and what is and is not built.
For: AffiliatesSingle sign-on, audit log, data residency and custom weighting, each with its release state.
For: Enterprise buyers
Releases, research
and policies.
What has shipped and when, the writing behind the method, and the terms the site runs on.
Releases
Shopify is the only billing authority for Shopify merchants. Rank Sniper subscriptions and add-ons will be billed through Shopify when the app is available; nothing is charged on ranksniperhq.com.
- ChangelogRecord
Every capability’s state — shipped, beta, planned — the dated releases, the open research questions and the field log.
For: Everyone How tiers are banded by catalogue size, never by pillar. No tier is on sale yet.
For: Merchants- FoundersProgramme
Founder terms are being reconciled. No Founder purchase is available, and a request is recorded, never charged.
For: Early merchants
Research and evidence
The crawler index, the lexicon and the field guides cite vendor documentation beside each external fact, with the evidence class of every source shown.
- BlogArticles
Longer writing on answer engines, AI retrieval and Shopify catalogues.
For: Everyone - ProjectionModel · assumptions stated
The modelling behind agent-traffic projections, with the assumptions written down.
For: Merchants · analysts
Policies
Read before you scan a store that is not yours, or before you write to us.
How to read
any of it.
Two conventions run through every document here.
A version is always stated. The rubric, the pillar layer and the check registry each carry a number, so a score can be traced to the rules in force when it was produced. The registry’s number is still a draft, and is labelled as one.
Unshipped work is labelled as unshipped, in the document itself. Where you see Planned or In development, it is load-bearing: that capability does not run yet.
If two pages on this site contradict each other, that is a defect. Mail hello@ranksniperhq.com with both URLs and we will reconcile them.
