yolo-inc.co.uk — AI Site Grade

Analysis

That's interesting — the check_headers call returned 403 (Cloudflare challenge page) while the earlier fetch_url returned 200. This confirms Cloudflare is doing JS-challenge-based filtering that sometimes triggers. Let me now compile the audit.

Here is the audit:

---

YOLO Inc — AI-Visibility Audit

The site's llms.txt and robots.txt advertise sophisticated AI-commerce endpoints (UCP/MCP, Shop skill, agent discovery), yet every one of those endpoints — agents.md, /.well-known/ucp, sitemap_agentic_discovery.xml, sitemap_blogs_1.xml — returns a Cloudflare JS challenge wall (403) to both browser and GPTBot UAs. The infrastructure is configured to talk to AI agents but blocks them on arrival.

Crawler Access

All 11 tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Bytespider, Applebot-Extended, anthropic-ai, Perplexity-User, and a plain browser) receive a 200 with identical 112KB payload on the homepage. No UA-based blocking exists. However, the robots.txt contains zero AI-bot-specific directives — no Disallow for GPTBot, no Allow override for Google-Extended. The Shopify-default User-agent: * with Allow: / governs all AI crawlers equally. The llms.txt exists (a Shopify boilerplate) but the agent-facing endpoints it references (agents.md, /.well-known/ucp) are behind Cloudflare JS challenges that block both browsers and bots, making the entire agent-commerce promise unreachable.

Cold-Knowledge Gap

A frontier LLM queried cold about "YOLO Inc retail group UK" returned: "I do not have specific, verified information" — zero recall of the brand, its founder Scott Woodhead, its brands (Simply Hammocks, Amazonas, Scayl), its Richmond location, or its Rishi Sunak visit. The site describes a 12-year journey from a kitchen-table startup to a multi-brand retail group with products in Tesco, Walmart, and John Lewis, yet no external search results surface for the brand name, its founder, or its key milestones. The brand is functionally invisible to both web search and AI training data.

Schema Posture

Every page carries the same minimal Organization schema with sameAs links to Twitter, Facebook, Instagram, and YouTube. The WebSite schema with SearchAction appears only on the homepage. No FAQPage, Product, BreadcrumbList, LocalBusiness, or Article (with author/publisher) schema exists anywhere. Blog posts use Article schema but lack dateModified, publisher logo, or image fields. The Organization schema omits foundingDate, foundingLocation, numberOfEmployees, description, and logo — all fields that would help AI engines contextualize the brand.

External Signals

Web searches for the brand name, its founder, and its retail presence return zero indexed results across multiple query variations. No press coverage, no Reddit threads, no reviews, no Wikipedia entry, no Crunchbase profile. The brand's own blog posts (covering a Rishi Sunak visit, multiple awards, acquisitions) are the only content describing its existence, and those posts are not discoverable via external search. The DNS uses GoDaddy nameservers and Microsoft 365 mail; the site is Shopify-hosted behind Cloudflare with a google-site-verification TXT record present, confirming Google Search Console access exists but has not translated into indexed visibility.

Findings

1. Cloudflare JS challenges block all agent-facing endpoints High

   The site's llms.txt and robots.txt advertise endpoints like agents.md, /.well-known/ucp, and sitemap_agentic_discovery.xml, but every one of these returns a 403 Cloudflare JS challenge to both browsers and GPTBot, making the agent-commerce infrastructure unreachable.

   What to change: Remove the Cloudflare JS challenge from agent-facing paths (agents.md, /.well-known/ucp, sitemap_agentic_discovery.xml, sitemap_blogs_1.xml) so that AI crawlers can access them.

2. Brand has zero indexed results in web search High

   Multiple web searches for the brand name, founder Scott Woodhead, and key brands (Simply Hammocks, Amazonas, Scayl) returned zero results. The site's blog posts about a Rishi Sunak visit and awards are not discoverable via external search.

   What to change: Submit the sitemap to Google Search Console, improve on-page SEO (title tags, meta descriptions, heading structure), and build external backlinks through PR, partnerships, or listings.

3. Frontier LLM has zero knowledge of the brand High

   A cold query to a frontier LLM about 'YOLO Inc retail group UK' returned no specific information about the brand, its founder, its brands, or its milestones. The brand is absent from AI training data.

   What to change: Increase external visibility through press releases, guest articles, Wikipedia, Crunchbase, and other authoritative sources to get the brand into training corpora.

4. Robots.txt lacks AI-bot-specific directives Medium

   The robots.txt contains no Disallow or Allow rules for AI crawlers like GPTBot, Google-Extended, or ClaudeBot. The default User-agent: * with Allow: / governs all bots equally, missing opportunities to guide AI crawlers to important content.

   What to change: Add explicit Allow directives for AI crawlers to access agent endpoints (once unblocked) and consider disallowing low-value paths.

5. Organization schema omits key contextual fields Medium

   Every page carries Organization schema with sameAs links, but it lacks foundingDate, foundingLocation, numberOfEmployees, description, and logo. These fields would help AI engines understand the brand's identity and history.

   What to change: Add foundingDate, foundingLocation, numberOfEmployees, description, and logo to the Organization schema on all pages.

6. No FAQPage, Product, or BreadcrumbList schema on relevant pages Medium

   The site does not use FAQPage, Product, BreadcrumbList, or LocalBusiness schema anywhere, missing opportunities for rich results and AI context.

   What to change: Add FAQPage schema to FAQ sections, Product schema to product pages, BreadcrumbList to all pages, and LocalBusiness schema for the physical location.

7. Blog Article schema lacks dateModified, publisher logo, and image Medium

   Blog posts use Article schema but are missing dateModified, publisher logo, and image fields, reducing their eligibility for rich results and AI understanding.

   What to change: Add dateModified, publisher logo, and image fields to all Article schema instances on blog posts.

8. Sitemap subpages return 403 to bots High

   The sitemap index file is accessible, but sub-sitemaps (sitemap_pages_1.xml, sitemap_blogs_1.xml) return 403 to both browsers and GPTBot, preventing crawlers from discovering all URLs.

   What to change: Ensure sub-sitemaps are publicly accessible without Cloudflare challenges.

9. No external backlinks or mentions found High

   Web searches for the brand and its founder returned zero results, indicating no external backlinks, press coverage, or social mentions indexed by search engines.

   What to change: Build external backlinks through PR, partnerships, guest posting, and listings on directories like Crunchbase, LinkedIn, and Wikipedia.

10. llms.txt references endpoints that are blocked High

    The llms.txt file exists and references agents.md and /.well-known/ucp, but both endpoints are blocked by Cloudflare JS challenges, making the llms.txt misleading for AI agents.

    What to change: Either unblock the referenced endpoints or remove them from llms.txt until they are accessible.

What's working

• llms.txt file is published and accessible — The site hosts an llms.txt file (3987 bytes) that advertises AI-commerce endpoints, showing awareness of AI agent discovery standards.
• Robots.txt is accessible and contains basic rules — The robots.txt returns 200 and includes User-agent: * with Allow: /, ensuring all crawlers can access the homepage and other content.
• Homepage returns 200 to all 11 tested AI crawlers — All 11 AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) receive a 200 response with identical payload on the homepage, with no UA-based blocking.
• Organization schema with sameAs links on every page — Every page includes Organization schema with sameAs links to Twitter, Facebook, Instagram, and YouTube, providing basic brand identity to AI engines.
• Google Search Console is verified via TXT record — A google-site-verification TXT record is present in DNS, indicating the site owner has access to Google Search Console for monitoring and troubleshooting.
• Sitemap index is publicly accessible — The sitemap index file (sitemap.xml) returns 200 and lists 13 URLs, providing a starting point for crawlers to discover site content.
• Blog contains detailed, newsworthy content — The blog includes a 711-word article about a Rishi Sunak visit, demonstrating the site produces substantive content that could attract external attention.
• DNS and hosting infrastructure is stable — The site has consistent DNS records (A, NS, TXT) and is hosted on Shopify behind Cloudflare, providing reliable uptime and security.