perkyblenders.com — AI Site Grade

Analysis

Cloudflare JS challenge blocks every AI crawler from accessing any content on perkyblenders.com

The site is a Shopify store (hosted at 23.227.38.32) behind Cloudflare's managed JS challenge, and every single AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended, ChatGPT-User, Perplexity-User, anthropic-ai — receives a 403 with a Cloudflare JS challenge wall. No bot gets past to see any product, pricing, or brand content.

Crawler Access

compare_bot_access on the homepage returned 403 for all 11 user-agents tested, including a plain browser UA. The response is a Cloudflare "Verifying your connection..." page (~8.8 KB of JS challenge HTML) with zero visible content. The robots.txt and llms.txt endpoints also return 403 — they are behind the same wall, so no crawler can even read access rules. The site runs on Shopify (IP 23.227.38.32, TXT records confirm include:shops.shopify.com) with Cloudflare as the CDN/WAF. This is a blanket block, not a selective UA-based policy.

Cold-Knowledge Gap

The LLM model queried cold describes Perky Blenders as a London-based specialty coffee roastery founded in 2015 by Adam and Victoria, emphasizing B Corp certification, zero-waste roasting, direct trade, and a subscription model. The model claims they were "one of the first UK roasters to achieve B Corp certification." However, the actual site content (visible only via Wayback snapshots) makes no mention of B Corp, zero-waste, direct trade, or the founders' names. The homepage tagline is "Roasted in East London. Posted Everywhere. For Everyone." The wholesale page describes a "family-owned and operated specialty coffee roaster with 8 coffee shops of our own" and mentions a franchise model — a detail entirely absent from the LLM's prior knowledge. The model's knowledge appears to be hallucinated or based on a different brand entirely.

Schema Posture

The homepage carries only a bare Organization schema with name, URL, and sameAs links (pointing to Facebook, Instagram, Twitter/X, YouTube). A WebSite schema with SearchAction is also present. No Product schema exists on product listing pages. No FAQPage, BreadcrumbList, LocalBusiness, or Review schema was detected on any fetched page. The schema is minimal — it identifies the brand but provides no structured data about products, pricing, or business details that AI engines could extract.

External Signals

No external search results were found for perkyblenders.com, "Perky Blenders" coffee, or any variant across multiple search queries. No Trustpilot, Reddit threads, press mentions, or review sites surfaced. The brand has zero indexed external footprint in current search results. The sameAs schema references Facebook, Instagram, Twitter/X, and YouTube accounts, but none of these profiles appeared in search results either. This total absence of off-domain signals means AI engines have no corroborating third-party content to draw from when describing the brand.

Findings

1. Cloudflare JS challenge blocks all AI crawlers from accessing any content High

   Every AI crawler tested (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended, ChatGPT-User, Perplexity-User, anthropic-ai) receives a 403 with a Cloudflare JS challenge wall. No bot can see any product, pricing, or brand content.

   What to change: Disable the Cloudflare JS challenge for known AI crawler user-agents, or serve a static HTML version of the site to those bots.

2. Robots.txt and llms.txt are behind the same Cloudflare wall, returning 403 High

   The robots.txt and llms.txt endpoints return 403, so crawlers cannot even read access rules. This prevents any bot from understanding which paths are allowed or disallowed.

   What to change: Serve robots.txt and llms.txt from a path that bypasses the Cloudflare JS challenge, or configure Cloudflare to allow access to these files.

3. Sitemap returns 403, preventing crawlers from discovering site structure High

   The sitemap endpoint returns 403, so no crawler can discover the site's URL structure. This severely limits indexing even if the JS challenge were removed.

   What to change: Ensure the sitemap is accessible to crawlers by bypassing the Cloudflare challenge for known bot user-agents.

4. Zero external search results found for the brand or domain High

   Multiple web searches for 'perkyblenders.com', 'Perky Blenders coffee', and related terms returned zero results. No Trustpilot, Reddit, press mentions, or review sites were found. The brand has no indexed external footprint.

   What to change: Build external signals through PR, reviews, social media activity, and backlinks to establish an off-domain presence.

5. LLM prior knowledge about the brand is largely hallucinated High

   The LLM's cold knowledge describes Perky Blenders as B Corp certified, zero-waste, direct trade, and founded by Adam and Victoria. The actual site content (via Wayback) makes no mention of these claims. The model's knowledge appears to be fabricated or based on a different brand.

   What to change: Publish accurate brand information on the site and ensure it is accessible to crawlers so that LLMs can learn correct details.

6. Schema markup is minimal, lacking Product, FAQ, and LocalBusiness schemas Medium

   The homepage only has bare Organization and WebSite schemas. No Product schema on product pages, no FAQPage, BreadcrumbList, LocalBusiness, or Review schema. This limits structured data extraction by AI engines.

   What to change: Add Product schema to product pages, and consider adding LocalBusiness, FAQPage, and BreadcrumbList schemas where appropriate.

7. No Product schema on collection pages Medium

   The coffee collection page (visible via Wayback) contains no Product schema markup, so AI engines cannot extract product details like name, price, or description in a structured format.

   What to change: Add Product schema to each product on collection pages, including name, price, description, and availability.

8. About page returns 404, removing brand story from crawlers Medium

   The /pages/about and /pages/our-story URLs return 404. The brand's story, mission, and founder details are not accessible to crawlers, contributing to the hallucinated LLM knowledge.

   What to change: Restore the About page with accurate brand information and ensure it is accessible to crawlers.

9. Blog section returns 404, no content marketing for AI visibility Medium

   The /blogs URL returns 404, indicating no blog content is published. This removes a key channel for generating crawlable, indexable content that AI engines can reference.

   What to change: Create a blog with articles about coffee, brewing guides, and brand stories to generate crawlable content.

10. Social media profiles not found in search results Low

    Despite sameAs schema referencing Facebook, Instagram, Twitter/X, and YouTube, no social media profiles appeared in search results. This suggests the accounts may be inactive or not indexed.

    What to change: Ensure social media profiles are active, linked from the site, and discoverable by search engines.

What's working

• Organization schema present on homepage — The homepage includes an Organization schema with name, URL, and sameAs links to social media, providing basic brand identification for AI engines.
• WebSite schema with SearchAction present — A WebSite schema with a SearchAction is included on the homepage, enabling AI engines to understand site search functionality.
• Wayback Machine snapshots preserve historical site content — Multiple Wayback snapshots exist (2024, 2025, 2026), preserving some site content for historical reference, though current live site is blocked.