# Legible report: Hollow Oak Coffee Roasters - **Score:** 44/100, grade E (Mostly invisible) - **Store:** https://hollowoak.example/ - **Product page:** https://hollowoak.example/product/ethiopia-guji-natural/ - **Platform:** WooCommerce (high confidence) - **Scanned:** 2026-10-06 09:14 UTC (demo report, fictional store) - **Online report:** https://legible.digitalage.studio/report/demo-hollow-oak ## Pillars | Pillar | Score | Weight | Pass | Warn | Fail | | --- | --- | --- | --- | --- | --- | | Access | 63 | 30% | 6 | 0 | 2 | | Understanding | 77 | 30% | 3 | 3 | 1 | | Trust | 30 | 20% | 0 | 2 | 2 | | Transaction | 52 | 20% | 2 | 1 | 1 | ## Access (63/100) ### [FAIL] AI search and shopping agents are allowed robots.txt blocks OAI-SearchBot, Claude-SearchBot and PerplexityBot. These agents decide whether your products appear in AI search answers. _Why it matters:_ Search agents (OAI-SearchBot, Claude-SearchBot, PerplexityBot, Googlebot, Bingbot) build the indexes assistants search before recommending a product. User-triggered agents (ChatGPT-User, Claude-User, Perplexity-User) fetch your page while a shopper waits. Blocking either removes you from the answer. - OAI-SearchBot (OpenAI): Blocked on / by "Disallow: /" (line 15) - ChatGPT-User (OpenAI): Blocked on / by "Disallow: /" (line 15) - Claude-SearchBot (Anthropic): Blocked on / by "Disallow: /" (line 15) - Claude-User (Anthropic): Blocked on / by "Disallow: /" (line 15) - PerplexityBot (Perplexity): Blocked on / by "Disallow: /" (line 15) - Perplexity-User (Perplexity): Allowed - Googlebot (Google): Allowed - Bingbot (Microsoft): Allowed - Amzn-SearchBot (Amazon): Allowed **Fix:** Allow search and user-triggered agents explicitly. Keep blocking training crawlers if you want to. - If an SEO plugin (Yoast, Rank Math, AIOSEO) manages robots.txt, edit it there: Yoast → Tools → File editor; Rank Math → General Settings → Edit robots.txt. - Check security or "block AI" plugins: several add blanket AI-bot blocks that include search agents. - If Cloudflare is in front, check Security → Bots → "Block AI bots" and AI Crawl Control: these override robots.txt. `robots.txt (AI agents section)` ```txt # --- 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.xml ``` ### [FAIL] Fast first byte Slowest time to first byte: 1720 ms. Agents with tight timeouts will give up. _Why it matters:_ User-triggered agents fetch pages while someone waits for an answer, with short timeouts. A slow server is a skipped store. - /: 1380 ms - /product/ethiopia-guji-natural/: 1720 ms **Fix:** Cache full HTML pages so they are served without hitting the application. - Enable full-page caching (host cache, LiteSpeed Cache or WP Rocket) so the HTML is served without PHP on every request. - Exclude only cart, checkout and my-account from the cache. ### [PASS] Homepage answers an agent HTTP 200. _Why it matters:_ Every agent starts with an HTTP request. Anything other than a fast 200 with HTML ends the visit before it begins. - Status: 200 - Final URL: https://hollowoak.example/ - Redirects: 0 - Content-Type: text/html; charset=UTF-8 ### [PASS] No bot wall in front of the store Bots and browsers receive the same page. _Why it matters:_ Bot-protection that challenges every non-browser client blocks AI agents even when robots.txt welcomes them. Agents cannot solve JavaScript challenges or CAPTCHAs. - As LegibleBot: HTTP 200 - As a browser: HTTP 200 - Size difference: 0 KB ### [PASS] robots.txt is valid robots.txt parses cleanly: 2 groups, 1 sitemap. _Why it matters:_ RFC 9309 says a robots.txt that errors with 5xx means "crawl nothing", and an HTML page served as robots.txt is noise. A clean file also points agents at your sitemap. - Groups: 2 - Sitemap lines: 1 - Unrecognised lines: none ### [PASS] XML sitemap lists your products Valid sitemap with 6 product URLs. _Why it matters:_ Crawlers that build AI search indexes discover product URLs from sitemaps far more reliably than from links, especially on large catalogues. - Location: https://hollowoak.example/sitemap_index.xml - Found via: robots.txt - Type: Sitemap index (4 child sitemaps) - Product sitemap: https://hollowoak.example/product-sitemap.xml (6 URLs) ### [PASS] Lean HTML 7 KB of HTML for /product/ethiopia-guji-natural/. _Why it matters:_ Agents download and tokenise your HTML. Megabytes of inline scripts and styles bury product facts and can hit size caps before the content. - HTML size: 7 KB - Inline script: 0 KB in 6 tags - Visible words: 157 ### [PASS] Pages are not marked noindex No noindex directives on the pages scanned. _Why it matters:_ A noindex meta tag or X-Robots-Tag header tells search agents to drop the page from their index, even when robots.txt allows crawling. - Homepage: no directive - Product page: no directive ### [INFO] Training crawler policy 7 training crawlers blocked, 1 allowed. _Why it matters:_ Training crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot and others) collect content for future models. Blocking them is a legitimate business choice and does not affect AI search visibility. Legible reports your stance but does not score it. - GPTBot (OpenAI): Blocked - ClaudeBot (Anthropic): Blocked - Google-Extended (Google): Blocked - Applebot-Extended (Apple): Allowed - Amazonbot (Amazon): Blocked - meta-externalagent (Meta): Blocked - CCBot (Common Crawl): Blocked - Bytespider (ByteDance): Blocked ## Understanding (77/100) ### [FAIL] OpenGraph product preview OpenGraph is mostly missing (og:description, og:image and og:type). _Why it matters:_ Chat interfaces render link previews and many agents fall back to OpenGraph when JSON-LD is missing. og:title, og:image and og:type are the minimum. - og:title: Ethiopia Guji Natural - Hollow Oak Coffee Roasters - og:description: missing - og:image: missing - og:url: https://hollowoak.example/product/ethiopia-guji-natural/ - og:type: missing **Fix:** Add og:description, og:image and og:type to the product template. ### [WARN] Complete Product structured data Product schema is 65% complete. Missing: gtin / mpn, brand, shippingDetails, hasMerchantReturnPolicy and aggregateRating. _Why it matters:_ Schema.org Product and Offer JSON-LD is the most reliable way for agents and shopping indexes to read price, currency, stock, identifiers, shipping and returns without guessing from layout. - name: Ethiopia Guji Natural - image: https://hollowoak.example/wp-content/uploads/2026/09/guji.jpg - description: Natural process coffee from the Guji zone. Notes of blueberry, dark chocolate an - offers.price: 16.5 - offers.priceCurrency: EUR - offers.availability: http://schema.org/InStock - sku: HO-GUJI-250 - gtin / mpn: missing - brand: missing - shippingDetails: missing - hasMerchantReturnPolicy: missing - aggregateRating: missing **Fix:** Add the missing Product fields. The template below is pre-filled with what Legible found. - WooCommerce outputs basic Product JSON-LD on its own. Fill the native "GTIN, UPC, EAN or ISBN" field (Inventory tab, WooCommerce 9.2+) and a brand for every product. - Shipping and return details are not in the default markup: add them through your SEO plugin's schema settings or a small snippet hooked to woocommerce_structured_data_product. - Avoid two plugins both printing Product schema: duplicates with different prices confuse agents. `Product JSON-LD (product template)` ```html ``` ### [WARN] One clear H1 with the product name 2 H1 headings. The product name should be the only one. _Why it matters:_ Extractors use the heading outline to split a page into sections. One H1 naming the product, then H2s for details and reviews, makes the page easy to chunk. - H1: Hollow Oak Coffee Roasters | Ethiopia Guji Natural - H2: 3 **Fix:** Demote logo and section titles to other elements; keep one

for the product. ### [WARN] llms.txt guide for agents No llms.txt found. _Why it matters:_ llms.txt is a proposed markdown index of a site's most useful pages. No major assistant has confirmed it uses the file, so it carries little weight here, but it is cheap and gives agents a clean map of products and policies. - llms-full.txt: not found **Fix:** Publish /llms.txt. This one is generated from the pages Legible found on your site. - Upload llms.txt to the WordPress root (next to wp-config.php), or use an SEO plugin that generates one (Yoast and Rank Math both offer llms.txt generation). `/llms.txt` ```markdown # Hollow Oak Coffee Roasters > Specialty coffee roasted weekly in Zagreb. Single origins and blends, shipped across Croatia and the EU. ## Products - [Ethiopia Guji Natural](https://hollowoak.example/product/ethiopia-guji-natural/) - [Colombia Huila Washed](https://hollowoak.example/product/colombia-huila-washed/) - [Oak House Espresso](https://hollowoak.example/product/oak-house-espresso/) ## Categories - [Shop](https://hollowoak.example/shop/) - [Single origin](https://hollowoak.example/product-category/single-origin/) - [Blends](https://hollowoak.example/product-category/blends/) ## Policies - [Privacy Policy](https://hollowoak.example/privacy-policy/) - [Terms & Conditions](https://hollowoak.example/terms-and-conditions/) - [Contact](https://hollowoak.example/contact/) ## Optional - [Our story](https://hollowoak.example/our-story/) ``` ### [PASS] Product facts are in the raw HTML Name, price and 157 words of content are in the server HTML. _Why it matters:_ Most AI fetchers do not run JavaScript. If the name, price and description only appear after scripts run, the agent sees an empty page and moves on. - Visible words (no JS): 157 - Product name in text: Yes - Price in text: 16.50, 16.50, 14.90 ### [PASS] Organization and WebSite schema Organization and WebSite schema identify the store as "Hollow Oak Coffee Roasters". _Why it matters:_ Organization and WebSite markup tells an agent the store's official name, logo, URL and social profiles, so it can tell your shop apart from resellers and lookalikes. - Organization: Hollow Oak Coffee Roasters - WebSite: Hollow Oak Coffee Roasters - logo: present - sameAs: missing ### [PASS] Canonical URL and language Canonical set, language en-US. _Why it matters:_ A canonical URL collapses filter and tracking variants into one product, and a lang attribute tells the agent which language and market the price and policies apply to. - canonical: https://hollowoak.example/product/ethiopia-guji-natural/ - html lang: en-US ## Trust (30/100) ### [FAIL] Policy pages are linked No shipping and returns page is linked from the homepage or product page. _Why it matters:_ Before recommending a purchase, assistants look for shipping costs, the return window and who to contact. In the EU, consumers have a 14-day right of withdrawal for most online purchases (Directive 2011/83/EU, Art. 9), so returns terms are a deciding fact. - Shipping: no link found - Returns: no link found - Privacy: https://hollowoak.example/privacy-policy/ - Terms: https://hollowoak.example/terms-and-conditions/ - Contact: https://hollowoak.example/contact/ **Fix:** Link shipping and returns from the site footer. - Link shipping, returns, privacy and terms pages in the footer menu (Appearance → Menus or the Site Editor footer). Set the Terms page under WooCommerce → Settings → Advanced. ### [FAIL] Visible price matches structured data JSON-LD still says EUR 16.50, the struck-through regular price. Shoppers see 14.90. Agents will quote the higher price. _Why it matters:_ When the price a shopper sees differs from the price in JSON-LD, agents quote the wrong number or distrust both. Google Merchant Center suspends listings for mismatches, and under EU consumer law the price shown must be the price charged. - JSON-LD price: EUR 16.50 - Current prices on page: 14.90 - Struck-through prices: 16.50 - Microdata price: none **Fix:** Generate JSON-LD from the same price the template displays, including sale prices. - Typical cause: a caching or SEO plugin prints the regular price while the theme shows the sale price. Purge caches after price changes and keep one schema source. ### [WARN] HTTPS everywhere, with HSTS HTTPS works, but no HSTS header is sent. _Why it matters:_ Agents that hand a shopper off to checkout will not send them to an insecure page. HSTS proves the store never falls back to plain HTTP. - Final URL scheme: https - http:// redirects to https: yes (301) - Strict-Transport-Security: not sent **Fix:** Send an HSTS header. - Add the Strict-Transport-Security header at the web server or CDN; security plugins such as Really Simple SSL can also add it. `Response header` ```txt Strict-Transport-Security: max-age=31536000 ``` ### [WARN] Business identity is machine-readable Organization schema found, but address, contact details and legal name or VAT ID are missing. _Why it matters:_ Agents weigh whether a merchant is real. A legal name, postal address and a contact point in Organization schema are the strongest signals short of a marketplace listing. - address: missing - email / telephone / contactPoint: missing - legalName / vatID: missing **Fix:** Add address, contact details and legal name or VAT ID to the Organization node. ## Transaction (52/100) ### [FAIL] UCP business profile No UCP profile at /.well-known/ucp, so agents cannot discover a checkout. Few WooCommerce stores publish one yet. _Why it matters:_ The Universal Commerce Protocol (UCP), announced by Google in January 2026, lets agents discover a store's capabilities from /.well-known/ucp and complete checkout through a standard API. It powers buying in Google AI Mode and Gemini. Current spec version: 2026-08-25. **Fix:** Publish a UCP profile backed by a working checkout implementation. - Several WordPress.org plugins now publish a UCP profile and checkout endpoints for WooCommerce (search the directory for "Universal Commerce Protocol"). Test any of them on staging first: they take part in checkout. - Whatever you install, confirm /.well-known/ucp returns valid JSON with a dev.ucp.shopping.checkout capability. `/.well-known/ucp (skeleton)` ```json { "ucp": { "version": "2026-08-25", "services": { "dev.ucp.shopping": [ { "version": "2026-08-25", "spec": "https://ucp.dev/2026-08-25/specification/overview/", "transport": "rest", "endpoint": "https://hollowoak.example/ucp/v1", "schema": "https://ucp.dev/2026-08-25/services/shopping/rest.openapi.json" } ] }, "capabilities": { "dev.ucp.shopping.checkout": [ { "version": "2026-08-25", "spec": "https://ucp.dev/2026-08-25/specification/shopping/checkout/", "schema": "https://ucp.dev/2026-08-25/schemas/shopping/checkout.json" } ], "dev.ucp.shopping.fulfillment": [ { "version": "2026-08-25", "spec": "https://ucp.dev/2026-08-25/specification/shopping/extensions/fulfillment/", "schema": "https://ucp.dev/2026-08-25/schemas/shopping/fulfillment.json", "extends": "dev.ucp.shopping.checkout" } ] }, "payment_handlers": {} }, "keys": [] } ``` ### [WARN] Agentic Commerce Protocol readiness (signal) 2 of 3 ACP prerequisites in place. _Why it matters:_ OpenAI and Stripe's Agentic Commerce Protocol (ACP) launched in September 2025 to let shoppers buy inside ChatGPT. There is no public discovery file: merchants are onboarded through OpenAI and submit a product feed. In March 2026 OpenAI moved checkout back to merchants' own sites, so discovery in ChatGPT now depends on that feed and on crawlable pages. Legible scores the prerequisites, not enrolment. - OAI-SearchBot allowed: no - Product structured data: yes - Feed source available: yes **Fix:** Apply to OpenAI's merchant program and submit a product feed. - Merchants apply at chatgpt.com/merchants. Shopify and Etsy merchants are onboarded through their platform. - The WooCommerce Store API (/wp-json/wc/store/v1/products) is public by default unless a plugin disables it: it is a ready-made product feed. - For ChatGPT, merchants apply through OpenAI's merchant program and submit a product feed; for Google AI Mode, connect Google Merchant Center with the "Google for WooCommerce" extension. ### [PASS] Machine-readable catalogue 2 catalogue signals detected. _Why it matters:_ Agent channels (ChatGPT shopping, Google AI Mode, Copilot) prefer a structured product feed they can refresh over crawling pages. A feed keeps price and stock current between crawls. - Signal: WooCommerce Store API (/wp-json/wc/store/v1/products, on by default) - Signal: Product sitemap (6 URLs) ### [PASS] Add-to-cart works without scripts The product page has a server-rendered add-to-cart form or link. _Why it matters:_ Browser-driving agents (ChatGPT agent, Gemini in Chrome and similar) click through your real checkout. A plain form or link for add-to-cart in the server HTML is the most robust path when no protocol is available. - Cart form in HTML: yes - Add-to-cart link: no - Add-to-cart button: yes ### [INFO] Platform and remediation path Detected WooCommerce (high confidence). _Why it matters:_ What you can fix, and how fast, depends on the platform. Shopify merchants can switch most of this on; WooCommerce, Magento and custom stores need it built or configured. - Signal: WooCommerce generator meta tag - Signal: /wp-content/plugins/woocommerce/ assets - Signal: woocommerce body or element classes - Signal: WordPress REST API header ## What an agent extracts From https://hollowoak.example/product/ethiopia-guji-natural/, about 245 tokens from 7 KB of HTML. | Fact | Found | Source | | --- | --- | --- | | Product name | Ethiopia Guji Natural | both | | Price | EUR 16.50 | both | | Availability | InStock | both | | Brand | missing | — | | GTIN / EAN | missing | — | | Shipping | missing | — | | Returns | missing | — | | Rating | missing | — | ## Requests made - 200 https://hollowoak.example/ (Homepage (as LegibleBot), 1400 ms) - 200 https://hollowoak.example/ (Homepage (as a browser, for bot-wall comparison), 1400 ms) - 200 https://hollowoak.example/robots.txt (robots.txt, 230 ms) - 301 http://hollowoak.example/ (HTTP to HTTPS redirect probe, 110 ms) - 404 https://hollowoak.example/llms.txt (llms.txt, 1000 ms) - 404 https://hollowoak.example/llms-full.txt (llms-full.txt, 1000 ms) - 404 https://hollowoak.example/.well-known/ucp (UCP business profile, 1000 ms) - 200 https://hollowoak.example/sitemap_index.xml (XML sitemap, 660 ms) - 200 https://hollowoak.example/product-sitemap.xml (Product sitemap, 610 ms) - 200 https://hollowoak.example/product/ethiopia-guji-natural/ (Product page (as LegibleBot), 1740 ms) Evaluated against UCP 2026-08-25 and the agent list of 2026-10-07. Agent categories: Training crawler, Search / index, User-triggered. --- Generated by Legible, a Digital Age product (https://digitalage.studio/en/).