2026-06-15
The 2026 AI visibility checklist for e-commerce stores
AI-referred traffic is now real enough to measure, track, and optimize for. This is the checklist we use when auditing stores — every item is binary (pass/fail), every fix is specific.
Work through it from top to bottom. The first section (crawler access) is where most stores fail, and it's also the fastest to fix. Schema is the highest-leverage lever for shopping recommendations. Monitoring is where you close the loop.
---
Layer 1: Crawler access
AI shopping assistants only recommend stores their data partners can crawl. If your robots.txt blocks them, you don't exist in their training data or real-time product indexes.
- [ ] GPTBot is allowed — `User-agent: GPTBot / Allow: /` in robots.txt
- [ ] ClaudeBot is allowed — `User-agent: ClaudeBot / Allow: /`
- [ ] PerplexityBot is allowed — `User-agent: PerplexityBot / Allow: /`
- [ ] Google-Extended is allowed — for Google's AI overviews and shopping surfaces
- [ ] OAI-SearchBot is allowed — OpenAI's newer shopping crawler
- [ ] No wildcard block (`Disallow: /`) that catches these bots — check that none of your existing rules accidentally block AI crawlers
- [ ] Robots.txt links to your sitemap — `Sitemap: https://yourstore.com/sitemap.xml`
How to check: Run `curl https://yourstore.com/robots.txt` and read every rule. Or run the free aiListing audit — this is the first thing it checks.
---
Layer 2: Discoverability signals
After crawler access, AI systems need a map to navigate by.
- [ ] XML sitemap exists and is valid — all product and category pages included, no 404s in the sitemap
- [ ] Canonical tags are correct — especially on paginated collection pages
- [ ] llms.txt exists at `yourdomain.com/llms.txt` — structured site summary for language models
- [ ] llms.txt lists key product categories — not just the homepage
- [ ] Organization schema is present on the homepage — `@type: Organization` with name, url, description
llms.txt is quick to add. It's a plain text file at your domain root. See the llms.txt standard for format guidance, or generate one automatically with any aiListing paid plan.
---
Layer 3: Product structured data
This is the highest-leverage layer for shopping AI. When a customer asks "best X under €Y," the AI reads product structured data to answer — not your prose descriptions.
- [ ] Schema.org Product on every product page
- [ ] `name` is specific and includes the brand — "Nike Air Max 270" not "Air Max"
- [ ] `description` is a real description, not a marketing tagline
- [ ] `offers.price` is accurate and includes `priceCurrency`
- [ ] `offers.availability` is set — `InStock`, `OutOfStock`, or `PreOrder`
- [ ] `offers.priceValidUntil` is set where relevant (sales, promotions)
- [ ] `brand.name` is consistent across all products — inconsistent brand names confuse AI systems
- [ ] `gtin` or `gtin13` is present where available — GTINs (barcodes) are the AI's equivalent of a product ID
- [ ] `image` includes at least one high-quality image URL
- [ ] `aggregateRating` is present if you have reviews — this is a trust signal for AI recommendations
- ] Markup validates — use Google's [Rich Results Test for spot checks
Reality check: Most stores pass a few of these but not all. The `gtin` field is the most commonly missing — and the one that makes products unambiguously identifiable across AI systems. If you have GTIN data in your inventory system, getting it into your product schema is one of the highest-ROI single actions on this list.
---
Layer 4: Technical health
AI crawlers behave like simplified browsers — no JavaScript execution, no session cookies, no custom HTTP headers.
- [ ] Collection/category pages render without JavaScript — the product list is visible in a plain HTML response
- [ ] Product pages render without JavaScript — title, price, description, availability all present in the raw HTML
- [ ] Page load time is under 3 seconds for the crawler (no JS needed, but slow servers still time out)
- [ ] No login wall or Cloudflare "bot" challenge on product pages
- [ ] No JavaScript-dependent price display — prices must be in the HTML, not calculated and injected by JS
How to check: Use `curl -L https://yourstore.com/products/example-product | grep -i "schema"` to see what the raw HTML contains. If the structured data is absent, it's likely being injected by JavaScript.
---
Layer 5: Content quality
AI systems quote and paraphrase your content when recommending you. What they quote is what your customer hears.
- [ ] Product titles are specific and accurate — include the key attributes a buyer would search for
- [ ] Product descriptions answer buyer questions — materials, dimensions, compatibility, use cases
- [ ] Image alt text is descriptive — "blue running shoe, side view" beats "image1.jpg"
- [ ] Category page descriptions exist and explain what the category covers
- [ ] No duplicate content across similar product variants — AI systems learn to distrust pages that look like copies
---
Monitoring: the layer most stores skip
A one-time audit tells you where you are. Share-of-answer monitoring tells you whether it's getting better.
- [ ] Define 10–50 buying-intent queries your customers actually ask — "best X in Y" questions, not brand queries
- [ ] Run them monthly across ChatGPT, Claude, Gemini, and Perplexity (or automate this)
- [ ] Track your mention rate per assistant — they have different data sources and different answer patterns
- [ ] Compare against your top 2–3 competitors — share-of-answer is zero-sum in many categories
- [ ] Set a threshold for "good" — what mention rate justifies your investment in AI visibility?
aiListing's monitoring automates this: you define the queries, it runs them weekly across all four assistants and reports your share of answer with a trend line. Basic plan starts at €29/month.
---
How to use this checklist
Start with Layer 1. Blocked crawlers is the most common finding and takes an hour to fix. Everything else is irrelevant if the bots can't reach you.
Then Layer 3. Product structured data is the highest-leverage change for actually appearing in shopping recommendations, but it takes the most effort at scale.
Run the free audit before and after changes to see your grade move. The audit checks Layers 1–5 automatically and identifies which specific items are failing.
Set up monitoring once you've fixed the structural issues — that's how you know whether AI assistants are actually starting to recommend you.