shoreprojects.com — AI Site Grade

Analysis

The live site is entirely invisible to every AI crawler and browser alike

Shore Projects is a UK-based watch brand (Shore Projects Limited, company 10080729) selling direct-to-consumer watches inspired by the seaside. The live site at shoreprojects.com returns HTTP 403 with a Cloudflare JS challenge wall to every single user-agent tested — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Applebot-Extended, Bytespider, and even a standard browser. No AI crawler, search engine bot, or human browser can reach a single byte of real content. The homepage, /robots.txt, /llms.txt, /sitemap.xml, /pages/about, and /collections/all-watches all return the same Cloudflare challenge page with zero visible product content.

Crawler Access

All 11 user-agents tested return 403 blocked with identical Cloudflare challenge HTML (~8.8 KB). The site runs on Cloudflare's "Managed Challenge" mode, which requires JavaScript execution and cookie acceptance before serving any content. This blocks every AI crawler unconditionally — none execute JS or pass Cloudflare challenges. The DNS resolves to 23.227.38.32 (Shopify's infrastructure), confirming the site is a Shopify store, but Shopify's own edge is wrapped in Cloudflare's challenge layer. No robots.txt file is reachable, so there are no AI-bot directives at all — the absence of rules is moot because the challenge wall blocks everything before any rule could apply.

Cold-Knowledge Gap

A frontier LLM queried cold about "Shore Projects" describes it as a UK-based creative agency specializing in brand strategy, design, and digital experiences — work with London Design Festival and Boiler Room. This is a completely different entity. The actual shoreprojects.com sells watches, not agency services. The watch brand has zero external footprint in search results: no reviews, no Reddit threads, no press mentions, no social media profiles surfaced by web search. The Wayback Machine shows the site has existed since at least 2013 and was actively selling watches as recently as January 2026, but the brand has no discoverable off-domain signal that would inform an AI engine's knowledge base.

Content & Schema

The Wayback snapshot reveals a standard Shopify storefront: watches priced in multiple currencies, interchangeable straps, 100m waterproofing, 316L marine-grade stainless steel, a Sommer Ray collaboration, and a donation model (10% of profits to Marine Conservation Society). The JSON-LD schema is non-standard — it uses a custom @type: "Shore Projects" instead of Product, Organization, or WebSite. No Product schema, no BreadcrumbList, no FAQPage schema despite having an FAQ page with rich Q&A content. The FAQ page contains extensive shipping, returns, and warranty information that would be highly valuable for AI answer extraction, but it carries no structured markup.

External Signals

The brand is a digital ghost. Web searches for "Shore Projects watch", "shoreprojects.com", and "Shore Projects review" return zero results across DuckDuckGo. No Reddit mentions, no press coverage, no influencer content surfaced. The only discoverable external presence is a Facebook page and Instagram account referenced in the site's navigation, but neither appears in search results. The company is registered in England (Solar House, 282 Chase Rd, London N14 6NZ) and uses Google Workspace for email, but none of this corporate information is discoverable through standard web search.

Findings

1. Cloudflare challenge wall blocks all AI crawlers and browsers High

   The live site returns HTTP 403 with a Cloudflare JS challenge page to every user-agent tested, including GPTBot, ClaudeBot, and standard browsers. No AI crawler can access any content.

   What to change: Remove the Cloudflare challenge wall or configure it to allow AI crawler user-agents through. Use Cloudflare's bot management to bypass the challenge for known AI bots.

2. robots.txt is unreachable due to Cloudflare challenge High

   The robots.txt file returns a 403 error, so no crawler directives are accessible. Even if directives existed, the challenge wall blocks access before they could be read.

   What to change: Ensure robots.txt is served without a challenge wall. Add explicit allow rules for AI crawlers.

3. Sitemap.xml is unreachable High

   The sitemap.xml returns a 403 error, preventing crawlers from discovering the site's URL structure.

   What to change: Serve sitemap.xml without a challenge wall and submit it to search engines.

4. llms.txt is not served Medium

   The llms.txt file returns a 403 error, so AI crawlers cannot discover a curated content guide.

   What to change: Create and serve an llms.txt file with links to key pages like product collections and about page.

5. Brand has zero external search footprint High

   Web searches for 'Shore Projects watch', 'shoreprojects.com', and related terms return zero results across DuckDuckGo. No reviews, press, or social media profiles are discoverable.

   What to change: Build external signals through PR, influencer partnerships, and social media engagement. Ensure social profiles are indexed and linked from the site.

6. LLM cold knowledge misidentifies the brand as a creative agency High

   A frontier LLM queried about 'Shore Projects' describes it as a UK-based creative agency, not a watch brand. The actual watch brand has no presence in AI training data.

   What to change: Increase the brand's online footprint with structured data, press releases, and content that AI crawlers can index.

7. JSON-LD uses custom @type instead of standard schema High

   The site's JSON-LD uses a custom @type 'Shore Projects' instead of standard types like Product, Organization, or WebSite. This prevents AI engines from understanding the entity.

   What to change: Replace custom @type with standard schema.org types: Product for watches, Organization for the brand, and WebSite for the site.

8. No Product schema on product pages Medium

   The site lacks Product schema markup on product pages, which would help AI engines extract pricing, availability, and descriptions.

   What to change: Add Product schema with properties like name, price, currency, availability, and description to all product pages.

9. FAQ page lacks FAQPage schema Medium

   The FAQ page contains extensive Q&A content but has no FAQPage structured data, missing an opportunity for AI answer extraction.

   What to change: Add FAQPage schema with Question and Answer properties to the FAQ page.

10. Missing BreadcrumbList schema Low

    The site does not use BreadcrumbList schema, which helps AI engines understand site structure and navigation.

    What to change: Add BreadcrumbList schema to all pages to indicate navigation hierarchy.

11. Social media profiles not discoverable via search Medium

    The site references Facebook and Instagram accounts, but these profiles do not appear in web search results, limiting external signals.

    What to change: Ensure social media profiles are public and linked from the site with proper Open Graph tags. Encourage indexing by search engines.

What's working

• Wayback Machine snapshot reveals rich product content — Archived snapshots show a fully functional Shopify store with detailed product descriptions, pricing, and brand story, indicating the site has valuable content that could be indexed if accessible.
• FAQ page contains extensive Q&A content — The FAQ page has over 10,000 words of shipping, returns, and warranty information that would be valuable for AI answer extraction if properly marked up.
• Site runs on Shopify with reliable infrastructure — The site is hosted on Shopify's platform (DNS resolves to Shopify IP), which provides robust e-commerce capabilities and SEO-friendly defaults if properly configured.