hotfutures.co.uk — AI Site Grade

Analysis

Cloudflare wall blocks every AI crawler — and the live site is invisible to the open web

The live site at hotfutures.co.uk returns a 403 Cloudflare JS challenge page to every user-agent tested — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Applebot-Extended, Bytespider, anthropic-ai, and a standard browser all receive the same "Verifying your connection..." wall. No AI crawler can access a single byte of real content. The robots.txt and llms.txt endpoints also 403, meaning neither directive file nor AI-friendly content map exists. The sitemap at /sitemap.xml is equally blocked. The site runs on Shopify (evidenced by hot-futures.myshopify.com references in archived product pages) behind Cloudflare (IP 23.227.38.32, a known Shopify/Cloudflare edge), with DNS managed by GoDaddy (ns71.domaincontrol.com).

Cold-Knowledge Gap

A frontier LLM queried cold about "Hot Futures" described it as a UK-based futures trading education and signals platform — a complete hallucination. The actual site is an independent London eyewear brand selling handcrafted acetate sunglasses and optical frames from a Brick Lane, Shoreditch storefront. The LLM fabricated an entire trading-signal business model, pricing tiers, Telegram channels, and mixed user reviews. This gap is extreme: the brand's actual identity (premium fashion eyewear) is entirely absent from the model's prior, while a fictional competitor narrative occupies that space.

Content & Schema Posture

Archived snapshots (Wayback Machine, latest from November 2025) reveal a Shopify storefront with product collections named Trinity, Aurora, Cupid, Baby Racer, Good Vibrations, Ghost, Blaze, Dazed, Groover, Club Kid, Hustler, and Euphoria. Products are priced around GBP 105 / USD 135, made from premium acetate with CR39 lenses, designed in London and handmade in Shenzhen. The "Our Story" page names founders Tanya and Jake, who met as vintage fashion business owners. The site claims press mentions in Vogue, Refinery 29, and Highsnobiety — though no indexed web results corroborate these. JSON-LD schema is minimal: only BreadcrumbList and WebSite/Organization types exist on archived pages. No Product schema, no FAQPage schema (despite a real FAQ page existing), no Review schema. The FAQ page covers shipping, returns, payment methods, and collaboration inquiries — structured as plain <h3> headings with no markup.

External Signals

The brand has near-zero external web footprint. Searches for hotfutures.co.uk, "Hot Futures" eyewear, the Brick Lane store, and founder names return no indexed results on DuckDuckGo, no Reddit threads, no Trustpilot reviews, no press articles, and no social media profiles surfaced by search. The site's own "Our Story" page claims press in Vogue, Refinery 29, and Highsnobiety, but no evidence of these mentions exists in searchable form. The Instagram handle @hotfutures is referenced in archived site code but does not appear in search results. The brand is essentially invisible to the open web beyond its own domain.

Surprising Findings

The most striking finding is the total identity mismatch between what AI models believe about this brand (futures trading signals) and what it actually is (fashion eyewear). This is not a subtle positioning gap — it is a complete category error. Additionally, the Cloudflare JS challenge blocks all traffic indiscriminately, including browser UAs, meaning the site is effectively offline for anyone who does not pass the JavaScript challenge. The most recent Wayback snapshot (November 2025) shows a 200 status, suggesting the site was accessible to archive crawlers recently, but the live site currently denies everything. The Shopify myshopify.com subdomain reference in archived product pages (hot-futures.myshopify.com) indicates the store was originally on a Shopify subdomain before moving to the custom domain.

Findings

1. Cloudflare JS challenge blocks every AI crawler from accessing the live site High

   The live site returns a 403 Cloudflare JS challenge page to all tested user-agents, including GPTBot, ClaudeBot, PerplexityBot, and standard browsers. No AI crawler can retrieve any content.

   What to change: Remove or relax the Cloudflare JS challenge for known AI crawler user-agents, or serve a static HTML version to bots.

2. Robots.txt and llms.txt endpoints are blocked (403) High

   Both /robots.txt and /llms.txt return 403 errors, preventing crawlers from reading directives or discovering AI-friendly content.

   What to change: Ensure robots.txt and llms.txt are publicly accessible and contain appropriate directives for AI crawlers.

3. Sitemap.xml is blocked (403) High

   The sitemap at /sitemap.xml returns a 403 error, preventing search engines and AI crawlers from discovering site pages.

   What to change: Make sitemap.xml publicly accessible and ensure it lists all important pages.

4. AI models hallucinate Hot Futures as a trading signals platform High

   A frontier LLM queried cold described Hot Futures as a UK-based futures trading education and signals platform, fabricating pricing tiers, Telegram channels, and reviews. The actual brand is a London eyewear label selling handcrafted sunglasses and optical frames.

   What to change: Publish structured data (Product, Organization, FAQ) and build external citations (press, social media, reviews) to correct the AI knowledge gap.

5. No Product schema on product pages Medium

   Archived product pages lack JSON-LD Product schema, missing opportunities for rich results and AI entity extraction.

   What to change: Add JSON-LD Product schema to all product pages with name, description, price, availability, and image.

6. FAQ page lacks FAQPage schema Medium

   The FAQ page covers shipping, returns, and payments but uses plain HTML headings with no structured data markup.

   What to change: Add FAQPage schema to the FAQ page to enable rich results and AI-friendly Q&A extraction.

7. Near-zero external web presence High

   Searches for the brand, its products, founders, and store location return no indexed results on major search engines. No Reddit threads, Trustpilot reviews, press articles, or social media profiles are discoverable.

   What to change: Build external signals by claiming social media profiles, submitting to directories, and securing press coverage.

8. Claimed press mentions in Vogue, Refinery 29, and Highsnobiety are not verifiable Medium

   The 'Our Story' page claims press coverage in major fashion outlets, but no indexed web results or archived articles corroborate these mentions.

   What to change: Ensure press mentions link to actual articles or provide verifiable citations.

9. Live site is inaccessible to standard browsers due to JS challenge High

   The Cloudflare JS challenge blocks not only bots but also standard browser user-agents, effectively making the site offline for users who cannot execute JavaScript.

   What to change: Configure Cloudflare to allow direct access for known good user-agents or serve a static fallback.

10. Organization schema lacks brand details Low

    The Organization schema on the site is minimal and does not include brand name, logo, social links, or description.

    What to change: Expand Organization schema with name, logo, sameAs URLs, and description.

What's working

• Archived product pages show a diverse collection of eyewear — Wayback Machine snapshots reveal a well-organized Shopify storefront with 12+ product collections, detailed product descriptions, and pricing.
• Brand story page provides founder narrative and origin — The 'Our Story' page details the founders' background and the brand's London roots, which is valuable for AI entity understanding.
• FAQ page covers common customer questions — A dedicated FAQ page addresses shipping, returns, payments, and collaborations, providing useful content for AI extraction.
• Site built on Shopify, a robust e-commerce platform — Shopify provides built-in SEO features, structured data capabilities, and scalability, which can be leveraged for AI visibility.
• Wayback Machine has multiple snapshots of the site — Historical snapshots from 2022 to 2025 are available, indicating the site has been active and accessible to archive crawlers in the past.