eatsurreal.co.uk — AI Site Grade

Analysis

Surreal UK — AI-Visibility Audit

The live eatsurreal.co.uk domain is entirely inaccessible to every AI crawler tested — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, and even a standard browser all receive a 403 Cloudflare JS challenge wall with zero content delivered. The site is a Shopify storefront (IP 23.227.38.32, Cloudflare CDN) that requires JavaScript execution and cookie acceptance before serving any HTML, meaning AI crawlers that cannot run JS see nothing at all.

Crawler Access

Every bot across the full compare_bot_access matrix — 11 user-agents including GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended, and anthropic-ai — returns 403 with ~8.8KB of Cloudflare challenge HTML. No robots.txt file is served (also 403, Cloudflare challenge). No llms.txt exists (also 403). No sitemap.xml is accessible. The site has effectively zero AI-crawl surface area: no directives, no content map, no bot-accessible content.

Cold-Knowledge Gap

The LLM cold-knowledge query describes Surreal as a UK high-protein, zero-sugar cereal brand with Frosted and Cocoa flavours, bold marketing, and some consumer criticism over pricing. This matches the brand positioning found in Wayback snapshots. However, the live site's actual content — including newer products like Granola, Chocolate Pops, Cookies & Cream, and Honey PB & Cocoa — is completely invisible to AI models because no crawler can reach it. The cold knowledge is stuck on an older product set and cannot refresh.

Schema Posture

Wayback snapshots reveal the site uses only Organization and WebSite schema types. No Product schema is present on product pages (e.g., /products/chocolate), despite those pages displaying pricing, ratings, nutritional data, and reviews. No FAQPage schema exists on the FAQ page, which contains a rich Q&A structure about orders, subscriptions, and allergens. No BreadcrumbList, Review, or NutritionInformation schema is deployed anywhere. The schema is minimal and misses every opportunity to structure the data AI crawlers would use for rich snippets and knowledge panels.

External Signals

The brand has retail presence in Holland & Barrett, Booths, and Selfridges (stated in the FAQ), and claims award-winning status and press mentions ("As seen in..."). However, web searches for the brand name, domain, and product terms return zero indexed results from DuckDuckGo — a striking absence that suggests the Cloudflare wall may also be suppressing search-engine indexing. The Instagram handle @eat_surreal and Facebook page exist but are not surfaced in search results.

Content & Structure

The site has strong answer-format signals — FAQ content, comparison tables ("Us vs Them"), nutritional data, and customer reviews — but none of this is marked up with structured data. The homepage heading structure is chaotic: a single H1 ("New Products Just Launched!" or "Surreally Healthy Cereal") followed by dozens of duplicate H2 headings ("Whats your flavour?" repeated 9 times, "CHANGE THE WAY YOU SEE CEREAL." repeated 10 times). This flat, repetitive heading hierarchy undermines semantic clarity for any parser that does get through.

Findings

1. Cloudflare JS challenge wall blocks all AI crawlers High

   Every AI crawler tested (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended, anthropic-ai) receives a 403 with Cloudflare challenge HTML. No bot can access any page content.

   What to change: Disable the JS challenge wall for AI crawler user-agents, or serve a static HTML version of the site to those bots. Add explicit allow rules in Cloudflare for GPTBot, ClaudeBot, and other AI crawlers.

2. No robots.txt file accessible High

   The robots.txt endpoint returns a 403 Cloudflare challenge, so no crawler can read directives. This prevents any bot from understanding crawl permissions or sitemap location.

   What to change: Serve a static robots.txt file that allows AI crawlers and points to the sitemap. Ensure it is accessible without JS execution.

3. No sitemap.xml accessible High

   The sitemap endpoint returns a 403 Cloudflare challenge, so crawlers cannot discover the site's URL structure. This severely limits indexing.

   What to change: Generate and serve a static sitemap.xml listing all important pages (products, FAQ, about, nutrition). Ensure it is accessible without JS.

4. No llms.txt file Medium

   The llms.txt endpoint returns a 403, so AI models have no machine-readable guide to the site's content or structure.

   What to change: Create an llms.txt file that lists key pages and a brief summary of the site, and serve it without JS challenge.

5. No Product schema on product pages High

   Product pages like /products/chocolate display pricing, ratings, and nutritional data but lack Product structured data. This prevents AI crawlers from extracting product details for rich snippets and knowledge panels.

   What to change: Add JSON-LD Product schema to all product pages, including name, description, price, currency, availability, aggregateRating, and nutrition information.

6. No FAQPage schema on FAQ page Medium

   The FAQ page contains rich Q&A content about orders, subscriptions, and allergens but lacks FAQPage structured data. This misses an opportunity for rich results in search and AI answers.

   What to change: Add FAQPage JSON-LD schema to the FAQ page, marking up each question and answer pair.

7. No NutritionInformation schema on product pages Medium

   Product pages display nutritional data (protein, carbs, sugar, etc.) but do not use NutritionInformation schema. This data is valuable for AI assistants answering dietary queries.

   What to change: Add NutritionInformation schema to product pages, including serving size, calories, protein, carbohydrates, sugar, and fat.

8. No BreadcrumbList schema Low

   The site does not implement BreadcrumbList schema, which helps crawlers understand site hierarchy and can appear in search results.

   What to change: Add BreadcrumbList JSON-LD schema to all pages to indicate navigation path.

9. Flat and repetitive heading structure on homepage Medium

   The homepage uses a single H1 followed by dozens of duplicate H2 headings (e.g., 'Whats your flavour?' repeated 9 times, 'CHANGE THE WAY YOU SEE CEREAL.' repeated 10 times). This undermines semantic clarity for parsers.

   What to change: Restructure headings to use unique, descriptive H2s for each section. Avoid repeating the same heading text.

10. Zero search engine indexing on DuckDuckGo High

    Web searches for the domain, brand name, and product terms return zero indexed results on DuckDuckGo, suggesting the Cloudflare wall also blocks search engine crawlers.

    What to change: Allow search engine crawlers (Googlebot, Bingbot) through the Cloudflare challenge. Submit sitemap to Google Search Console and Bing Webmaster Tools.

11. LLM cold knowledge is stuck on older product set Medium

    LLM knowledge describes only Frosted and Cocoa flavours, while the site now sells Granola, Chocolate Pops, Cookies & Cream, and Honey PB & Cocoa. New products are invisible to AI models.

    What to change: Allow AI crawlers to access product pages so models can refresh their knowledge with current offerings.

12. No external signals surfaced in search results Medium

    Despite retail presence in Holland & Barrett, Booths, and Selfridges, and claimed press mentions, web searches return zero results for the brand. This indicates poor off-site visibility.

    What to change: Build backlinks from retail partner sites and press mentions. Ensure social media profiles are indexed and linked from the website.

What's working

• Organization and WebSite schema present on homepage — The homepage includes Organization and WebSite JSON-LD schema, providing basic brand identity and site name to crawlers.
• Rich FAQ content with Q&A structure — The FAQ page contains detailed, well-structured Q&A content covering orders, subscriptions, allergens, and nutrition, which is valuable for AI answers once schema is added.
• Nutritional data displayed on product pages — Product pages show detailed nutritional information (protein, carbs, sugar, fat) per serving, which is useful for AI assistants answering dietary queries once schema is added.
• Customer reviews present on product pages — Product pages include customer reviews with ratings, which can be marked up with Review schema to enhance rich snippets.
• Comparison tables ('Us vs Them') present — The site includes comparison tables that contrast Surreal with competitors, which can be marked up with structured data for rich results.
• Wayback Machine snapshots available for content recovery — Historical snapshots of the site exist on the Wayback Machine, allowing content recovery and verification of past product listings.
• Shopify platform with built-in structured data capabilities — The site runs on Shopify, which supports adding JSON-LD schema via themes or apps, making it easier to implement missing schemas.
• Clear brand identity and positioning — The site clearly communicates Surreal as a high-protein, low-sugar cereal brand for adults, with consistent messaging across pages.