gruum.com — AI Site Grade

Analysis

Cloudflare Challenge Blocks All AI Crawlers from Every Page

Every AI crawler tested — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended, and Bytespider — receives a 403 Cloudflare challenge page when attempting to access https://www.gruum.com/. The homepage returns zero words of visible content to any automated request. The robots.txt contains no AI-specific rules (no mention of any AI bot), but the Cloudflare WAF layer renders those rules moot: no crawler gets past the JavaScript challenge to even read the robots file's directives. The llms.txt returns a 404 (the 404 page itself is also behind Cloudflare). The sitemap.xml is also 403-blocked, meaning AI crawlers cannot discover any URLs on the site.

Cold-Knowledge Void

When asked about "gruum" cold, the LLM returned: "I do not have any specific, verifiable information about an entity named 'Gruum.'" The model could not confirm what the brand does, who it serves, or any products. This is a complete knowledge vacuum for a brand that claims "1.4 million customers" and "over 33,000 5-star reviews." The gap between the brand's self-described scale and the LLM's total ignorance is the single most striking finding.

Content Buried Behind Cloudflare

The Wayback Machine reveals a fully functional WooCommerce/WordPress site with rich content. The homepage (archived January 2025) shows a broad product catalog spanning skin care, hair care, body care, sun care, shave, self care, dental, beard, and kids categories. The mission page describes a Manchester-founded brand inspired by Scandinavian design, with sustainability claims including partnerships with rePurpose Global (plastic offsetting) and Ecologi (tree planting). The site uses Yoast SEO Premium with proper WebSite, Organization, WebPage, and BreadcrumbList schema. The blog has regular content through November 2024. None of this content is accessible to AI crawlers in real time.

External Signal Absence

DuckDuckGo searches for "gruum," "grüum," "gruum skincare," and related terms returned zero results across multiple queries. No Trustpilot pages, no Reddit threads, no press mentions, no review sites surfaced. The DNS records show OpenAI and Anthropic domain verification tokens (openai-domain-verification=dv-*, anthropic-domain-verification=*), indicating the brand has proactively registered with both AI companies for crawling — yet the Cloudflare challenge blocks those same verified crawlers. The site runs on Cloudflare with a strict Content Security Policy that only allows Cloudflare challenge scripts, preventing any automated extraction.

Findings

1. Cloudflare challenge blocks all AI crawlers from every page High

   Every AI crawler tested receives a 403 Cloudflare challenge page when accessing gruum.com. The homepage returns zero words of visible content to automated requests. The sitemap.xml is also blocked, preventing URL discovery.

   What to change: Configure Cloudflare WAF to allow verified AI crawlers (GPTBot, ClaudeBot, etc.) through the challenge, or serve a static HTML version to known bot user agents.

2. LLM has zero knowledge of the brand High

   When asked about 'gruum' cold, the LLM returned no verifiable information, unable to confirm the brand's products, mission, or scale. This is a complete knowledge vacuum despite the brand claiming 1.4 million customers and 33,000 5-star reviews.

   What to change: Allow AI crawlers through Cloudflare and ensure key pages are indexable so LLMs can learn about the brand.

3. Robots.txt contains no AI-specific rules Medium

   The robots.txt file has only one user-agent rule and does not mention any AI bots. While the Cloudflare block makes this moot, the absence of explicit AI directives means the site cannot signal crawling preferences to compliant bots.

   What to change: Add explicit allow/disallow rules for AI crawlers in robots.txt, such as allowing GPTBot and ClaudeBot.

4. llms.txt file returns 404 Medium

   The llms.txt file, which could provide a structured summary for LLMs, is missing and returns a 404 error. This is a missed opportunity to give AI crawlers a concise overview of the site's content.

   What to change: Create an llms.txt file with a brief description of the brand, key pages, and product categories.

5. Sitemap.xml is blocked by Cloudflare High

   The sitemap.xml returns a 403 error, preventing AI crawlers from discovering the site's URL structure. This severely limits the ability of crawlers to find and index content.

   What to change: Ensure sitemap.xml is accessible to all crawlers by excluding it from Cloudflare challenge rules.

6. No external signals found in search results High

   DuckDuckGo searches for 'gruum' and related terms returned zero results across multiple queries. No Trustpilot pages, Reddit threads, press mentions, or review sites were found, indicating a lack of external backlinks and citations.

   What to change: Build external signals through PR, guest posting, review site listings, and social media engagement to increase brand visibility.

7. Verified AI crawlers blocked despite DNS tokens High

   DNS records show OpenAI and Anthropic domain verification tokens, indicating the brand proactively registered with both AI companies for crawling. However, the Cloudflare challenge blocks those same verified crawlers, rendering the tokens useless.

   What to change: Configure Cloudflare to allow verified crawlers from OpenAI and Anthropic through the challenge, matching the DNS verification.

8. Rich content inaccessible to AI crawlers High

   Wayback Machine archives reveal a fully functional WooCommerce/WordPress site with rich content including product catalog, blog posts, mission page, and reviews. None of this content is accessible to AI crawlers in real time due to the Cloudflare block.

   What to change: Allow AI crawlers through Cloudflare to make this content indexable by LLMs.

9. Strict CSP prevents automated extraction Medium

   The site's Content Security Policy only allows Cloudflare challenge scripts, preventing any automated extraction of content even if a crawler could bypass the challenge.

   What to change: Relax the CSP to allow known AI crawler user agents to access content directly.

10. No Google search results for the domain High

    A site:gruum.com search returned zero results, indicating the site is not indexed by Google. This compounds the AI visibility problem as LLMs often rely on search engine indexes.

    What to change: Ensure the site is accessible to Googlebot and submit the sitemap to Google Search Console.

What's working

• Rich content available in Wayback Machine — Archived versions of the site show a comprehensive product catalog, blog, mission page, and reviews, indicating the site has substantial content that could be leveraged for AI visibility once access is granted.
• DNS verification tokens for OpenAI and Anthropic — The DNS records include verification tokens for OpenAI and Anthropic, showing the brand has proactively registered with these AI companies for crawling, which is a positive step that just needs to be operationalized.
• Yoast SEO Premium schema implemented — Archived pages show proper WebSite, Organization, WebPage, and BreadcrumbList schema markup, which helps search engines and AI crawlers understand the site structure when accessible.
• Regular blog content through November 2024 — The blog has regular posts, indicating ongoing content creation that could attract AI crawler attention once access is granted.
• Clear brand mission and sustainability claims — The mission page clearly articulates the brand's values, including sustainability partnerships with rePurpose Global and Ecologi, which could be compelling content for AI crawlers.