Field guides
for Shopify catalogues.
Five evergreen references on how search engines, answer engines, generative engines and AI agents read a Shopify store — each tied to the checks Rank Sniper runs, each citing the documentation it relies on. Reference, not news.
Five references.
One per hard question.
Each guide takes one question a Shopify merchant cannot answer from the admin — what their structured data says, which facts an agent needs, whether a page is quotable, what llms.txt is worth, and what AI shopping programmes ask of a catalogue.
One question per guide.
Shopify structured data
- SEO
- AIO
Where the Product, Offer and ProductGroup JSON-LD on a Shopify product page comes from, what Google’s merchant-listing and variant documentation asks of it, how theme and app markup collide, and exactly how Rank Sniper’s scan reads it.
Read the guide →Product data for AI agents
- GEO
- AIO
The identity, attribute and transaction fields an AI shopping agent needs from a Shopify catalogue — SKU, barcode and GTIN, variants and options, product type, vendor, tags, metafields, weight and availability — where each lives in Shopify, and which facts only you can supply.
Read the guide →Answer-engine readiness
- SEO
- AEO
How to make a Shopify product page quotable: answer-first descriptions, numbers with units, lists and question-shaped headings, and honest FAQ markup — plus the snippet controls Google documents for AI Overviews and AI Mode, and how the AEO pillar scores it.
Read the guide →llms.txt for Shopify
- GEO
What the llms.txt proposal is, what no search or AI vendor has committed to doing with it, why Rank Sniper still checks for it in the GEO pillar, how to write one for a Shopify catalogue, and the HTML page answering 200 that the scan refuses to count.
Read the guide →Agentic commerce for Shopify
- GEO
- AIO
The AI shopping programmes and protocols a Shopify merchant meets today — Shopify’s Agentic Storefronts, OpenAI’s product feed and checkout specifications, ACP and Google’s UCP — each as its owner documents it, what every one of them needs from your catalogue, and what Rank Sniper checks.
Read the guide →The lexicon
Every term the guides use — from JSON-LD and ProductGroup to control tokens and transactability — defined once, with Shopify specifics and sources.
Open the lexicon →Reference pages,
not field notes.
The journal and the field guides cover some of the same ground. They are built for different jobs.
The journal is dated field notes: a story, an argument and an audit you can run in fifteen minutes, written on a given day. The field guides are the reference layer underneath. Each is written to be returned to — organised by question, with an on-page table of contents, the exact checks Rank Sniper runs for its subject, and a full list of sources. Where a journal post already tells a story well, the guide links to it rather than retelling it.
Three rules hold on every guide:
- External facts cite their owner. What Google, OpenAI, Shopify or anyone else requires or offers is stated from their own documentation, dated, and listed in the guide’s sources. Where a fact could only be found in a news report, it is worded as a report; where it could not be confirmed at all, the guide says so.
- Rank Sniper numbers come from code. Every weight, count and check label is read from the scoring modules, so a guide cannot disagree with the methodology.
- Availability comes from one table. Anything Rank Sniper does or will do carries its release state, from the same table every page reads.
Guides are re-reviewed when their sources change; each shows its publication and review dates. The terms they use are defined in the lexicon, and the four disciplines they are organised by are set out on the pillars page.
Guide, pillar,
concept, check.
How each guide connects to the four pillars, to the lexicon and to what Rank Sniper measures today.
| Pillars | Key concepts | What Rank Sniper checks | |
|---|---|---|---|
| FG-01 · Shopify structured data | SEO · AIO | Structured data, JSON-LD, schema.org, Product schema | Variant-level offers (12 of 108); Price with priceCurrency (12 of 108); Availability in schema (12 of 108); Schema conflict detection (8 of 108) |
| FG-02 · Product data for AI agents | GEO · AIO | SKU, GTIN, Variant, Handle | SKU coverage (14 of 108); Structured attributes (16 of 108); Shipping weight (10 of 108); Real variant options (8 of 108); Vendor and provenance attribution (16 of 82); Entity consistency (8 of 108) |
| FG-03 · Answer-engine readiness | SEO · AEO | AEO, Answer engine, FAQ schema, Citation | Description depth (20 of 86); FAQPage / HowTo schema (20 of 86); List and table density (16 of 86); Answer-first structure (16 of 86); Question-shaped headings (14 of 86) |
| FG-04 · llms.txt for Shopify | GEO | llms.txt, GEO, Generative engine, Machine readability | llms.txt presence and quality (20 of 82) |
| FG-05 · Agentic commerce for Shopify | GEO · AIO | Agentic commerce, AI shopping, Product feed, User-initiated fetch | Variant-level offers (12 of 108); Price with priceCurrency (12 of 108); Availability in schema (12 of 108); SKU coverage (14 of 108); Shipping weight (10 of 108) |
Read, then
check your own store.
The free scan reads the same storefront signals the guides describe, from the raw response, and scores all four pillars.
