pulsaruk.com — AI Site Grade

Analysis

Pulsaruk.com is entirely invisible to every AI crawler — the live site returns a Cloudflare JS challenge wall (403) to all user-agents including GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and even standard browsers, making its actual content unreachable by any automated system.

Crawler Access

Every AI crawler tested — GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Bytespider, Applebot-Extended — receives a 403 with a Cloudflare JS challenge page (cf-ray header present). The robots.txt and llms.txt endpoints also return the same challenge wall rather than actual directives. The site has no robots.txt rules for any AI bot because the file is never served. The sitemap.xml is equally blocked (403). The only accessible subdomain is store.pulsaruk.com (a distributor portal), which returns 200 with real product content but is a separate e-commerce system.

Cold-Knowledge Gap

A frontier LLM queried cold about "Pulsar UK" initially described the brand as a social listening and audience intelligence platform acquired by Cision in 2019 — a complete category error. The same model queried with "Pulsar UK high visibility workwear" correctly identified the brand as a hi-vis workwear manufacturer competing with Portwest and Regatta. This split means AI engines have no reliable prior for what pulsaruk.com actually sells. The site's Cloudflare wall prevents any live retrieval from correcting the record, so AI-generated answers about the brand will default to whichever Pulsar entity has more textual footprint on the open web.

Content & Schema Posture

The live site's content is only accessible via the Wayback Machine. The homepage describes PULSAR as a certified high-visibility apparel brand founded in 1979, with collections including PULSAR Protect, Evolution, Life, Blizzard, and FR/ARC. The site claims 300+ distribution partners, 4+ million garments sold, and a 2024 relocation to a 45,000 sq ft Worcester HQ. The homepage carries LocalBusiness and WebSite schema, but the LocalBusiness object uses the name "Aboutpulsar" (likely a typo) and references an old address in Moons Moat North, Redditch — contradicting the site's own text about the 2024 Worcester relocation. Deeper pages (collections, sustainability, blog, guide-to-hi-viz) carry no JSON-LD schema at all. The blog has 12+ posts from 2024-2025 covering sustainability, product launches, and industry awards, but none of this content is crawlable.

External Signals

Web searches for "pulsaruk.com", "Pulsar UK workwear reviews", and "PULSAR hi-vis UK" returned zero indexed results from DuckDuckGo. The brand has LinkedIn, Instagram, Vimeo, YouTube, Facebook, and Twitter presences (listed in the site footer), but these social profiles are not discoverable via standard web search queries. The store subdomain runs on the Aphix Software e-commerce platform and carries Organization schema with a correct phone number (01527 962012). No third-party reviews, Reddit threads, or press coverage appeared in search results — the brand has a near-zero external citation footprint that AI engines can reference.

Findings

1. Cloudflare JS challenge wall blocks all AI crawlers High

   Every AI crawler tested receives a 403 with a Cloudflare JS challenge page, preventing any automated access to the site's content. The robots.txt, llms.txt, and sitemap.xml endpoints are also blocked.

   What to change: Remove the JS challenge wall for known AI crawler user-agents (GPTBot, ClaudeBot, etc.) and serve a static HTML version of the site to those bots, or configure Cloudflare to bypass the challenge for verified crawlers.

2. No robots.txt rules for any AI bot High

   The robots.txt endpoint returns a 403 Cloudflare challenge, so no directives are served to any crawler. This means AI bots have no guidance on allowed paths.

   What to change: Serve a robots.txt file that allows AI crawlers to access the site, and ensure it is not blocked by Cloudflare.

3. Sitemap.xml blocked by Cloudflare High

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

   What to change: Serve a valid sitemap.xml that is accessible to all crawlers.

4. llms.txt endpoint blocked Medium

   The llms.txt endpoint returns a 403, preventing AI models from discovering the site's content via this standard.

   What to change: Create and serve an llms.txt file that lists key pages for AI consumption.

5. Cold-knowledge gap misidentifies brand as social listening platform High

   A frontier LLM queried cold about 'Pulsar UK' initially described the brand as a social listening and audience intelligence platform acquired by Cision, not a hi-vis workwear manufacturer. The site's Cloudflare wall prevents live retrieval from correcting this error.

   What to change: Allow AI crawlers to access the site so that live content can correct the brand's identity in AI knowledge bases.

6. LocalBusiness schema has typo and outdated address Medium

   The homepage's LocalBusiness schema uses the name 'Aboutpulsar' (likely a typo) and references an old address in Redditch, contradicting the site's own text about a 2024 relocation to Worcester.

   What to change: Correct the schema name to 'PULSAR UK' and update the address to the current Worcester headquarters.

7. Deeper pages lack JSON-LD schema Medium

   Pages such as collections, sustainability, blog, and guide-to-hi-viz carry no JSON-LD schema at all, missing opportunities for rich results and AI understanding.

   What to change: Add appropriate JSON-LD schema (e.g., Product, Article, FAQPage) to all content pages.

8. Zero external citation footprint in web search Medium

   Web searches for the brand name, reviews, and related terms returned zero indexed results from DuckDuckGo, indicating no third-party mentions, reviews, or press coverage that AI engines can reference.

   What to change: Build external citations through PR, reviews, and backlinks to improve brand visibility in AI knowledge sources.

9. Social profiles not discoverable via web search Low

   The brand's LinkedIn, Instagram, and other social profiles are listed in the site footer but are not discoverable through standard web search queries, limiting external signals.

   What to change: Ensure social profiles are linked from authoritative external sites and optimize them for search engine indexing.

10. Store subdomain is separate and not linked from main site Medium

    The store.pulsaruk.com subdomain is a separate e-commerce system with its own schema, but it is not accessible from the main site due to the Cloudflare wall, and it may not be indexed by AI crawlers either.

    What to change: Integrate the store subdomain with the main site or ensure it is also accessible to AI crawlers.

What's working

• Content preserved in Wayback Machine — The site's content is fully accessible via the Wayback Machine, providing a fallback for historical analysis and demonstrating that the site has substantial content.
• Homepage has LocalBusiness and WebSite schema — The homepage includes JSON-LD schema for LocalBusiness and WebSite, which helps search engines understand the business type.
• Store subdomain has Organization schema with correct phone — The store.pulsaruk.com subdomain carries Organization schema with a correct phone number, aiding local search.
• Blog with regular content updates — The blog has 12+ posts from 2024-2025 covering sustainability, product launches, and industry awards, providing fresh content for AI models if accessible.
• Guide to Hi-Viz page with educational content — The guide-to-hi-viz page contains 1054 words of educational content about hi-vis standards, which could be valuable for AI knowledge if crawled.
• Sustainability page with detailed content — The sustainability page has 1815 words of content, demonstrating commitment to environmental issues.
• Accreditations and policies page — The site has a dedicated page for accreditations and policies, which can build trust with AI models and users.