Agent-ready. An AI agent can find, understand and buy from you.

• ✓ robots.txt allows agent crawlers ⓘ What we checked: Your site has a small doorman file that tells visiting AI services whether they're welcome. We read what yours says.
  Why it matters: Many stores block AI tools by accident — often a copied setting — without ever deciding to.
  If ignored: Assistants politely obey the "keep out" sign and quietly shop somewhere that lets them in. · 16.0/16.0
  robots.txt allows GPTBot, ClaudeBot, PerplexityBot and Google-Extended.
• ✓ No blocking / cloaking of AI bots ⓘ What we checked: We visited your store twice — once as a normal shopper, once as an AI assistant — and compared what each one got to see.
  Why it matters: If assistants get a blocked or empty page while humans see your shop, to them your store simply doesn't exist.
  If ignored: Every sale that starts with "ask your assistant" goes to a competitor, and you never see it happen. · 8.0/8.0
  AI bots get the same access and content as a normal visitor.
• ✓ Fast enough response for agents ⓘ What we checked: We timed how fast your store answers when a page is requested.
  Why it matters: AI assistants check several shops in seconds; a slow answer means yours gets skipped, not waited for.
  If ignored: You lose comparisons you would have won on price or product, purely on speed. · 4.0/4.0
  Fast response (652 ms on the homepage) — agents won't time out.
• ✓ llms.txt present ⓘ What we checked: We looked for llms.txt — a one-page, plain-text introduction of your store, written for AI assistants.
  Why it matters: It's the cheapest way to tell assistants what you sell, in your own words, before they guess from your pages.
  If ignored: Assistants describe your store from whatever they piece together — or from what others say about you. · 4.0/4.0
  /llms.txt present — points agents to your key pages.
• ✓ Sitemap available ⓘ What we checked: We checked for a site map — the machine-readable index of every page your store has.
  Why it matters: It's how assistants discover products beyond the few your homepage links to.
  If ignored: Most of your catalog stays invisible: assistants only ever find your front window. · 4.0/4.0
  Sitemap found via robots.txt.
• ✓ Content accessible without JS rendering ⓘ What we checked: We read your page the way most assistants do: the raw text your server sends, before any visual code runs in a browser.
  Why it matters: If your products only appear after that code runs, an assistant reading the raw page sees an empty shop.
  If ignored: A full catalog that looks like a blank storefront to every text-reading assistant. · 4.0/4.0
  Content present in raw HTML (645784 visible characters).

• ✓ Product JSON-LD present ⓘ What we checked: We checked whether your product pages carry a structured product sheet — name, price, stock — in the standard format machines read.
  Why it matters: Assistants don't "look at" your beautiful page; they read this sheet. No sheet, no product.
  If ignored: You're not comparable, not quotable and not buyable — the three things an AI shopper needs. · 12.0/12.0
  Schema.org Product found in JSON-LD (product page).
• ✓ Structured price + currency ⓘ What we checked: We checked whether your price (with its currency) is written in that machine-readable product sheet.
  Why it matters: "How much is it?" is the first question every shopper asks — the assistant must answer it with certainty, not guess from the page.
  If ignored: Assistants either skip you or show you without a price next to competitors who have one. Nobody picks the mystery price. · 8.0/8.0
  price=59.99 USD.
• ✓ Structured availability ⓘ What we checked: We checked whether your product sheet says if the item is in stock right now.
  Why it matters: An assistant completing a purchase won't gamble on availability — it recommends what it can confirm.
  If ignored: Even products sitting in your warehouse get treated as "maybe unavailable" and left out. · 5.0/5.0
  availability=http://schema.org/InStock.
• ✗ Structured brand ⓘ What we checked: We checked whether your brand name is part of the machine-readable product sheet.
  Why it matters: It's how assistants connect your products to your name when someone asks for you — or for "a brand like X".
  If ignored: Your products float around nameless; the reputation you've built doesn't transfer to AI shopping. · 0.0/3.0
  No structured brand.
  I fixed this — validate ↻
• ✓ Product identifier (SKU / GTIN) ⓘ What we checked: We looked for a unique product code (like the number under a barcode) in your product sheet.
  Why it matters: It's how an assistant is certain it's ordering exactly YOUR item — the 250ml one, not the 500ml.
  If ignored: Wrong-item mistakes and cautious assistants that prefer stores where identity is certain. · 4.0/4.0
  SKU/GTIN/MPN present — reliable product resolution.
• ✗ Aggregated reviews (aggregateRating) ⓘ What we checked: We checked whether your customer reviews and stars are published in machine-readable form (only if you really have them).
  Why it matters: Assistants weigh trust signals when ranking similar offers — invisible reviews count for nothing.
  If ignored: A competitor with worse reviews — but readable ones — outranks you in every recommendation. · 0.0/3.0
  No aggregateRating — the agent can't compare your reputation.
  I fixed this — validate ↻

• ✓ Structured variants ⓘ What we checked: We checked whether your options — sizes, colors, formats — exist as structured choices, not just dropdown menus on the page.
  Why it matters: "Order it in size M" only works if size M exists as data the assistant can select.
  If ignored: The sale dies at the last step: the assistant found you, chose you, and couldn't finish. · 10.0/10.0
  Variants exposed as data (3 variants in products.json).
• ~ Attributes as fields (not prose) ⓘ What we checked: We checked whether your product specifics — material, dietary labels, capacity — are data, not just sentences in a description.
  Why it matters: Shoppers ask assistants for "vegan", "cotton", "under 200g" — filters only catch products whose traits are machine-readable.
  If ignored: You vanish from filtered searches you should win — the shortlists are built without you. · 4.0/8.0
  Few structured attributes: option:Flavor.
  I fixed this — validate ↻
• ✓ Product feed / catalog signals ⓘ What we checked: We looked for a product feed — a single file listing your whole catalog that machines can read in one pass.
  Why it matters: It's the difference between an assistant browsing your store aisle-by-aisle or receiving your full catalog instantly.
  If ignored: Assistants know three of your products; your competitor's entire catalog is on the table. · 7.0/7.0
  Feed signals: valid products.json (Shopify), OpenGraph product.

The next wave: do the agents that shop for real buyers get in (the "Agent" class Cloudflare now filters), and can they transact with you over the emerging rails (UCP, A2A, ARD)? Almost every store scores +0 here today — these are pure BONUS points: you can't lose any, and early movers pull ahead. Below them, the visibility signals that decide whether AI assistants can even see and cite you — the traps that don't show in a browser.

• ✗ Shopify/UCP agent endpoint (/api/ucp/mcp) ⓘ What we checked: We checked whether your store exposes the new "agent checkout counter" that Shopify-connected assistants use to browse and buy directly.
  Why it matters: It lets an assistant complete a purchase through a dedicated door, instead of clumsily filling your human checkout.
  If ignored: None today — almost nobody has this yet. That's exactly why having it early is a lead, not a repair. · worth +4 pts
  No UCP MCP endpoint detected (HTTP 404) — agents on the UCP rail (Shopify catalog/checkout) can't transact here.
  I fixed this — validate ↻
• ✗ A2A Agent Card (/.well-known/agent-card.json) ⓘ What we checked: We looked for your store's "business card for AI agents" — a small public file saying what your store can do for them.
  Why it matters: It's how future assistants will discover stores they can talk to directly, rather than reading pages.
  If ignored: None today — adoption is near zero everywhere. Early movers get found first when it switches on. · worth +3 pts
  No A2A Agent Card — your store publishes no machine-readable agent for buyer-agents to discover and call. (So do ~all stores today: this is the frontier, not the baseline.)
  I fixed this — validate ↻
• ✗ ARD AI Catalog (/.well-known/ai-catalog.json) ⓘ What we checked: We looked for your AI catalog file — a brand-new standard (backed by Google, Microsoft and GitHub) listing what your site offers to AI agents.
  Why it matters: It's set to become the yellow pages of the agent web; GitHub's assistant already uses it to find services.
  If ignored: None today — almost 0% of the web has one, including its own authors. Publishing one puts you ahead of nearly everyone. · worth +3 pts
  No AI Catalog — under the new Google/Microsoft ARD spec (June 2026), agents look here first to learn what a site offers. Adoption is ~0% today, so publishing one puts you ahead of nearly the entire web (including the spec authors).
  I fixed this — validate ↻
• ✓ Add-to-cart action detectable ⓘ What we checked: We looked at your product page the way an agent does — the raw text, before any scripts run — for a visible "add to cart" action it could use.
  Why it matters: Reading your product is step one; step two is finding WHERE the purchase starts. If the buy button only appears after scripts run, an agent sees the product but no way to buy it.
  If ignored: The sale dies one step from the finish line: chosen, priced — and unbuyable.
  The product page exposes a machine-visible add-to-cart action in its raw HTML — an agent can locate where the purchase starts.
• ✓ Shopping-agent access (Agent class) ⓘ What we checked: We knocked on your door as the specific AI assistants that shop for real people (the ones ChatGPT, Claude and Perplexity send when a customer is ready to buy).
  Why it matters: New security defaults (notably Cloudflare's) increasingly block these buyers by accident, along with genuine scrapers.
  If ignored: The most valuable AI visitor there is — one with a human buyer behind it — bounces off your door.
  On-demand shopping agents (ChatGPT-User, Claude-User, Perplexity-User) load the site like a normal visitor. The site is behind Cloudflare — check the AI-crawler settings there.
• – x402 / HTTP-402 payments ⓘ What we checked: A future standard letting AI agents pay for things directly over the web. There's nothing to check yet — we track it for you.
  Why it matters: When it lands, stores that support it will be payable by agents without a human card form.
  If ignored: None today. We'll flag it here the day it becomes checkable.
  No standard discovery path exists yet for x402 — we track the spec and will probe it the moment a convention settles.
• ✓ Citation-rail access (Bingbot, OAI-SearchBot, Google-Extended) ⓘ What we checked: We knocked on your door as the reading services that build the libraries AI assistants answer from — Bing's and OpenAI's index readers — and read your rules for Google's Gemini switch.
  Why it matters: Assistants don't browse the live web when they answer; they consult these libraries. A store missing from them either isn't mentioned — or gets described from guesswork (it happened to us).
  If ignored: You can welcome the shopping agent and still be invisible to it: the recommendations go to stores that exist in the libraries.
  Bingbot and OAI-SearchBot get in, and Google-Extended is allowed — the indexes feeding ChatGPT, Copilot and Gemini answers can all read this store.
• – Content-Signal directives (robots.txt) ⓘ What we checked: We read the small switchboard some sites carry (Content-Signal) that tells machines whether content may be used in search and in AI answers.
  Why it matters: One switch set to "no" — often a copied default, not a decision — quietly withdraws your whole store from AI-generated answers.
  If ignored: Silent self-exclusion: everything else can be perfect and no assistant will surface you.
  No Content-Signal directives — the Cloudflare-era content switches aren't set on this store (that's the common case; nothing is being blocked by them).
• ✓ Canonical address coherence ⓘ What we checked: Every page declares one official address. We checked that yours points at the address where your store actually answers — not at a variant that forwards visitors elsewhere.
  Why it matters: If the declared address forwards (www vs no-www is the classic), every page tells machines "the real page is elsewhere".
  If ignored: Credit gets split and answer engines quietly prefer stores whose identity is unambiguous. Usually one site setting to fix.
  The declared canonical address matches where the site actually answers — no identity contradiction for machines to untangle.
• ✗ Machine entry points advertised at first contact ⓘ What we checked: We checked whether your homepage points machines to the resources you already publish for them — a plain-text guide for assistants (your llms.txt), a product feed — right on the first page they load, instead of making them hunt for where those live.
  Why it matters: An assistant usually loads only your homepage. If nothing there points to those resources, it assumes they don't exist — even when you publish them. A real assistant bounced off us this way.
  If ignored: You can publish everything an assistant needs and still look empty to the one that only glances at your front page.
  The homepage points to no machine resources — no <head> link to llms.txt, a feed or an agent endpoint, and no HTTP Link header. An agent that fetches only the root sees no signposts and can conclude there's no machine access, even when you serve those files. Link them from the page and echo them in a Link response header.
  I fixed this — validate ↻
• ✗ Returns & shipping in offers (P6 preview) ⓘ What we checked: We checked whether your product offers state, in machine-readable form, your return policy and your shipping details.
  Why it matters: "What does it really cost, and can I send it back?" — an agent must answer both before committing a buyer's money.
  If ignored: The agent can't compute the true total, so it buys where it can — and Google flags this same gap on your product listings.
  Offers carry no machine-readable return policy or shipping details — an agent can't compute the true total cost of buying from you, and Google's own Search Console flags this too.
  I fixed this — validate ↻