wearebound.co.uk — AI Site Grade

Analysis

bound (wearebound.co.uk) — AI-Visibility Audit

The homepage and all critical entry points (robots.txt, llms.txt, agents.md, blog, FAQ) are behind a Cloudflare JS challenge wall that returns 403 to every AI crawler tested — yet the site's product and collection pages are fully accessible, creating a bizarre inverted funnel where AI crawlers can see individual products but cannot reach the homepage, sitemap, or any navigational context.

Crawler Access

Every AI crawler tested — GPTBot, ClaudeBot, Google-Extended, PerplexityBot, OAI-SearchBot, Bytespider, Applebot-Extended, ChatGPT-User, and anthropic-ai — receives a 403 "Verifying your connection" Cloudflare challenge page on the homepage, robots.txt, llms.txt, and agents.md. The compare_bot_access result is uniform: all 11 UAs blocked. However, product pages (e.g. /products/maine-football-shirt) and collection pages (e.g. /collections/newest-in) serve 200 with full HTML content to browser UAs. The Cloudflare "Managed Challenge" mode is inconsistently applied — some collection pages like /collections/more-than-a-game-world-cup-exclusive-capsule are also blocked, while /collections/newest-in is not. There is no robots.txt file reachable by crawlers (403), meaning no AI-bot directives exist at all. No llms.txt or agents.md is accessible.

Cold-Knowledge Gap

A frontier LLM queried cold about wearebound.co.uk returned: "I do not have specific, verifiable information about wearebound.co.uk" — zero prior knowledge. The brand is invisible to AI models without live retrieval. The site describes itself as "bound", a UK contemporary-streetwear label founded in 2018 by Jake, selling knitwear, football shirts, outerwear, and accessories at £15–£195. The gap between the site's actual content (342 words on About Us, 200+ products, press mentions from Style and Fashion magazines) and what AI models know cold is total.

Schema Posture

The site uses a single Organization schema type on every page, with the same sameAs array (Twitter, Facebook, Instagram) and the brand name "bound". Product pages add a Product schema with Offers including price, priceCurrency (GBP), and availability. However, there is no WebSite schema, no BreadcrumbList, no ItemList on collection pages, and no FAQPage schema despite FAQ content being present. The Organization schema lacks logo, description, foundingDate, or address — all of which the About Us page explicitly contains ("Est 2018", UK-based).

External Signals

The About Us page claims press features in "Style" and "Fashion" magazines, plus a collaboration with Arctic Monkeys' Matt Helders. However, web searches for "wearebound" return zero indexed results on DuckDuckGo. The brand has an Instagram account (@wearebound), Facebook page, and Twitter handle, but no external reviews, Reddit threads, or press articles surfaced in search. DNS records confirm a Shopify store (SPF includes shops.shopify.com, Google MX, Klaviyo for email). The sitemap lists ~777 URLs including a blog sitemap, but the blog itself is behind the Cloudflare wall.

Surprising Findings

The agents.md file is listed in the sitemap (a Shopify AI-agent convention) but returns 403 — the site explicitly signals intent to support AI agents but then blocks them. The homepage returned 1.7MB of HTML to GPTBot on one attempt (200) but 403 on the next, indicating Cloudflare's challenge is inconsistent rather than a hard block. The brand name is "bound" (lowercase), the domain is wearebound.co.uk, and the Shopify store name is "we are bound" — three different brand identifiers across schema, URL, and checkout, creating fragmentation for entity resolution.

Findings

1. Cloudflare JS challenge blocks all AI crawlers from homepage and key entry points High

   Every AI crawler tested receives a 403 Cloudflare challenge page on the homepage, robots.txt, llms.txt, and agents.md. Product and collection pages are inconsistently accessible, creating an inverted funnel where crawlers can see products but not the site's navigational context.

   What to change: Disable the JS challenge for AI crawler user agents by allowing known bots through Cloudflare's bot management or by serving static HTML without challenge to verified crawlers.

2. No robots.txt accessible to crawlers High

   The robots.txt file returns a 403 Cloudflare challenge page, meaning AI crawlers cannot read any crawl directives. No AI-bot rules are in place.

   What to change: Ensure robots.txt is served without a JS challenge so crawlers can read directives. Add explicit allow/disallow rules for AI bots.

3. Total cold-knowledge gap for the brand High

   A frontier LLM queried cold about wearebound.co.uk returned zero verifiable information. The brand is invisible to AI models without live retrieval, despite having substantial content on the site.

   What to change: Improve AI visibility by allowing crawlers to index the site and by building external signals such as press mentions, reviews, and social media presence that can be referenced by AI models.

4. Inconsistent Cloudflare challenge blocks some collection pages but not others Medium

   The collection page /collections/newest-in is accessible (200), while /collections/more-than-a-game-world-cup-exclusive-capsule returns 403. This inconsistency confuses crawlers and reduces indexation.

   What to change: Apply a consistent access policy across all collection pages, either allowing all crawlers or blocking none.

5. Missing WebSite, BreadcrumbList, ItemList, and FAQPage schema Medium

   The site uses only Organization and Product schema types. No WebSite schema, BreadcrumbList, ItemList on collection pages, or FAQPage schema despite FAQ content. The Organization schema lacks logo, description, foundingDate, and address, all available on the About Us page.

   What to change: Add WebSite schema with searchAction, BreadcrumbList on all pages, ItemList on collection pages, and FAQPage schema on the FAQ page. Enrich Organization schema with logo, description, foundingDate, and address.

6. agents.md listed in sitemap but returns 403 Medium

   The sitemap includes an agents.md file, signaling intent to support AI agents, but the file is behind the Cloudflare challenge and returns 403 to all crawlers.

   What to change: Serve agents.md without a JS challenge and populate it with AI agent directives.

7. Fragmented brand identifiers across schema, domain, and checkout Medium

   The brand name is 'bound' (lowercase) in schema, the domain is wearebound.co.uk, and the Shopify store name is 'we are bound'. This fragmentation complicates entity resolution for AI models.

   What to change: Standardize the brand name to a single canonical form across schema, domain, and checkout. Use the same name in Organization schema and Shopify settings.

8. Blog and blog sitemap blocked by Cloudflare challenge Medium

   The blog at /blogs and the blog sitemap at /sitemap_blogs_1.xml return 403, preventing AI crawlers from indexing blog content.

   What to change: Allow AI crawlers to access the blog and its sitemap by removing the JS challenge for known bots.

9. FAQ page blocked by Cloudflare challenge Medium

   The FAQ page at /pages/faq returns 403, preventing crawlers from accessing structured Q&A content that could be used for rich results.

   What to change: Allow AI crawlers to access the FAQ page and add FAQPage schema markup.

10. Zero external search results for the brand High

    Web searches for 'wearebound' return no indexed results on DuckDuckGo. The brand has no external reviews, Reddit threads, or press articles surfaced in search, despite claiming press features.

    What to change: Build external signals by securing press coverage, encouraging customer reviews, and maintaining active social media profiles that are indexed by search engines.

11. llms.txt not accessible Low

    The llms.txt file returns 403, preventing AI models from discovering a machine-readable summary of the site's content.

    What to change: Create and serve an llms.txt file without a JS challenge, providing a summary of the site's content for AI models.

What's working

• Product and collection pages serve full HTML to browser user agents — Product pages like /products/maine-football-shirt and collection pages like /collections/newest-in return 200 with full HTML content, including product descriptions, prices, and images.
• Product schema with Offers on product pages — Product pages include Product schema with Offers containing price, priceCurrency (GBP), and availability, which helps AI models understand product details.
• Sitemap lists ~777 URLs including blog sitemap — The sitemap is accessible and lists a large number of URLs, including a blog sitemap, indicating good internal linking structure.
• Organization schema present on all pages — Every page includes an Organization schema with sameAs links to social media profiles, providing a consistent entity reference.
• About Us page contains brand story, founding date, and location — The About Us page includes the brand's founding year (2018), founder name (Jake), and UK base, which are valuable for entity understanding.
• Shopify infrastructure with proper DNS records — DNS records confirm a Shopify store with SPF, Google MX, and Klaviyo, indicating a professionally managed e-commerce setup.