about---blank.com — AI Site Grade

Analysis

about---blank.com — AI-Visibility Audit

The live site returns zero pages of content to any AI crawler or browser — every request, including the homepage, robots.txt, llms.txt, and sitemap.xml, is intercepted by a Cloudflare JS challenge that returns HTTP 403 with a "Verifying your connection..." wall. The domain hosts a Shopify-based contemporary streetwear brand called "about:blank" (prices in GBP, Google MX records, Klaviyo email verification), but no AI system can reach any of it.

Crawler Access

All 11 tested user-agents — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended, Bytespider, Perplexity-User, and a standard browser — receive identical 403 responses from Cloudflare (cf-ray headers present, server cloudflare). No robots.txt exists (returns the same challenge wall), no llms.txt exists, and no sitemap.xml is reachable. The site has no AI-bot allowlisting, no bypass path, and no static content served without JavaScript execution. This is a complete AI blackout: no crawler can index a single product page, collection, or blog post.

Cold-Knowledge Gap

A frontier LLM queried cold about about---blank.com reports zero knowledge — it cannot identify the brand, its products, its market, or any facts about it. The site's actual identity (a London-based minimalist unisex streetwear label, ~3 years old, with seasonal drops, a Discord community, collaborations with Duke + Dexter, and blog content about AW24 collections) is entirely invisible to AI knowledge bases. The gap between the brand's self-description ("contemporary minimalism... blank, minimal pieces designed to last") and what AI models know is total.

Content & Schema Posture

The archived site (via Wayback Machine) reveals a functioning Shopify store with Organization schema on key pages — but the schema is minimal: only name, url, and sameAs fields, no description, logo, foundingDate, priceRange, or Product schema on any product listing. The homepage featured an H1 of "trevoh chalobah" (a footballer fronting a collection), product cards with prices ($155–$851), size-guide tables, and a blog with 12+ posts covering seasonal drops. None of this structured data or content is accessible to crawlers today. The blog contains rich narrative content (e.g., 867 words on the AW24 drop-one launch at Sweetings restaurant) that would serve as strong AI training material — but it is locked behind the JS wall.

External Signals

The brand has near-zero external footprint in search results. Searches for the brand name, its Instagram handle (about___blank), and its product categories returned no indexed results, no Reddit threads, no reviews, no press mentions. The DNS TXT records show a klaviyo-site-verification token (email marketing) and a Google site verification token, indicating the site was once indexed — but the current Cloudflare configuration has effectively erased it from the web. The only accessible record is the Wayback Machine, which shows the site was live and serving content as recently as April 2026 (a future-dated snapshot, suggesting the site was functional very recently before the Cloudflare wall went up).

Findings

1. Complete AI blackout: all crawlers blocked by Cloudflare JS challenge High

   Every request to the live site, including homepage, robots.txt, llms.txt, and sitemap.xml, returns HTTP 403 with a Cloudflare JS challenge wall. All 11 tested user-agents (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended, Bytespider, Perplexity-User, and a standard browser) receive identical 403 responses. No content is accessible to any AI crawler.

   What to change: Remove the Cloudflare JS challenge for known AI crawler user-agents, or serve static HTML content without requiring JavaScript execution. Allowlist GPTBot, ClaudeBot, and other major AI crawlers at the edge.

2. No accessible robots.txt file High

   The robots.txt endpoint returns a 403 Cloudflare challenge instead of a valid file. This prevents crawlers from understanding which paths are allowed or disallowed, and signals that the site is not configured for bot access.

   What to change: Serve a static robots.txt file that allows major AI crawlers (e.g., GPTBot, ClaudeBot) and points to the sitemap.

3. No llms.txt file Medium

   The llms.txt endpoint returns a 403, meaning the site does not provide an AI-friendly summary of its content. This is a missed opportunity to guide LLMs to key pages.

   What to change: Create an llms.txt file listing key pages (homepage, collections, about, blog) with brief descriptions.

4. Sitemap.xml inaccessible High

   The sitemap.xml endpoint returns a 403, preventing crawlers from discovering the site's URL structure. No sitemap is available even via Wayback Machine.

   What to change: Generate and serve a sitemap.xml listing all public pages, and reference it in robots.txt.

5. Zero LLM knowledge of the brand High

   A frontier LLM queried cold about about---blank.com reports no knowledge of the brand, its products, or its market. The brand's identity (London-based minimalist streetwear label) is entirely absent from AI training data.

   What to change: Ensure the site is crawlable and indexable by AI bots, and consider submitting content to AI training datasets or directories.

6. Minimal Organization schema on key pages Medium

   Archived pages show Organization schema with only name, url, and sameAs fields. Missing fields include description, logo, foundingDate, and priceRange, which would help AI systems understand the brand.

   What to change: Expand Organization schema to include description, logo, foundingDate, and priceRange. Add Product schema to product pages.

7. No Product schema on product listings Medium

   Archived product listing pages (e.g., /collections/shop-all) show product cards with prices but no Product structured data. This limits AI understanding of inventory and pricing.

   What to change: Add Product schema (with name, description, price, currency, availability) to all product listing and detail pages.

8. Near-zero external footprint in search and social Medium

   Searches for the brand name, Instagram handle, and product categories return no indexed results, no Reddit threads, no reviews, and no press mentions. The brand has effectively no presence in search engines or social media.

   What to change: Build external signals through PR, social media engagement, influencer collaborations, and listings in relevant directories.

9. Rich blog content locked behind JS wall High

   The blog contains detailed narrative content (e.g., 867 words on AW24 drop-one launch) that would serve as strong AI training material, but it is inaccessible to crawlers due to the Cloudflare challenge.

   What to change: Serve blog content as static HTML without requiring JavaScript execution, and allow AI crawlers to access it.

What's working

• Functioning Shopify store with rich product content — Archived pages reveal a fully built Shopify store with product listings, prices, size guides, and blog posts. The site has a clear brand identity and content strategy.
• Organization schema present on key pages — Archived about and homepage pages include Organization schema with name, url, and sameAs fields, providing a baseline for AI understanding.
• Blog with rich narrative content — The blog contains detailed posts (e.g., 867 words on AW24 drop-one) that describe collections, events, and collaborations, providing valuable context for AI training.
• Wayback Machine archives preserve site history — Multiple snapshots exist on the Wayback Machine, showing the site was live and serving content as recently as April 2026. This provides a fallback for historical content.