letscooee.com — AI Site Grade

Analysis

Cooee (letscooee.com) is invisible to frontier LLMs despite running a mature Shopify CRO business with 68 five-star reviews and 23 published case studies — the cold-knowledge gap is total, and the site's technical AI-readiness is undermined by missing foundational infrastructure.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended — receive a full 200 response with the same 131KB payload as a browser. Bytespider is the sole bot blocked (403) by Cloudflare. The site runs on Cloudflare with Webflow as the CMS, served via AWS Lambda (x-wf-region header). No JS-rendering risk exists: the homepage delivers ~1,600 words of visible text on plain GET. However, robots.txt returns an empty body (200, 0 bytes) — no directives at all, meaning no explicit allowance or disallowance for any crawler. llms.txt returns 404. sitemap.xml returns 404. The site has no machine-readable content map for AI crawlers.

Cold-Knowledge Gap

Asked cold, a frontier LLM reports zero knowledge of "letscooee" — cannot confirm what the company does, who it serves, or any products. This is a complete knowledge vacuum. The site itself describes a mature Shopify app (founded 2020, UK-registered company #12581047) with 300+ brands, 68 Shopify reviews at 5.0 stars, 23 case studies featuring brands like Voltas, Tupperware, Durex India, Phool, and Wellbeing Nutrition. The gap between the model's blank slate and the site's rich evidence base is absolute.

Schema Posture

Zero JSON-LD structured data exists on any page examined — homepage, product-benefits, pricing, case-studies, about-us, blogs, and comparison pages all return empty schema arrays. The sole exception is the Shopify App Store listing (SoftwareApplication with AggregateRating: 5.0, 68 ratings), which is off-domain. The site has no Organization, WebSite, FAQPage, Article, or BreadcrumbList markup anywhere. The pricing page has an H2: FAQs heading with visible FAQ content, but no FAQPage schema wraps it. The blog has 26+ articles with dates and authors but no Article or BlogPosting schema.

External Signals

The Shopify App Store listing is the strongest external signal: 68 reviews, 99% at 5 stars, with recent reviews from May 2026. DNS records confirm OpenAI domain verification (openai-domain-verification=dv-JODiwsLFeej45qpeNyHuAYZs), suggesting the brand has engaged with OpenAI's publisher program — yet no llms.txt or sitemap exists to feed that pipeline. Web searches for "letscooee" and "Cooee app" return zero indexed results on DuckDuckGo for Reddit threads, press mentions, or third-party reviews outside the Shopify ecosystem. The brand has comparison pages targeting Rebuy, Mason, OptiMonk, and WisePops — direct competitors — but those pages also lack schema.

Content Quality

Case studies are substantive (1,600+ words each, with tables, data points, and methodology). Blog posts are well-structured with FAQ sections and real metrics. The homepage makes specific claims ("10X higher conversions in 90 days", "30X AOV boost", "1 click setup"). However, the case study listing page shows a template placeholder issue: every case study excerpt contains the same generic text "The rise of RESTful APIs has been met by a rise in tools for creating, testing, and managing them" as the description — a Webflow template remnant that has not been replaced with actual summaries.

Findings

1. Robots.txt returns empty body, no crawler directives High

   The robots.txt file at letscooee.com returns a 200 status with zero bytes, providing no instructions to any crawler. This leaves AI bots without explicit guidance, potentially causing them to crawl inefficiently or miss content.

   What to change: Create a robots.txt file that explicitly allows GPTBot, ClaudeBot, and other AI crawlers to access the site, and disallow any non-public paths.

2. Sitemap.xml returns 404, no content map for crawlers High

   The sitemap at letscooee.com/sitemap.xml returns a 404 error, meaning AI crawlers have no machine-readable index of the site's pages. This reduces the likelihood of all pages being discovered and indexed.

   What to change: Generate and submit an XML sitemap covering all important pages (homepage, product, pricing, case studies, blogs, comparison pages) and reference it in robots.txt.

3. llms.txt returns 404, no AI-friendly content guide High

   The llms.txt file at letscooee.com/llms.txt returns a 404 error. This file is used by LLMs to quickly understand the site's structure and key content, and its absence means AI crawlers lack a concise entry point.

   What to change: Create an llms.txt file that lists the site's most important pages (e.g., homepage, product, pricing, case studies) with brief descriptions, following the llms.txt standard.

4. Zero JSON-LD structured data on any page High

   Every page examined (homepage, product-benefits, pricing, case-studies, about-us, blogs, comparison pages) lacks any JSON-LD structured data. No Organization, WebSite, FAQPage, Article, or BreadcrumbList schema is present, severely limiting how AI crawlers understand and represent the site's content.

   What to change: Add JSON-LD structured data to all pages: Organization schema on the homepage, WebSite schema site-wide, FAQPage schema on the pricing FAQ section, Article/BlogPosting schema on blog posts, and BreadcrumbList on all pages.

5. Frontier LLMs have zero knowledge of Cooee High

   When queried cold, a frontier LLM reports no knowledge of 'letscooee' — cannot confirm the company's purpose, products, or customers. This complete knowledge vacuum exists despite the site's mature business with 300+ brands, 68 Shopify reviews, and 23 case studies.

   What to change: Improve AI visibility by implementing llms.txt, sitemap, structured data, and ensuring AI crawlers can access and index all key content. Consider submitting to OpenAI's publisher program (domain verification already exists).

6. Case study listing page shows template placeholder text Medium

   The case study listing page displays generic placeholder text 'The rise of RESTful APIs has been met by a rise in tools for creating, testing, and managing them' as the description for every case study excerpt, indicating a Webflow template remnant that was not replaced with actual summaries.

   What to change: Replace the placeholder text on the case study listing page with unique, descriptive summaries for each case study.

7. Zero indexed external mentions outside Shopify ecosystem Medium

   Web searches for 'letscooee' and 'Cooee app' return no results on DuckDuckGo for Reddit threads, press mentions, or third-party reviews outside the Shopify App Store. This lack of external signals limits the brand's visibility to AI crawlers that rely on cross-references.

   What to change: Build external backlinks and mentions through PR, guest posts, and social media to increase the brand's footprint beyond the Shopify ecosystem.

8. Bytespider crawler blocked by Cloudflare Low

   Bytespider (ByteDance's crawler) receives a 403 response from Cloudflare, while all other major AI crawlers are allowed. This blocks content from being indexed by ByteDance's AI products.

   What to change: If desired, allow Bytespider access by adjusting Cloudflare WAF rules to permit its user-agent.

What's working

• All major AI crawlers except Bytespider are allowed — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, and Applebot-Extended all receive a 200 response with full HTML content, ensuring AI crawlers can access the site's text.
• OpenAI domain verification DNS record present — The DNS TXT record includes 'openai-domain-verification=dv-JODiwsLFeej45qpeNyHuAYZs', indicating the brand has engaged with OpenAI's publisher program, which can help with AI visibility once other infrastructure is in place.
• Shopify App Store listing with 68 five-star reviews — The Shopify App Store listing has 68 reviews with a 5.0 aggregate rating, providing strong social proof and external signals that can be leveraged for AI visibility.
• Case studies are detailed and data-rich — Case studies are 1,600+ words each, containing tables, data points, and methodology, providing high-quality content that AI crawlers can use to understand the product's value.
• Blog posts are well-structured with real metrics — Blog posts include FAQ sections, real metrics, and are dated with authors, providing content that could be enhanced with Article schema.
• Comparison pages target key competitors — The site has dedicated comparison pages for Rebuy, Mason, OptiMonk, and WisePops, which can help capture search traffic and provide AI crawlers with clear differentiation content.