red-badger.com — AI Site Grade

Analysis

Red Badger: A Content-Rich Site with a Critical Schema Gap and a Curious Future-Dated News Item

The most striking finding is that Red Badger's site publishes news articles and events dated in 2026 (e.g., "Red Badger Joins NVIDIA Partner Network" dated 30 April 2026), which is either a content-management error or a deliberate staging artifact — and AI crawlers ingesting this will surface a credibility problem for any model that checks the current year.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive a full 200 response with identical byte payload (173,104 bytes) as a browser baseline. No UA-based blocking exists. The site runs on Cloudflare with HubSpot CMS (evidenced by hsLang query params, hubspotemail.net SPF, and HubSpot-specific response headers). The robots.txt uses a single User-agent: * rule blocking only HubSpot preview/admin paths (/_hcms/preview/, /hs/manage-preferences/, etc.) and sample URLs. No AI bot is explicitly named. No llms.txt exists (returns a 404 HTML page of 102KB — a bloated error page that itself wastes crawler budget).

Cold-Knowledge Gap

The LLM prior knows Red Badger as a London-based consultancy founded in 2010 by Cain Ullah and Ben Jones, famous for GOV.UK Verify and the Lloyds Bank mobile app. The actual site does not mention GOV.UK Verify or Lloyds anywhere on the homepage, about page, or case studies. The site instead leads with London Business School (MyLBS), Nando's (ordering platform and loyalty), Santander PagoFX, British Council, OVO Energy, and Security Bank. The cold knowledge is stale by roughly 2-3 years — it references a reputation snapshot from early 2023 and misses the entire Rust/Crux open-source framework story, the NVIDIA partnership, the Cape Town hub, and the Rockborne data/AI partnership.

Schema Posture

Every page examined carries only a bare-minimum Organization schema with a single url property — no name, description, logo, sameAs, foundingDate, founder, knowsAbout, or makesOffer. Case study pages (e.g., Nando's ordering platform) have no Article or CaseStudy schema. The resources/articles page has VideoObject schemas but no BlogPosting or Article markup. This is a systemic structured-data deficiency across the entire domain.

Content Architecture Fragmentation

The site is split across two HubSpot portals: red-badger.com (the main marketing site, ~54 URLs in sitemap) and content.red-badger.com (the blog, case studies, news, and resource hub). The main sitemap only lists pages on the primary domain — the entire content subdomain (dozens of articles, 26+ case studies, news items) is absent from the sitemap. This means AI crawlers relying on sitemap discovery will miss the majority of the site's substantive content. The content.red-badger.com subdomain has its own HubSpot instance with no cross-sitemap linking.

Future-Dated Content Anomaly

The events page lists six upcoming events from June-July 2026 and a news article headlined "Red Badger Joins NVIDIA Partner Network to Scale Agentic AI for..." dated 30 April 2026. If these are genuine future events, the site is publishing them far in advance. If they are placeholder dates or a CMS error, they will confuse any AI model that performs temporal reasoning. No external press coverage of an NVIDIA partnership was found via search.

Findings

1. News article dated April 2026 raises credibility concerns High

   A news article titled 'Red Badger Joins NVIDIA Partner Network to Scale Agentic AI for...' is dated 30 April 2026. No external press coverage of an NVIDIA partnership was found. AI models performing temporal reasoning may flag this as an error or hallucination, damaging trust.

   What to change: Correct the date of the NVIDIA partnership article to the actual publication date, or remove it if it is a placeholder. Ensure all dates on the site reflect real calendar dates.

2. No Article or CaseStudy schema on any page High

   Every page examined carries only a bare-minimum Organization schema with a single url property. Case study pages (e.g., Nando's ordering platform) have no Article or CaseStudy markup. The resources/articles page has VideoObject schemas but no BlogPosting or Article markup. This systemic structured-data deficiency prevents AI crawlers from understanding content type and relevance.

   What to change: Add Article schema to all blog posts and news articles, and CaseStudy schema to all case study pages. Include properties such as headline, datePublished, author, and description.

3. Content subdomain absent from sitemap High

   The main sitemap at red-badger.com only lists pages on the primary domain. The entire content subdomain (content.red-badger.com), which hosts dozens of articles, case studies, and news items, is not included. AI crawlers relying on sitemap discovery will miss the majority of the site's substantive content.

   What to change: Include all URLs from content.red-badger.com in the main sitemap, or create a separate sitemap for the subdomain and reference it in robots.txt.

4. Cold knowledge about Red Badger is 2-3 years out of date Medium

   The LLM prior knows Red Badger for GOV.UK Verify and Lloyds Bank mobile app, but the site does not mention these anywhere. The site instead leads with London Business School, Nando's, Santander PagoFX, and others. The cold knowledge misses the entire Rust/Crux open-source framework story, the NVIDIA partnership, the Cape Town hub, and the Rockborne data/AI partnership.

   What to change: Update the site's homepage and about page to prominently feature current flagship projects (e.g., CRUX, NVIDIA partnership, Cape Town hub) to align with the brand's actual recent work.

5. No llms.txt file exists Medium

   The llms.txt file returns a 404 HTML page of 102KB, wasting crawler budget. An llms.txt file would help AI crawlers efficiently discover key content.

   What to change: Create an llms.txt file listing the most important pages (e.g., about, services, case studies, blog) to guide AI crawlers.

6. Organization schema lacks key properties Medium

   Every page carries only a bare-minimum Organization schema with a single url property. Missing properties include name, description, logo, sameAs, foundingDate, founder, knowsAbout, and makesOffer. This limits how AI models can understand and cite the organization.

   What to change: Expand the Organization schema to include name, description, logo, sameAs (links to LinkedIn, Twitter, etc.), foundingDate, founder, and makesOffer.

7. Events page lists events through July 2026 Medium

   The events page lists six upcoming events from June-July 2026. If these are genuine, they are published far in advance. If they are placeholder dates, they will confuse AI models performing temporal reasoning.

   What to change: Review all event dates for accuracy. Remove or correct any placeholder dates to avoid misleading AI crawlers.

8. Robots.txt does not explicitly allow or block AI bots Low

   The robots.txt uses a single User-agent: * rule blocking only HubSpot preview/admin paths. No AI bot is explicitly named. While this means AI bots are implicitly allowed, the lack of explicit rules may cause some crawlers to be cautious.

   What to change: Add explicit allow rules for major AI crawlers (GPTBot, ClaudeBot, etc.) to ensure they crawl without hesitation.

What's working

• All major AI crawlers receive full access — All tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended) receive a 200 response with identical content as a browser. No UA-based blocking exists.
• Site has substantial written content across two portals — The site contains hundreds of pages of substantive content, including case studies, blog posts, news articles, and event listings. The content subdomain alone has over 4500 words on its main page.
• Resources page includes VideoObject schema — The resources/articles page has VideoObject schemas, which helps AI crawlers understand video content on that page.
• Fast server response with Cloudflare CDN — The site uses Cloudflare CDN, providing fast response times and good uptime. Headers indicate Cloudflare is properly configured.