AI Site Grade

birdandblendtea.com — AI Site Grade

Cloudflare challenge wall blocks every AI crawler from all content, making the entire domain invisible to AI engines for live retrieval.

Bird & Blend Tea Co.'s entire site is blocked by a Cloudflare JS challenge that returns HTTP 403 to all AI crawlers, preventing any content from being indexed or cited by AI engines.

Findings
11
Evidence checks
33
Completed
30 May 2026

Analysis

I have enough data to write a comprehensive audit. Let me compile it.

Cloudflare Challenge Wall Blocks Every AI Crawler From All Content

The site at birdandblendtea.com is a Shopify-hosted ecommerce store for Bird & Blend Tea Co., a UK-based loose-leaf tea brand with a strong reputation and rich product catalog — but every single AI crawler, including GPTBot, ClaudeBot, Google-Extended, PerplexityBot, and Applebot-Extended, receives a Cloudflare JS challenge (HTTP 403) identical to a browser baseline, making the entire domain invisible to AI engines for live retrieval.

Crawler Access

All 11 tested user-agents (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Bytespider, Applebot-Extended, and a standard browser) return HTTP 403 with ~8.8KB of Cloudflare challenge HTML — the same "Verifying your connection..." page. No bot receives actual content. The robots.txt (retrieved via Wayback Machine) is a standard Shopify template with no AI-bot-specific rules — it does not mention GPTBot, ClaudeBot, Google-Extended, or any AI crawler by name. The llms.txt returns the same Cloudflare 403 wall. DNS records confirm Cloudflare nameservers (hans.ns.cloudflare.com, tori.ns.cloudflare.com) and Shopify hosting (A record 23.227.38.65).

Cold-Knowledge Gap

The LLM prior on Bird & Blend Tea Co. is surprisingly detailed: it knows the brand was founded as Bluebird Tea Co. in Brighton (2012), rebranded in 2020, sells dessert-inspired loose-leaf blends and matcha, runs a Tea Tasting Club subscription, and is praised for sustainability and customer service. This prior knowledge is richer than what any AI crawler can currently verify live — the site's actual content (over 100 blends, B Corp certification, 20k+ reviews, 7+ physical stores, 280k+ trees planted) is entirely inaccessible to the models that would cite it. The gap is not in what the brand says but in the models' inability to confirm it.

Schema Posture

Product pages carry robust JSON-LD: Product schema with aggregateRating (e.g., 4.8/5 from 1,018 reviews), Offer with GBP pricing, brand, and mpn. The homepage and content pages carry Organization and WebSite schema with SearchAction. No FAQPage schema is used despite the site having a dedicated FAQ page (/pages/bird-and-blend-tea-faqs) and multiple FAQ-style sections on product pages (brewing instructions, size guides). The FAQ page itself returned zero visible text from the archive — it appears to be JS-rendered accordion content that even the Wayback Machine could not capture.

External Signals

The brand claims "20k+ 5 Star Reviews" on the homepage and displays Trustpilot quotes on the "Our Story" page. The sitemap reveals a substantial content footprint: 122+ product URLs, 30+ pages (store locations for Brighton, London, Manchester, Bristol, Cardiff, Nottingham, Oxford, Norwich, Exeter, Worthing), and a blog with three sections (News, Tea Academy, Recipes) containing hundreds of articles. The Tea Academy blog covers educational topics like cold brew methods, caffeine comparisons, and decaf tea — the exact question-answer content that AI engines surface in featured snippets. None of this is crawlable.

Surprising Finding

The Cloudflare challenge is not UA-discriminatory — it blocks browsers and bots identically — which means the site is effectively invisible to all non-JavaScript HTTP clients. This is unusual for a Shopify store, which typically serves server-rendered HTML to crawlers. The Cloudflare "Managed Challenge" mode appears to be set at the zone level, requiring every request to pass a JS challenge before reaching the Shopify origin. The result: the brand's entire AI visibility posture is a single point of failure at the CDN layer, not in robots.txt or content quality.

Findings

  1. Cloudflare JS challenge blocks all AI crawlers with HTTP 403 High

    Every tested AI crawler (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, Applebot-Extended, and others) receives a Cloudflare JS challenge page (HTTP 403) identical to a browser baseline. No bot receives actual content, making the entire domain invisible to AI engines for live retrieval.

    What to change: Configure Cloudflare to bypass the JS challenge for known AI crawler user-agents (e.g., GPTBot, ClaudeBot, Google-Extended) by creating a WAF rule or using the 'Skip' action in the Security settings.

  2. Robots.txt lacks AI crawler directives Medium

    The robots.txt file is a standard Shopify template with no rules for GPTBot, ClaudeBot, Google-Extended, or any other AI crawler. While the Cloudflare block makes robots.txt moot, the absence of explicit directives leaves no room for selective access.

    What to change: Add explicit allow/disallow rules for AI crawlers in robots.txt to signal intent once the Cloudflare block is resolved.

  3. LLMs.txt returns Cloudflare 403 Medium

    The llms.txt file, intended to provide AI-friendly site summaries, is blocked by the same Cloudflare challenge and returns HTTP 403. This prevents AI engines from discovering the file even if they could access other content.

    What to change: Ensure llms.txt is accessible to AI crawlers by bypassing the Cloudflare challenge for that path or user-agents.

  4. FAQ page content is JS-rendered and uncapturable Medium

    The dedicated FAQ page (/pages/bird-and-blend-tea-faqs) returned zero visible text from the Wayback Machine archive, indicating the content is rendered via JavaScript accordion components that even the archive could not capture. This prevents AI crawlers from indexing FAQ content that could be used for featured snippets.

    What to change: Implement server-side rendered or static HTML for FAQ content, or use structured data (FAQPage schema) to expose questions and answers in a crawlable format.

  5. No FAQPage schema despite FAQ content Medium

    The site has a dedicated FAQ page and FAQ-style sections on product pages (brewing instructions, size guides), but no FAQPage structured data is used. This misses an opportunity for AI engines to surface Q&A content in rich results.

    What to change: Add FAQPage schema to the FAQ page and any product page sections that contain question-answer pairs.

  6. Rich brand knowledge unverifiable by AI crawlers High

    LLMs have detailed prior knowledge about Bird & Blend Tea Co. (founded 2012, rebranded 2020, dessert-inspired blends, Tea Tasting Club, B Corp certification, 280k+ trees planted), but none of this can be verified live because the site is entirely blocked. This creates a gap where AI citations may be inaccurate or absent.

    What to change: Resolve the Cloudflare block to allow AI crawlers to access and verify the site's content, ensuring accurate citations.

  7. No search engine results for the domain High

    Multiple web searches for the domain and brand returned zero results, indicating the site is not indexed by major search engines. This is consistent with the Cloudflare block preventing crawlers from accessing content.

    What to change: Resolve the Cloudflare block to allow search engine crawlers to index the site.

  8. Blog content (Tea Academy, Recipes) blocked from AI crawlers High

    The sitemap reveals a blog with three sections (News, Tea Academy, Recipes) containing hundreds of articles covering educational topics like cold brew methods and caffeine comparisons. This content is ideal for AI featured snippets but is entirely inaccessible due to the Cloudflare block.

    What to change: Allow AI crawlers to access blog content by bypassing the Cloudflare challenge for those paths.

  9. Product pages with rich schema blocked from AI crawlers High

    Product pages carry robust JSON-LD (Product schema with aggregateRating, Offer, brand, mpn) but are blocked by the Cloudflare challenge. This prevents AI engines from using this structured data for rich results or product citations.

    What to change: Allow AI crawlers to access product pages to leverage existing structured data.

  10. Store location pages blocked from AI crawlers Medium

    The sitemap lists 30+ pages for physical store locations (Brighton, London, Manchester, etc.). These pages are blocked by the Cloudflare challenge, preventing AI engines from surfacing local business information.

    What to change: Allow AI crawlers to access store location pages to improve local visibility.

  11. Single point of failure at Cloudflare CDN layer High

    The Cloudflare 'Managed Challenge' mode is set at the zone level, requiring every request to pass a JS challenge before reaching the Shopify origin. This means the entire AI visibility posture depends on a single CDN configuration, and any change to that configuration could restore or block access entirely.

    What to change: Configure Cloudflare to allow AI crawlers by creating a WAF rule that bypasses the JS challenge for known bot user-agents.

What's working

  • Product pages carry rich JSON-LD structured data — Product pages include Product schema with aggregateRating (e.g., 4.8/5 from 1,018 reviews), Offer with GBP pricing, brand, and mpn. This structured data is well-formed and would be valuable for AI engines if accessible.
  • Homepage carries Organization and WebSite schema — The homepage and content pages include Organization and WebSite schema with SearchAction, providing clear identity and search functionality metadata.
  • Sitemap reveals large content footprint with 122+ products and blog — The sitemap shows 122+ product URLs, 30+ pages, and a blog with three sections (News, Tea Academy, Recipes) containing hundreds of articles. This indicates a rich content base that, if accessible, would provide strong signals for AI visibility.
  • LLMs have detailed prior knowledge about the brand — LLMs know the brand's history (founded 2012 as Bluebird Tea Co., rebranded 2020), product categories (dessert-inspired blends, matcha), subscription service (Tea Tasting Club), and sustainability efforts (B Corp, 280k+ trees planted). This prior knowledge provides a foundation for AI citations if the site becomes accessible.
  • Trustpilot reviews and testimonials displayed on site — The homepage claims '20k+ 5 Star Reviews' and the 'Our Story' page displays Trustpilot quotes. These external signals, if crawlable, would enhance credibility and provide social proof for AI engines.
  • B Corp certification mentioned in LLM prior — The brand's B Corp certification is part of the LLM prior knowledge, indicating a strong sustainability narrative that could be leveraged for AI visibility if verified on the site.
  • Tea Academy blog covers educational topics ideal for featured snippets — The blog includes educational articles on cold brew methods, caffeine comparisons, and decaf tea. This question-answer content is exactly the type that AI engines surface in featured snippets, but it is currently blocked.

Track birdandblendtea.com across AI search

This is one snapshot. Open the interactive report to inspect evidence, or grade another site free.

Open this AI Site Grade Grade another site Track your brand