Agent-readiness audit UCP 2026-08-25 17 AI agents
Shoppers now ask ChatGPT, Gemini, Claude and Perplexity what to buy, and Gemini can check out without leaving the chat. Legible reads your store the way they do: no JavaScript, through robots.txt, structured data and commerce protocols. Then it writes the fixes.
No store handy? Open a sample report
Sample report · fictional store
Hollow Oak Coffee Roasters
WooCommerce
Sep 2025
OpenAI and Stripe publish the Agentic Commerce Protocol. ChatGPT starts selling products inside the chat.
Jan 2026
Google announces the Universal Commerce Protocol. Stores publish a profile at /.well-known/ucp and agents check out through it.
Mar 2026
OpenAI moves checkout back to merchants' own sites. Being found and read inside ChatGPT now depends on your pages and your feed.
~99%
of UCP-verified stores run on Shopify. WooCommerce, Magento and custom stores barely register.
Source: UCP Checker platform data, Oct 2026
The problem
A shopper sees a polished product page. An agent sees whatever the server sends before any script runs, filtered through robots.txt and your CDN's bot rules. These are the four failures Legible finds most often.
Blocking GPTBot is a choice. Blocking OAI-SearchBot, Claude-SearchBot and PerplexityBot removes your products from the answer, and many block lists include them.
Client-rendered product pages reach an AI fetcher as an empty shell. No name, no price, no reason to recommend you.
Sale prices that never reach JSON-LD make agents quote the old price, and Google Merchant Center disapproves listings for the same mismatch.
Without a UCP profile, an agent can recommend your product and then complete the purchase with a store that is set up to sell.
How it works
1Fetch
Up to 15 polite requests as LegibleBot: homepage, robots.txt, sitemap, a product page, llms.txt and /.well-known/ucp. Public addresses only, every redirect re-checked.
2Read
No browser, no JavaScript. The same raw HTML an AI fetcher gets, parsed into the text and structured data an agent can actually use.
3Score
Twenty-five checks in four weighted pillars, one score from 0 to 100. A failure that makes the rest irrelevant, like a bot wall, caps the score.
4Fix
Every failing check comes with steps for your platform and a snippet generated from your own pages: robots.txt, llms.txt, JSON-LD, UCP.
What Legible checks
Can an agent reach your pages at all?
robots.txt rules for 17 named agents, bot walls, sitemaps, speed and size. The difference between blocking a training crawler and blocking a shopper.
Can it read what you sell without running JavaScript?
What survives without JavaScript: product facts in raw HTML, schema.org Product and Offer completeness, OpenGraph, headings and llms.txt.
Can it verify who you are and what the terms are?
Shipping, returns, privacy and terms pages an agent can follow, HTTPS with HSTS, a verifiable business identity, and prices that agree.
Can it start a purchase through a protocol?
A UCP business profile validated against the spec, catalogue feeds, ACP prerequisites, a no-JS add-to-cart path, and your platform.
Every weight and threshold is published. Read the methodology.
Agent's-eye view
Left: the raw HTML the server sends. Right: the markdown an agent extracts from it. Same product page, no JavaScript. Every report includes this view for your store.
<div id="__next">
<div class="app-loading" aria-busy="true">
</div>
</div>
<noscript>You need to enable JavaScript to run this app.</noscript>
<script>/* 117 KB */</script>
<script type="application/json">/* 503 B */</script>0 words
Without JavaScript this page has no readable text. An agent gets nothing to quote, compare or recommend.
Only structured data survived
Atlas Ceramics renders its product page in the browser. The agent receives a loading placeholder and a JSON blob, falls back on a thin JSON-LD block, and never sees the description, stock or shipping terms.
Fixes, not findings
Legible does not hand you a generic checklist. It writes the files with your URLs, prices and paths, for the platform it detected.
Hollow Oak · WooCommerceLets AI search and user-triggered agents in, keeps training crawlers out (Hollow Oak blocked them, so that choice is kept), and repeats the private WooCommerce paths that a named group would otherwise lose.
# --- AI agents (generated by Legible) ---
# Before pasting: delete any existing groups for the agents named below.
# Groups for the same agent are merged, so old rules would still apply.
# Search and user-triggered agents: allowed, so products can appear
# in ChatGPT, Claude, Perplexity, Google AI Mode and Copilot answers.
# A named group replaces the * group, so your * rules are repeated here.
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Googlebot
User-agent: Bingbot
User-agent: Amzn-SearchBot
Allow: /
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Disallow: /*?add-to-cart=*
# Training crawlers: your current choice is kept. Blocking them does
# not remove you from AI search.
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Google-Extended
User-agent: Amazonbot
User-agent: meta-externalagent
User-agent: CCBot
User-agent: Bytespider
Disallow: /
User-agent: Applebot-Extended
Allow: /
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Disallow: /*?add-to-cart=*
Sitemap: https://hollowoak.example/sitemap_index.xmlPlatforms
Shopify merchants can switch most of this on. Everyone else has to build agent-readiness on purpose. Legible detects your platform and tells you what that means on your stack.
It runs a large share of independent stores and barely appears in UCP. Legible knows where WordPress stores break for agents:
Agentic Storefronts and the UCP profile Shopify publishes for you, robots.txt.liquid edits, and theme schema gaps.
Robots configuration per store view, structured-data extensions, and what a custom UCP binding involves.
Microdata-only themes, JSON-LD modules and robots.txt regeneration.
Server rendering, and SPA fallbacks that answer /llms.txt and /.well-known/ucp with an HTML shell.
Pricing
One store, whenever you need it
€0
For a store that sells every day
€29/ month
For studios and freelancers with client stores
€99/ month
Prices exclude VAT. Pro and Agency are onboarded by hand during early access: request a spot by email and we reply within two working days.
Done for you, by Digital Age
Legible is built by Digital Age, a software studio in Zagreb that builds fast WooCommerce stores for EU merchants. We implement the fixes from your report, then re-scan before handover so you see the score move.
No. SEO tools measure rankings and traffic. Legible tests whether software agents can fetch, parse and buy from your store. Crawlability and structured data overlap with SEO; user-triggered agents, bot walls, JavaScript-only rendering and commerce protocols do not.
That is your call, and Legible does not score it. Training crawlers do not decide whether you appear in AI answers. Search agents such as OAI-SearchBot and PerplexityBot, and user-triggered agents such as ChatGPT-User, do. Block the first group if you like; keep the second.
It is a proposal (llmstxt.org) and no major assistant has confirmed reading it, so it is worth 1 of 16 points in the Understanding pillar. It takes five minutes to publish, so Legible generates one from your own pages.
Yes. UCP is an open specification. Several WooCommerce plugins on WordPress.org now publish a profile and checkout endpoints, and custom stores can implement the REST or MCP binding. Legible validates your /.well-known/ucp profile against the published shape (version 2026-08-25).
ACP merchants are onboarded through OpenAI with a product feed (applications at chatgpt.com/merchants), so there is no public file to detect. Since March 2026 the purchase completes on the merchant’s own site. Legible checks the prerequisites it can see: OAI-SearchBot access, product data and a feed source.
Because most AI fetchers do not. Vercel’s analysis of AI crawler traffic (December 2024) found that OpenAI’s and Anthropic’s crawlers download JavaScript files but do not execute them. If a fact only appears after scripts run, assume an agent never sees it.
About 10 to 15 GET requests with the user agent LegibleBot/1.0: the homepage (twice, once as a browser, to detect bot walls), robots.txt, the sitemap, one product page, llms.txt and /.well-known/ucp. No more than two run at once, each has an 8-second timeout and a 2.5 MB cap. Private and internal addresses are refused.
The findings, the request log and a short excerpt of one product page, so your report link keeps working. Reports expire after 90 days in production. Nothing is shared or sold.