aspinallfoundation.org — AI Site Grade

Analysis

Expired SSL Certificate Blocks the Root Domain — All AI Bots Hit a Dead End on aspinallfoundation.org

The bare domain https://aspinallfoundation.org presents an expired SSL certificate that causes a connection failure for every HTTP client — browser, GPTBot, ClaudeBot, Google-Extended, PerplexityBot, and all others tested via compare_bot_access. All 11 bot UAs returned status 0 with an SSL error. The site only resolves successfully on https://www.aspinallfoundation.org (the www subdomain), which redirects cleanly from http://aspinallfoundation.org. AI crawlers that attempt the bare domain first — as many do — will receive a hard failure, not a redirect.

Crawler Access

On https://www.aspinallfoundation.org, every AI bot tested receives a 200 status with full HTML content (107,500 bytes, identical to browser baseline). No UA-based blocking, no Cloudflare challenge, no JS shell. The robots.txt contains a User-Agent: * rule disallowing only system directories (/umbraco/, /bin/, /config/, etc.) and a NinjaBot block — no AI-specific directives exist. No llms.txt file is present (404). The sitemap.xml is well-formed with 477 URLs covering conservation projects, animal pages, park info, and support pages.

Content & Schema Posture

The site contains zero JSON-LD structured data across all pages inspected — homepage, about page, FAQ, support, donations, media centre. No Organization, NGO, FAQPage, WebSite, or BreadcrumbList schema is present. The FAQ page (/frequently-asked-questions/) has 20+ question-answer pairs in plain HTML with zero FAQPage markup, making them invisible to AI answer engines. The homepage uses a single H1 ("Aspinall Foundation") and multiple H2/H3 headings with rich conservation narrative text (~1,335 words), but no structured answer-format signals beyond plain lists.

Cold-Knowledge Gap

The LLM cold-knowledge query returned a strong prior: the foundation is known for gorilla reintroduction, the two Kent parks (Howletts and Port Lympne), the "gorilla passport" program, founder John Aspinall's controversial background, and a 2023 gorilla death controversy. The actual site does not mention the 2023 incident at all, nor does it address John Aspinall's casino/gambling background or any controversy. The site positions itself purely around conservation achievements ("1,500 animals rescued or rewilded", "75+ gorillas rewilded", "world first cheetah cubs born in wild to captive-born parents") — a gap that means AI models drawing on training data may surface the controversy without the site providing its own framing.

External Signals

The "Our work in the news" page aggregates press coverage from The Guardian, Bloomberg, The Times, ITV News, Tatler, The Express, and The Ethicalist — high-authority outlets covering elephant rewilding to Kenya, gorilla reintroductions, and the Bua Noi shopping-mall gorilla campaign. DNS records show the site uses AWS Route53 nameservers, Microsoft 365 for mail, and HubSpot email marketing. The blog lives on a separate subdomain (blog.aspinallfoundation.org) running a different platform, creating a fragmented content footprint that AI crawlers must follow across domains.

Canonical & Redirect Fragmentation

Multiple pages have canonical URLs that differ from their own URL. The FAQ page lives at /frequently-asked-questions/ but declares canonical /faq/. The support page at /the-aspinall-foundation/support-us/ declares canonical /support/. The donations page at /donations/ declares canonical /donate/. These mismatches create ambiguity for AI crawlers about which URL to index and cite. The bare domain SSL failure compounds this — any AI model that learned aspinallfoundation.org (without www) from training data cannot verify it against the live site.

Findings

1. Expired SSL certificate on root domain blocks all AI crawlers High

   The bare domain https://aspinallfoundation.org has an expired SSL certificate, causing connection failures for all HTTP clients including all AI bots. The site only resolves on https://www.aspinallfoundation.org, but many AI crawlers attempt the bare domain first and receive a hard failure.

   What to change: Renew the SSL certificate for aspinallfoundation.org and ensure it redirects to https://www.aspinallfoundation.org.

2. Zero JSON-LD structured data across all pages High

   No JSON-LD structured data is present on any inspected page, including the homepage, about page, FAQ, support, donations, and media centre. Missing schema types include Organization, NGO, FAQPage, WebSite, and BreadcrumbList.

   What to change: Add JSON-LD structured data for Organization, WebSite, FAQPage, BreadcrumbList, and other relevant schema types to all pages.

3. FAQ page lacks FAQPage schema markup High

   The frequently-asked-questions page contains over 20 question-answer pairs in plain HTML but has no FAQPage structured data, making the content invisible to AI answer engines and voice assistants.

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

4. Canonical URL mismatches create indexing ambiguity Medium

   Multiple pages declare canonical URLs that differ from their own URL. The FAQ page at /frequently-asked-questions/ declares canonical /faq/, the support page at /the-aspinall-foundation/support-us/ declares canonical /support/, and the donations page at /donations/ declares canonical /donate/. These mismatches confuse AI crawlers about which URL to index and cite.

   What to change: Ensure each page's canonical URL matches its own URL, or set up proper redirects from the canonical target to the actual page.

5. No llms.txt file for AI crawler guidance Medium

   The site does not provide an llms.txt file (returns 404), missing an opportunity to guide AI crawlers to the most important pages and provide context about the organization.

   What to change: Create an llms.txt file listing key pages and a brief summary of the organization for AI crawlers.

6. Site omits known controversies, creating knowledge gap Medium

   LLM cold knowledge includes the 2023 gorilla death controversy and founder John Aspinall's casino background, but the site does not address these topics. AI models may surface negative information without the site providing its own framing.

   What to change: Consider adding a page or section that addresses controversies transparently to provide balanced context for AI models.

7. Blog hosted on separate subdomain fragments content footprint Low

   The blog lives on blog.aspinallfoundation.org, a separate subdomain running a different platform. This creates a fragmented content footprint that AI crawlers must follow across domains, potentially diluting authority.

   What to change: Consider moving the blog to a subdirectory of the main domain to consolidate content authority.

8. No AI-specific directives in robots.txt Low

   The robots.txt file contains no directives for AI bots like GPTBot, ClaudeBot, or Google-Extended. While this allows full access, it also means no guidance is provided for crawl rate or allowed paths.

   What to change: Add specific directives for AI bots to manage crawl rate and explicitly allow key content paths.

What's working

• All AI bots receive full HTML content on www subdomain — Every tested AI bot receives a 200 status with 107,500 bytes of HTML content on https://www.aspinallfoundation.org, identical to the browser baseline. No UA-based blocking, Cloudflare challenges, or JavaScript shells are present.
• Well-formed sitemap with 477 URLs — The sitemap.xml is well-formed and contains 477 URLs covering conservation projects, animal pages, park info, and support pages, providing a clear crawl path for search engines and AI crawlers.
• Rich narrative content on conservation achievements — The homepage and about pages contain detailed, well-written narrative text about conservation achievements, including specific numbers like '1,500 animals rescued or rewilded' and '75+ gorillas rewilded', which are valuable for AI knowledge extraction.
• Press coverage from high-authority outlets — The 'Our work in the news' page aggregates coverage from The Guardian, Bloomberg, The Times, ITV News, and other authoritative sources, providing strong external signals for AI models.
• Clear heading structure on homepage — The homepage uses a single H1 tag and multiple H2/H3 headings, providing a clear content hierarchy that helps AI crawlers understand page structure.
• Robots.txt allows full crawling of content — The robots.txt file only disallows system directories and NinjaBot, allowing all other bots including AI crawlers to access the entire content area.