Cassian™ Docs
Features

LLM Readiness

How Cassian scores your store's readiness for AI-powered shopping — Layer 5 of the Cassian Score™.

LLM Readiness

LLM Readiness is the fifth layer of your Cassian Score™, weighted at 10%. It measures how well your store is positioned for the next wave of e-commerce discovery: AI-powered shopping assistants.

The way customers find and evaluate products is changing. AI systems embedded in search engines, browsers, and voice assistants are increasingly answering shopping queries — "What's a good running shoe for flat feet under $150?" — and returning specific product recommendations rather than a list of links. Stores that are structured for AI readability appear in these results. Stores that aren't, don't.

LLM Readiness is the lowest-weighted layer, but it's often where the fastest wins are. Many of the fixes are one-time tasks that take less than an hour.


What Cassian checks

llms.txt presence

llms.txt is an emerging standard — a plain text file placed at the root of your store (e.g., yourstore.com/llms.txt) that tells AI systems what your store sells, who you are, and how to interpret your catalogue.

Think of it like robots.txt, but for AI systems rather than search engine crawlers. robots.txt tells crawlers what to index. llms.txt tells AI assistants how to represent your store in response to customer queries.

A missing llms.txt is the single most commonly flagged LLM Readiness issue — and one of the quickest to fix.

What goes in an llms.txt file:

  • Your brand name and a brief description of what your store sells
  • Your primary product categories
  • Your brand values and differentiators (what makes your store the right choice)
  • Key information about your shipping, returns, and customer service
  • Any important facts that AI systems should know when describing your store

Example format:

# Your Store Name

Your Store Name sells [category] products for [audience]. We specialise in [differentiator].

## What we sell
- Product category one: [brief description]
- Product category two: [brief description]

## Key facts
- Ships to: [countries/regions]
- Returns policy: [summary]
- Founded: [year]

## Contact
- Support: [email or URL]

Where to add in Shopify: The most straightforward method is to add a new page in your Shopify theme and configure a custom route. Alternatively, use a Shopify Files app that allows placing static files at the store root. See the Shopify Theme documentation for your specific theme.

Adding llms.txt also improves your Technical Health score — it's one of the checks in that layer too. Creating it is a cross-layer win.

Structured data completeness

Structured data (schema markup) is the primary way AI systems extract machine-readable information from web pages. The more complete and accurate your schema, the more reliably AI systems can represent your products.

Cassian evaluates the breadth and accuracy of your schema markup across:

  • Product schema — Is it present? Does it include name, description, image, price, availability, brand, SKU? The more attributes present, the better.
  • Offer schema — Is pricing data (price, currency, availability) correctly marked up within the Product schema?
  • Review/AggregateRating schema — If you have product reviews, are they marked up so AI systems can reference them?
  • FAQ schema — On pages with FAQ content, is FAQPage schema present?
  • Organisation schema — Is your brand identity (name, logo, URL) marked up at the site level?

Partial schema (some attributes missing) is better than no schema, but each missing attribute reduces the confidence AI systems have when representing your products.

FAQ schema coverage

FAQ content marked up with FAQPage schema is directly eligible to appear in AI-generated answers to customer queries. If a customer asks an AI assistant "Do you have a return policy?" and your FAQ page has schema, the AI can extract and quote your answer.

Cassian checks:

  • Pages that contain FAQ-format content (question/answer pairs) — are they using FAQPage schema?
  • Schema that's present — is it correctly structured (using mainEntity, acceptedAnswer, etc.)?
  • FAQ schema reaching product pages — product-level FAQs are often the highest-value schema to add

Content extractability

AI systems need to extract clean information from your pages. Cassian AI evaluates whether your content can be reliably parsed:

  • JavaScript rendering dependency — Content that only renders after JavaScript execution may not be visible to AI crawlers that don't execute JavaScript. This is common with headless Shopify setups or apps that load content asynchronously.
  • DOM structure clarity — Unusual or deeply nested HTML structures can make it harder for AI systems to correctly associate product images, prices, and descriptions.
  • Content behind interactions — Tabs, accordions, or "read more" toggles that hide content behind a click. AI systems typically see the page as initially rendered — content inside collapsed elements may not be extracted.
  • Third-party content interference — Pop-ups, cookie banners, or overlay elements that appear on page load and obscure content before the page body can be read.

High extractability means AI systems can reliably read your content. Low extractability means your carefully written descriptions may not reach AI-powered search results regardless of their quality.

Brand consistency

AI systems build a representation of your brand from all the content they find across your pages. Inconsistent naming, varying taglines, and contradictory brand claims make it harder for AI to produce reliable answers about your store.

Cassian checks:

  • Brand name consistency — Is your brand name spelled and capitalised the same way across all pages? Minor variations (e.g., "AcmeCo" vs "Acme Co" vs "ACMECO") accumulate into a confused brand signal.
  • Product naming conventions — Are product names consistently structured across your catalogue? Inconsistent naming (some products with "by [Brand]" at the end, others without) creates ambiguity.
  • Contact and policy consistency — Is your shipping policy described consistently across the pages that mention it? AI systems may surface different answers from different pages if the content differs.

Answer-ready formatting

When an AI assistant answers a shopping query, it draws from the text it can extract from product pages. Content written in complete, natural language sentences is significantly more usable than the same information presented as bullet-point attribute lists.

Cassian flags pages where product descriptions consist primarily of specification bullets without any prose content. This overlaps with the Content Quality check for thin content — both layers flag it, for different reasons.

Example: low answer-readiness

- Material: 100% cotton
- Weight: 280gsm
- Care: Machine wash cold
- Origin: Portugal

Example: high answer-readiness

Woven from 280gsm 100% Portuguese cotton, this t-shirt is substantial enough to hold its
shape after repeated washes. Machine washable cold, it softens with wear rather than
pilling. If you're after something that lasts years rather than seasons, this is it.

Both versions contain the same information. The second version is far more usable by an AI assistant answering "What are the best quality basics for men?" The spec-only version is not usable at all.


How important is LLM Readiness?

LLM Readiness is weighted at 10% — it's the lowest-weighted layer. A poor LLM Readiness score won't tank your overall Cassian Score. But the trend is clear: AI-powered shopping is growing, and the stores that are positioned for it now will benefit compoundingly as adoption increases.

The good news: most LLM Readiness improvements are one-time tasks. Adding llms.txt, adding FAQ schema to key pages, and ensuring your descriptions have prose content — once done, these improvements persist.

Quick wins (under 1 hour each)

Add llms.txt file. Add FAQ schema to your FAQ page. Write intro paragraphs for your top 10 products.

Medium effort (1–4 hours)

Add Product schema to all product pages (if missing). Add FAQ sections to top collection pages. Audit brand naming across all pages.

Ongoing

Write new product descriptions with prose content from the start. Maintain llms.txt as your catalogue evolves.


Where to see LLM Readiness results

  • Issues page → filter by "LLM Readiness" category. All LLM readiness issues listed by severity.
  • Scans page → click any scan → LLM Readiness section shows your layer score and all issues found.
  • Dashboard overview → the LLM Readiness card shows your current layer score.

Common questions

How do I add an llms.txt file to Shopify? The most common approach is to create a new Shopify page, publish it, then configure a custom URL redirect from /llms.txt to that page. Alternatively, some themes support adding custom files directly, or you can use a Shopify Files app. Cassian checks for the file at the standard /llms.txt path.

Will fixing LLM Readiness improve my search engine ranking? Not directly — traditional search engine rankings and AI-powered search surfaces are different systems. Improving LLM Readiness affects your visibility in AI-generated answers (in search engines that use AI overviews, browser-integrated assistants, voice search, etc.), not your traditional organic ranking. That said, several LLM Readiness improvements — structured data, FAQ schema — also benefit traditional SEO.

Is llms.txt actually a real standard, or is Cassian inventing it? It's a real and growing standard, proposed by prominent developers in the AI and web communities. Major AI systems have begun supporting it. It's in the same early-adoption phase that robots.txt was in the 1990s — not yet universal, but moving in that direction. Stores that adopt it early have a head start.

My LLM Readiness score is 45 — should I drop everything to fix it? At 10% weight, a 45% LLM Readiness score reduces your Cassian Score by about 5.5 points compared to a perfect layer. Focus on Technical Health and Content Quality first if those layers are also below target. Then come back to LLM Readiness for the quick wins.

I have FAQ schema on my FAQ page but Cassian still flags it — why? Cassian may have detected that the schema is malformed — a common issue with manually written JSON-LD. Check that your schema uses the correct format: @type: FAQPage, with mainEntity containing an array of objects with @type: Question and acceptedAnswer. Use Google's Rich Results Test tool to validate your schema.

Content extractability is flagged but our store seems normal. What does that mean? If your store uses JavaScript-heavy product rendering, headless architecture, or loads content dynamically after the page initially renders, AI crawlers may not be seeing your full content. This doesn't affect what customers see in their browser — it only affects whether external systems (AI crawlers, search engine bots) can read your content without executing JavaScript. If your Shopify store uses a standard theme, this is usually not an issue.

On this page