warrendale-wagyu.co.uk — AI Site Grade

Analysis

Warrendale Wagyu's core informational pages — "who-we-are", "why-wagyu", "what-we-do", "contact-us", "wagyu-word", and "rewards" — all return zero words of visible text to any crawler, including GPTBot, ClaudeBot, and browser UAs, because the BigCommerce Stencil theme renders their body content entirely via JavaScript that no AI crawler executes.

Crawler Access

All major AI bots (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, anthropic-ai, Bytespider, Applebot-Extended) receive HTTP 200 with full HTML shell from Cloudflare — no UA-based blocking. The robots.txt explicitly names 43 AI user-agents with a Crawl-delay: 10 and disallows only cart/checkout/admin paths. However, the HTML these bots receive is a JS-dependent BigCommerce Stencil shell. The homepage yields 18 words of visible text. Category pages like /steaks/ and /wagyu-boxes/ fare better (~380-400 words of product-list text), but the brand's narrative pages are invisible to every crawler.

Cold-Knowledge Gap

The LLM prior knows Warrendale Wagyu as "one of the few UK farms to raise full-blood Japanese Wagyu (Tajima strain) outside Japan, with a closed herd" and mentions "ethical, grass-fed rearing with a grain-finish" and "traceability from farm to fork." The actual site contains none of this information in crawlable text. The who-we-are page has H2 headings ("Who are we?", "Meet the Farmers") but zero body text. The what-we-do page has H1 "What is Wagyu?" and H2 "Environment and animal welfare" — also zero body text. The site's most differentiated story (closed Tajima herd, British Wagyu pioneer) is entirely absent from what AI crawlers can read.

Schema Posture

Every page carries the same minimal Corporation schema with name, URL, phone, and sameAs links to Facebook and Instagram. Product pages add a Product schema with offers (price, availability, SKU). There is no LocalBusiness, Organization with founding date, FAQPage, Article, Recipe, or BreadcrumbList schema anywhere. The recipe pages (46 recipes exist in the sitemap) lack Recipe schema entirely — a significant missed signal for AI answer engines.

External Signals

The site has near-zero external footprint discoverable via search. No Trustpilot, no Reddit threads, no press mentions, no review sites surface for "Warrendale Wagyu." The what-we-do page links to restaurant partners (Tomahawk Steakhouse, Solita, The Ivy, Tickton Grange) but those links are in the JS-rendered content block that crawlers cannot read. The llms.txt returns a 404. The sitemap lives at /xmlsitemap.php (not /sitemap.xml, which 404s) and is well-structured with pages, products, categories, and news sub-sitemaps. No Wayback Machine snapshot exists, suggesting the domain may be relatively recent or has blocked archiving.

Findings

1. Core informational pages render zero visible text to any crawler High

   Pages like /who-we-are/, /why-wagyu/, /what-we-do/, /contact-us/, /wagyu-word/, and /rewards/ return HTML shells with no body text because the BigCommerce Stencil theme relies on JavaScript that no AI crawler executes.

   What to change: Implement server-side rendering (SSR) or static prerendering for all key pages so that HTML content is included in the initial response without requiring JavaScript execution.

2. No llms.txt file published Medium

   The site returns a 404 for /llms.txt, missing an opportunity to provide structured brand information directly to AI crawlers.

   What to change: Create an llms.txt file at the root with a concise brand summary, key URLs, and factual claims about the closed herd and farming practices.

3. LLM prior knowledge of the brand is not reflected on the site High

   The LLM prior knows Warrendale Wagyu as a pioneer of closed-herd Tajima Wagyu in the UK, but the site's crawlable content contains none of this information, creating a mismatch between what AI knows and what the site actually says.

   What to change: Add the closed-herd Tajima story, ethical farming details, and traceability claims as static HTML text on the /who-we-are/ and /what-we-do/ pages.

4. Recipe pages lack Recipe schema markup Medium

   The site has 46 recipe pages (e.g., /recipes/mexican-wagyu-burger/) but none include Recipe structured data, missing a key signal for AI answer engines and rich results.

   What to change: Add Recipe schema markup (with ingredients, instructions, cook time, etc.) to all recipe pages.

5. No FAQPage or BreadcrumbList schema on any page Medium

   The site uses only Corporation and Product schema. Missing FAQPage, BreadcrumbList, Article, and LocalBusiness schema limits visibility in AI-generated answers and rich snippets.

   What to change: Add BreadcrumbList schema to all pages, FAQPage schema to the delivery-returns-faqs page, and LocalBusiness schema with founding date and location.

6. Near-zero external signals from reviews, press, or social mentions Medium

   Web searches for reviews, Reddit threads, Trustpilot, and press mentions return zero results, indicating the brand has little to no discoverable external footprint that AI crawlers can use to validate authority.

   What to change: Encourage customer reviews on platforms like Trustpilot, engage in relevant online communities, and seek press coverage or backlinks from reputable food/agriculture sites.

7. Restaurant partner links are invisible to crawlers Low

   The /what-we-do/ page links to restaurant partners (Tomahawk Steakhouse, Solita, The Ivy, Tickton Grange) but these links are inside JS-rendered content that crawlers cannot read, losing potential authority signals.

   What to change: Move partner links into static HTML content on the /what-we-do/ page so they are crawlable.

8. Homepage contains only 18 words of visible text High

   The homepage returns only 18 words of crawlable text, providing almost no context to AI crawlers about the brand or its offerings.

   What to change: Add a static HTML hero section with a brand introduction and key value propositions.

9. Sitemap located at non-standard path Low

   The sitemap is at /xmlsitemap.php instead of the conventional /sitemap.xml, which may not be automatically discovered by all crawlers.

   What to change: Add a redirect from /sitemap.xml to /xmlsitemap.php, or generate a standard sitemap.xml file.

10. No Wayback Machine snapshot exists for the domain Low

    The domain has no archived snapshot on the Wayback Machine, which may indicate a recent launch or that archiving has been blocked, reducing historical credibility signals.

    What to change: Ensure the site allows archiving by not blocking the Internet Archive in robots.txt or via meta tags.

What's working

• All major AI bots are allowed to crawl the site — The robots.txt explicitly names 43 AI user-agents and only disallows cart/checkout/admin paths, ensuring broad crawler access.
• Category and product pages contain substantial crawlable text — Pages like /steaks/ and /wagyu-boxes/ return 380-400 words of product-list text, providing useful content for AI crawlers.
• Product pages include Product schema with offers — Product pages have Product structured data including price, availability, and SKU, which helps AI understand product offerings.
• Delivery and returns page has rich crawlable content — The /delivery-returns-faqs/ page contains 1824 words of text, providing detailed information that AI can use for answers.
• Sitemap is well-structured with multiple sub-sitemaps — The sitemap at /xmlsitemap.php includes separate sub-sitemaps for pages, products, categories, and news, aiding crawler discovery.
• Site uses Cloudflare for performance and security — Cloudflare headers are present, providing CDN and DDoS protection which helps with site reliability.