facethefuture.store — AI Site Grade

Analysis

The .store domain is a dead end — it 403s every AI crawler with a Cloudflare JS challenge and does not redirect to the real site.

The domain facethefuture.store resolves to the same Shopify-hosted infrastructure as www.facethefuture.co.uk (IP 23.227.38.70, Cloudflare), but it returns a Cloudflare JS challenge wall to every visitor — browser, GPTBot, ClaudeBot, PerplexityBot, Google-Extended, all get a 403 with a "Verifying your connection..." page. No redirect, no content, no robots.txt served from this domain. The actual retail operation lives at www.facethefuture.co.uk, which is a mature Shopify store with 5,000+ product URLs, 18 years of trading history, and a 4.76 / 5.0 rating across 23,218 reviews on reviews.co.uk.

Crawler Access Paradox

The .co.uk homepage passes all AI crawlers with full content (200, ~1.5MB HTML, no JS-shell). However, every sub-page — product pages, blog, about-us, collections, the UCP endpoint, even agents.md — hits the Cloudflare JS challenge wall for all bots and browser alike. The homepage is the only publicly crawlable page. The robots.txt has no AI-specific directives (no GPTBot, ClaudeBot, Google-Extended rules), meaning the default * rules apply — but the Cloudflare WAF overrides them anyway on deep pages. The llms.txt exists and is well-crafted, describing UCP endpoints and agent workflows, but the UCP endpoint itself (.well-known/ucp) returns 403.

Cold-Knowledge Gap

The LLM knows Face the Future as a CQC-registered virtual clinic founded in 2003 by dermatology nurses and pharmacists, specializing in prescription-strength skincare and custom-compounded formulations (tretinoin, hydroquinone). The actual .co.uk site presents itself as a cosmeceutical e-commerce retailer stocking SkinCeuticals, Jan Marini, Medik8, Environ, Obagi, and iS Clinical — with no mention of CQC registration, virtual consultations, or custom prescriptions on the homepage. The clinic operations live on a separate domain (facethefutureclinic.co.uk). The LLM's prior conflates the clinic and the store into one entity; the store site does nothing to reinforce the clinical authority the model already attributes to the brand.

Schema and Content Posture

The homepage carries Organization and WebSite JSON-LD with correct address, VAT ID, phone, and social profiles — but no Product schema, no FAQPage, no MedicalBusiness or HealthAndBeautyBusiness typing. The heading structure is flat (no H1 on the main hero section until "Build A Routine" far down the page). Despite 1,500+ words of visible text, the page is a dense product grid with no structured answer-format signals (FAQ, comparison tables, how-to guides) that AI answer engines prize.

External Signals

The brand's strongest external signal is the reviews.co.uk profile with 23,218 reviews and a 4.76 average — a massive trust signal that no AI crawler can reach from the .store domain and that the .co.uk site links to but does not embed or schema-markup on its own pages. The clinic domain has its own separate review system. No press coverage, Reddit threads, or major media mentions surfaced in search — the brand's off-domain footprint is almost entirely customer reviews.

Findings

1. facethefuture.store returns 403 to all AI crawlers with no redirect High

   The .store domain resolves to the same Shopify infrastructure but returns a Cloudflare JS challenge wall to every visitor, including GPTBot, ClaudeBot, and PerplexityBot, with no content or redirect to the real site.

   What to change: Redirect facethefuture.store to www.facethefuture.co.uk via a 301 redirect and remove the Cloudflare JS challenge for known AI crawler user agents.

2. All sub-pages on .co.uk are blocked by Cloudflare JS challenge High

   Every sub-page — product pages, blog, about-us, collections, UCP endpoint, agents.md — returns a 403 with a Cloudflare JS challenge for both browsers and AI crawlers. Only the homepage is publicly crawlable.

   What to change: Configure Cloudflare WAF to allow known AI crawler user agents (GPTBot, ClaudeBot, Google-Extended, PerplexityBot) to access sub-pages without JS challenge.

3. Robots.txt lacks AI-specific directives Medium

   The robots.txt file has no rules for GPTBot, ClaudeBot, Google-Extended, or other AI crawlers, leaving them subject to default allow rules that are overridden by Cloudflare WAF.

   What to change: Add explicit allow directives for AI crawlers in robots.txt, e.g., 'User-agent: GPTBot Allow: /'.

4. llms.txt exists but UCP endpoint is blocked High

   The site serves a well-crafted llms.txt describing UCP endpoints and agent workflows, but the UCP endpoint itself (.well-known/ucp) returns 403, making the llms.txt effectively useless.

   What to change: Ensure the UCP endpoint is publicly accessible and not blocked by Cloudflare WAF.

5. Homepage lacks Product and FAQ schema Medium

   The homepage carries Organization and WebSite JSON-LD but no Product, FAQPage, or MedicalBusiness schema, missing opportunities to appear in rich AI answers.

   What to change: Add Product schema to product listings and FAQPage schema for common skincare questions.

6. Homepage has flat heading structure with no H1 until far down Low

   The homepage lacks a clear H1 in the hero section; the first H1 appears late in the page ('Build A Routine'), reducing semantic clarity for crawlers.

   What to change: Add a descriptive H1 in the hero section, e.g., 'Premium Cosmeceutical Skincare & Custom Prescriptions'.

7. Homepage does not reinforce clinical authority known to LLMs Medium

   The LLM knows Face the Future as a CQC-registered clinic, but the store homepage presents only as a cosmeceutical retailer with no mention of CQC registration, virtual consultations, or custom prescriptions.

   What to change: Add a section highlighting clinical credentials, CQC registration, and virtual consultation services to bridge the gap between LLM knowledge and site content.

8. 23,000+ reviews not embedded or schema-marked on site Medium

   The site links to a reviews.co.uk profile with 23,218 reviews and a 4.76 rating, but does not embed review snippets or use AggregateRating schema on its own pages.

   What to change: Embed review widgets or add AggregateRating schema to the homepage and product pages using the reviews.co.uk data.

9. Homepage lacks FAQ, comparison tables, or how-to guides Medium

   Despite 1,500+ words, the homepage is a dense product grid with no structured answer-format content (FAQ, comparison tables, how-to guides) that AI answer engines prioritize.

   What to change: Add an FAQ section or comparison tables for popular product categories to improve chances of appearing in AI answer boxes.

10. Limited off-domain footprint beyond reviews Low

    No press coverage, Reddit threads, or major media mentions surfaced in search; the brand's external presence is almost entirely customer reviews on a single platform.

    What to change: Build off-domain presence through guest posts, PR, or partnerships to increase brand mentions and backlinks.

What's working

• Homepage passes all AI crawlers with full content — The .co.uk homepage returns 200 with ~1.5MB HTML content to all 11 tested AI crawlers, including GPTBot, ClaudeBot, and Google-Extended.
• llms.txt is well-crafted with UCP endpoints and agent workflows — The site serves a 4336-byte llms.txt describing UCP endpoints and agent workflows, demonstrating proactive AI visibility efforts.
• Homepage includes Organization and WebSite JSON-LD with correct details — The homepage carries Organization and WebSite schema with accurate address, VAT ID, phone, and social profiles, providing basic structured data.
• 23,218 reviews with 4.76 average on reviews.co.uk — The brand has a massive external trust signal with 23,218 customer reviews and a 4.76/5.0 rating, which can be leveraged for AI visibility.
• Mature Shopify store with 5,000+ product URLs and 18 years of trading — The .co.uk site is a well-established Shopify store with extensive product catalog and long trading history, providing a strong foundation.
• Sitemap available with 80 URLs and index enabled — The site has a sitemap at /sitemap.xml with 80 URLs and index enabled, aiding crawler discovery.