# What each check means The check ids in the Shopworthy report, what a failing one means, and what usually fixes it. Weights come with each check in the report (`checks[].weight`); higher weight, bigger effect on the score. A check with weight 0 is reported but not scored. The report's `fixes[]` holds drafted files for many of these (`id`, `title`, `filename` = where it goes, `lang`, `why`, `content`, and `template: true` when it needs the merchant's values). Use them as the starting point, then fit them to the platform. ## Can assistants get in? | Check | Failing means | Usual fix | |---|---|---| | `robots-assistants` | robots.txt turns some AI assistants away (OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User) | Allow them in robots.txt; fix id `robots` | | `robots-search` | robots.txt blocks Googlebot or bingbot, which feed Gemini, AI Mode and Copilot | Allow them | | `live-fetch` | robots.txt allows the bots, but a firewall, CDN or bot-protection rule turns them away when they actually visit | CDN or firewall settings; fix id `waf`. See platforms.md "CDN and firewall" | | `indexable` | `noindex` (meta tag or header) on pages that should be found | Remove it from product, collection and policy pages; fix id `noindex` | | `content-signal` | Content Signals say `ai-input=no`, telling assistants not to use the pages in answers | Set `ai-input=yes` if the merchant wants to appear (their choice) | | `rate-limit` | The site rate-limits page requests, so crawlers miss pages | Raise limits for verified crawlers at the CDN | | `no-js` | Much of the content needs JavaScript; assistants that do not run it see less | Server-render product names, prices and policies | | `sitemap` | No sitemap | Most platforms make one at `/sitemap.xml`; link it from robots.txt | ## Can they understand the store? | Check | Failing means | Usual fix | |---|---|---| | `meta` | Title or description does not say what the store sells | Rewrite the homepage title and meta description in shoppers' words | | `structured-data` | Little or no JSON-LD | Organization on every page, Product on product pages; fix ids `org`, `product` | | `identity` | Business identity markup incomplete (name, logo, contact, sameAs) | Organization JSON-LD; fix id `org` | | `offers` | Products and prices cannot be read reliably | Product + Offer JSON-LD with price, currency, availability; fix id `product` | | `price-consistency` | The price in the markup differs from the price shown | Make the template read the same variable the page shows | | `reviews` | Ratings are not in markup | AggregateRating in Product JSON-LD from the real review app data, never invented | | `contact` | Contact details are not machine-readable | ContactPoint in Organization JSON-LD | ## Can they act and compare? | Check | Failing means | Usual fix | |---|---|---| | `policies` | Return, shipping, terms or privacy pages are not linked where assistants look | Link them from the footer; on Shopify, a policy-links snippet | | `policy-schema` | Return and shipping terms are not in structured data | MerchantReturnPolicy and OfferShippingDetails; fix id `terms`, with the store's real return window | | `actions` | Cart or contact actions need JavaScript | A plain form fallback for add-to-cart | | `forms` | Form fields have no labels | Add labels | | `semantics` | Page structure is hard to follow (headings, landmarks) | Real headings and landmarks | | `https` | Not fully HTTPS | Redirect HTTP to HTTPS | ## Reported, not scored `llms-txt` (optional file, little evidence assistants rely on it; fix id `llms`), `training` (whether training bots are blocked: the merchant's choice), `agent-api` (MCP server card; fix id `mcp`), `ucp` (Google's Universal Commerce Protocol profile at `/.well-known/ucp`; fix id `ucp`; on Shopify the platform publishes it).