AI Site Grade
mous.co — AI Site Grade
Mous.co is entirely invisible to AI crawlers due to a Cloudflare JS challenge that blocks all HTTP clients, including GPTBot, ClaudeBot, and PerplexityBot.
Mous.co's Cloudflare JS challenge blocks all AI crawlers and search bots, making the site completely invisible to LLMs and suppressing its search footprint.
- Findings
- 8
- Evidence checks
- 35
- Completed
- 30 May 2026
Analysis
Mous.co is entirely invisible to every AI crawler — and the live site returns zero content to any HTTP client
Every request to mous.co, regardless of User-Agent, is met with a Cloudflare JS challenge (HTTP 403). The homepage, robots.txt, llms.txt, sitemap.xml, product pages, and all subdomains (uk.mous.co, eu.mous.co) return the same "Verifying your connection..." shell with fewer than 10 words of visible text. No bot — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, or even a standard browser — receives any actual content.
Crawler Access
The robots.txt (recovered via Wayback Machine) is the default Shopify template. It contains no AI-bot-specific directives — no Disallow for GPTBot, ClaudeBot, Google-Extended, or PerplexityBot. The User-agent: * block disallows standard Shopify paths (cart, checkout, admin, account, search, policies). The sitemap is declared and contains four sub-sitemaps (products, pages, collections, blogs) with hundreds of URLs. However, the live robots.txt and sitemap.xml are both behind the Cloudflare challenge, meaning no crawler can reach them either. The llms.txt returns a 403 — no such file is served.
Cold-Knowledge Gap
The LLM knows Mous as a Kickstarter-born phone case brand (2014, $2.5M raised) with AiroShock foam, Kevlar/carbon fiber cases, the Limitless series, and a reputation for surviving 35-foot drops. It also recalls 2023-2024 complaints about inconsistent MagSafe magnet strength and slow customer service. The actual site (via Wayback) reveals Mous has expanded far beyond phone cases into backpacks, luggage, wireless chargers, laptop sleeves, and a collaboration with Mercedes-AMG F1. The homepage prominently features "LUGGAGE, REINVENTED" — a suitcase line — and "Built for F1. Built for you." The cold model has no awareness of the luggage line, the backpack line, the IntraLock mechanical mounting system, or the Mercedes-AMG partnership. The brand story page mentions a Red Dot Design Award for the Evolution case, which the model also does not cite.
Schema Posture
The site uses Organization, Corporation, Website, BreadcrumbList, and CollectionPage schema types. Product pages carry Product + Offer schema with price, currency, SKU, and availability. However, the Organization schema contains a fictional US address ("254 Chapman Rd, Ste 209, Newark, Delaware 19702") on some pages and a UK address ("new kings court, Chandler's Ford, Eastleigh") on others — inconsistent. The telephone number (+447557121428) is a UK mobile. No FAQPage, HowTo, VideoObject, or Review schema types are present despite the site displaying customer reviews and FAQ content visually.
External Signals
DuckDuckGo returned zero search results for any query related to Mous — a striking absence that suggests the site's Cloudflare wall may be suppressing its search footprint. The Wayback Machine shows the site has been captured since 2015 with 3,720 captures of robots.txt alone, indicating a long-established domain. The DNS points to Shopify (A record 23.227.38.32, Shopify's standard IP), with MX via Microsoft 365 and TXT records for Klaviyo, Facebook, and Apple domain verification.
Findings
Cloudflare JS challenge blocks all AI crawlers and search bots High
Every request to mous.co, regardless of User-Agent, receives a Cloudflare JS challenge (HTTP 403) with fewer than 10 words of visible text. No bot, including GPTBot, ClaudeBot, PerplexityBot, Google-Extended, or OAI-SearchBot, receives any actual content.
What to change: Remove the Cloudflare JS challenge for known AI crawler User-Agents, or serve a static HTML version of the site to those bots.
Robots.txt and sitemap.xml are inaccessible behind Cloudflare challenge High
The live robots.txt and sitemap.xml return 403 due to the Cloudflare JS challenge, preventing crawlers from discovering allowed paths or the site's URL structure.
What to change: Ensure robots.txt and sitemap.xml are served without a JS challenge, or host them at a separate domain that is not blocked.
llms.txt file returns 403 and is not served Medium
The llms.txt file, which could provide AI crawlers with structured guidance, is not available and returns a 403 error.
What to change: Create and serve an llms.txt file with a summary of the site and links to key pages, ensuring it is not blocked by Cloudflare.
Zero search results on DuckDuckGo for any Mous-related query High
DuckDuckGo returned zero results for multiple queries about Mous, indicating the Cloudflare wall may be suppressing the site's search footprint entirely.
What to change: Remove the Cloudflare JS challenge for search engine bots to allow indexing.
Cold LLM knowledge lacks awareness of luggage, backpacks, and Mercedes-AMG partnership Medium
The LLM knows Mous only as a phone case brand, but the site now sells luggage, backpacks, wireless chargers, and has a Mercedes-AMG F1 collaboration. This gap means AI-generated answers will omit major product lines.
What to change: Allow AI crawlers to access the site so that LLMs can index the full product catalog.
Organization schema contains inconsistent and fictional addresses Medium
The Organization schema lists a fictional US address on some pages and a UK address on others, with a UK mobile phone number. This inconsistency can confuse AI parsers and reduce trust.
What to change: Use a single, accurate business address in the Organization schema across all pages.
Missing FAQPage, HowTo, VideoObject, and Review schema types Medium
Despite displaying customer reviews and FAQ content visually, the site does not include structured data for these elements, missing opportunities for rich results in AI and search.
What to change: Add FAQPage, HowTo, VideoObject, and Review schema markup to relevant pages.
Product page URL returns 404 in Wayback Machine Low
A product page URL for a MagSafe-compatible aramid fibre case returned a 404 error in the Wayback Machine, suggesting the URL structure may have changed or the product was delisted.
What to change: Ensure product URLs are stable or implement proper redirects for removed products.
What's working
- Domain has been active since 2015 with 3,720 Wayback captures — The domain mous.co has been captured by the Wayback Machine since 2015, indicating a long-established online presence with a rich history of content.
- Site is hosted on Shopify with standard DNS and email configuration — The site uses Shopify's standard IP address and has proper DNS records, including MX for Microsoft 365 and TXT for Klaviyo, Facebook, and Apple domain verification.
- Default Shopify robots.txt allows standard paths and declares sitemap — The robots.txt (from Wayback) follows Shopify's default template, disallowing only admin/cart/checkout paths and declaring a sitemap, which is a good baseline for crawler access.
- Homepage includes Organization, Website, BreadcrumbList, and CollectionPage schema — The homepage uses multiple schema types (Organization, Website, BreadcrumbList, CollectionPage) which provide structured context to AI crawlers.
- Product pages include Product and Offer schema with price, currency, SKU, and availability — Product pages carry structured data for Product and Offer, including price, currency, SKU, and availability, which is beneficial for AI understanding.
Track mous.co across AI search
This is one snapshot. Open the interactive report to inspect evidence, or grade another site free.