How to get your Shopify store cited by Claude

Claude does not maintain a product catalog, does not have a shopping tab, and does not participate in the Agentic Commerce Protocol that OpenAI shipped with Shopify. When a buyer prompts Claude for product research, Claude decides whether the question needs web search, issues a search through its retrieval partner, and cites whichever pages best answer the query with high confidence. That pipeline is deliberately conservative — Claude would rather decline to cite than cite the wrong source.

Fewer citations per answer means each citation matters more. Claude tends to pick 2-3 authoritative sources and weave them into one confident answer, whereas Perplexity leans toward 5-8 sources with direct quotes. That has practical implications for Shopify merchants: being in Claude's answer at all is harder, and being the only one cited is the norm rather than the exception.

The single most leveraged move for Claude citations is a well-curated llms.txt. Anthropic has documented that ClaudeBot fetches /llms.txt when it discovers a new domain and uses the curated URL list as a prioritization signal for which pages to index more heavily. No other major answer engine documents this contract with the same specificity — ChatGPT, Gemini, and Copilot read the file empirically but do not publicly commit to weighting it.

What to include

Your 5-10 hero products, your best buyer guides (6-12 months old or newer), your shipping and returns policies, your about page, any proprietary research you have published.

What to exclude

Every product dump (auto-generated from sitemap), filtered collection URLs, thank-you pages, cart URLs, and anything you would not want the engine quoting in a direct recommendation.

Format rule

Markdown. H1 (brand name), optional blockquote (one-sentence description), H2 section headings, then bulleted links with short descriptions — the spec from Jeremy Howard's proposal.

Size target

20-40 entries. Under 20 reads as sparse; over 50 dilutes curation and signals auto-generation.

Claude's editorial posture treats first-party claims as necessary but insufficient. If you are the only source on the internet saying your moissanite watch weighs 128 grams, Claude will either omit that fact or cite it with a hedge. If three sources — your PDP, a Reddit thread, and a Trustpilot review — all corroborate the same fact, Claude cites your PDP as the primary source with much higher confidence. This posture is partly a hallucination mitigation and partly a trust-calibration mechanism, and it makes the shape of Shopify GEO work on Claude distinct.

The corroboration sources that move Claude

• Reddit threads — particularly in product-research subreddits (r/watches, r/skincareaddiction, r/frugalmalefashion). Claude treats Reddit as a high-authority corroboration source for consumer product claims.
• Trustpilot public profile — Claude fetches and parses it. A Trustpilot page with substantive review text corroborates product claims; a page with only star ratings does not.
• Judge.me public storefront — similar weight to Trustpilot when the reviews include product detail, not just stars.
• YouTube reviews with transcripts — Claude can read YouTube captions via its web retrieval layer, and a 10-minute review with specs matches first-party claims powerfully.
• Editorial coverage on publisher sites — niche publications, not just Wirecutter. A Blog to Watch review carries more weight than a press release republish.

The five-move list below is ordered by how much each move shifts Claude citation count on the panels we have measured. Moves 1 and 2 are universal GEO work that benefits every engine; 3, 4, and 5 are where Claude's posture rewards specific tactics more than its peers.

1. Unblock ClaudeBot everywhere

Whitelist ClaudeBot in robots.txt, Cloudflare Bot Management, Shopify's bot rules, and any WAF layer. Verify with server-log grep for a ClaudeBot hit in the last 14 days.

2. Ship Product + FAQPage schema on every PDP

Claude's retrieval layer reads schema to extract structured answers. FAQPage especially — it is the block Claude lifts from most often on sizing, shipping, and materials queries.

3. Curate llms.txt with 20-40 canonical entries

This is the single highest-leverage Claude-specific move. Ship a curated file, not an auto-generated one, and update it quarterly.

4. Earn third-party corroboration on top SKUs

Reddit seeding (organic, not manipulated), Trustpilot reviews with substantive text, Judge.me storefront content, YouTube review outreach. Two corroborating sources per hero product is the minimum bar.

5. Publish original data or research

Claude weights first-party research and proprietary datasets heavily. Publish a buyer survey, a product test result, or a category benchmark once a quarter — this becomes a citable source for you specifically.

Claude's answers are non-deterministic and session-sensitive — the same prompt from the same user can produce materially different citations across two sessions. That is not a bug; it is part of how Claude randomizes research to avoid answer monocultures. The implication for measurement is that a single-prompt test is almost useless. The defensible cadence is a 20-query panel run weekly, with citation rate (fraction of sessions in which you appear) as the primary metric and position (when you do appear) as the secondary.

1. 1Pick 20 buyer-intent queries that a real customer would ask Claude — mix brand, category, comparison, and problem-statement classes.
2. 2Run each query three times in a fresh Claude session (no Projects, no prior context) and record whether your store was cited.
3. 3Log the result weekly, same day, same time, same account. Track citation rate week over week, not answer text.
4. 4Flag any query where your citation rate drops 20%+ week over week — that is the signal to investigate what changed (feed, schema, llms.txt, competitor push).
5. 5Quarterly, rotate 5 of the 20 queries to reflect seasonal buyer intent or new product launches.

Claude is the engine most likely to demote a brand that games the signals, because corroboration is the weight it leans on hardest. If your Reddit mentions look manufactured, if your Trustpilot reviews look bought, if your llms.txt looks auto-generated, Claude applies a higher skepticism threshold — and that skepticism propagates to every future query about your brand on every Claude surface.

• Do not seed Reddit with coordinated posting from new accounts. Claude's corroboration detection flags this pattern reliably. Earn organic Reddit mentions by building genuinely useful content in the relevant subreddit.
• Do not auto-generate llms.txt from your sitemap. Claude's prioritization heuristic rewards curation density — a dumped sitemap reads as noise.
• Do not write 'Claude-optimized content' separately from the rest of your content. Claude's weighting rewards the same structural moves (answer-first, FAQ schema, self-contained passages) that benefit every other engine.
• Do not fabricate FAQ answers to match query templates. Claude cross-checks FAQ claims against review text and support responses — a fabricated answer that contradicts a customer review gets both demoted.